English boss, Spanish foreman: making the relay work

You have a good setup on paper. You run the office and the customers in English. Your foreman, call him Hector, runs the crew in Spanish. He is sharp, the guys trust him, and for three years he has been the bridge that makes the whole thing work. So you lean on him. Every instruction you have goes to Hector, and Hector turns it into Spanish for the crew. Every question from the crew comes back through Hector in English. It feels efficient. One person, both languages, no confusion.

Then one Tuesday Hector wakes up with a fever, and by 9am you understand exactly what you built. The site is quiet. Nobody knows the sequence for the day, nobody can reach the customer, and the two questions the crew has are sitting in Spanish that you cannot answer. You did not build a bilingual company. You built a company that runs on one man’s phone, and that man is home sick.

This is the relay problem, and it is understandable why it happens. Hector is good at it, so you use him for it. But a relay is a single point of failure, and on a small crew that failure has a real cost. This guide, part of our running a bilingual crew series, is about naming where the relay bends and unloading it, so Hector goes back to running the job instead of carrying your words.

A day in the relay life

Watch where the instructions actually bend. It is not one big break. It is a hundred small ones.

7:10, you tell Hector the Ramirez job needs the master bath roughed today and the customer wants the shutoff moved to the left wall. Hector is driving, so he half-hears it, gets the rough part, files the shutoff detail as “something about the left wall.” 7:40, he relays it to the crew in Spanish, and the shutoff detail is now a maybe. 10:15, a plumber on the crew has a question about the shutoff, asks Hector, Hector is on another site and does not pick up. 10:40, the crew makes a reasonable guess and moves it left, but not where the customer meant. 2pm, you text Hector asking if the shutoff got moved, he texts the crew, the crew sends a photo back, Hector forwards it to you. By the time you see it, four people have touched one instruction and it has changed shape twice.

Nobody in that chain did anything wrong. Hector relayed in good faith. The crew made a fair call. But look at what the relay cost you: the customer’s one specific request got softened into a guess, the plumber’s question waited two hours for an answer that lived in one busy man’s pocket, and you found out where things landed hours after you could have corrected them. Every message went through a human who was also trying to run a job, and every hop was a place for the message to bend.

Run that day across a five-man crew and the bends add up. If half of Hector’s day is translation, you are paying a foreman’s wage for a job you could have handed to the tool. Say he spends three hours a day relaying instead of leading. That is most of a workday, every day, spent moving words instead of checking work. And on the Tuesday he is out, all of it stops at once.

Where the relay actually breaks

The same failures show up on every bilingual crew that runs through one person.

The detail gets softened. A verbal instruction relayed by a busy man loses its edges. “Left wall, forty-two inches” becomes “on the left somewhere.” The specifics are exactly what the customer will inspect, and they are exactly what a relay drops first.

The question waits on one phone. When the only path from the crew to you runs through Hector, the crew is stuck whenever Hector is unreachable. He is on a roof, in a truck, on another site. The work either stops or guesses, and both cost you.

The answer never gets back to the crew. You answer Hector. Hector meant to tell the crew. He got pulled onto something else. The crew never hears it, does the thing the old way, and you find out on the callback. The information existed. It just never completed the last hop.

One sick day goes dark. This is the one that should scare you. Everything the crew needs to work lives in Hector’s head and Hector’s phone. When he is out, there is no record for anyone else to read. The site does not slow down. It stops.

The fix: unload the relay

The move is not to find a second bilingual person to back up Hector. It is to stop routing words through a person at all. You want the instruction written down once, in a place the crew reads directly, in the language they read, so Hector stops carrying words and goes back to checking work.

Written beats verbal here for the same reason it always does: written instructions do not bend on the drive to the site. If you get the task down in text, the tool can put it in front of the crew in Spanish and put their reply in front of you in English, both directions, without Hector being the wire. There is a whole guide on writing task instructions a bilingual crew can’t misread, and the short version is: one task, one clear action, one photo when the work calls for proof. “Move the shutoff to the left wall, 42 inches off the floor, send a photo before you close the wall” reads the same in either language and leaves nothing to soften.

When the words carry themselves, Hector’s job changes back to what you hired him for. He is not the translator anymore. He is the foreman who reads the same task the crew reads, walks over, and checks that the shutoff landed where the customer wanted. Proof on the task does a lot of this work: a photo of the finished rough answers “did it get done right” in a language neither of you has to translate. That is the idea behind photos as common ground, and it takes another load off the relay.

This is also how you stop being the bottleneck on the English side. The broader problem, running a crew whose language you do not fully share, is worth reading on its own if you are the boss in that spot: managing a Spanish speaking crew when your Spanish is thin. The relay is one piece of it. Unloading the relay is the piece you can fix this month.

The relay got your company this far, and it is easy to see why you leaned on Hector for it. But it is a load he should not be holding, because it makes him fragile and it makes your whole site fragile with him. The hard read is that it broke a while ago, quietly, on every softened detail and every unanswered question, and you only noticed on the Tuesday he was out. It breaks past a handful of people, and the cost is a dark job site and softened instructions you pay for in rework.

Where this leaves the tool

This is the problem Crewmigo is built for. Each job is its own thread that remembers, so the day’s tasks live in the job, not in Hector’s memory. The thread translates both directions on the paid plan: you write the instruction in English, the crew reads it in Spanish, their reply comes back in English, and nobody has to be the wire. The task carries a photo when the work calls for proof, so Hector checks the work instead of relaying words about it, and sign-off happens by rank when the job is actually done. We are new, so put one job on it, the one where a softened instruction cost you last month, and watch whether the words still bend when Hector is not the one carrying them.