A compliant REACH safety data sheet translation is never just a word-for-word job. It has to be a translation plus a technical and legal revision, checked against Annex II to REACH and the updates in Commission Regulation 2020/878. That means swapping in local exposure limits, emergency numbers and waste codes, not just converting words. Skip the technical check and you don’t have a safety data sheet. You have a nicely worded liability risk.

What Annex II actually demands from your SDS

Annex II exists to keep safety data sheets consistent across the EU, so a worker in Bratislava gets the same protection information as one in Berlin. It sets out 16 sections, from hazard identification through to “other information”, and every one of them has to appear in the right order with the right headings.

Here’s the bit people miss: translating the words in those 16 sections isn’t the same as making them correct for the market you’re selling into. Some sections need genuinely local content, not just local language.

• Section 1 needs the correct local supplier or importer details, not a carried-over address from the source document.
• Section 2 has to carry classification and hazard statements that match the destination country’s enforcement practice.
• Section 8 needs national occupational exposure limits, which vary by member state and don’t translate, they get replaced.
• Section 16 must list the full, untranslated text of every H and P code referenced earlier, in the target language.
• Exposure scenarios and the CSR (where they apply) need the same local labelling text and waste classification codes as the rest of the document.

Get any of these wrong and the SDS reads fine but tells the wrong story. That’s the gap a proper technical revision is there to close.

Why translation alone won’t make it compliant

Here’s the part nobody wants to hear: translating an SDS doesn’t hand off your legal responsibility. Under REACH, the supplier placing the substance or mixture on the market stays on the hook for what the SDS says, in every language it’s published in. A translation agency can produce a technically flawless document, but if the underlying data is wrong, that’s still your problem.

So what goes wrong most often? Three things, over and over:

1. Hazard and precautionary statements get left in English in Section 16, when they need to appear in full, in the target language.
2. Exposure limits get copied straight across instead of being swapped for the destination country’s own occupational limits.
3. Emergency contact numbers and national poison centre details go missing, often because nobody asked the client for them.

National guidance confirms SDS must be provided in the official language of the member state where the product is placed on the market, and that some sections demand country-specific data that a translator simply won’t have without being told. That’s exactly why a technical revision, someone checking classification codes, hazard phrases and local figures against current rules, matters as much as the language work itself.

When you need to update your SDS, and how long it takes

Your SDS isn’t a one-and-done document. It needs updating the moment any of these happen:

• New information surfaces about a hazard, even if it doesn’t change the classification.
• A new risk-management measure becomes available or relevant.
• An authorisation is granted or refused, or a restriction kicks in.
• The classification of the substance or mixture changes.

National guidance is clear that these updates have to happen without delay, so build that into your planning rather than treating it as an afterthought.

For timelines: a straight translation of a standard SDS usually moves faster than one that also needs a technical revision, since the revision stage involves checking classification data and sourcing local figures. Build in extra time for anything with exposure scenarios attached.

Pro Tip: Keep a version log with dates and trigger reasons for every SDS update. It saves hours when an inspector or a client asks why a document changed.

How a specialist workflow handles REACH SDS translation

A proper SDS job isn’t one person bashing it out in an afternoon. It runs in stages, and each stage catches something the last one couldn’t.

• Intake and terminology check: the source SDS, glossary and any existing reference material get reviewed before translation starts.
• Translation by a subject-matter linguist: someone who knows chemical and regulatory terminology, not a generalist.
• Regulatory technical revision: classification, hazard codes and local data (exposure limits, emergency numbers, waste codes) get checked against current rules.
• Quality assurance pass: a second set of eyes checks formatting, section order and consistency against Annex II.
• Delivery with version tracking: so you’ve got a clean record of what changed and when.

For this kind of compliance-sensitive text, services like HumanLegal and HumanPro are built around exactly this layered approach, pairing linguistic accuracy with the kind of scrutiny regulatory documents need. HumanPlus sits alongside them for projects that need an extra editorial layer. None of these are a single-step “translate and send” job, and for an SDS, that’s precisely the point.

What to send your translator before the project starts

Want this to go smoothly? Hand over the right files upfront. Here’s what to prepare:

1. The original SDS in its most current, approved version.
2. The UFI (Unique Formula Identifier), if your product has one.
3. Any CSR or exposure scenario documents linked to the substance.
4. Current labels and product identifiers used in your target market.
5. Classification data and supporting safety data used to reach it.
6. A glossary of preferred terminology, if you have one from past translations.

On formats: editable source files (Word, XML, InDesign) move faster through the workflow than scanned PDFs, which need extra conversion steps before anyone can even start translating.

Pro Tip: Ask any provider upfront who signs off on the technical revision, what their update turnaround looks like, and how they handle confidential formulation data. Those three questions tell you more than any sales pitch will.

Speed matters, but not more than getting it right

Here’s our honest take: everyone wants their SDS translated yesterday, especially when an authorisation deadline is looming. Fair enough. But a fast SDS with the wrong exposure limit or a missing emergency number isn’t fast, it’s a liability sitting in a nicely formatted document.

The smarter move is setting up a standing relationship with a provider who already knows your product range and your glossary, so repeat updates (and you will have repeat updates) move quickly because the groundwork’s already done. Accuracy first, speed by design, not by shortcut.

— glocco®

How we handle REACH SDS translation at glocco®

We treat safety data sheet translation as what it actually is: a compliance job wearing a linguistic hat. That’s why our workflow pairs subject-matter translation with proper technical revision, so the document that lands in your inbox is ready for the market you’re selling into, not just readable in that language.

For SDS and other regulated content, HumanLegal handles the compliance-heavy end of things, while HumanPro covers high-accuracy technical translation with review built in. Both pair naturally with the kind of localisation workflow we use across regulated sectors, which you can read more about in our breakdown of cutting errors across EU localisation projects.

Got an SDS that needs translating, updating or revising? Pull together the checklist items above and get in touch for a quote.

FAQ

What makes a safety data sheet REACH-compliant?

A REACH-compliant SDS follows the 16-section structure set out in Annex II, as amended by Commission Regulation 2020/878, and includes accurate, locally relevant data in sections like exposure limits and emergency contacts. It must also be provided in the official language of the member state where the product is placed on the market.

Is a literal translation enough for an SDS?

No. A literal translation covers the language but misses country-specific data like national exposure limits, waste codes and emergency contact numbers, which need to be sourced and inserted, not translated. A technical revision checks that this local data is correct alongside the language itself.

Who is legally responsible for SDS accuracy after translation?

The supplier placing the substance or mixture on the market remains responsible for the content of the SDS in every language version. Translating the document doesn’t transfer that responsibility to the translation provider.

How often does an SDS need updating?

An SDS needs updating without delay whenever new hazard information emerges, a new risk-management measure becomes available, or an authorisation or restriction decision affects the substance, according to national guidance. A classification change also triggers an immediate update.

What should I send a provider before requesting an SDS translation?

Send the current SDS version, the UFI if one exists, any CSR or exposure scenario documents, current product labels, and classification data. Editable source files move through the process faster than scanned PDFs.

Sources

• Annex II to Regulation (EC) No 1907/2006 (REACH)
• Karta bezpečnostných údajov | Zdroje informácií | REACH (national ministry guidance)

Recommended

• Audit Ready Security Protocol Translation for Procurement Managers
• Avoid ŠÚKL Delays: PV Document Translation for Slovak Procurement
• Pass MDR/IVDR audits: five stage IFU translation for regulatory teams
• Five Stage SmPC Translation Workflow Slovak Teams Use to Avoid Rework