Oil & gas
Case Study: 130 SDS into Spanish in 10 Days
A Texas Gulf Coast refinery operator had 10 business days to put 130 Spanish safety data sheets in front of its crews before an OSHA audit. Our team delivered in 9, and the audit closed with zero linguistic findings.
Every hazard and precautionary statement matched the standardized phrasing under OSHA 29 CFR 1910.1200, verified code by code.
The client asked for 10 business days. All 130 SDS and 40 safety signs were in their hands on day 9, revised and QA-checked.
An ATA-certified English-to-Spanish translator with a mechanical engineering degree and 16 years in EHS documentation ran the team.
The client and the clock
The client is a refining and petrochemical operator on the Texas Gulf Coast, the kind of facility where a large share of the hourly workforce speaks Spanish as a first language. An OSHA audit was on the calendar. Under the Hazard Communication Standard, chemical hazard information has to be genuinely accessible to the people handling the chemicals, and the EHS team knew its Spanish-language coverage had gaps.
The scope they brought us: 130 safety data sheets covering process chemicals, additives, and maintenance products, plus 40 pieces of safety signage posted around the units. Everything had to be in Spanish, consistent with the English originals, and ready for review in 10 business days. Facilities like this one sit within our home region, which is one reason Houston-area technical translation has been part of our core work since 2011. It is also typical of what our oil and gas clients ask for: high stakes, fixed dates, no room for approximation.
The challenge: GHS consistency at speed
An SDS is a codified document. OSHA 29 CFR 1910.1200 aligns US hazard communication with the GHS system, which means hazard statements (H-codes) and precautionary statements (P-codes) carry standardized wording. "H225: Highly flammable liquid and vapour" cannot be paraphrased. Its Spanish rendering has to be the recognized standard phrase, identical on every one of the 130 sheets where it appears.
That is exactly where speed becomes dangerous. Split 130 sheets among several translators without preparation and each one will produce fluent, defensible Spanish, and the phrasing will drift from sheet to sheet. An auditor comparing two SDS for similar solvents notices that kind of drift immediately. The signage added a second consistency layer: a warning posted on a tank had to use the same words as section 2 of the SDS for the product inside it. This is why SDS translation is a discipline of its own rather than a volume job.
What we did
We assigned Miguel Ferrer as project lead. Miguel is ATA-certified for English into Spanish, holds a BS in Mechanical Engineering, and has spent 16 years translating for industrial machinery, oil and gas, and EHS clients. SDS and safety signage are two of his named specialties. Before that career he spent 4 years as a maintenance engineer in a bottling plant, so he has stood in front of the kind of signage he now translates.
The first move was to slow down in order to go fast. Before any of the 130 sheets went into translation, Miguel built and locked a GHS termbase: every H-code and P-code present in the corpus, mapped to its standardized Spanish statement, plus the recurring section headers and product-category terms. Only then did the volume work start, with 3 translators drawing on the locked termbase and a shared translation memory, and 1 independent reviser checking every sheet behind them.
The decision that made the deadline: locking the GHS termbase before translation began. It cost half a day up front. It removed every terminology debate from the following 8 days and made the automated H/P code checks meaningful, because there was exactly one approved rendering to check against.
On top of human revision, we ran automated QA passes on every file, screening the H-codes and P-codes against the termbase, and catching number, tag, and consistency issues that tired eyes miss on sheet 118 of 130. The 40 safety signs were translated last, pulling their wording directly from the finished SDS so that tank labels and data sheets spoke identical technical Spanish.
The result
All 130 safety data sheets and all 40 signs were delivered on day 9, one business day ahead of the deadline, each one translated, independently revised, and QA-checked. The EHS team had a full day for internal review they had not planned on having.
The audit took place as scheduled. It produced zero remarks on the Spanish-language hazard communication. Not a finding, not an observation. Shortly afterward, the client extended the program and asked us to translate its lockout/tagout procedures, the documents that govern how equipment is de-energized before maintenance. When an EHS manager hands you the LOTO procedures after an audit, that is the review that matters.
Key numbers
| Metric | Detail |
|---|---|
| Volume | 130 safety data sheets + 40 safety signs |
| Language pair | English to Spanish (US workforce) |
| Deadline | 10 business days quoted, delivered in 9 |
| Team | 3 translators + 1 independent reviser, led by Miguel Ferrer |
| Reference standard | GHS under OSHA 29 CFR 1910.1200, locked termbase for H/P statements |
| Deliverables | Formatted Spanish SDS, print-ready signage, GHS termbase |
| Outcome | Zero linguistic findings at the OSHA audit; follow-on LOTO project |
Facing a similar deadline?
If an audit date, an insurance requirement, or a new crew has put your Spanish SDS library on a countdown, send us the file list and the date. You will get an itemized quote within one business hour, and a straight answer on whether the timeline is achievable; request yours here.
Questions about this project
How did you keep 130 SDS consistent across three translators?
By removing the variables before work started. A locked GHS termbase gave all three translators one approved Spanish rendering for every H-code, P-code, and recurring header, and a shared translation memory propagated repeated passages in real time. The independent reviser and the automated code checks then verified compliance sheet by sheet, rather than debating word choices.
Could you handle a larger SDS library on a similar timeline?
Usually, yes. The method scales: the termbase preparation takes roughly the same time whether the library holds 130 sheets or 500, and we can widen the translator team because the locked terminology keeps everyone aligned. What we will always do first is check your deadline against the real volume and tell you honestly whether it holds.
Do you also translate the safety signage that goes with the SDS?
Yes, and preferably in the same project. On this engagement the 40 signs were translated after the data sheets, pulling wording straight from the finished SDS so a tank label and its corresponding sheet never disagree. Signage delivered separately, months apart, is where inconsistencies typically creep in.
Which variant of Spanish did the refinery crews receive?
US workplace Spanish, written to be immediately clear to a workforce with mostly Mexican and Central American roots. For standardized GHS statements the wording follows the recognized official phrasing, which does not vary by country. For headers, signage, and free text, Miguel's team chose vocabulary that reads naturally across regional backgrounds.