The morning that decides everything
Contractor inductions have a shape that employee training never does: they happen under time pressure, to strangers, in batches you did not choose. A groundworks crew arrives at seven. A pair of lift engineers turns up mid-morning without warning. An agency sends four names and five people. Every one of them needs inducting before they work, and every hour they stand waiting is money someone is losing loudly.
The traditional answer is the scheduled induction session, and it fails precisely because of that shape. If inductions run at nine on Tuesdays, a crew arriving Wednesday waits nearly a week or, more honestly, gets walked on with a promise to catch the paperwork up later. The supervisor who delivers the talk has an actual job, so sessions get compressed, skipped or delegated to whoever is nearest. The site's control over who works uninducted becomes a matter of goodwill and memory, at exactly the moment goodwill and memory are busiest.
The fix is not a faster talk. It is removing the appointment entirely: induction as a walk-up service that runs whenever someone arrives, delivered the same way every time, with the record created automatically.
Self-service induction, the morning they arrive
Here is what the seven o'clock rush looks like with a walk-up kiosk. The crew arrives. Each person steps up to the screen, picks the induction, and types in their name and company. No account, no login, no password sent to an office email they cannot reach from a muddy yard. The course runs at their pace: text and images of the actual site, video where it earns its place, narrated audio for those who take in a spoken briefing better than screens of writing, which on a mixed-language crew is more people than most sites assume.
At the end comes an assessment, multiple choice and true-or-false, marked against a pass threshold the site controls, defaulting to 80%. Pass, and a certificate prints on the spot with a human-readable number tying that person to that site, that course and that attempt. The contractor clips it to their paperwork, the record lands in the register, and they sign in and start work. The supervisor never left the job. The gatehouse never made a judgement call.
Because the kiosk caches published course content to its own disk, a wobbly site connection does not stop the morning: inductions carry on and completions upload when connectivity returns. On the kind of site where the network arrives after the workforce does, that detail is the difference between a system and a promise.
Requirements that catch everyone, including the crew you forgot
Kiosk delivery only works if the right people are unmissably in scope. That is a rules problem, not a diligence problem, and it is what a requirements engine is for.
Bound to all contractors by default. The site induction binds to every contractor, including the subcontractor's subcontractor nobody told the office about. Coverage does not depend on someone maintaining a list of companies.
Named bindings for the specialist cases. The asbestos briefing for the strip-out crew, the permit course for the hot works team: bound to named individuals, so specialist requirements land on exactly who needs them.
One published version for every presenter. A draft and published lifecycle means the course at the kiosk is always the current signed-off version. Two contractors inducted a month apart heard the same thing, and the record shows which version each completed.
A register that reads at a glance. Valid, expiring soon and expired filters, plus dashboard tiles for completions today, in progress, expiring this week and overdue this month, each clicking through to exactly who.
Returning workers and the red screen
Contractor churn cuts both ways. Crews leave, and crews come back: the electricians return for second fix, the maintenance contractor reappears for the winter shutdown, the same agency faces cycle through three sites in a season. Returning workers are where paper systems quietly fail, because the question is no longer has this person been inducted but is that induction still valid here, and nobody at the gate can answer it from a folder.
Software answers it at the moment of entry. A returning contractor whose certificate is still valid signs in and walks on, no repeat induction, no queue. One inside the warning window sees amber at sign-in with the exact expiry date, a nudge to renew before the day it bites. And one whose induction has expired meets a clear red screen: sign-in refused, reason stated, retake the course at the kiosk beside them. It is not a confrontation, it is a fact, delivered the same way to every person on every crew.
That physical stop is the entire difference between induction records and induction management. A report that lists lapsed certificates relies on someone reading it, finding the person, and having the argument at the gate anyway. The red screen has the argument for you, at the only moment it can still change the outcome, before the person is on site.
An induction system is only as strong as what happens when the certificate has expired and the contractor is standing at the gate. If the answer is not a refused sign-in, it is not enforcement.
Choosing a system: questions worth asking in the demo
The category is crowded, and the differences that matter do not show up on feature grids. Put these to any vendor with the screen in front of you.
Ask to watch a complete walk-up induction with no login, from choosing the course to holding the printed certificate, and time it against your usual gatehouse rush. Ask what a returning contractor with a lapsed certificate sees at sign-in, and insist on seeing the refusal rather than hearing about the report. Ask who edits the course when the site layout changes next month: if the answer involves the vendor, every revision has a lead time and a cost. Ask what happens to a half-finished induction when the connection drops. And ask how the induction record connects to the rest of the day: sign-in, the live on-site register, the muster list. An induction system that stands alone still leaves the gatehouse stitching systems together by hand.
The pattern across all five questions is the same. Contractor inductions are a gate function, not a training function. Buy them as part of how people enter the site, and the enforcement comes built in. Buy them as a standalone course library, and you will spend the next year building the enforcement yourself.
