The Bilingual Lead Is Doing a Second Job
Why this matters
Every multilingual shop has one or two people who make it run: the lead who briefs the crew in two languages, talks to the customer at the door, takes the office's call to explain a part name to another crew, and helps a helper read a pay stub at lunch. None of that is on their job description, most of it is not counted anywhere, and all of it is real work. When their own jobs run long or their numbers slip, it looks like a performance problem. When they make a mistake at 4:30 in the afternoon, it looks like carelessness. Usually it is neither. It is the predictable result of doing two jobs in one day, and only one of them being visible.
What the second job actually contains
Interpreting is only part of it. A bilingual lead in a field-service shop typically carries some mix of:
- Crew interpreting: the morning briefing, job changes, corrections, safety instructions, in both directions.
- Customer interpreting: scope at the door, questions during the job, the walkthrough at the end.
- Remote interpreting: calls from the office to explain something to another crew, a customer callback in Spanish, an inspector's correction list.
- Translation: close-out notes, work orders, a supplier's instructions, a label.
- Personal help for coworkers: pay stubs, a doctor's form, a letter from a landlord or a school. Not company business, but done on company time because nobody else can.
- Cultural brokering: explaining what the owner meant, why a customer reacted the way they did, why a new rule exists.
- Informal training: re-explaining a task to a new hire who did not follow the first explanation.
Each item is small. Counted across a day, they are a part-time job.
Why interpreting is tiring in a way that does not show
Interpreting is not the same as speaking two languages. It means holding one person's words in memory while producing them in another language, in real time, while also deciding what to keep, while also doing your own work. Professional interpreters treat it as demanding enough that, on long assignments, court and conference interpreters commonly work in pairs and switch roughly every half hour, because accuracy drops with sustained effort. Your lead is doing it alone, in bursts, all day, between their own tasks, often outdoors and on their feet.
What fatigue does to interpreting is specific and predictable:
- Omissions. A clause drops out, often the qualifier or the exception.
- Simplification. A nuanced answer becomes yes or no.
- Number and negation errors. The two things that matter most on a job are the two things a tired interpreter is most likely to flip.
- Answering instead of relaying. Rather than translating the question, the lead answers it themselves, because it is faster. Sometimes they are right. This is also how filtering starts (see related: Leading a Crew Whose Language You Do Not Speak Well).
These errors cluster late in the day and late in the week, which is also when the lead's own work is under the most time pressure.
The hidden cost to their own work
Every interruption costs more than its own length, because the lead has to stop, switch, and then find their place in their own task again. A lead whose jobs run long, whose production lags another lead's, or who is the last to finish close-out paperwork may be the most productive person in the shop once the second job is counted.
There is also a safety cost. A lead who answers an interpreting call while on a ladder, on a roof, or with hands in energized equipment has split their attention at exactly the wrong moment. Set the rule plainly: interpreting calls go to voicemail while the lead is at height, inside a panel or doing any task the job's hazard briefing flagged, and the office waits or uses a phone interpreter service instead (see related: Using a Phone Interpreter Service).
How to recognize it
Signs that the second job has grown past what one person can carry:
- The lead's own jobs run long, and nobody can say why.
- Their mood visibly drops through the day; they are short with people after 2 p.m.
- They start avoiding calls from the office.
- They skip lunch because lunch is when the crew brings them personal paperwork.
- Interpreting errors appear late in the day or the week, not early.
- They mention, more than once, that they are tired of being "the translator."
The most useful thing an owner can do is count it, because a second job nobody has measured cannot be recognized, reduced or paid for.
Interpreting the lead should not be asked to do
Some interpreting is wrong to hand the lead even when they are willing. A disciplinary conversation with someone on their own crew puts them in the position of delivering the boss's words to a coworker they work beside every day, and the coworker will remember who said them. A complaint about the lead, by definition, cannot go through the lead. An injury report, a medical conversation or a wage dispute needs an interpreter whose accuracy is not in question if it is ever reviewed, and whose relationship with the person is not part of the story. For these, use a phone interpreter service or a professional, and tell the lead why: it protects them as much as anyone.
Worked example: one week, counted
Hector leads a three-person plumbing crew. He is the shop's only bilingual lead. His production has lagged the other lead's for months: about 4 completed jobs a week against 5, on similar work averaging about 7 hours a job. The owner asks Hector to keep a simple log for one week, with every interpreting or translating request, who asked, and roughly how many minutes it took. These figures are illustrative of the method, not a benchmark. Tuesday looked like this:
INTERPRETING LOG - HECTOR (LEAD) TUE
TIME ASKED BY WHAT MIN
07:05 office job changes to crew 10
07:40 customer scope at the door 8
09:15 office call other crew: part name 4
10:30 helper pay stub question 12
11:50 inspector correction list 15
13:20 office call customer callback 9
14:10 helper doctor's form 10
15:30 new hire re-explain task 7
16:45 office close-out notes ES->EN 14
-------------------------------------------------
REQUESTS 9 TOTAL 89 MIN
not for his own crew or job: 09:15, 13:20 = 13 MIN
personal help for coworkers: 10:30, 14:10 = 22 MIN
The week. Across five days the log shows 41 requests totaling about 390 minutes, or 6.5 hours, against a scheduled week of 45 hours. That is about a seventh of his week (6.5 of 45 hours, roughly 14 percent). Tuesday's 89 minutes is close to that share of a 9-hour day.
Comparing like with like. Hector's production gap is about one job a week, which at about 7 hours a job is roughly 7 hours of field time. The log shows about 6.5 hours of interpreting. Both are hours in the same week, and they are close: the gap is essentially the second job. The comparison is approximate, and some of the interpreting (the inspector's list, the close-out notes) served Hector's own jobs, so not all of it displaced field work. But it is enough to stop treating his numbers as a performance problem.
The error that week. On Thursday at 16:30, a customer told Hector in English that the basement shutoff valve "doesn't hold." Hector, finishing his own close-out with a helper waiting, relayed it to the helper in Spanish as the shutoff being in the basement. The helper closed it, cut the line, and the valve passed water. The flow was stopped at the street shutoff within a couple of minutes, with a wet floor and no damage beyond cleanup, but the water reached the floor near a basement outlet. The helper was right to leave the outlet alone and kill the basement circuit at the panel before mopping, standing on dry floor to do it, and the shop's practice now is to cut only after the valve has been tested by opening a fixture downstream and confirming no flow. The error was a dropped clause late in the day, the most predictable kind of fatigue error, on the 32nd of the week's 41 requests.
What the owner changed.
- Office calls that are not about Hector's own job now go to a phone interpreter line. That removes the "not for his own crew" category entirely.
- The shop's work order templates, safety cards and close-out form are translated once (see related: Translating SOPs and Checklists for the Crew), which cut the daily close-out translation.
- Personal paperwork help moved to a scheduled 30 minutes on Friday, paid, at the shop, and the owner pointed crew members to community resources for anything legal or medical.
- Interpreting calls go to voicemail when Hector is at height or in a panel.
- The owner started a conversation about recognizing the role in pay, which has its own card (see related: Setting a Language Pay Differential Fairly).
A month later Hector logged another week: 24 requests, about 3.5 hours. His completed jobs rose to 5 in two of the following four weeks.
What changes the answer. If a shop has two or three bilingual people, the load can be rotated rather than reduced; the risk then is that the most fluent one still ends up carrying it, so log all of them. If the lead is the only person who can run the morning briefing, that part of the second job cannot be delegated, only scheduled early in the day, when accuracy is best.
How to verify you got this right
Ask each bilingual person in the shop to log one week. Total the hours, and write down what share of their week it is. If you cannot answer "how many hours a week does our shop spend on interpreting, and who does it," you have not yet recognized the second job, whatever you pay for it.
References
- See related: Leading a Crew Whose Language You Do Not Speak Well
- See related: Setting a Language Pay Differential Fairly
- See related: Using a Phone Interpreter Service
- See related: Translating SOPs and Checklists for the Crew