Site Safety Training in Every Crew Language

Quick answer — Site safety training has to be understood, not merely delivered. Work out the languages actually spoken on site rather than the ones on the contract, and evidence understanding rather than attendance.

Vitra.ai Universe keeps one site vocabulary across drawings, documents and talks.

Attendance is not understanding

A signed attendance sheet records that someone was present. It does not record that they followed the briefing, and on a site with several first languages those are different things.

That gap is invisible until an incident, at which point the training record is examined and the question becomes what the person actually understood.

Find out which languages, from the site

The languages on a site are rarely the ones anyone planned for. Labour arrives through subcontractors and agencies, and it changes between packages.

Informal translation by a bilingual colleague is the most common arrangement on sites, and it is worth recognising rather than pretending otherwise. It also means one person carries a responsibility nobody assigned them. It works well enough most days and fails in the situations that matter, since the person translating is not trained in the content and is often junior to whoever is briefing. Naming that arrangement in the training plan is more honest than assuming it away.

Translate what people act on first

Not everything needs translating, and starting with the corporate documents wastes the budget on the material furthest from the work.

The order that works is the day-one induction, then the method statements and RAMS for the work someone is actually doing, then emergency and evacuation instructions, then signage, then the policy documents that sit above all of it.

Evidence understanding, not attendance

Short verification questions in the person's own language, asked and recorded, are worth more than a longer signature sheet.

They also surface the case where the translation was fine and the instruction was not, which is the finding worth having. Keeping the language of delivery attached to the record is the part usually missed, and it is what makes the record meaningful later. That case is more common than a mistranslation and much harder to see, because everyone involved did their job correctly. Keeping the language of delivery attached to the record is what makes it meaningful later.

Keep the words the same everywhere

The name of a hazard, a permit, a piece of plant or a control measure should be the same in the briefing, the drawing, the sign and the toolbox talk.

A pinned glossary in translation memory does that across every document type, and quality control checks it rather than sampling — which matters when subcontractors bring their own documents into the set.

The rest of the set

• Inductions, RAMS, method statements, video training, safety policy - Tenders, contracts, permits - Drawings, progress reports, snagging, handover

More at Vitra for construction.

FAQ

How do you know which languages a site needs? From the site rather than the contract. Subcontractor and agency records, induction data, what supervisors know about who translates for whom, and incident records showing where instructions did not land.

What should be translated first? The day-one induction, then the method statements and RAMS for the work someone is actually doing, then emergency instructions and signage. Corporate policy documents come last, not first.

Is an attendance sheet enough evidence of training? No. It records presence, not understanding. Short verification questions asked and recorded in the person's own language are worth more, along with the language the briefing was delivered in.

Why does terminology consistency matter on site? Because a hazard, permit, machine or control measure named differently in the briefing, the drawing and the sign creates doubt at the moment someone is deciding what to do.