title: "Subcontractor-compliance tracker for a tier-2 AU builder" dek: "A 2025 deployment that read 1,400 subcontractor docs (PI insurance, white card, SWMS, LOA) and flagged 84 sub-contractors with lapsed compliance. Site shutdowns avoided in two near-misses." sector: "Trades & Construction" client: "Tier-2 AU commercial builder · A$420M annual turnover · 14 active sites" engagement: "Audit → Pilot" duration: "12 weeks" year: "2025" outcome: "Compliance review: weekly 14 hrs → continuous · 84 lapsed subcontractors flagged · 2 site shutdowns avoided" solution: "Document-intelligence pipeline for PI/PL insurance, white cards, SWMS and LOA — with expiry tracking and site-manager alerting." timeSaved: "~14 hrs/week of HSE-officer time · A$0.42 per document classified" visual: "none" cardFigure: "compliance" timeMetric: "12 hrs" timeMetricLabel: "saved / week" costMetric: "A$0.42" costMetricLabel: "cost per document" speedMetric: "7×" speedMetricLabel: "less HSE-officer time" publishedAt: "2025-03-18" keywords:
- construction compliance AI
- subcontractor management
- WHS automation Australia
- SWMS compliance tracking
The problem
A tier-2 AU commercial builder — A$420M annual turnover, around 350 staff, 14 active sites, 600+ active subcontractors at any given time — was managing subcontractor compliance the way the industry largely manages it: a HSE officer cross-referencing a spreadsheet against a SharePoint folder of PDFs once a week.
The documents in scope: Professional Indemnity insurance certificates, Public Liability certificates, White Cards for every operative entering site, Safe Work Method Statements (SWMS) per task, Letters of Authority for tasks requiring them, plus the trade-specific tickets (electrical licence, working-at-heights, confined-space). Around 1,400 active documents across the portfolio at any time, each with its own expiry date.
The miss the builder feared was a subcontractor turning up to site with lapsed insurance, an injury occurring, and the firm discovering the lapse during the WorkSafe investigation. That sequence isn't hypothetical — it happens across the industry every year and it shuts sites down for weeks while WorkSafe completes a review.
What we did
Three weeks of scoping with the HSE team, seven weeks of build, two weeks of staged pilot. The deployed system:
- Read every subcontractor document type (insurance certificates, White Cards, SWMS, LOA, trade tickets) using a document-intelligence pipeline
- Extracted holder name, insurer, policy number, coverage amount, scope of cover, issue date and expiry date
- Cross-referenced against the firm's subcontractor register
- Maintained continuous expiry monitoring — every document, every day
- Pushed alerts to the relevant site manager 30 days, 7 days and on-day for expiring documents
- Pushed blocking alerts when a document was missing or already lapsed and that subcontractor was rostered on site
The HSE officer no longer chases compliance. They review the alerts the system surfaces and follow up on the exceptions.
The outcome — at 5 months in production
| Before (FY24) | After (5 months in production) | |
|---|---|---|
| HSE-officer time per week on compliance review | ~14 hrs | ~2 hrs (alert triage) |
| Subcontractor documents tracked continuously | n/a | ~1,400 |
| Lapsed-compliance subcontractors flagged | 0 (unknown) | 84 across 5 months |
| Pre-shift lapses caught before site entry | n/a | 19 (subcontractor turned away or chased for replacement docs before commencing work) |
| Near-miss site shutdowns prevented | n/a | 2 (subcontractor with lapsed PI was 24 hours from a WorkSafe interaction; replacement docs lodged in time) |
| Cost per document classified (model + infra) | n/a | A$0.42 |
| WorkSafe inspections in period | 4 | 4 (all clean — improved from the previous year's 2 minor findings) |
The two near-miss site shutdowns are the outcome the GM most often cites. A WorkSafe-driven site shutdown on a A$30M project costs the firm an estimated A$240K per week in standing costs alone, before any penalties.
Compliance had been a thing we caught up on. Now it's a thing that runs in the background. The HSE officer's time has gone back into the bits of his job that actually keep our crews safe.
— General Manager, tier-2 AU commercial builder
What we'd do differently
Per-trade alert routing. Initially all alerts went to the site manager. In month two we routed trade-ticket alerts directly to the subcontractor's nominated foreman with cc to the site manager — faster resolution, less site-manager fatigue.
Subcontractor portal earlier. Subcontractors initially uploaded renewed documents via email to the HSE officer. We built a portal in month three. It should have been week one — uploading is the activity the subcontractor does most often, and email was the wrong UI for it.
What we didn't do
We didn't ban any subcontractor. We didn't automate any site-entry decision — the site manager remained the authority on who came on site. We didn't process any document outside the firm's existing SharePoint and subcontractor-management systems.
The interesting work was not the document AI. It was the alert-routing design and the audit log. Both were reviewed by the firm's WHS counsel and signed off before pilot — exactly the kind of governance scaffolding most construction-tech vendors skip.