A safety data sheet landed on my desk last week with 84 hazard and precautionary statements, and my first job wasn't to translate a single one of them. It was to figure out which ones I was even allowed to touch.
That sounds backwards. It isn't. The best thing a specialist can do with certain sentences is refuse to be creative with them.
The phrases that come with a serial number
If you've done SDS work, you know the ones I mean. "Keep away from heat, hot surfaces, sparks, open flames and other ignition sources. No smoking." "Causes serious eye damage." "IF SWALLOWED: Immediately call a POISON CENTER or doctor." These aren't prose. Under the GHS — the system most of the world's chemical labeling runs on, folded into the EU's CLP regulation — every one of those carries a code. H-codes for hazards, P-codes for precautions. H318. P210. P305+P351+P338.
The point of the code is that the sentence is fixed. Regulators publish the official wording in each of their official languages. You don't write "causes severe eye injury" because it reads a little smoother. If the code is H318, the approved text is the approved text, comma placement and all. An SDS reviewer, or worse, an inspector, will check your rendering against the official table. Get clever and you've introduced a discrepancy in a document whose entire job is to be identical across borders.
So the workflow flips. On a normal technical file I read the source and produce the target. On these, I read the source, read off the H- or P-code, and go pull the sanctioned wording from the reference list. The translation already exists. My job is retrieval and matching, not composition. The skill is spotting a coded statement hiding inside a paragraph of free text a supplier stuffed together, and not "improving" it.
Miss that distinction and you'll spend an hour polishing a sentence that was never yours, and you'll be wrong for your trouble.
And when your language never got the memo
Here's where it stops being tidy. GHS has official tables in the big languages. Turkmen isn't one of them. There is no state-published, regulator-blessed list of H- and P-statements in Turkmen that I can retrieve and drop in with a clear conscience.
So what do I actually do? I stop pretending the problem doesn't exist and I tell the PM. Because a client asking for "the SDS in Turkmen" usually thinks they're asking for the same deterministic thing they'd get in German — pull the official phrase, done. They're not. In Turkmen I'm authoring the safety statement, not quoting it. That's a different level of liability and it should be a different conversation.
My rule: translate the coded statements myself, but keep them absolutely consistent across the whole document and across every document I do for that client. If H318 becomes a particular Turkmen sentence, it stays that sentence forever — locked in a termbase, flagged as regulated, never paraphrased. I'll often keep the code visible in a comment or even in the delivered file if the format allows, so the next person can verify what I mapped to what. And I hand back a note saying, plainly: these renderings are mine, there's no official Turkmen GHS table, here's the source I aligned to. Now the risk is where it belongs — visible, with the people who can accept or reject it.
The alternative is that three translators over three years produce three different Turkmen wordings for "causes serious eye damage" and nobody notices until a worker reads one that's softer than it should be.
The register trap underneath all of it
Separate from the coded phrases, oil & gas safety text has a register problem that catches people who are excellent at, say, marketing. Corporate English hedges. "Personnel should ensure appropriate measures are considered where practicable." A warning label can't afford that mush. When the instruction matters — lockout before service, no smoking, evacuate — the target has to land as a command, blunt, no cushioning.
English blurs shall, should, and must until they're nearly interchangeable in a tired writer's hands. In a Permit to Work procedure they are not interchangeable. One is an obligation, one is a recommendation, one is a hedge. I nail down which is which before I write a word of target, and if the source is genuinely ambiguous, that's a query, not a guess. Guessing here isn't a style choice. It's the gap between "you must" and "you might want to" standing between someone and a live line.
The smoothest sentence in a safety document is often the most dangerous one — because smooth usually means someone softened an order into a suggestion. My job is to keep it hard.
Know which sentences you're forbidden to invent, know which language never handed you the official version, and know when a polite verb is quietly lying about how serious it is. That's most of the job. The words are the easy part.