Skip to main content

Running a Multilingual Construction Crew on WhatsApp

· 9 min read
Vikas Singhvi
Vikas Singhvi
Founder

On most construction sites, the language the crew works in isn't the language the report is written in. Crews in India move between states. Gulf construction runs on a workforce drawn from across South Asia and beyond. Finishing crews on US jobs often work in Spanish. In each case the foreman's morning update is a voice note in his own language in a WhatsApp group, and someone bilingual retypes it into English every evening, or it never gets recorded. This post is about closing that gap without pushing an English-first app onto the crew.

It's 7:10am. Before the first material is unloaded, the civil foreman on Tower B sends a voice note to the site WhatsApp group:

"Aaj 14 log hain. Third floor ki shuttering kal complete ho gayi, aaj se steel binding shuru. Cement khatam hone wala hai, store ko list bhej di hai."

Fourteen on site. Third-floor shuttering finished yesterday, steel binding starts today, and cement is running low; the list has already gone to the store. Thirty seconds, in Hindi and English mixed, with no form and no app. It's the most accurate account of that crew's day, and it exists only as audio in a group chat.

The Working Language Is Rarely the Reporting Language​

This isn't a niche case. It's the normal shape of a construction workforce in most markets:

  • India. Construction employed an estimated 7.47 crore (74.7 million) people in 2022-23 (RBI KLEMS data, via the Ministry of Labour & Employment), and crews often travel across states for work. A single site can have a Hindi-speaking civil crew, a Bengali- or Odia-speaking labour gang, and a Telugu- or Tamil-speaking MEP team, all reporting to engineers who write the DPR in English.
  • Middle East. Saudi Arabia alone had nearly 3 million non-Saudi workers employed in construction in Q1 2025 (GASTAT, via the Gulf Labour Markets and Migration programme), much of that workforce recruited from South Asia. On-site coordination happens in Hindi, Urdu, Bengali, Malayalam or Arabic. Reports to the consultant and the client are in English.
  • United States. In the finishing trades, more than half the workers are foreign-born: drywall 57%, roofers 53%, painters 53% (NAHB, 2024 data). On many of those crews the working language is Spanish, and 54% of US Hispanic adults use WhatsApp (Pew Research, 2024).

The pattern is the same everywhere. The huddle, the headcount and the "we're blocked" happen in one language. The DPR, the client report and the dashboard are in another, and WhatsApp is where the two meet.

Swap the site and the voice note sounds different. On a finishing crew in Texas, it might be:

"Buenos días. Hoy somos nueve. Terminamos el hang en el segundo piso ayer, hoy empezamos el tape. Nos falta compuesto, mandé la lista al almacén."

Different language, same update: headcount, progress, what's next, what's short.

Where the Day's Record Actually Lives​

Walk the chain backward from your daily progress report and it ends at that morning voice note.

The foreman speaks the update because that's fastest and it's in his language. It lands in the WhatsApp group. Then, whether your office runs on an Excel DPR, an ERP or a project platform, someone has to get it from a voice note in Hindi, Arabic or Spanish into an English form field.

That someone is usually a bilingual site engineer or supervisor. Every evening they open the groups, listen to the voice notes, translate in their head and type an English summary into the report. What the office reads the next morning is a translated, compressed, end-of-day version of what the foreman said in real time.

The signal was clean when it was sent. It degrades on the way to your dashboard.

Why the English-First Field App Was Never Going to Work Here​

The standard fix is to put an app in the foreman's hands and ask him to log progress. On a multilingual crew, that fails for a reason that has nothing to do with smartphones or effort.

The app is in English: the dropdowns, the field labels, the work-item names. The foreman is fluent in the work but not in the interface. Asking him to translate his own update into a form, in a second language, at the end of a ten-hour shift is a tax his English-speaking counterpart doesn't pay.

Language barriers on mixed-language crews are well documented as a safety and coordination problem in construction. That's not because anyone lacks skill. It's because information stops moving cleanly when it has to cross a language line to be recorded, and an English-only form adds a language line exactly where you don't want one.

WhatsApp doesn't. It carries Hindi, Arabic, Spanish, voice notes and mid-sentence language switching natively, because the foreman is just talking.

The Translation Step Nobody Put on the Schedule​

Here's the cost. Like most coordination costs, it's invisible because it's spread across people already on payroll.

Your bilingual engineer spends part of every evening turning voice notes and mixed-language messages into English report entries for each active site. Across several sites, that's most of an evening, every evening, done by one of your more valuable people. When that person is on leave or moves on, the daily report degrades until someone else picks up the translation work.

And it's not just progress reporting. The same gap shows up in attendance. The foreman's headcount message, "aaj 14 log, Ramesh nahi aaya", gets hand-translated into the attendance sheet, then reconciled against the labour contractor's invoice at month end. Same message, retyped twice, with a translation in the middle. (We wrote about that chain in The Payroll Leak on Every Construction Site Nobody Is Measuring.)

What Multilingual-by-Default Looks Like​

The crew keeps sending messages and voice notes in their own language to the same WhatsApp group they use now. Nothing changes for the foreman.

Velora connects to that group and reads it in whatever language it arrives in. Voice notes are transcribed, and the progress, headcount, material shortages and commitments are extracted and structured. The daily progress report, the labour report and the dashboard come out in English, for the office, the consultant and the client. If something's missing, such as a headcount that wasn't mentioned or a commitment with no follow-up, Velora asks the foreman directly, in his language, in the same group, and logs his answer.

Your bilingual engineer stops being a nightly translation service. The office reads a clean English record that's current by the hour instead of reconstructed at 9pm. And the original message stays attached to every entry, timestamped, if anyone ever needs to check what was actually said.

What It Isn't​

Velora isn't a translation app you hand to the crew, and it isn't a chat tool you're asking anyone to adopt. There's no app for the foreman, no login and no new group.

It reads the WhatsApp group the crew already uses, in the language they already use it in, and gives the office a structured English record. Languages supported today include English, Hindi, Telugu, Arabic and Spanish, among others, including messages that switch between languages mid-sentence.

Frequently asked questions

Is there a construction daily report tool that works for crews who don't speak English?
Yes. Velora connects to the WhatsApp group your crew already uses, reads their messages and voice notes in Hindi, Arabic, Spanish, Telugu and other languages, and produces the daily progress report, labour report and dashboard in English for the office. Follow-up questions to the foreman go back in his language. The crew installs nothing and changes nothing about how they communicate.
Why don't foremen on multilingual crews use English construction apps?
Not because of smartphones or effort, but because the app's fields, labels and menus are in English. Asking a foreman who is fluent in the work but not the interface to translate his own update into an English form at the end of a long shift is a tax his English-speaking counterpart doesn't pay. WhatsApp carries voice notes and mixed-language messages natively, so the update just gets sent.
How multilingual are construction workforces in India, the Middle East and the US?
Highly. India's construction sector employed an estimated 74.7 million people in 2022-23 (RBI KLEMS), with crews frequently working outside their home state and language. Saudi Arabia had nearly 3 million non-Saudi construction workers in Q1 2025 (GASTAT), much of that workforce from South Asia. In the US, more than half of drywall, roofing and painting workers are foreign-born (NAHB, 2024 data), and many finishing crews work in Spanish.
Does Velora translate the messages, or just read them?
It reads and structures them. Messages and voice notes in the crew's language are extracted into structured progress, issues, commitments and attendance; the reports and dashboard are generated in English. The original message stays attached to each record with its timestamp. Velora is not a real-time interpreter or a comms tool for the crew.

See It on Your Own Groups​

If your crews run on WhatsApp in a language other than the one your reports are written in, your daily record already exists. It's just trapped in voice notes and getting retyped every night.

  • 👉 Explore Velora: see how messages, voice notes and photos in any language are structured by AI, for your team to review.