In this article
The server calls out "table 4, prawn cocktail, allergy" to the pass. The cook nods. Twenty minutes later a shrimp starter lands on table 4 — the cook heard "table 4", not "allergy".
That scenario is invented, but the pattern behind it isn't. In a growing number of European kitchens, the people on the pass work across four, five, sometimes six different first languages at once — Polish, Moroccan Arabic, Romanian, Portuguese, Ukrainian, Syrian Arabic, alongside the local language. This site already knows that reality well: the free Chef Abroad dictionary exists precisely because a cook takes a job in a kitchen where they barely speak the local language, nods at the instructions, and hopes it was the right answer.
What nothing on this site — and almost nothing in the trade press — has ever addressed on its own is what that language mix means the moment it goes wrong. Not awkward. Dangerous. An allergy order that gets garbled between a non-native server and a non-native cook isn't a language slip, it's an incident that was waiting to happen. A cancelled order that doesn't land pulls a wasted dish and an angry guest. A fire call that doesn't reach the person standing closest to the stove is something you don't want to think about.
This article treats that gap as an operational risk, not an etiquette question. Four systems, in the order a kitchen would realistically build them — from a core vocabulary everyone knows to a confirmation protocol for anything that can hurt someone — plus a calculator that tells you how exposed your own shift is today.
Why this is more than a matter of politeness
Aviation and healthcare already solved this problem — just not for a kitchen. For decades, most air accidents turned out not to be caused by mechanical failure but by miscommunication between crew members, which is why the industry moved to mandatory "readback": whoever receives an instruction repeats it back verbatim, and only then is it considered confirmed. Hospitals adopted the same protocol under the name closed-loop communication, and the U.S. Joint Commission has reported that poor communication is a contributing factor in more than 60% of reported serious hospital adverse events — not a lack of knowledge, a lack of communication.
A busy kitchen on a Friday night sits closer to a cockpit than an office in its risk profile: noise, time pressure, several voices at once, and decisions that can't be undone once a plate leaves the pass. The difference is that a pilot gets a standardised protocol and a cook gets a rota. Almost nobody explicitly trains a brigade in how a message survives when sender and receiver don't share a first language — it's simply assumed to "work itself out" over a few months on the job.
It usually does — until the moment it doesn't, and that moment doesn't wait for a convenient night. The four systems below cost no language course and no extra headcount. They cost a few hours to set up and the discipline to keep them running on the busiest night, precisely when the temptation to drop them is greatest.
The ultimate guide Staff & Operations: Everything for a Team That Stays From onboarding to rota to burnout: the complete guide for anyone running a hospitality team. Open the guideThe four systems
None of these four replaces the others — together they cover four different ways a message gets lost along the way: too few shared words, no backup when the spoken word fails, no confirmation for the one type of message that matters most, and no structure for whoever is new.
1. A shared core vocabulary — not fluency
The goal isn't for everyone to learn the local language. That's unrealistic in the short term, and it isn't what a shift actually needs. What is needed: 40 to 50 words that literally everyone on the floor recognises regardless of native language — the names of the fourteen legal allergens, "hot", "behind", "86'd", the station names, "fire", "cancel that". That's a list you can walk through in one shift and bed in within two weeks.
This is exactly why the Chef Abroad dictionary on this site offers 250 words in 24 languages, split into sets of 10: not because a brigade needs 250 words, but because every kitchen needs a different core set of 40 to 50, and you should be able to build that from a larger, already-translated pool rather than improvising it every time.
The discipline isn't in making the list — that takes an hour — it's in testing it. On a trial shift, don't ask "do you understand?", ask "repeat back what I just said". That's exactly the principle of system 3 below, applied to the training itself.
One order carrying an allergy crosses a language boundary four times between guest and plate. Every hand-off is a place a word can be lost — and two of them happen exactly when the kitchen has the least time to notice.
The two flagged hand-offs aren't a coincidence — they're precisely the two that system 3 (closed-loop confirmation) addresses directly; system 2 (the visual backup) already covers much of the other two.
2. A visual backup for every spoken instruction
A kitchen at 8:30 pm is loud, and a missed word doesn't get a second chance. Anything safety-critical that's said out loud should therefore also exist somewhere in writing — not as extra paperwork, but as a safety net for the moment the spoken word fails. A station board with names and tasks. A prep sheet with quantities in numbers, not sentences. An allergen matrix on the wall next to the pass, instead of inside one person's head.
This is exactly why this site builds separate tools for those two things instead of leaving them to chance: the kitchen station plan puts down in black and white who stands where and what happens there, and the allergen chart lays the fourteen EU allergens per dish out in a matrix anyone can read without having to decode a sentence. Numbers, symbols and a fixed spot on the wall work across a language barrier in a way a spoken sentence never can.
This doesn't replace the spoken word — it gives it a second chance. A server calling out "allergy, table 4" and an allergen matrix that already flags the same table are two independent signals. Only one of them has to land.
An illustrative estimate, not a measured figure: the more distinct native languages meet on one shift, the smaller the share of a full kitchen vocabulary that happens to overlap — unless a core vocabulary has been explicitly trained, which by construction stays high regardless of how many languages come together.
These aren't measured percentages from this or any kitchen — they illustrate the pattern: incidental overlap falls with every extra language; a trained core vocabulary of 40 to 50 words (system 1) does not.
3. Closed-loop confirmation for anything that can hurt someone
This is the system aviation and emergency medicine have used for decades and that almost no kitchen applies deliberately: for anything that can physically harm someone, an instruction is never confirmed with a nod or an "okay" — it is repeated back verbatim by whoever receives it. "Table 4, nut allergy." — "Confirmed: table 4, no nuts." That costs two seconds, and it's the only moment a misheard word can still be caught before the plate leaves the pass, instead of after.
The distinction from an ordinary acknowledgement is exactly why it works: a nod confirms that something was heard, not what was heard. "Okay" says nothing about the content. A literal repeat-back puts the content back on the table, and any error in it becomes visible to both sides immediately — before it's too late.
Keep this to what can actually hurt someone: allergies, cross-contamination, fire calls, and cancellations that need to pull a dish off the pass. Confirming everything drowns the system in its own discipline; confirming only what matters most keeps it alive on a busy Friday.
4. A bilingual buddy for the first two weeks
A new non-native starter who's simply put on the rota learns the kitchen's language by making mistakes — and the first two weeks are exactly the period when those mistakes are most expensive, because nobody yet knows which instructions did and didn't land. A structured buddy with enough shared language to translate in the moment isn't an extra cost — it's a shift in when the mistakes happen: during onboarding, under supervision, instead of during a full house.
This connects directly to the five steps of good onboarding this site already describes, and it goes beyond what the new-starter training plan tool offers by default: add one line to that plan — who the buddy is, and which language they share — and the rest of the plan works exactly as it already does.
Two weeks isn't arbitrary. That's roughly how long the core vocabulary from system 1 takes to bed in when it's repeated daily. After those two weeks, the buddy shifts from translator to colleague — not because the language gap is gone, but because the core vocabulary has bridged it by then.
How exposed is your shift?
This isn't a certified safety audit — it's a working rule of thumb combining three things: how wide the language gap is on an average shift, and which of the four systems are already in place. Enter your own numbers.
The score says nothing about how good your team is — non-native staff isn't the problem, unstructured communication is. It only says how much of that gap is still uncovered today.
Exposure score
Enter your own shift.
—
How it's calculated: base risk = (number of languages ÷ staff count) × 100, then every checked system lowers that figure by a fixed percentage, shown above. No hidden assumptions, no measured data from your venue — only what you type in.
A score of zero is rare and that's fine — the point isn't to reach zero, it's to know which system moves the needle first. Run the calculator again in two weeks and see if the number moves.
The four systems, side by side
What each system prevents, and which tool on this site sets it up.
| System | Prevents | Tool on this site |
|---|---|---|
| 1. Shared core vocabulary | a word nobody recognises at the moment it counts | Chef Abroad (250 words, 24 languages) |
| 2. Visual backup | a missed spoken instruction with no second signal | Kitchen station plan + allergen chart |
| 3. Closed-loop confirmation | an allergy or fire call that doesn't land | No tool needed — a two-second habit |
| 4. Bilingual buddy | two weeks of mistakes nobody notices | New-starter training plan + 5-step onboarding |
Four terms, briefly
- Core vocabulary
- The 40 to 50 words literally everyone on the shift recognises regardless of native language — not fluency, recognition of the essentials.
- Closed-loop confirmation
- An instruction is never confirmed with a nod — it is repeated back verbatim by whoever receives it, so an error becomes visible before it's too late.
- Language-gap risk
- The larger the share of your shift that speaks a different first language than the rest, the higher the chance an instruction loses something along the way.
- Bilingual buddy
- A colleague with enough shared language with a new starter to translate in the moment, structurally assigned for the first two weeks.
The point
A multilingual brigade isn't a problem you solve by having everyone learn the same language — that takes years, and most kitchens don't have that time. It's a risk you manage by building four systems, none of which require fluency: a small shared core vocabulary, a visual backup, a confirmation habit for what can hurt someone, and a structure for whoever is new.
None of the four costs a course or an extra headcount. They cost a few hours to set up and the discipline to keep them running on exactly the nights the temptation to drop them is greatest — because those are also the nights a missed word costs the most.
Start with the calculator above. Enter your own shift, see which system is missing, and add it this week. Not next quarter — this week, because the next busy Friday arrives faster than the next training session.