10 July 2026 · 5 min read
White Card compliance tracking: what GCs actually need to get right
Every individual stepping onto a construction site in Australia needs their own White Card — this part every GC already knows. Where it gets complicated is tracking it accurately once you’re running several projects with overlapping crews, because a White Card is tied to the person, not the company they work for.
The company-vs-individual mistake
A subcontracting company might have five employees, and only three of them are ever actually on your site. If your compliance tracking treats "this company is White Card compliant" as a single yes/no answer instead of tracking it per individual, you can end up with a perfectly valid card on file for someone who isn’t even the person who showed up to work today. This is the single most common gap we see: reusing a verified document across people instead of across projects.
The fix is straightforward once you see the problem: track White Card status per individual worker, and make sure that record travels with that specific person across whichever of your projects they’re assigned to — but never gets silently satisfied by someone else’s card just because they work for the same company.
What actually causes a gap on-site
The most common real-world failure isn’t a missing card, it’s a mismatched one — a worker is inducted and tracked under one name, then a different person from the same crew shows up to actually do the work. The second most common is simply expiry: a White Card doesn’t expire in most states, but induction and site-specific requirements often have their own renewal cadence that isn’t the same as the card itself.
What good tracking looks like
A compliance system that tracks this correctly should require its own verification per person, per assignment — not reuse a previous person’s record just because the company name matches. That’s a deliberate design choice in how Novato models tradie compliance: some documents (like Public Liability Insurance) genuinely are company-level and can be reused across a subcontractor’s different jobs, but White Card is explicitly excluded from that reuse, because it’s the one document type where reusing someone else’s record is a real safety gap, not just a shortcut.