Run the eligibility and designation clocks from the day the employer knew, draft the notice with its fitness-for-duty flag on it, and hold that notice for the named administrator who signs and serves it.
A request lands, and five business days open on the eligibility notice — 29 CFR 825.300(b)(1).
02
A trigger date is set by a person, and the clock is counted from that day, not from the ticket.
Reason
03
A certification goes out, and fifteen calendar days are allowed under 29 CFR 825.305(b).
04
A form comes back thin, and seven calendar days to cure are put in writing — 825.305(c).
05
A designation is drafted, and the fitness-for-duty flag rides on it — 29 CFR 825.312(d).
Decide
06
Intermittent time is drawn down at the smallest increment in use — 29 CFR 825.205(a)(1).
07
A notice is served, and a delivery record is kept beside it rather than a sent flag.
Out
08
A designation runs late, and the harm question at 825.301(d) goes to a person, not a ledger.
09
Execute ledger and notice write actions only inside the boundaries agreed at implementation.
→Product statement
Clock-keeping, drafting and the delivery record belong to the agent. The determination and the signature belong to a named leave administrator, and a notice a system dated for a signer who never read it is still that signer's notice.
Example workflow
One leave request, signal to designation
AgentHuman
1Leave signal receivedThe request or the absence record, the day it was known, and the worksite it attaches to
2Eligibility notice clockedThe five-business-day deadline at 29 CFR 825.300(b)(1), counted from the trigger date a person sets
3Certification chased and loggedWhat the provider returned, the day it arrived, and the cure window still open under 825.305(c)
4Controls appliedClock checks, increment checks, fitness-for-duty flag checks and delivery-record checks
No human action required
Stages 1 to 4 run unaided, and nothing is designated at any of them — 29 CFR 825.300(d)(1) puts the designation on the employer in all circumstances, and the administrator lane opens at the designation gate.
5DecisionSplits at the designation gate
Certification sufficient
Goes to the named administrator to designate.
Anything unclear
Adds an employment-counsel read first.
Administrator review
The file is held with the certification, the days left on the clock, and the checks that ran.
Designate · Request cure · Send for a counsel read
Designated — by the named administrator▼
6Leave ledger and payroll records updatedOnly where write access and the retention policy allow it
7Outcome reviewedClock adherence, proof of delivery, corrections and what review found
Corrections
Each administrator correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing the designation notice.
Deciding a condition is a serious health condition.
Judging whether a late notice caused harm.
Determining undue hardship under 42 U.S.C. 12112(b)(5).
Automation boundaryAgent acts unaided
✓Count the five business days from the trigger date.
✓Carry the fitness-for-duty flag through onto the designation notice.
✓Reconcile intermittent increments against the smallest one recorded.
✓Hold the drafted notice until a named person signs it.
Nothing is designated except by a named administrator, inside the boundaries agreed.
Conducting the 29 CFR 1630.2(o) interactive process.
Contacting the treating health care provider.
Denying coverage on a certification never returned.
Changes to the ledger, the clock or the notice.
Example output
One leave file, annotated
This serves a leave team whose notices may be read back in a courtroom years after the absence closed; below is one leave file exactly as the agent leaves it, undesignated.
Leave file · designation pendingIllustrative example
Case
Recorded as
Clock
Evidence on file
Confidence
Held for
Continuing absence, certification returned
Certification logged, not judged
Designation open
WH-380-E returned, 3 August 2026
Held undesignated
The named administrator, by name
As receivedAssembled from what the provider returned, and it says nothing about whether the condition qualifies.
What the file holdsCertification returnedBusiness days leftDelivery record
Why no designation hereDesignating the leave is a determination a named administrator makes.
ActionDesignateRequest cureSend for a counsel read
What the score decidesThe Texas v. Bondi panel opinion of 15 August 2025 was vacated on 14 January 2026.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every leave fileFrom the day its clock started
03Evidence
Where the evidence goes
No leave-administration error rate is quoted here: the published enforcement series counts only actions where a violation was found, and prints no denominator to divide by.
01Approved path
The notice has its own clock
Wallace v. FedEx, Nos. 11-5500 / 11-5577, 6th Cir., 22 August 2014 — $173,000 — turned on an unsigned form and a warning given aloud. Whether the absence qualified was never contested.
02Human review
Checked, and it read the other way
The withdrawals expected here did not happen. The EEOC guidance of 9 May 2016 on employer-provided leave is still published, no FMLA opinion letter has been withdrawn since January 2025, three were added instead, and Part 825 is unamended since 2013.
04Build an evidence trail
The request, the day it was known and the administrator who designated it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Absence and time recordsHRIS · time and attendance logs Absence dates and hours worked
Leave case recordsLeave system · case store Certifications and notice dates
Carriers and administratorsThird-party administrators · carriers Claim status and paid benefits
Agent
Leave administration and notices
Runs the clocks Drafts the notices Holds for the administrator
State paid-leave programmesState programme portals · rulings Benefit decisions and their dates
No published error rate exists for leave administration, so a programme figure can read clean while intermittent chronic-condition leave carries the corrections. Nestack reports by leave class.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Intermittent chronic-condition leave
8.9%
3.7×
Review
Multi-programme state leave
6.3%
2.6×
Review
Retroactive designation cases
3.9%
1.6×
Watch
Single continuous parental leave
1.8%
0.7×
Normal
Bar: correction-rate lift vs. continuous-leave baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a late designation costs
A loop closes when the leave designated after the fact is a standing case. That suite is what the next designation run is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on intermittent chronic-condition leave.
02Diagnose
The employee told at exhaustion that weeks had been counted back behind them is worked backwards until one cause is left standing.
03Improve
Designations ship numbered, and the notices behind them travel attached.
04Verify
A single missed notice case stops the whole designation issuing.
05Learn
One case joins the suite, and one line joins the designation rules.
Learn → DetectThe return edge. The next designation run answers to a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope set beside the delivery timeline. Week structure follows the six-week plan — discovery, systems, clock build, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Designation-boundary and certification-clock rules.
02Absence, certification and payroll data.
03Deadline-adherence and certification-chase reporting.
04Leave signal intake.
05Trigger date and clock binding.
06Clock scoring and review routing.
07Administrator designation workflow.
08Leave-and-payroll integration.
09Designation and notice cases.
10Guardrails and certification controls.
11Notice-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 tierPilotOne entity, one leave cycleProductionProduction leave workflowAdvancedMultiple entities / programmes
Introduced at Pilot
Clock rules run to your policies✓✓✓
Named administrator designation✓✓✓
Entitlement-balance baseline✓✓✓
Introduced at Production
Reporting by leave class—✓✓
Administrator review workflow in your systems—✓✓
Approved ledger write-back—✓✓
Absence-and-payroll integration—✓✓
Introduced at Advanced
Multi-programme concurrency rules——✓
Cross-entity designation packs——✓
Large intermittent-leave volumes——✓
Multi-programme concurrency controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, leave volume, approval controls and deployment requirements.
Separate from buildBuild 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 bringWe build with it
01Your live leave policies and the programmes they run against→Policy capture and designation-boundary definitionWeek 1
02Representative absence, certification and payroll access→System binding, clock logic and the entitlement baselineWeek 2
03Your worksites and the administrators they name→Clock mapping, trigger binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Absence, certification and payroll assessment, then integration setupWeek 2
05Notices you would not want dated→Designation cases and the failure roundWeek 4
06What no notice may decide→Clock scoring, review routing, guardrails and release controlsWeek 3
07A named administrator who designates→Release to the named administrator, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
A band is exactly as wide as its phase costs, so the fifth week carries two where one would look tidier.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Policy discovery, designation boundary and the automation boundaryW2System integration and the entitlement-balance baselineW3Clock logic, notice drafting and release controlsW4Evaluation suite, designation cases and the failure roundW5Absence and payroll integration, pilot notices and targeted correctionsW6One leave cycle run under the leave administrator, then Agent Care handover
Reading the bandEach band runs across only the weeks its own work is named for, and week five is shared by design.
At the end of W6Once the notice record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · HR AI agent
Build a leave agent around the clock your last designation notice never proved.
Show us one designation notice and the day its clock started. Then read 29 CFR 1636.3, which still prints a requirement a federal court vacated on 21 May 2025 and ordered removed, with no note on eCFR. Reading the published regulation is not enough to know the law.
