A practical subcontractor onboarding checklist for site managers

A lot of the friction around subcontractor compliance — RAMS missing at the gate, accreditation nobody's checked recently, an induction rushed through under time pressure — traces back to the same root cause: information that should have been gathered and reviewed before a subcontractor's first day is instead being chased for the first time on the morning work is due to start.

Why the timing matters more than the checklist itself

It's tempting to think the fix here is a more thorough checklist, but the more important fix is moving the checklist earlier — ideally completed and reviewed before a subcontractor is even travelling to site for the first time, not on the morning itself when there's no real time to deal with a gap properly. The same information, gathered a week in advance versus discovered at the gate, produces completely different outcomes: one is a routine administrative step, the other is a stand-off that delays the whole crew.

What to gather before appointment

• –Current SSIP accreditation, or equivalent evidence of organisational health and safety management, checked as genuinely current
• –Insurance documentation appropriate to the work being carried out
• –A track record or references relevant to the specific type of work, not just general trade experience
• –Details of the specific individuals or crew expected on site, where known in advance
• –Confirmation of who within the subcontractor's business is responsible for producing and standing behind their RAMS

What to confirm shortly before the first day on site

A second, closer-to-the-date check catches things that can change between appointment and actual start — has the RAMS for the specific task actually been submitted and reviewed, are the individuals confirmed to attend still the ones originally checked, has anything about the site conditions changed since the RAMS was written. This closer check is deliberately lighter than the initial appointment review — it's not re-litigating the whole competence decision, just confirming nothing material has shifted since it was made.

A worked example

A groundworks subcontractor is appointed three weeks ahead of a project starting. Accreditation, insurance and general competence are checked and confirmed at appointment. Two days before their start date, a quick check confirms whether their RAMS has actually been submitted — it hasn't, because the person responsible for writing it at the subcontractor's end has been on leave. That gap, caught two days out, is a phone call and a slightly awkward conversation. The same gap, discovered at the gate on the morning work is due to start, is a crew standing idle and a much worse conversation for everyone involved.

Building it into how work gets scheduled, not as a separate task

A checklist that lives as a standalone document, disconnected from how work is actually scheduled, tends to get forgotten under the pressure of a busy week — it's easy for a step like confirming the RAMS is in to fall off a to-do list competing against the daily reality of running a site. It works better folded directly into the scheduling process itself: a subcontractor doesn't get confirmed onto the programme for a given date until the pre-arrival checks are complete, making the checklist a genuine gate in the process rather than an aspiration that's easy to skip when things get busy.

Handling repeat subcontractors without skipping steps

It's tempting to shortcut this for subcontractors who've worked on previous projects without issue, but a subcontractor's status can change between projects — accreditation lapsing, the specific crew being sent this time differing from last time, the nature of the work being materially different even if the trade is nominally the same. A lighter-touch version of the checklist for a known, trusted subcontractor is reasonable; skipping it entirely on the assumption that a previous good experience still holds is how a gap eventually slips through unnoticed.

Common mistakes

• –Gathering competence and accreditation information for the first time on the morning work is due to start
• –Treating repeat subcontractors as exempt from onboarding checks entirely, rather than applying a lighter, proportionate version
• –Not confirming shortly before the start date that RAMS has actually been submitted, rather than assuming appointment-stage checks still hold
• –Keeping the checklist as a separate document nobody actually consults when scheduling work
• –Not recording who specifically is expected on site, making it harder to check individuals against what was agreed at appointment
• –Assuming a subcontractor's own project manager has passed on all the relevant information to the crew actually turning up