Key Takeaways
- Hispanic workers now make up 34% of the U.S. construction workforce, and that share is growing. When a significant portion of your crew can’t contribute to safety reporting, your risk picture has gaps.
- Research shows that roughly half of injured Hispanic construction workers don’t report their injuries to a supervisor. That underreporting creates blind spots in your safety data and weakens your documentation in an audit or courtroom.
- OSHA requires employers to provide safety training in a language workers can understand. That obligation extends to the systems you use to collect field data — if workers can’t participate in your reporting process, you have a compliance gap.
- Voice-driven tools like Safety Mojo’s Conversational Forms and Flex PTP let crews report observations, complete Pre-Task Plans (PTPs), and submit forms in English or Spanish, turning multilingual field input into structured, searchable safety data.
- Closing the language gap goes beyond translating signs. Every worker on site needs a way to participate in the system that captures, tracks, and responds to hazards.
The Reporting Blind Spot on Multilingual Jobsites
Construction has spent the last decade getting serious about safety data. More digital forms, more dashboards, and more processes have improved safety processes and procedures at a rapid pace. The volume of information flowing off a hyperscale jobsite would have been unimaginable fifteen years ago.
But if your safety program is only run in English, a large chunk of your workforce likely can’t participate effectively.
Fun fact: 34% of the U.S. construction workforce communicates more comfortably in Spanish than English. On most sites, close to zero percent of safety observations come in Spanish. Those two numbers don’t add up, and the gap between them is where risk builds undetected because the reporting system doesn’t speak your crew’s language.
On a hyperscale site with 50+ subcontractors and thousands of workers, the gap between a worker’s ability to recognize a hazard and their ability to get it into the record can leave entire trades invisible to the safety team. The result is incomplete risk data, weaker documentation, and exposure that compounds quietly until someone gets hurt or an inspector shows up.
This article breaks down where the language gap comes from, why it gets worse at scale, and what it takes to build a reporting system that works for every worker on the project.
The Hidden Risk of a Silent Workforce
The language gap in construction safety occurs when workers can’t effectively report hazards due to language barriers, creating blind spots in the data GCs rely on to manage risk.
The scale of this gap is significant and growing. According to a CPWR data bulletin published in December 2024, Hispanic workers now represent 34% of the U.S. construction workforce, up from 16.5% in 2000. The number of Hispanic construction workers nearly doubled from 2.2 million to 4.0 million between 2011 and 2023 alone. On hyperscale data center builds, where workforce density runs into the thousands, a substantial portion of any given crew may be more comfortable communicating in Spanish than in English.
That workforce composition matters for safety outcomes. The Bureau of Labor Statistics reported that of the 1,229 Hispanic or Latino worker fatalities recorded across all industries in 2024, 68.5% (842 deaths) occurred among foreign-born workers. In construction specifically, CPWR’s analysis found that fatal injuries among immigrant Hispanic construction workers increased 103.9% from 2011 to 2022.
The underreporting problem makes these numbers even more concerning. A study published by the National Association of Safety Professionals, surveying 500 construction workers (85% of whom identified as Hispanic), found that only about half of injured Hispanic workers reported their injuries or illnesses to a supervisor. The reasons range from fear of retaliation to language barriers that make the reporting process itself inaccessible.
For a GC managing a multi-contractor site, this creates a specific problem: if a third or more of your workforce isn’t feeding data into your safety system, the hazard picture your team relies on every morning is incomplete. You’re making decisions about where to focus site walks, which zones need attention, and which subs are performing well — but the data underneath those decisions has a hole in it swallowing up every worker who couldn’t participate.
OSHA Expectations vs. Reality
OSHA’s position on language and safety training is clear, and it goes beyond posting bilingual signs in the break trailer.
The agency’s Training Standards Policy Statement establishes that all required safety training must be presented “in a manner that employees receiving it are capable of understanding.” In practical terms, that means employers must use both a language and vocabulary that workers can comprehend. A separate OSHA interpretation letter specific to construction confirms there is no requirement that training be in English — the obligation is that whatever communication system you use actually works for the people receiving it.
This principle doesn’t just apply to classroom-style orientation sessions. It extends to the daily touchpoints where safety information flows between crews and management: morning huddles, PTP completion, hazard observations, near-miss reports, and corrective action follow-ups. If a Spanish-speaking crew member spots an unguarded floor penetration near an active work zone but has no practical way to get that observation into your system, the gap between what OSHA expects and what’s actually happening on your site is wider than a translated safety poster can fix.
Most sites address the language gap with a combination of bilingual foremen, translated documents, and the hope that enough information flows through informal channels. These approaches help, but they’re fundamentally one-directional: they push information down to workers without creating a reliable path for field observations to flow back up. A bilingual foreman can relay a toolbox talk in Spanish, but that same foreman can’t be everywhere at once to catch every hazard that a Spanish-speaking crew member might otherwise report.
Basically, that language gap becomes a documentation gap. On a hyperscale site where OSHA’s multi-employer citation policy holds the GC accountable for hazards created by any sub, the inability to capture field data from your entire workforce is a material weakness in your safety program.
How Voice-Driven Reporting Closes the Language Gap
Bilingual voice-driven reporting lets workers describe hazards in their own language, then converts that input into structured, searchable data that feeds the same system as every other crew’s submissions.
The mechanism is straightforward. A crew member opens the app on their phone, taps record, and describes the observation in Spanish. The platform transcribes the audio, extracts the relevant fields — location, trade, hazard type, conditions, controls — and structures the data into a format that safety managers and superintendents can review, sort, and act on in English.
Here’s what that looks like in practice, using Safety Mojo as an example:
- Conversational Forms let workers complete safety observations, inspections, incident reports, and other forms by speaking naturally in English or Spanish. The platform captures the narrative and routes the data into structured form fields up to 80% faster than traditional digital forms. A concrete finisher who spots rebar protruding near a walkway can describe the hazard in Spanish, and the observation reaches the safety manager’s dashboard in the same structured format as every English-language submission on the project.
- Flex PTP handles Pre-Task Plans the same way. Crews keep using whatever PTP form they already have — paper, whiteboard, PDF — and snap a photo with their phone. The platform extracts and scores the data using AI, including hazard identification, control measures, PPE selections, and permit requests. Crews can also complete PTPs by voice in English or Spanish, which eliminates the temptation to pencil-whip a form when the fields don’t match the language you think in.
- Ask Mojo gives field crews voice-activated access to safety manuals, SOPs, and project-specific documents in English or Spanish. A foreman who needs to check a lockout/tagout procedure before energized work can ask the question out loud and get an answer pulled directly from the uploaded documentation. That means no binder hunting, no guessing, and no waiting for a bilingual supervisor to become available.
The practical effect is that Spanish-speaking crews go from being passive recipients of translated information to active contributors of safety data. Their observations, their PTP entries, and their near-miss reports become part of the same dataset that drives every decision on the project.
Turning Multilingual Field Data into Site-Wide Visibility
Capturing multilingual field data only matters if it reaches the people who can act on it. On a hyperscale build with dozens of subcontractors, the challenge is consolidation.
Safety Mojo’s My Day Dashboard pulls PTP submissions, permit requests, safety observations, and corrective actions into a single view. A safety director checking the dashboard at 6:30 a.m. sees the same structured data whether the source was a Spanish-speaking concrete crew or an English-speaking electrical sub. No translation delay, no data sitting in a separate system waiting for someone to interpret it.
That consolidated view makes a few things possible that fragmented data can’t:
- Participation gaps become visible. If three trades are submitting detailed PTPs every morning and a fourth trade has submitted nothing for two days, you know where to focus before the gap turns into a missed hazard. When the barrier to submission drops — because workers can now complete forms in their own language — participation tends to go up, and so does the quality of the data.
- Subcontractor accountability gets objective. Safety Mojo’s Contractor Scorecard tracks PTP completion rates, observation volume, corrective action closure times, and incident history by sub. When a concrete contractor’s crews start submitting detailed observations in Spanish that they previously weren’t capturing at all, the scorecard reflects that shift and gives the GC data to distinguish between subs who are genuinely engaged and those who aren’t.
- Safety data connects to the broader project ecosystem. Safety Mojo integrates with platforms like Procore and Autodesk, syncing PTPs, observations, corrective actions, and permit status into the tools your project management team already uses. Multilingual safety data becomes part of the same project record that owners, insurers, and auditors review.
For a deeper look at how PTP data supports legal defensibility, see our article on transforming PTPs into defensive intelligence.
Building a Safety Program That Includes Every Worker
Closing the language gap takes more than a single technology decision. It requires rethinking how you design your safety program, moving from one that assumes English fluency to one that meets workers where they are.
A few practical steps can help make that shift concrete:
Identify the languages on your site early. During contractor onboarding, ask subs to report the primary languages spoken by their crews. On hyperscale builds, Spanish is typically the dominant non-English language, but depending on the region and the trades involved, you may also encounter Portuguese, Haitian Creole, or Mandarin. Knowing this upfront lets you plan rather than react.
Make reporting accessible in every language your workforce speaks. Translated signs and bilingual orientations are a starting point, but they only address one-way communication. The real test is whether every worker on your site can submit an observation, complete a PTP, or flag a near miss without needing someone else to translate for them. Voice-driven tools that accept input in multiple languages remove that dependency.
Monitor participation rates by trade and language. If your overall PTP completion rate looks healthy but one crew’s submissions are consistently generic or missing, the language barrier may be the culprit. Track completion and quality scores by sub, and look for patterns that correlate with workforce composition. Targeted coaching tends to close these gaps faster.
Use bilingual foremen as coaches, not bottlenecks. Bilingual supervisors are valuable, but they shouldn’t be the only conduit between Spanish-speaking crews and the safety management system. When every worker can submit data directly, bilingual foremen can spend their time coaching crews on hazard recognition and PTP quality rather than serving as full-time translators.
Don’t overlook document access. A Spanish-speaking crew member who can report a hazard but can’t look up the relevant procedure still has a gap. Tools like Ask Mojo let crews search safety manuals and SOPs by voice in their own language, which means the same worker who submits an observation can also verify the correct control measure without leaving the field.
For broader strategies on managing safety across multilingual teams, see our guide on how to manage safety for a multilingual workforce.
Closing the Language Gap in Construction Safety
The language gap in construction safety isn’t a new problem, but the scale of modern builds makes it more consequential than ever. When you’re managing a campus-level data center project with thousands of workers and 50+ subcontractors, even a small percentage of your workforce going silent in the reporting system creates meaningful blind spots.
Closing that gap means moving beyond translated documents and bilingual signage toward systems that let every worker contribute field data in the language they’re most comfortable with. When a Spanish-speaking crew member can describe a hazard into their phone and have that observation show up on the safety manager’s dashboard alongside every other report on the project, you’ve eliminated the bottleneck. The safety record reflects what’s actually happening across the entire site.
That complete picture is what separates a safety program that manages risk from one that merely documents compliance. And it’s what protects your organization when an auditor, an OSHA inspector, or a plaintiff’s attorney asks what you knew about conditions on the site.
Give every worker a voice in your safety program. Book a demo to see how Safety Mojo’s multilingual AI helps teams capture field data from every crew on the project.
Frequently Asked Questions
What is the language gap in construction safety?
The language gap in construction safety is the distance between a worker’s ability to spot a hazard and their ability to report it effectively through the channels available to them. It most commonly affects non-English-speaking workers on sites where safety reporting systems, forms, and communication default to English. The result is underreported hazards, incomplete safety data, and documentation gaps that weaken both compliance and legal defensibility.
Does OSHA require safety training in languages other than English?
OSHA does not mandate any specific language, but it does require that training be delivered in a language and vocabulary workers can understand. The agency’s 2010 Training Standards Policy Statement makes clear that “train” and “instruct” mean presenting information in a manner employees can understand. If your crew doesn’t speak English, training in English alone doesn’t satisfy the requirement.
How does voice-driven reporting help non-English-speaking workers?
Voice-driven reporting lets workers describe hazards, complete forms, and submit observations by speaking naturally in their own language. The platform transcribes the input and routes it into structured form fields that safety managers can review in English. This removes the need for a translator or bilingual supervisor to be present every time a non-English-speaking worker needs to contribute safety data.
What percentage of construction workers are Hispanic or Latino?
According to CPWR data using BLS Current Population Survey figures, Hispanic workers represented 34% of the U.S. construction workforce in 2023, up from 16.5% in 2000. The number of Hispanic construction workers grew from approximately 2.2 million to 4.0 million between 2011 and 2023.
How does the language barrier affect construction safety reporting?
Language barriers reduce the volume and quality of safety data coming from non-English-speaking crews. Research published by the National Association of Safety Professionals found that only about half of injured Hispanic construction workers reported their injuries to a supervisor. When a significant portion of the workforce can’t or won’t participate in the reporting system, hazards go unrecorded, near misses go uninvestigated, and the safety team operates with an incomplete risk picture.
Can AI tools really bridge the language gap on construction sites?
AI-powered voice tools can significantly narrow the gap by converting spoken input in one language into structured safety data in another. They don’t replace the need for bilingual supervisors, cultural awareness, or inclusive safety culture — but they do remove the mechanical barrier that prevents non-English-speaking workers from contributing to the reporting system. The effect is more complete data, which leads to better decisions and stronger documentation.
