HR AI agent · Joining and leaving
Employee Onboarding and Offboarding AI Agent
Assemble the joiner file, hold section 2 of the Form I-9 for the named representative who examines the documents and signs the attestation, and carry the leaver deadlines that run on money.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named attestor
- Somebody looks
- After launch
- Agent Care
What this agent does
Assembles the file, never signs it
In
- 01
A joiner starts, and the section 2 clock runs from hire — 8 CFR 274a.2(b)(1)(ii)(B).
- 02
A document is presented, and what arrived is recorded without a view on whether it is genuine.
Reason
- 03
A list is offered, and which document to show stays the choice of the person presenting it.
- 04
An extra document is asked for, and 8 U.S.C. 1324b(a)(6) is read before the ask goes out.
- 05
A remote look is proposed, and E-Verify standing is checked against 88 FR 47749 first.
Decide
- 06
A mismatch is contested, and revocation and pay holds are held back until the case closes.
- 07
A leaver is coded, and discharge or resignation goes back to a human before final pay.
Out
- 08
A file ages, and retention runs on 8 CFR 274a.2(b)(2)(i)(A), which the leaving date sets.
- 09
Execute provisioning and revocation only inside the approval boundaries agreed at implementation.
Product statement
Assembly, sequencing and retention belong to the agent. The examination and the signature belong to a named representative, and filling the form for a signer who did not look moves the exposure onto that signer rather than dividing it.
Example workflow
One joiner, offer to attestation
- 1Offer accepted and hire date setStart date, work location, legal entity and the state whose separation rules will apply
- 2Joiner file opened and clockedThe three-business-day section 2 deadline, counted from the hire date on the payroll record
- 3Documents received and loggedWhat the joiner chose to present, the day it arrived, and the copies retained against it
- 4Checks appliedDocument-request checks, list-neutrality checks, E-Verify standing and deadline proximity
No human action required
Stages 1 to 4 run unaided, and nothing is attested at any of them — 8 CFR 274a.2(a)(3) puts that signature under penalty of perjury, and the representative lane opens at the examination gate.
Goes to the named representative to examine.
Adds an immigration-counsel read first.
Representative review
The file is held with the documents presented, the deadline left, and the checks that ran.
Attest · Request correction · Send to counsel review
Attested — by the named representative
- 6Directory, payroll and records updatedOnly where write access and the records policy allow it
- 7Outcome measuredDeadline adherence, request neutrality, corrections and what review found
Corrections
Each representative correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Signing the section 2 attestation.
- Examining a document a joiner presents.
- Judging that a document appears genuine.
- Recording a leaver as discharged or resigned.
Automation boundary
Agent acts unaided
- ✓Count the three business days from the hire date.
- ✓Hold the joiner file unattested until a named representative looks.
- ✓Carry each separation deadline through to the payroll administrator.
- ✓Check E-Verify standing before any remote look.
Nothing is attested except by a named representative who looked, inside the boundaries.
- Deciding whether a mismatch may end employment.
- Refusing a document a joiner has offered.
- Judging wilfulness under Cal. Lab. Code section 203.
- Changes to the checklist, the entity or the clock.
Example output
One joiner record, annotated
This serves a people-operations team whose files may be read by an inspector years after the person joined; below is one joiner record exactly as the agent leaves it, unattested.
Joiner record · section 2 pending
Illustrative example- Stage
- New joiner, documents presented
- Recorded as
- Documents logged, not examined
- Deadline
- Section 2 open
- Evidence held
- List B and List C, 3 August 2026
- Confidence
- Held unattested
- Held for
- The named representative, by name
As received
Assembled from what the joiner chose to present, and it claims nothing about whether it is genuine.
What this record holds
- Documents presented
- Deadline left
- Copies retained
Why no attestation here
Attesting under penalty of perjury is something a named person does.
What the score decides
No 2026 adjustment exists; the range at 28 CFR 85.5 still runs from 3 July 2025.
Action
AttestRequest correctionSend to counsel reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every joiner file
From the offer that opened it
Where that evidence is used
No Form I-9 edition date is printed here: uscis.gov could not be read on the day of writing, and only the OMB approval at 1615-0047, expiring 31 May 2027, was confirmed.
Somebody has to look
8 CFR 274a.2(b)(1)(ix) dropped the same room and the physical handling, and kept a live video interaction with the individual presenting the documents. It stopped at the person.
Searched for, and not there
Of the three regimes usually invoked to make revocation sound urgent, 45 CFR 164.308(a)(3)(ii)(C) is addressable and carries no deadline, 15 U.S.C. 7262 says nothing about it, and PCI DSS is contractual. The hard leaver clocks are money.
Build an evidence trail
The step, the evidence it required and the representative who attested it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
HR and payroll systems
- HRIS
- payroll
- time records
- Hire dates and separation events
Verification records
- Form I-9 store
- E-Verify
- Attestation status and copies
Directory and access systems
- Identity provider
- device records
- Accounts opened and later revoked
Agent
Joining and leaving checklists
- Assembles the file
- Runs the deadline clocks
- Holds for the representative
Separation and final pay
- Termination notices
- benefit plans
- Discharge or resignation coding
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six catches between the file and the signature
Six catches upon one latch, the last the surest. What releases is drawn in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a file may go forward
- L3
- Leaves the attestation to a named representative
- L4 – L5
- Keep the step and the attestation behind it
- L6
- Halts the checklist at the attestation when signals degrade
How Nestack evaluates it
Evaluate the whole joiner run — not only the file that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the file an inspector would read
- E1Final-output evaluationDid the file record which documents were actually presented?
- E2Step-level evaluationDid the agent read the right hire date, the right entity and the live checklist?
- E3Tool evaluationDid it write to the correct joiner and the correct record?
- E4Confidence calibrationDo low-confidence files actually attract more representative corrections?
- E5Slice evaluationHow does performance change across specific joiner classes?
- E6Business outcomeHow many files needed a correction before the representative attested?
Floor — the checklist a file is run against
Failure modes
Where each failure originates in the agent
Seven failure modes, each shown where it first becomes visible in the run.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- UA-03
Superseded form template read
The stored template is not the one now published.
Stage gathers
The hire date, the documents and the copies
02 · Reasoning
2 modes
- UA-04
Extra documents requested
A safer setting asks for more than the law allows.
- UA-06
Genuineness assumed, not examined
A file reads as verified with nobody having looked.
Stage proposes
The document list, the deadline and the checks
03 · Tool / write
2 modes
- UA-02
Remote look without standing
The alternative runs where E-Verify standing lapsed.
- UA-05
Revocation on a contested mismatch
Access and pay stop while the case is still open.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- UA-01
Attested, examination unrecorded
The record shows a signature but not the looking.
Stage returns
The file a named signer reads before signing
05 · Change / Version
1 mode
- UA-07
Silent deadline drift
A rule moves and the stored clock keeps the old one.
Stage tracks
Model, prompt, checklist rules and form dates
- Sev-1 · a signature on an unseen document
- Sev-2 · a leaver deadline missed by a day
- Sev-3 · standing lapses, file held back
Affected slices
Remote-examination joiners absorb the corrections
No published error rate exists for commercial electronic I-9 systems, so a site figure can read clean while remote-examination joiners carry the corrections. Nestack reports by joiner class.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Remote-examination joiners | 12.0% | 3.7× | Review | |
| Multi-state separations | 8.5% | 2.6× | Review | |
| Contested-mismatch cases | 5.3% | 1.6× | Watch | |
| Standard in-person joiners | 2.4% | 0.7× | Normal |
Bar: correction-rate lift vs. in-person joiner baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What a late final payment costs
A loop closes when the form completed by nobody in particular is a standing case. That suite is what the next joiner run is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on remote-examination joiners.
- 02
Diagnose
The leaver whose accounts shut within the hour while final pay ran past Cal. Lab. Code 201 is worked backwards until one cause is left standing.
- 03
Improve
The checklist goes out numbered, and the evidence beneath it rides with it.
- 04
Verify
One attestation case still failing is enough to hold the start back.
- 05
Learn
It is kept for good, and the checklist rules are amended in the same commit.
Learn → Detect
The return edge. The next joiner run is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, systems, checklist build, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Attestation-boundary and joiner-checklist definition.Week 1
- 02Verification, payroll and directory data.Week 1, Week 2
- 03Step-to-attestation and deadline-coverage reporting.Week 1, Week 2
- 04Joiner document intake.Week 2
- 05Hire date, entity and clock binding.Week 2, Week 3
- 06Deadline scoring and review routing.Week 3
- 07Representative attestation workflow.Week 3, Week 4
- 08Directory and payroll integration.Week 5
- 09Attestation and deadline cases.Week 4, Week 5
- 10Guardrails and provisioning controls.Week 4
- 11Step-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne entity, one joiner cycle | ProductionProduction joining workflow | AdvancedMultiple entities / states |
|---|---|---|---|
| Introduced at Pilot | |||
| Checklist run to your steps | ✓ | ✓ | ✓ |
| Named representative attestation | ✓ | ✓ | ✓ |
| Joiner-and-leaver baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by step class | — | ✓ | ✓ |
| Representative review workflow in your systems | — | ✓ | ✓ |
| Approved provisioning write-back | — | ✓ | ✓ |
| Directory-and-payroll integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-state separation rules | — | — | ✓ |
| Cross-entity joiner packs | — | — | ✓ |
| Large joiner and leaver volumes | — | — | ✓ |
| Multi-state final-pay controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, joiner volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your live joining and leaving checklists
→Checklist capture and attestation-boundary definition
Week 102Representative HRIS, payroll and directory access
→System binding, step logic and the joiner baseline
Week 203Your legal entities and the representatives they name
→Checklist mapping, step binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→HRIS, payroll and directory assessment, then integration setup
Week 205Records you would not want inspected
→Attestation cases and the failure round
Week 406What no checklist may certify
→Deadline scoring, review routing, guardrails and release controls
Week 307A named representative who attests
→Release to the named representative, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Two of these phases genuinely share week five, and no band was stretched to make the column tidier.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Checklist discovery, attestation boundary and the automation boundary
W2System integration and the joiner-and-leaver baseline
W3Step logic, deadline clocks and release controls
W4Evaluation suite, attestation cases and the failure round
W5Directory and payroll integration, pilot joiners and targeted corrections
W6One joiner cycle run under the people-operations lead, then Agent Care handover
- Reading the band
- Each band spans only the weeks its own work is named for, and week five is shared by design.
- At the end of W6
- Once the attestation record validates, Agent Care takes the agent up.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · HR AI agent
Build a joining and leaving agent around the examination your last attestation assumed.
Show us one joiner file and the signature on its section 2. If the signer cannot say which documents were examined, the signature carries work the examination never did. An AI tool has already produced the citizenship-status version of that failure: DOJ, 25 February 2026.
- Typical delivery
- 4–6 weeks
- Deployment
- Your live checklists
- Named attestor
- Somebody looks
- After launch
- Agent Care available
Nestack Agents · Joining and leaving
AGT-HR-05 · Agent Care available after launch