Contractor Induction & Onboarding Tracker

Site-specific content a generic safety card can't: the site's hazard profile (live systems, traffic routes, overhead work, hazardous substances), emergency arrangements (alarms, muster points, first aid), the permit-to-work system and who issues permits, exclusion and restricted zones, PPE rules, incident-reporting lines, and the site's disciplinary rules. Plus the contractor's own scope interface — where their work meets others'. The test of a good induction is operational: a contractor who completes it knows what can hurt them here, what to do when the alarm sounds, and who to ask before starting anything non-routine.

Most sites run annual refreshes, with earlier re-induction triggered by significant changes — new hazards, changed layouts or processes, major incidents, or a long absence from site. Some high-hazard facilities run shorter cycles or per-project inductions. The expiry isn't bureaucratic: induction content goes stale as the site changes, and a contractor working on a two-year-old briefing is operating on outdated hazard information. Track 'valid till' per contractor per site, route expiring ones through 'Refresh due', and treat an expired induction exactly like a missing one at the gate.

Insurance first — liability certificates with limits that meet the contract, current dates, and ideally your organization named as additional insured where required. Then qualifications: trade licenses for licensed work (electrical, gas, pressure systems), and competence cards for high-risk activities (working at height, confined space). Then the safety paperwork: risk assessments/method statements (RAMS) or JSAs for the actual scope, not generic templates. Verification means checking issuer, dates and scope — a photocopied, expired or wrong-scope document discovered after an incident is functionally a missing one, with the liability to match.

Because the population flows. At any moment some contractors are newly requested, some are mid-document-chase, some are scheduled for induction, most are cleared, and a few are expiring or barred — and the operational question ('can this person work today?') is a status lookup, not a checklist audit. The board makes the gate decision binary and visible, surfaces the stuck states (docs requested two weeks ago, no movement), and produces the compliance metrics (cleared vs pending) that client audits sample. A checklist documents one contractor's journey; the board governs the whole site's contractor population.