Most of what goes wrong here has no cure — a missed payment schedule, an unlicensed engagement, an uninsured loss. The agent verifies and counts down; the administrator decides.
Query the issuing regulator's licence register and record status, class and expiry against the check timestamp.
02
Query the state labour-hire register for every provider named on the engagement, and record what came back.
Reason
03
Run the security-of-payment countdown in business days under the Act of the state that governs the claim.
04
Run insurance-expiry countdowns, and list which endorsements are on file and which arrived as a certificate only.
05
Assemble the prequalification pack and list every item that is missing, expired or self-declared.
Decide
06
Assemble engagement-status indicators as evidence, recording which test the jurisdiction applies and its current status.
07
Route the open countdowns, the failed checks and the missing endorsements to the named administrator.
Out
08
Retain every check, timer, escalation and acknowledgement against the engagement file.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent verifies and escalates; the contracts administrator issues the schedule and the commercial manager engages the sub — and a window that has closed, or an engagement already made, has no way back.
2Registers queriedLicence status, class and expiry, labour-hire licence, certificates and endorsements, each with its check time
3Pack assembledMissing and expired items, open countdowns, indicators and confidence
4Controls appliedRegister-freshness checks, business-day countdowns in the governing jurisdiction, endorsement checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nobody is cleared and no schedule is issued at any of them — the agent is verifying, and the administrator's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the administrator to decide.
Low confidence
Adds a risk-manager read first.
Administrator decision
The pack is held with its register results, its open timers and the confidence.
Accept pack · Reject · Send to risk review
Accepted — recorded against the engagement▼
6Prequalification systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedRegister-check freshness, escalation acknowledgements, missing-item outcomes and post-engagement findings
Rejections
Every rejection is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding whether a worker is an employee or a contractor.
Telling a worker they are a contractor.
Issuing, approving or varying a payment schedule.
Clearing a subcontractor or labour-hire provider.
Automation boundaryAgent acts unaided
✓Query licence and labour-hire registers and timestamp the result.
✓Run payment and insurance countdowns.
✓Assemble the pack and list what is missing or expired.
✓Compile safety metrics and incident history into a briefing pack.
Any write happens inside the boundaries agreed at implementation, never a statutory one.
Accepting or waiving an insurance requirement, or confirming cover.
Issuing or varying a scope letter or a subcontract.
Conducting or attesting a right-to-work or I-9 check.
Issuing a default notice or a termination.
Example output
One engagement check, annotated
Everything the agent reports is attached to the register it was read from.
Verification output · single engagementIllustrative example
Trade
What was checked
Expiry
Source register
Confidence
Status carried
Electrical sub
Contractor licence, class and scope checked against the issuing regulator's register
Expires in 9 days
Regulator register
91%
Verified — not cleared
As receivedTaken from the issuing register and the documents on file — nothing on this side is written by the agent.
What was readRegulator licence registerLabour-hire registerCertificate and endorsements
Why this statusThe register reads current for this class today — the administrator still decides.
ActionAccept packRejectSend to risk review
What the score decidesBelow the threshold the pack picks up a risk-manager read before the administrator.
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 engagementFrom the issuing register
03Verification
Verify against the source
Licence, labour-hire and insurance status are read from the issuing register or the endorsement itself, and every check is stamped with its time.
01Approved path
Check the register, not the PDF
Register checks, countdowns and prequalification packs are done before the administrator opens the file.
02Human review
Send review where cure runs out
Running countdowns and missing endorsements are marked, so the administrator's read starts where nothing can be fixed afterwards.
04Build an evidence trail
What was checked, when, and against which register stays on the engagement file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Prequalification and screeningAvetta ISNetworld (ISN)
Project and subcontract managementProcore Autodesk Construction Cloud · TradeTapp
Progress claims (AU)Payapps Progressclaim.com
Agent
Subcontractor management
Reads the registers Runs the countdowns Holds for the administrator
Workforce and registersAssignar · Damstra Licence · labour-hire registers
The unremediable-exposure rate counts engagements and payment cycles where an agent error produced an exposure with no cure available, which is most of what can go wrong on this page.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-tier subcontracting with labour hire
7.9%
3.3×
Review
US state-licensed residential trades
6.0%
2.5×
Review
Cross-border and migrant labour
3.6%
1.5×
Watch
Repeat subs, one jurisdiction
1.2%
0.5×
Normal
Bar: unremediable-exposure lift vs. an all-engagement baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop ends where the next test starts
A cycle is finished when the failure sits in the regression suite as a case the next release must pass.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Unremediable-exposure rate rises in an engagement slice.
02Diagnose
The administrator reads the register results first, then the timer log, until one of them accounts for it.
03Improve
The correction carries its version and the engagement records behind it.
04Verify
The affected cases are re-run before anything ships.
05Learn
It lands in the permanent suite and in the verification checklist.
Learn → DetectThe return edge. Every later cycle begins against a suite this one made 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, verification workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Engagement workflow discovery and boundary work.
02Register and claims source assessment.
03Jurisdiction, licence-class and endorsement mapping.
04Register ingestion and status normalisation.
05Verification and countdown logic.
06Confidence scoring and escalation routing.
07Administrator workflow.
08Prequalification and claims integration.
09Verification regression cases.
10Guardrails and engagement controls.
11Check-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 trade, one jurisdictionProductionProduction engagement systemsAdvancedMultiple entities / jurisdictions
Introduced at Pilot
Register checks and countdowns✓✓✓
Administrator decision✓✓✓
Verification baseline✓✓✓
Introduced at Production
Reporting by engagement type—✓✓
Review workflow in your systems—✓✓
Approved write-back—✓✓
Compliance dashboard integration—✓✓
Introduced at Advanced
Multi-jurisdiction rule sets——✓
Multi-stage commercial review——✓
High engagement volume——✓
Enterprise engagement controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, engagement 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 prequalification requirements and forms→Register mapping and verification-rule setupWeek 1
02Representative engagement files→Verification baseline, register queries and countdown logicWeek 2
03Your insurance schedule and endorsement standards→Insurance and endorsement mapping, and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Register, prequalification and claims assessment, then integration setupWeek 2
05Engagements you would not repeat→Verification cases and the evaluation suiteWeek 4
06The checks that must clear before an engagement proceeds→Confidence scoring, escalation routing, guardrails and approval controlsWeek 3
07Named administrators to receive the packs→Administrator decision 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
Phases occupy the weeks they are actually worked. Week 5 runs evaluation and pilot together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Engagement workflow discovery, jurisdiction mapping and the boundaryW2Register integration and the verification baselineW3Countdown logic, confidence scoring and escalation controlsW4Evaluation suite, guardrails and failure-mode testingW5Prequalification integration, pilot engagements and targeted correctionsW6One engagement and payment cycle under the administrator, then handover
Reading the bandA bar stops where its named work stops. The week 5 overlap is real, not padding.
At the end of W6Everything verified against live engagements, with Agent Care carrying it forward.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Construction AI agent
Build a subcontractor agent around the administrator who decides.
Show us your registers, your insurance schedule and who issues the payment schedule. Which of your engagements could you not undo if the check turned out to be wrong? We start there, then name what the agent never touches.
