Post the roster against the written estimate it departed from, mark the shifts that moved inside the notice window, and leave the publishing to the manager who answers for it.
A roster is posted, and no federal statute governs the notice — the FLSA is silent.
02
A roster runs in Chicago, and 6-110-040 has meant fourteen days since 1 July 2022.
Reason
03
A retail roster posts in New York City, and the window is seventy-two hours, not fourteen.
04
A schedule is estimated at hire, and Oregon and Seattle want median hours, not average.
05
A roster diverges from that estimate, and SMC 14.22.025 makes Seattle issue it again.
Decide
06
A shift ends and the next starts, and Philadelphia 9-4604(1) counts nine hours, not ten.
07
A shift is picked up by consent in New York City, and 6 RCNY 7-606 wants it shift-specific.
Out
08
A roster is retired, and Philadelphia 9-4609(1) holds two years where the rest hold three.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Notice arithmetic and the retention clock belong to the agent. Nothing in these ordinances is signed, certified or filed; the manager who publishes the roster is named by your policy, not by the rule.
Example workflow
One roster, estimate to publication
AgentHuman
1Scheduling inputs receivedDemand forecasts, availability records, time-off requests or the estimate on file
2Notice context assembledThe location, the ordinance over it, the estimate issued at hire, the day it was last reissued
3Draft roster raisedThe shifts, the notice each carries, the rest gaps and confidence
4Controls appliedNotice-window checks, rest-interval checks, divergence checks and drafting confidence
No human action required
Stages 1 to 4 run unaided, and nothing is posted at any of them — the agent is drafting, and the manager lane opens at the notice gate.
5DecisionSplits at the notice gate
Notice intact
Passes to the workforce manager to publish.
Anything late
Adds a premium review first.
Premium review
The roster is held with its notice arithmetic, its divergences and the estimate behind it.
Publish · Amend shift · Send for premium review
Published — by the workforce manager▼
6Scheduling and time records updatedOnly where write access and records policy allow it
7Outcome evaluatedNotice coverage, estimate divergence, manager amendments and what review found
Amendments
Each manager amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Publishing a roster to a workforce.
Issuing the written good faith estimate.
Deciding a premium is owed on a change.
Arranging a swap between two workers.
Automation boundaryAgent acts unaided
✓Hold each roster against the estimate issued at hire.
✓Count the notice each shift carries against the local ordinance window.
✓Flag a rest gap shorter than the local interval.
✓Draft the estimate and its fields for the manager who issues it.
Nothing is posted to a workforce and no estimate is issued unless a named person does it.
Judging whether an ordinance covers a site.
Telling a worker their notice was adequate.
Accepting a consent to a short rest interval.
Changes to the roster, the estimate or the record.
Example output
One roster change, annotated
Our surgical scheduling agent, production schedule copilot and dock appointment agent all schedule things; this one schedules people and the notice they are owed.
Scheduling output · single shiftIllustrative example
Shift
Recorded as
Notice
Evidence of record
Confidence
Held for
Added shift, Seattle location
Added to a roster already posted
Short notice
Estimate at hire, 3 August 2026
Held unposted
The workforce manager, by name
As receivedBuilt out of the posted roster and the estimate on file — nothing beyond those two is claimed.
What the record holdsPosted rosterEstimate at hireShift-specific consent
Why no signature appears hereNo ordinance in force asks anyone to sign a roster or an estimate.
ActionPublishAmend shiftSend for premium review
What the score decidesBelow the configured threshold a roster picks up a premium review before the manager sees it.
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 rosterFrom the location that posts it
03Evidence
Where the evidence is used
An estimate template that satisfies Chicago does not satisfy Oregon: the field lists diverge, so each estimate is bound to the fields its own jurisdiction asks for and tested against those.
01Approved path
Nobody signs a roster
Nothing is signed, certified or filed anywhere in these regimes; the artefact is the written good faith estimate, and its weight comes from being issued on time, with the right fields, in the right language, and kept.
02Human review
What was checked, and not found
No federal predictive-scheduling law was located. The US Department of Labor states that “The FLSA has no provisions regarding the scheduling of employees, with the exception of certain child labor provisions”, and the Schedules That Work Act has been reintroduced without being enacted. No duty in any of the ordinances runs to a software vendor or to an algorithm: no certification, no audit, no conformity assessment and no disclosure of scheduling logic were found. The Euless ordinance was repealed on 24 September 2024 and is not carried here.
04Build an evidence trail
The schedule, the estimate it departed from and the manager who published it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Workforce managementUKG · Legion · Deputy Rosters, availability and time-off records
Time and attendanceClock records · punch data Hours worked against the shifts posted
Human resourcesWorkday · SuccessFactors Hire dates, locations and job records
Agent
Roster notice evidence
Reads the estimate Counts the notice Holds for the manager
Demand and payrollForecast feeds · payroll exports Premiums raised and premiums paid
Integration availability depends on the client's existing systems and API access.
Agent controls
Six gates between the model and the workforce
Six gates on one corridor, the last the narrowest. What passes is set out in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeFall back to republishing the last approved roster when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and notice rules; the amended Chicago rules took effect on 1 June 2026 and add the date the estimate was provided.Track
L4TraceabilityRecord each roster, the estimate under it, the notice each shift carried and every read of the file.Record
L3Manager releaseHold the roster for the named workforce manager; no ordinance asks for a signature, so that hold is policy rather than law.Gate
L2Notice guardrailsTest each shift against the local window and rest interval, and reject a consent that is general or standing rather than tied to the shift.Restrict
L1Confidence thresholdsRoute a late change to a premium review; in Seattle and Los Angeles a consent removes the prohibition but not the premium.Require review
Model coreRoster drafted — the shifts, the notice each carries, the rest gaps and confidence
L1 – L2Test whether a roster may stand
L3Hands the publishing to a named person
L4 – L5Keep the schedule and the estimate behind it
L6Republishes the previous roster when signals degrade
How Nestack evaluates it
Evaluate the whole scheduling run — not only the roster that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the roster the workforce reads
Depth of coverage ▼
E1Final-output evaluationDid the roster carry the notice that location owed?
E2Step-level evaluationDid the agent read the right estimate, the right site and the live ordinance?
E3Tool evaluationDid it read and write the correct roster and the correct shift?
E4Confidence calibrationDo low-confidence rosters actually attract more manager amendments?
E5Slice evaluationHow does performance change across specific locations?
E6Business outcomeHow many rosters needed an amendment before publication?
Floor — the notice a worker was given
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed at the stage where it first shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
NH-03
Stale ordinance read
The rule read is not the one now in force.
Stage gathersThe sites, the rules, the shifts and the hours
02 · Reasoning2 modes
NH-04
Window counted from wrong day
A notice window is counted off the wrong date.
NH-06
Repealed ordinance read as live
A dead ordinance is worked as a current one.
Stage proposesThe shifts, their notice and the rest gaps
03 · Tool / write2 modes
NH-02
Thin roster passed forward
A roster moves on with no premium review.
NH-05
Shift bound to wrong worker
The shift is filed against another worker.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
NH-01
Posted, notice unrecorded
The record shows the roster but not the notice given.
Stage returnsThe roster a manager posts and a worker reads
05 · Change / Version1 mode
NH-07
Silent window drift
An ordinance lengthens its notice, and the stored rule keeps the older one.
Stage tracksModel, prompt, notice rules and site fields
Sev-1 · a roster posted without noticeSev-2 · wrong window reaches the rosterSev-3 · source degrades, roster held back
A location-level notice-window figure can read clean while newly covered locations carry most of the rework. Nestack reports the amendment rate by location, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Newly covered locations
12.3%
3.7×
Review
Multi-ordinance metropolitan sites
8.8%
2.6×
Review
Seasonal and holiday sites
5.5%
1.7×
Watch
Stable single-ordinance sites
2.6%
0.8×
Normal
Bar: amendment-rate lift vs. single-ordinance baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a late text message costs
The loop shuts when the late change without notice is a regression case. That suite is what the next roster posted is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises on newly covered locations.
02Diagnose
The shift added at nine on a Friday night to a roster posted a fortnight ago is walked back until one cause is left standing.
03Improve
Every change goes out numbered, with the rosters that caused it attached.
04Verify
Nothing releases while one touched roster case is still red.
05Learn
The case stays on, and the notice rules are rewritten alongside it.
Learn → DetectThe return edge. The next roster 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, sources, roster drafting, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Notice-boundary and ordinance-coverage mapping.
02Workforce, time and HR sources.
03Shift-to-ordinance and estimate-completeness mapping.
04Roster and availability ingestion.
05Shift, notice and estimate binding.
06Divergence scoring and review routing.
07Manager publication workflow.
08Workforce-system integration.
09Notice-window and premium cases.
10Guardrails and consent controls.
11Roster-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 location, one cycleProductionProduction scheduling workflowAdvancedMultiple locations / ordinances
Introduced at Pilot
Roster drafting to your ordinances✓✓✓
Workforce manager release✓✓✓
Scheduled-population baseline✓✓✓
Introduced at Production
Reporting by jurisdiction—✓✓
Manager review workflow in your systems—✓✓
Approved write-back—✓✓
Time-and-attendance integration—✓✓
Introduced at Advanced
Multi-ordinance rule sets——✓
Cross-site roster packs——✓
Large scheduled populations——✓
Multi-ordinance notice controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, roster 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 locations and the ordinance each one sits under→Ordinance mapping, estimate capture and reissue clocksWeek 1
02Representative rosters, estimates and change records→Notice binding, window logic and the roster baselineWeek 2
03Your standing scheduling policy and the manager it names→Ordinance mapping, notice binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Workforce, time and HR source assessment, then integration setupWeek 2
05Rosters you would not want produced→Notice cases and the evaluation runWeek 4
06What no roster may settle→Divergence scoring, review routing, guardrails and release controlsWeek 3
07A named workforce manager to publish the roster→Manager publication workflow, 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
Widths here follow the work, not the grid, which is why one band runs under another in week five.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Scheduling workflow discovery, ordinance mapping and the automation boundaryW2Source integration and the roster baselineW3Roster drafting, notice logic and release controlsW4Evaluation suite, notice cases and regression testingW5Workforce-system integration, pilot rosters and targeted correctionsW6One scheduling quarter run under the workforce manager, then Agent Care handover
Reading the bandEach bar runs only as far as the work it names, and the fifth carries two phases at once.
At the end of W6Once the notice record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Operations AI agent
Build a scheduling agent around the shift that moved after the roster went up.
Show us one posted roster and the estimate the people on it were given at hire. A posted shift is changed by the workforce manager who published it and by nobody else, so the agent counts what a change costs in notice and holds the amended roster for that manager.
