Translating SOPs and Checklists for the Crew
Why this matters
A translated SOP that nobody field-tested is a document that looks like a safety program and works like a guess. The common pattern is that an owner hands the chemical-handling checklist to the one bilingual tech, who translates it on a Sunday, unpaid, and the Spanish copy goes in the truck. A year later the English copy has been revised twice and the Spanish one never, so half the crew is following a procedure the shop retired. The fix is not a better translator. It is a process: make the English worth translating, translate it with the right level of care, prove it works with the people who will use it, and change both languages together forever after.
The running case below follows one document through every step: a pool service shop with six techs, three of whom work primarily in Spanish, translating its procedure for adding chlorine and acid at a residential pool.
Step 1: Decide what gets translated, hazard-bearing documents first
List every document the field crew actually executes: SOPs, checklists, job-closeout forms, the vehicle inspection card. Rank them by the harm a misreading could cause, and translate from the top down. Office-only documents wait.
Case: the shop counts 22 documents. Seven are used in the field, and three of those involve a hazard: chemical handling, the pump-room electrical isolation card, and ladder use for screen enclosures. Those three go first; the other four follow once the process is proven on the first.
What breaks if you skip it: translating everything at once spreads the effort evenly across documents whose risk is not even, and the chemical SOP waits in the queue behind the uniform policy.
Step 2: Fix the English before anyone translates it
Most SOPs are written in a dense shop English that loses information in translation: long sentences, two actions per step, idioms, pronouns that point back three lines. Rewrite in plain English first:
- one action per step, in the order it is done;
- the safe action in positive form ("keep the lid closed"), with the prohibition said separately and flatly;
- every number with its unit spelled out;
- each thing called by one name, every time;
- no idioms ("top it off", "eyeball it", "hit it with acid").
Case: the original chemical SOP ran 9 steps and 410 words, averaging about 24 words a sentence, with several steps doing two things ("open the acid and add it slowly to a bucket of pool water, then walk it around the deep end"). The rewrite runs 12 steps and 260 words, averaging about 11 words a sentence. The steps went up because each now does one thing; the words went down by 150, about 37 percent of the original 410.
Why it is worth the hour: translation is usually priced by the word, so the rewrite cut the translation bill by about the same 37 percent. More important, the English-speaking techs now have a clearer SOP too. A translation can only be as clear as its source, and a confusing source produces a confidently confusing translation.
Step 3: Freeze the terms before translation starts
Hand the translator a short list of the trade terms in the document, each with the word your crew actually uses for it. Without the list, the translator picks the textbook term, which may not be the one your techs say. Building and maintaining that list is its own job; see related: Building a Two-Language Shop Glossary.
Case: the list has nine entries, including "muriatic acid", "liquid chlorine", "test kit", "skimmer" and "pump basket".
Step 4: Choose the level of care to match the document
Two routes, and the document decides which:
- Professional translation for anything hazard-bearing, anything a regulator might read, and anything legally significant. Give the translator the glossary, the plain-English source, and one paragraph explaining who uses the document and where. Ask whether they have trade or technical experience in your field; a general translator with no technical background is where flare nuts become flames.
- Careful in-house translation for low-risk documents (a parts-pickup checklist, a truck-stocking list), done by a bilingual employee on paid time, then read by a second bilingual person who did not do the translation. If the only bilingual person available is the translator, the field test in Step 5 becomes the second reader.
Do not use a pasted machine translation as the translation of record for any document in the first category. Where it breaks and why is covered elsewhere; see related: Machine Translation on the Job: Where It Breaks.
Case: the chemical SOP goes to a professional translator with the nine-term glossary. The shop's own bilingual lead reviews the result before Step 5.
Note on chemical documents: a translated SOP does not replace the safety data sheet or the container label. Under the federal Hazard Communication Standard, 29 CFR 1910.1200, the safety data sheet and the shipped label must be in English, and an employer may add or keep copies in other languages alongside them. The SOP tells the crew how your shop does the job; the SDS and label stay what they are.
Step 5: Field test it with the people who will use it
Give the translated document to two crew members who work in that language and did not see the draft. Have each walk through the procedure with it, step by step, saying aloud what they would do, while someone who knows the procedure watches. Then ask each, without the document, what the two steps they would never skip are.
Run it dry. A field test of a hazardous procedure never handles the live hazard. For chemical handling, walk through with empty, clearly marked containers or containers of plain water, at the shop, not at a customer's pool. Nobody pours real acid or chlorine to test a document.
Case: the walk-through finds two problems the translator and reviewer both missed.
- The translation used the correct technical term for muriatic acid ("acido clorhidrico"), but both techs know it from the jug and the supply house as "acido muriatico". One tech paused and asked whether it was a different product. The glossary gets a correction: print the crew's word, with the technical term in parentheses.
- The SOP's step 7 said, in plain Spanish, to add the acid to a bucket of water. One tech, from a different country than the translator, read the word used for bucket as a different, smaller container. Harmless here, but it shows a regional word choice. The step now names the container by its use: "the acid bucket, marked with red tape".
The critical step, never mixing chlorine and acid in the same bucket or adding them at the same spot in the pool, was understood correctly by both and said back unprompted as one of their two. That is the result the test exists to confirm. Hazard if misread: chlorine and acid combined release chlorine gas, which is why the step is written as its own line with no other action in it.
What breaks if you skip it: the shop only learns about the muriatic-acid pause when a tech skips the step because he thinks he does not have that product on the truck.
Step 6: Release both languages under one version number
From the moment both versions exist, they are one document in two languages, and they change together. Put a control header on both, give them the same document ID and the same version number, and keep a change log.
DOC CHEM-02 Adding chlorine and acid
EN v3.1 approved 04-02 R. Ortega
ES v3.1 approved 04-04 translator + 2 techs
CHANGE LOG
v3.1 Step 6 reworded: acid and chlorine go in
on separate trips around the pool
EN 04-02 ES 04-04
ES v3.0 pulled 04-02, change briefed
in Spanish at the 04-02 huddle
v3.0 Plain-language rewrite, 9 -> 12 steps
RULE A copy whose version does not match the
EN version comes out of the truck.
The rule at the bottom is the one that matters. An English edit to a safety step immediately pulls the old Spanish copy, and the change is briefed out loud in Spanish the same day, so nobody works from a stale page during the gap. A reasonable default is two working days to translate a safety change and ten for anything else; tune it to how fast your translator turns work around.
What breaks if you skip it: the drift described at the top of this article. Nobody decides to let the Spanish copy go stale; it happens because the English edit takes two minutes and nobody owns the second language.
Step 7: Re-test on a schedule and after every incident
Put each translated hazard document on an annual review, and re-run the Step 5 walk-through whenever a near miss involves that procedure, a new hire who works in that language joins, or the procedure changes more than one step at once.
Case: the first annual review is set for the following April. Two months in, a new tech from a third Spanish-speaking country joins, and the walk-through is run with him during his first week; it turns up one more regional word, which goes into the glossary.
What changes the approach
More than two languages. A shop with crew working in Spanish and Portuguese, or Spanish and Haitian Creole, multiplies the translation and the version control. Plain English and the glossary matter even more, because every confusing source sentence is now confusing twice. Pictures and photos of the actual equipment carry across all languages at once; see related: Safety Signs, Labels and Pictograms Across Languages.
Low literacy in any language. A worker who reads little in their first language gains nothing from a translated page. The procedure is then taught by demonstration and checked by demonstration, and the written copy serves the supervisor. Required training has its own rule about language and vocabulary; see related: Safety Training in a Language the Crew Understands.
A manufacturer already publishes the document in Spanish. Use it for the manufacturer's part, but do not assume it matches your shop's procedure, and it still goes through your field test.
References
- 29 CFR 1910.1200, Hazard Communication Standard (labeling and safety data sheet language provisions)
- See related: Building a Two-Language Shop Glossary
- See related: Machine Translation on the Job: Where It Breaks
- See related: Safety Training in a Language the Crew Understands
- See related: The Two-Language Work Order SOP