A kitchen in Dubai, Riyadh or Beirut is one of the most multilingual workplaces on earth. In a single shift you might have a Lebanese manager, an Egyptian chef, Indian and Nepali cooks, Filipino front-of-house staff, a Saudi or Emirati trainee and a Sudanese steward. The working language is “English”, in the sense that the manual is in English and everybody speaks some. The real language of instruction is whatever the person next to you speaks, which is why the same procedure is done four different ways on the same line.
Standard operating procedures written for this workforce have to work for people who read English well, people who read Arabic well, people who read neither well, and people who read both but think in a third language. This article covers how to write and present SOPs for that reality. It is the practical companion to our guide to standard operating procedures and how to write an SOP.
Why “just translate it” fails
Operators who recognise the problem usually produce two documents: the English manual and an Arabic translation. Both are then filed and neither is used, for four reasons:
- Two documents drift apart. The English version is updated; the Arabic is not. Within a year they describe different procedures.
- Translation preserves the prose problem. A three-page English procedure becomes a three-page Arabic procedure. Neither is read at 06:30.
- A third of the team reads neither. Hindi, Urdu, Malayalam, Tagalog, Nepali, Amharic. Translating into all of them is not realistic and not necessary.
- Vocabulary is not shared. “Sanitise”, “blanch”, “face up”, “86” mean nothing until defined, in any language.
The fix is not better translation. It is a different format.
Principle 1: One SOP, two languages, side by side
Keep a single master SOP in which every step appears in English and Arabic together, in the same numbered line or in two adjacent columns. The step is one unit; it is impossible to update one language without seeing the other. Where a term has a specific meaning in your operation, define it once at the top in both languages.
4. Probe one chilled item per category. Standard: 0–5°C.
اقرأ حرارة صنف واحد من كل فئة مبرّدة. المعيار: 0–5°م.
This also makes the SOP usable as a training device: a Nepali cook who is learning both languages sees them paired, step by step, every shift.
Principle 2: The photo is the standard
For anything visual, a picture does the work no translation can: how the shelf should look when faced, where the probe goes, what “clean” means on a grill, how the bag is packed, how the bed is made. One photo per visual step, taken in your own kitchen or store, with the standard circled or marked where helpful.
Photo standards are the only part of an SOP that is genuinely language-independent. Use them generously. Our articles on retail store SOPs and hotel housekeeping SOPs show how far photo standards can carry a procedure.
Principle 3: Numbers and symbols before words
A temperature range, a time limit, a count, a tick or a cross cross every language barrier. Write standards as numbers wherever possible and put them at the step, not in a separate section:
- “0–5°C” rather than “within the safe chilled range”
- “15 min” rather than “promptly”
- “200 ppm” rather than “correct concentration”
- “2 people sign” rather than “dual control”
A digital task enforces this naturally: a numeric field with a valid range is the same in every language and flags an out-of-range reading without anyone reading a sentence.
Principle 4: Controlled vocabulary
Pick one word for each thing and use it everywhere, in both languages. “Walk-in” is always “walk-in” and always the same Arabic term; it is never “the big fridge” in step 3 and “cold room” in step 7. Keep a short glossary of operational terms in English and Arabic (and informally in the other languages your team speaks, which the team will produce for you if you ask). Thirty terms cover most of a restaurant’s procedures.
Avoid idiom, phrasal verbs and abbreviations that are not on the glossary. “Make sure to go over the pass before you head off” is four comprehension problems in one sentence. “Clean the pass before leaving” is one step.
Principle 5: Imperative, short, one action
Write each step as a short command: verb, object, standard. One action per step. Under ten words where possible. This is good practice in any language and it is essential when the reader is working in their second or third. It also makes the Arabic shorter and clearer; long English sentences translate into longer Arabic ones.
Principle 6: Video with subtitles
A 60–90 second video of your best operator doing the task, filmed on your equipment, subtitled in English and Arabic, is the single most effective training asset for a mixed-nationality team. It needs almost no reading ability, it shows the standard, and it is watched repeatedly in a way a document never is. Attach it to the task so it opens at the moment of doing. See how to train staff on SOPs and prove compliance.
Principle 7: Test with the people who will use it
Hand the draft to a team member whose first language is neither English nor Arabic and watch them do the task from it. Every hesitation is a missing photo, an undefined term or a step that needs splitting. Then do the same with an Arabic-first reader and an English-first reader. Three rounds of this produce an SOP that works for the whole team, and it usually ends up shorter than the draft.
Ask the team to help with the glossary and the videos. People who contribute to a procedure follow it.
Arabic-specific notes
- Right-to-left layout. In a side-by-side format, the Arabic column sits on the right. In a digital task, make sure the interface supports RTL properly, including numbers and mixed-direction text like “0–5°C”.
- Dialect. Written Modern Standard Arabic is understood across the region, but operational terms differ between Levantine, Egyptian and Gulf usage. Pick the terms your team uses and put them in the glossary.
- Numerals. Decide whether to use Western (0–9) or Eastern Arabic (٠–٩) numerals and be consistent. Most Gulf operations use Western numerals for temperatures and times.
- Names of equipment and brands are usually kept in English letters inside Arabic text. That is fine; consistency matters more than purity.
Beyond Arabic and English
You cannot translate into every language on the team, and you do not need to. The combination of side-by-side Arabic–English, photos for every visual standard, numbers for every limit, a controlled glossary and a subtitled video reaches almost everyone. For the remaining gap, pair new hires with a buddy who shares their language for the first week, and use the SOP’s photos and video as the shared reference.
What this looks like in a system
The format above is awkward on paper: side-by-side text, photos per step, a video, a glossary. It is natural in a digital SOP:
- The master SOP, bilingual, with photos and the video, lives in a role-based library. In Opscale that is the operations library.
- The task version, with the bilingual step text, the photo and the numeric limit at each step, appears on the right phone at the right time through tasks and checklists. Opscale’s interface runs in Arabic and English with full right-to-left support.
- The AI checklist creator drafts the structured procedure from a description or an existing form in either language, so you start from a bilingual skeleton rather than a blank page.
- Completion, exceptions and inspection scores by branch are the same numbers regardless of what language the team reads; see restaurant SOPs: the twelve every branch needs for the set most groups start with.
Opscale was built in Beirut for teams exactly like this, and runs today for operators across Lebanon, Saudi Arabia and the UAE.
The team does not share a first language. It can share a procedure, if the procedure is written for the team rather than for the office.