Licences, tickets and inductions expire on their own dates, not on yours. The agent tracks absence, currency and the clock, and never examines a document — the named employer representative does that, and attests.
Tracks the currency of people, not the standing of firms
In
01
A worker mobilises, and the agent opens a file against the role, the site and the jurisdiction over it.
02
A role is scoped, and the agent separates what statute requires of it from what the client requires by contract.
Reason
03
A US hire starts, and the agent runs the three-business-day Section 2 clock and reports the fields left blank.
04
A UK engagement starts on or after 1 October 2026, and the agent tests whether a check exists before day one.
05
A ticket falls due, and the agent counts the renewal window down against the work already rostered for that person.
Decide
06
An Australian high risk task is rostered, and the agent checks the licence class held against the class it needs.
07
A file is called for, and the agent produces what is held and names what is not, with where each item came from.
Out
08
An engagement ends, and the retention clock runs on its own arithmetic in each jurisdiction, per person.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent reports absence, currency and dates — never a view on a document, and never a list of people by nationality, visa type or country of issue, whoever is asking and whatever the reason given.
Example workflow
One worker, mobilisation to file
AgentHuman
1Worker nominatedDirect labour, labour hire, or a subcontractor at any tier
2Requirements assembledThe role, the site, the jurisdiction and what each of them requires of this person
3File comparedWhat is held, what is absent, what expires and confidence
4Controls appliedAbsence checks, expiry-window checks, identity-match checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is examined, judged or attested at any of them — the agent compares records, and the representative's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the employer representative.
Low confidence
Adds a site manager read first.
Representative review
The file is held with what is absent, what expires and the confidence.
Clear · Hold · Send to site manager
Cleared — released to work▼
6Register and site access updatedOnly where write access and approval policy allow it
7Outcome evaluatedAbsences found late, expiries missed, holds overturned and files produced complete
Holds lifted
Every hold lifted in review is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Judging whether a document is genuine or belongs to the worker.
Signing or completing the attestation on the form.
Inferring, scoring or predicting immigration or citizenship status.
Listing workers by nationality, visa type or country of issue.
Automation boundaryAgent acts unaided
✓Map what the role, the site and the jurisdiction.
✓Compare that against what the file already holds, item by item.
✓Count down expiry, renewal and re-verification dates from the record.
✓Report what is absent, and hold the file open.
Any write happens inside the boundaries agreed at implementation, never ahead of an attestation.
Refusing or granting a worker entry to the site.
Certifying payroll or any statement about what was paid.
Granting, renewing or endorsing a licence, card or ticket.
Changes to currency rules or approval thresholds.
Example output
One worker, annotated
Subcontractor management checks the firm you engaged; this checks the person it sent.
Currency record · single workerIllustrative example
Role
Requirement
On file
Currency
Confidence
Consequence
Mobile crane operator
High risk work licence of the class the rostered lift actually needs
Expired, in window
Renewable — retraining after
91%
The PCBU must see written evidence
As receivedTaken from the register and the licence records as they stand — nothing on this side is written by the agent.
What was readEmployer licence registerSite induction recordHigh risk task roster
Why this reads amberIt lapsed inside the twelve-month renewal window, so it is renewable rather than gone.
ActionClearHoldSend to site manager
What the score decidesBelow the configured threshold the file picks up a site manager read before.
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 worker on fileFrom the register
03Currency
Check the person, not the firm
Read each requirement against the jurisdiction and the role on this site, and where the guidance is still draft, report it as draft.
01Approved path
It never reads a document
Routine renewals arrive already counted down against the work ahead.
02Human review
Send review to the ones that stop work
Absences and near expiries are marked, so the representative starts where the work is about to be blocked.
04Build an evidence trail
The worker, the requirement it maps to and the officer who attested stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Workforce and HR recordsWorkday · SuccessFactors Employment Hero · BambooHR
Site access and inductionDamstra · Rapid Global Biosite · SALTO site access
Licence and card registersCSCS Smart Check · CITB State WHS licence registers
Agent
Workforce licensing and currency
Reads the register Assembles the file Holds for the officer
Verification and inspectionE-Verify · Home Office check Notice of Inspection pack
A site-level file-completeness figure can read well while a few trades and engagement types carry the missing items. No regulator publishes a construction breakout, so Nestack reports yours by slice.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Third-tier subcontract
9.1%
3.7×
Review
Labour hire and agency
6.9%
2.8×
Review
High risk licensed trades
4.0%
1.6×
Watch
Direct labour, one site
1.9%
0.8×
Normal
Bar: missing-item-rate lift vs. a direct-labour baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Every cycle leaves one more test behind
A cycle closes when the lapsed ticket is a regression case. That suite is what the next start worked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Missing-item rate rises in one trade.
02Diagnose
The ticket that expired between induction and the lift it was needed for is traced back to one step.
03Improve
The fix carries a number, and the sites that forced it travel with it.
04Verify
Nothing goes out until every touched worker case has passed again.
05Learn
It is kept permanently, and the currency rules are amended alongside it.
Learn → DetectThe return edge. The next detection runs 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, currency workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workforce currency discovery and boundary definition.
02Register and HR source assessment.
03Jurisdiction, role and site requirement mapping.
04Person register ingestion and matching.
05Requirement comparison and absence logic.
06Confidence scoring and file routing.
07Employer representative review workflow.
08Register and site-access integration.
09Absence and expiry cases.
10Guardrails and attestation controls.
11Worker-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 site, one tradeProductionProduction register systemsAdvancedMultiple sites / jurisdictions
Introduced at Pilot
Currency checks to your rules✓✓✓
Representative review gate✓✓✓
File-completeness baseline✓✓✓
Introduced at Production
Reporting by trade—✓✓
Review workflow in your systems—✓✓
Approved write-back—✓✓
Site-access integration—✓✓
Introduced at Advanced
Multi-jurisdiction rule sets——✓
Multi-stage site approvals——✓
High headcount——✓
Multi-site currency controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, workforce size, 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 worker register and engagement types→Person-level register ingestion and matchingWeek 1
02Representative roles and the sites they cover→Requirement mapping and the absence-detection baselineWeek 2
03Your jurisdiction, role and site requirement rules→Requirement-rule mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Register, HR and site-access assessment, then integration setupWeek 2
05Files you would not want inspected→Expiry cases and the evaluation suiteWeek 4
06What no attestation may borrow→Confidence scoring, file routing, guardrails and approval controlsWeek 3
07Named employer representatives to review files→Representative review 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
These widths track the weeks the work genuinely fills, so the fifth band is doubled on purpose.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Workforce currency discovery, rule mapping and the automation boundaryW2Register integration and the absence-detection baselineW3Requirement comparison, confidence logic and review controlsW4Evaluation suite, guardrails and failure-mode testingW5Site-access integration, pilot crews and targeted correctionsW6One mobilisation run under the employer representative, then Agent Care handover
Reading the bandA bar spans only the weeks its own work is named in. The week 5 overlap is worked time, not padding.
At the end of W6The final checks clear on live crews and monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Construction AI agent
Build a workforce currency agent around the attestation you already carry.
Three jurisdictions, three accountable acts: a perjury signature in the United States, no signature at all in the United Kingdom where the absent check is the liability, and an Australian duty to see the evidence first. Never a view on anybody status — acting on such a flag is itself the offence.
