Training in a Language Your Crew Understands

A signature on a sign-in sheet is not comprehension. OSHA's position is that training must be delivered in a language and vocabulary workers understand.

There is a version of safety training that satisfies a filing cabinet and protects nobody. A worker sits through a session in a language they follow partially, signs the sheet because everyone signs the sheet, and goes back to work with a general impression that falls are bad.

The paperwork is complete. The worker is not protected.

What OSHA expects

OSHA has made its position clear in guidance to its own compliance officers: training required by OSHA standards must be presented in a manner that employees can understand. That includes both language and vocabulary.

In practice this means:

• If a worker's comprehension of English is limited, training must be delivered in a language they do understand.
• Vocabulary and literacy level must match the audience. Reading a standard aloud verbatim is not instruction.
• The obligation belongs to the employer. It does not transfer to the worker, a bilingual coworker, or a translated handout distributed after the fact.

An employer who provides training a worker cannot understand has not met the training requirement, regardless of what the sign-in sheet shows.

Why this matters more in construction

Construction and general industry employ a substantial Spanish-speaking workforce, particularly across Texas and the Gulf Coast. Fatality rates among Hispanic workers have been a persistent and well-documented concern in national statistics.

The causes are layered — job tenure, task assignment, and industry mix all contribute. But comprehension of safety instruction is one of the factors an employer can directly control, and it is often the cheapest one to fix.

The informal interpreter problem

The most common workaround is asking a bilingual worker to translate on the spot. It is well intentioned and it is unreliable:

• That worker is not a trained interpreter and may not know the technical vocabulary
• Safety terminology is precise — "arrest," "anchorage," "competent person," "permit-required" all carry specific meanings that do not survive casual translation
• It puts a worker in a position of responsibility they were never trained for or compensated for
• Nuance and qualifications get compressed out; what survives is the headline, not the conditions

Real training in the target language avoids all of this.

Translated does not mean equivalent

A slide deck run through translation software is not a Spanish course. Working idiom differs by region and trade, and a literal translation frequently produces text that is grammatically fine and practically meaningless on a jobsite.

Genuine bilingual training means the instructor teaches in that language — answers questions, works through examples, reads the room, and adjusts when something has not landed. That is not something a document can do.

Verify comprehension, not attendance

A sign-in sheet records who was present. It does not record who understood. Better checks:

• Ask workers to demonstrate — inspect the harness, identify the hazard, show where the SDS lives
• Ask open questions rather than yes-or-no questions. "Do you understand?" reliably returns "yes."
• Have a worker explain the procedure back in their own words
• Watch what happens on site over the following week, which is the only measurement that fully counts

The business case

Beyond compliance, comprehension shows up in outcomes that are easy to measure: fewer incidents, fewer recordables, lower experience modification rates, less rework from damaged material, and fewer stoppages. General contractors increasingly ask subcontractors how training is delivered, and being able to answer that every course runs in English or Spanish is a competitive advantage on prequalification.

The standard to hold yourself to

Every worker on your site can explain, in their own words, the hazards of their task and the controls that protect them. If that is true, the training worked. If it is not, no amount of documentation closes the gap.