The recurring problem
Three weeks before a turnaround the crew lists come in. Two hundred people from twelve subcontractors, out of five countries, with varying experience and varying command of the language. All of them have to know where they may and may not go, what the alarm means, where the assembly point is, and which rules apply here that do not apply elsewhere.
And all of them have to have demonstrably done that before they pass the gate.
The coordinator who has to arrange it usually does so with classroom sessions in the canteen. That works, until the numbers grow.
Why classroom delivery breaks down
At twenty people it is manageable. At two hundred, three problems stack on top of each other.
The arithmetic. Two hours per person, groups of fifteen: that is more than thirteen sessions. Count the preparation and the overrun and a full working week of somebody’s time goes into it, during the busiest period of the year.
Attendance. People arrive at different times, shifts change, a bus gets stuck. There is always a group that misses the session and then has to be done individually, usually by the same coordinator, usually on a Monday morning.
The evidence. An attendance list with signatures demonstrates that somebody sat in the room. It does not demonstrate that they understood it, and certainly not that they understood it in their own language.
Before the gate instead of behind it
The shift that solves it is simple in outline: the induction happens before anybody arrives on site, on their own phone, in their own language.
On contract confirmation the worker gets a link, through the subcontractor, over WhatsApp, however it reaches them. They work through five blocks of ten minutes with imagery of the real location, answer questions about situations rather than definitions, and finish with a verification step. Proof of completion goes automatically to the coordinator.
Whoever arrives on Monday is ready. Whoever is not became visible on Friday, while there was still time to make a call.
The effect on the coordinator is larger than the effect on the contractor: they no longer run sessions, they watch a list. In practice that recovers most of that working week.
What to arrange up front
Three things decide whether this succeeds, and none of them is technical.
Contractually. Put completed induction into the purchasing conditions as a condition of access. Without that hook it stays a request, and requests lose to a schedule.
Languages. Look at the real composition of your chains, not at what the main contractor states. In practice Polish, Romanian and Turkish are needed more often than people expect.
Making it site-specific. A generic safety module produces a tick and changes nothing. Imagery of your gate, your zoning, your assembly point is what people actually remember, and it is the part an outside party cannot invent for you.
It is also reusable. The base exists after the first project; for each following turnaround you adjust the project-specific module. That is a day’s work rather than starting again.
That same reusability applies to the rest of your training offering. How to build it without starting over each time is in the guide on setting up or renewing a corporate academy. The setup itself is described under site induction.