Managing subcontractor compliance across multiple sites

A subcontractor working across several sites for the same principal contracting business often ends up being assessed for competence and re-verified separately at each site, purely because each site manager is working from their own local records rather than a shared view of who's already been checked.

A worked scenario

Take a scaffolding subcontractor working across three live projects for the same principal contracting business. Their SSIP accreditation lapses in month four — they didn't renew in time, for whatever reason. At Site A, the site manager checks accreditation status monthly and catches it immediately, holding further work until it's sorted. At Site B, the site manager checked it at appointment six months ago and hasn't looked again since, so the same subcontractor keeps working there, unaccredited, for weeks. At Site C, nobody's even sure whether it was checked at appointment or not, because that site manager inherited the project partway through and the original records weren't handed over cleanly. Same subcontractor, same lapse, three completely different outcomes — purely because of where the record lived.

This isn't just inefficient — it's a genuine risk in both directions. A subcontractor whose accreditation lapsed at one site can keep working unnoticed at another if the two sites aren't sharing that information, and equally, a subcontractor who's genuinely well-vetted ends up re-proving the same thing repeatedly, which creates friction without adding real safety value.

Why this gets worse, not better, as an organisation scales

It's tempting to assume this is a problem that mostly affects very large, sprawling organisations, but it tends to bite hardest in the mid-size range — a business running four or five concurrent sites, big enough that site managers genuinely don't all know each other's subcontractors, but not yet large enough to have invested in a shared system for tracking them. A two-site operation can often get away with an informal phone call between site managers. A twelve-site operation usually has proper central systems by necessity. The four-or-five-site range is where informal coordination has already broken down but formal coordination hasn't yet been built — which is exactly where a subcontractor can slip through unnoticed at one site while being scrutinised properly at another.

What "shared record" actually needs to mean

A shared, organisation-wide record of subcontractor status — accreditation, current RAMS, past performance — visible across every site rather than siloed at each one, closes both gaps at once: it catches a lapse anywhere in the organisation, and it avoids re-doing verification that's already genuinely current. To actually work, it needs to be something site managers check as a matter of course, not an occasional cross-reference — if looking something up in the shared record takes longer than just re-doing the check locally, people will keep re-doing the check locally, and the shared record slowly becomes stale and untrusted.

What good coordination looks like day to day

In practice, this doesn't need to be complicated to work — it needs to be reliably used. A site manager appointing a subcontractor should be able to quickly check whether that subcontractor is already known to the organisation, what was last verified about them, and when, before deciding whether a fresh check is needed or an existing one is genuinely still current. The bar isn't a sophisticated system; it's that the check happens as a matter of routine, every time, rather than depending on whether a particular site manager happens to remember to ask around.

The handover problem specifically

One of the most common points where this breaks down is a site manager handover partway through a project — illness, a role change, a promotion. The incoming manager inherits a live project and a set of ongoing subcontractor relationships, but not necessarily a clear picture of exactly what's already been checked and when. If the outgoing manager's knowledge lived only in their head, or in personal notes rather than a shared record, that knowledge effectively disappears at the handover point, and the incoming manager is left either re-checking everything from scratch or, worse, assuming things are fine because nobody's flagged otherwise.

A cultural point, not just a systems one

It's tempting to treat this purely as a systems problem — get the right shared record in place and the issue solves itself. That's necessary but not sufficient. Site managers also need to genuinely trust that using a shared record is worth the effort, rather than seeing it as extra admin layered on top of their own local tracking. That trust tends to build when the shared record actually saves someone time early on — catching a lapse they wouldn't have otherwise known about, or confirming a subcontractor is already vetted so a fresh check isn't needed — rather than when it's introduced as a policy requirement with no visible benefit to the person using it day to day.

Common mistakes

• –Assuming a subcontractor's status is current everywhere because it was checked correctly at one site
• –Handing a project over between site managers without transferring a clear record of what's already been verified
• –Building a "shared" record that's really just a spreadsheet nobody outside one site actually opens
• –Treating this as a large-organisation problem, when it often hits hardest in the mid-size range where informal coordination has broken down
• –Re-vetting a subcontractor from scratch at a new site rather than checking whether a current assessment already exists elsewhere in the organisation
• –Letting a site manager handover happen without transferring what's known about current subcontractor status