Engineering documents
Technical Specification Translation Services
We translate construction and procurement specifications with the same discipline their authors used to write them: every shall stays binding, every section number stays put, every referenced standard keeps its exact designation. Contractors, engineering firms, and owners across the United States rely on our specialized translators to move spec books between English, Spanish, French, German, and 40 other languages without changing what the documents require.
Our translators work inside the CSI MasterFormat 50-division structure daily. Section numbers, titles, and the General/Products/Execution layout survive translation intact.
Shall, should, may, and will each carry different contractual weight. We render them consistently so an enforceable requirement never softens into a suggestion.
We align spec terminology with the drawing set and schedules, so the term on Sheet A-201 matches the one in Section 08 41 13 word for word.
The Spec Is What the Arbitrator Reads
On a construction or industrial project, the technical specification is a contract document. When a dispute reaches mediation or arbitration, nobody argues about what the superintendent remembers saying. The parties argue about what Section 07 92 00 says about joint sealants, and the panel reads it line by line. Technical specification translation therefore carries a burden that most translation work never faces: the target text can be quoted against you in a claim, years after the project closed out.
We have watched this play out. A steel fabricator in Monterrey once brought us a Division 05 section it had bid using a free machine translation. The English source called for hot-dip galvanized connection assemblies; the Spanish version the estimating team read said the assemblies were to be painted. The difference was worth about $180,000 on a Houston distribution center, and the fabricator ate most of it. Fifteen years of translating spec books for projects like that one have taught us to treat every finish schedule, tolerance, and submittal requirement as money.
Complementary means binding. Widely used US contract forms, including AIA A201 and EJCDC C-700, treat drawings and specifications as complementary: what one requires binds the contractor as if both required it. A requirement that drifts during translation does not stop being enforceable. It just becomes a surprise.
That is why our process pairs a translator who knows construction with an independent reviser who checks the target text against the source clause by clause. Nothing is paraphrased. If the English says the contractor shall provide certified mill test reports for each heat, the Spanish says exactly that, with the same scope and the same actor.
CSI MasterFormat: The Skeleton of American Spec Books
Almost every commercial and institutional project in the United States organizes its specifications by CSI MasterFormat, the numbering system maintained by the Construction Specifications Institute and Construction Specifications Canada. The current edition runs to 50 divisions, from Division 01 General Requirements through Division 48 Electrical Power Generation, each broken into six-digit sections such as 09 91 23 Interior Painting. Within each section, CSI SectionFormat imposes a three-part structure: Part 1 General, Part 2 Products, Part 3 Execution.
A translator who has never seen this architecture will mangle it. Division and section numbers must never change, because submittal logs, RFIs, and schedules of values all key off them. Section titles follow conventions that a target-language reader in the US market expects to recognize. And the three-part structure dictates where information lives: warranty language belongs in Part 1, product data in Part 2, installation tolerances in Part 3. Our teams keep that skeleton intact whether we are translating a spec book into Spanish for field distribution or converting a foreign specification into MasterFormat-styled English for a US owner.
| Division | Scope | Frequent translation pitfall |
|---|---|---|
| 03 Concrete | Cast-in-place, precast, grouting | Confusing slump, strength class, and exposure class systems (ACI vs EN 206) |
| 05 Metals | Structural steel, decking, fabrications | Finish terms: galvanized, primed, painted, powder-coated rendered loosely |
| 08 Openings | Doors, frames, glazing, hardware | Hardware sets and keying schedules losing their internal cross-references |
| 23 HVAC | Ductwork, piping, equipment | SMACNA pressure classes and imperial duct gauges mistranslated as metric |
| 26 Electrical | Distribution, wiring, devices | NEC conductor sizes (AWG/kcmil) converted to square millimeters by mistake |
The pitfalls in that table are not hypothetical. Each one comes from a document we were asked to repair after a first translation went wrong.
Construction Specification Translation for Foreign Bidders on US Work
Foreign contractors and suppliers win a growing share of American infrastructure and industrial work, and the first obstacle is always the spec book. A Spanish contractor pursuing a transit package reads pliego de condiciones at home; a German equipment supplier is used to a Leistungsverzeichnis; a French engineering firm thinks in terms of a CCTP. None of these documents maps neatly onto MasterFormat, and the differences are structural, not cosmetic. A CCTP mixes prescriptive requirements with measurement rules that a US spec would push into Division 01 or the bid form.
Our job in these projects runs in both directions. We translate American spec books so estimators in Madrid or Monterrey price the real scope, and we translate foreign specifications into English that US reviewers can evaluate without a decoder ring. When a European source document cites measurement conventions or contract customs with no US equivalent, we flag them in translator notes instead of silently forcing them into an American mold. Owners tell us those notes save entire rounds of clarification questions. From our base in Texas we support bidders in every US state, and our construction translation services team includes former estimators and specifiers who have sat on both sides of a bid opening. For heavy civil packages, bridges, and water infrastructure, the reviewers come from our civil group; you can learn more here.
Prescriptive or Performance: Two Kinds of Specs, Two Translation Problems
Specifiers write in two modes. A prescriptive specification names the product, the method, and sometimes the manufacturer: install self-adhered membrane flashing, 40 mil nominal thickness, lapped 3 inches minimum. A performance specification states results and how they will be verified: the assembly shall achieve a maximum air leakage of 0.04 cfm/sf at 1.57 psf when tested per ASTM E2357.
Each mode fails differently in translation. Prescriptive text fails on nouns. Trade names, proprietary product designations, and material grades must be carried over untouched, and generic descriptors around them must match how the US market actually names things. Performance text fails on numbers and test conditions. A translator who rounds 0.04 to 0.05, or drops the test pressure, has quietly rewritten the acceptance criterion. Our rule is absolute: values, units, and test designations are checked twice, once by the translator and once by the independent reviser, against the source. International tenders increasingly favor performance specifications precisely because they travel across borders better, and we handle them alongside product specification translation for the procurement packages that accompany them.
Shall, Should, and May: The Grammar of Obligation
Specification English is a small, strict language. Shall creates a duty. Should recommends. May permits. Will typically describes what the owner or a third party is going to do. Some agencies, following the plain-language movement, now use must instead of shall; the Federal Highway Administration and several state DOTs have gone that way in their standard specifications. A competent technical specification translation keeps this system coherent in the target language, which is harder than it sounds because many languages express obligation through mood or context rather than a single modal verb.
In Spanish, for example, deberá, debe, and podrá have to be assigned once, project-wide, and used without drift. If shall becomes deberá in Section 03 30 00 and debería in Section 07 21 00, a subcontractor can argue that the second requirement was advisory. We lock these choices into a project glossary before translation starts, and the glossary follows the project through every addendum. The same discipline applies to defined terms. If the agreement defines Substantial Completion, the target text uses one equivalent, capitalized the same way, every single time it appears across a 900-page spec book.
Keeping the Specs and the Drawings in Step
A specification never travels alone. It interlocks with the drawing set through keynotes, schedules, and abbreviations, and translation has to respect the pairing. If the drawings label a component GWB and the translated spec calls it plasterboard while the translated general notes call it drywall, field crews will treat them as three different materials. We build one termbase per project and apply it to both document families, which is why clients frequently hand us the plans and the spec book together. The team translating engineering drawings and the team working the spec sections share that termbase in real time.
Order-of-precedence clauses raise the stakes. Many contracts state that specifications govern over drawings in case of conflict. Translate the spec loosely and you have not just introduced an error; you have introduced the governing error. Our revisers run a dedicated coordination pass on cross-references: every mention of a drawing sheet, detail number, schedule, or spec section in the translated text is verified against the actual document set. On a recent airport package that pass caught 14 references to a demolition section that had been renumbered in Addendum 2 but not in the body text of six other sections. We fixed the translation and flagged the source errors to the architect.
Referenced Standards: Cite Them, Never Improvise Them
Spec sections lean on standards in nearly every paragraph: ASTM A123 for galvanizing, ACI 318 for structural concrete, AWS D1.1 for structural welding, NFPA 70 for electrical work. These designations are never translated, expanded, or substituted. ASTM A123 stays ASTM A123 in Spanish, French, and Mandarin. What does get translated is the prose around the citation, and that prose has to use the standard's own vocabulary, because an auditor or inspector will read the translated spec next to the standard itself.
The dangerous moment comes when a foreign specification cites a norm with no American twin, or a rough equivalent that is not identical. EN 1090 is not AWS D1.1 with an accent. When we translate a European spec for a US owner, we keep the EN citation and add a translator note identifying the nearest US reference and the fact that they differ, so the engineer of record makes the substitution decision, not the translator. Clients who need whole normative documents in English, not just the specs that cite them, use our standard translation services, and the two workstreams share terminology so the spec and the translated standard never disagree with each other.
How Our Technical Specification Translation Process Works
A typical engagement starts with the documents in whatever shape the project produced them: Word files from the specifier, PDFs assembled for bid, sometimes InDesign for design-build proposals. We quote from an exact word count with repetitions discounted, because spec books repeat heavily; Part 1 boilerplate recurring across 200 sections should not be billed 200 times. You get an itemized quote within one business hour, and for bid-driven schedules we routinely split large books across a coordinated team working from a shared glossary. Tender-phase clients often pair this service with our support for translating RFP and tender packages, since the instructions to bidders and the technical sections need to speak the same language.
Every project follows our ISO 17100-compliant workflow: translation by a certified specialist with construction experience, full independent revision by a second linguist, and a final verification of numbering, cross-references, and formatting. Techniwords is a member of the American Translators Association and GALA, and for public bids we issue a signed certificate of accuracy that accompanies the translated documents. Field distribution is a common final step; many general contractors ask us to produce Spanish technical translation of the safety-critical sections for their crews. And when the specification is only one document among many on your project, the full catalog of document types we handle is on this page.
Two practical notes from long experience. First, send addenda as they issue; we translate deltas quickly and keep version control on our side, so your bidders always hold the current set. Second, tell us who reads the translation. A spec translated for an estimating team can carry translator notes and flagged ambiguities; a spec translated for contract execution must be clean, final, and signature-ready. The two are different deliverables, and knowing which one you need changes how we build it.
Technical Specification Translation: Frequent Questions
Do you keep the CSI MasterFormat numbering in translated specifications?
Yes, always. Division and section numbers, six-digit codes, and the Part 1/2/3 structure are preserved exactly, because submittal registers, RFIs, and payment applications reference them. We translate section titles using the conventions US readers expect, but the numbering itself never changes. When we translate a foreign specification that does not follow MasterFormat, we keep its native structure and can add a cross-reference table mapping its sections to the closest MasterFormat divisions if your reviewers want one.
Can you handle a full foreign spec book, like a French CCTP or a German Leistungsverzeichnis?
Yes. We regularly translate complete CCTPs, Leistungsverzeichnisse, and pliegos de condiciones into English for US owners, lenders, and design teams, including volumes of 500 pages and more. These documents organize information differently from American spec books, so we preserve the source structure, flag measurement rules and contract customs that have no US equivalent, and deliver translator notes your engineers can act on. Large volumes are split across a coordinated team sharing one glossary, with a single reviser ensuring consistency.
What happens when the drawings and the specifications conflict?
We translate what each document says and never harmonize conflicts silently, because order-of-precedence clauses make that a legal question for the design team, not the translator. What we do is detect conflicts. Our coordination pass checks every cross-reference between translated specs and drawings, and when we find a genuine contradiction in the source, we report it in a query log. Clients tell us this log regularly catches issues their own QA missed, especially after addenda renumber sections.
Can the translation be certified for a bid submission?
Yes. For public procurements and formal bid submissions we provide a signed certificate of accuracy on company letterhead, stating the translator qualifications and affirming that the translation is complete and faithful. This satisfies the certified translation requirements of US federal, state, and municipal agencies, and of most international tendering authorities. If the receiving agency requires notarization, we arrange it. Tell us the submission requirements when you request a quote so the certification wording matches exactly what the instructions to bidders demand.
How fast can you translate a specification package?
A single section of 3,000 to 5,000 words is typically delivered in two business days with full independent revision. A complete spec book of 150,000 to 300,000 words usually runs two to four weeks depending on language pair and how much repeated boilerplate the book contains. For bid deadlines we compress schedules by adding vetted translators under one terminology lead, and we prioritize the divisions your estimators need first. Send the table of contents and deadline, and we will build the schedule around your bid date.
Do you translate specifications into Spanish for field crews?
Frequently. General contractors and safety managers ask us to translate execution-critical sections, especially Divisions 01 through 09 and the safety requirements, into Spanish for superintendents and crews. We match the terminology to what tradespeople in the US actually use on site, which is often different from textbook Spanish, and we keep it consistent with any translated drawings, signage, and toolbox materials on the same project. Many clients start with the sections tied to their highest-risk scopes and expand from there.
Send Us Your Spec Book Before the Bid Clock Runs Out
Share your table of contents, language pair, and bid date. Within one business hour you will have an itemized quote, a proposed schedule division by division, and the name of the terminology lead who will keep 300 sections speaking with one voice.
Get a Free Quote