A supervisor sees a translated notice for the first time because a shift lead has forwarded it from a group message. The revised deadline is right in the employer’s English email, but the translation still tells workers to ask by the old date. The reviewer who checked the translation did a careful job. The file she saw was simply not the file people received. A reliable translation workflow begins before translation and ends after publication.
Separate the employer’s message from the program documents it references. A program name is not a substitute for naming the action, the date and the owner of the next step. Keep branded names intact where they identify a real source, but don’t imply that a translated employer summary is a new issuer document or that the provider offers a language you have not verified.
Before sending a draft, mark words that do real work
Start with a stable plain-language draft. “Ask HR by Tuesday at 3 p.m. local time if you need the instructions in another format” is easier to translate than “Before the close of the previous period, employees are encouraged to contact appropriate personnel.” Give the translator the complete date, including the time zone if work sites differ, and tell them which words must match a label on the page. Is “receive” about delivery of a physical card, the availability of instructions, or a wage payment? Resolve that in the original before it becomes three different terms in another language.
Make a short glossary with ambiguous terms, definitions, and examples, and flag any phrase that cannot move without specialist review. Negation, deadlines, instructions for getting support, and words that distinguish required from optional steps are worth checking individually. Wherever an issuer label appears in English only, provide that exact label and a translated explanation if it helps employees locate it. The translated words should not invite readers to search the interface for a label that isn’t there. Avoid adding a second description of the same action if it introduces a conflicting term.
Review meaning, then test the delivery
Ask a qualified language professional to check the translation in context, not just to approve a spreadsheet of isolated strings. Show the body, links, subject line, file name and any training caption that carries a direction. Have a separate reviewer tell you in their own words who acts, what they need to find, and by when. Make mismatches part of a tracked revision rather than patching the most visible snippet alone. Digital.gov’s multilingual publishing guidance recommends qualified human review when translation software is used. Its context is government publishing; here it is a practical model, not a claim about which rules apply to private employers.
A bilingual supervisor may catch an unnatural phrase, but should not be made responsible for interpreting important terms without appropriate qualifications, support and time. The pilot should also ask employees who use the target language whether they can find the right section and next step. Make the session voluntary and use a made-up notice. A comprehension exercise is a test of the document, not a test of the employee. Give participants a private route to point out issues without broadcasting their preferred language to a team.
Protect the handoff from close-but-different copies
Use a release register with the source version, translated version, language, reviewer, destination and release date. If you revise a deadline after another language was approved, mark that version stale until it has been updated and checked. Decide how to replace paper copies that have gone out already. Identify wall postings, break-room bins and shift packets; a change on the intranet does not replace physical copies. Print or export a new version with a clear revision date and test the link or phone hours on the real published copy.
Give web editions a language selector whose label users can understand before switching. Use correct page language metadata and describe language changes in mixed-language text where appropriate. W3C’s explanation of language of parts shows why language metadata matters to how some assistive tools speak a passage. Read from a narrow device as well. An accurate translation can still fail after export if a translated action wraps beneath a fixed-height button or the right-to-left layout scrambles punctuation. Make sure the help contact doesn’t disappear after switching.
Give people a route when a translation is not ready
Put a verified route for language help in the released notice and give that channel a named backup during planned absences. Decide how to provide timely assistance for a material change your normal process did not catch. Do not route important questions to an employee’s child or ask a colleague on a crowded floor to handle personal account details. Ask the right organization team how to handle specific requests and obligations.
Use the PDF export review for bilingual attachments and the media checklist for translated training. To check whether a request actually reaches someone in time, run the format handoff drill.