Architecture Translation Services: Drawings, Specs, and BIM

Architecture crosses borders; its documents have to follow

American architecture has never been more international in both directions. US firms design towers in Riyadh, museums in Paris, and campuses in Monterrey, while European and Latin American practices win work on US soil through competitions, joint ventures, and developer relationships. Every one of these projects produces a bilingual document problem: the design was conceived in one language, the authorities and contractors read another, and the model sits in the middle holding both.

Architecture translation services have to cover an unusual range. On one desk sits a poetic competition narrative that must persuade a jury; on the next, a door hardware schedule where a mistranslated "cerradura antipánico" could fail a code review. Techniwords has translated for architecture and design teams for 15 years, and we staff both registers: linguists who can carry a design argument, and technical translators who know that a lintel is not a beam and a mullion is not a muntin. The two skills rarely live in the same person, so our teams pair them.

Translating in a BIM world: Revit parameters, families, and schedules

The drawing set stopped being the master document years ago. On a BIM mandate, the Revit model is the source of truth, and the translatable text lives in dozens of places most translation vendors never find: type and instance parameters, family and type names, room and space names, view titles, sheet names, keynotes, text notes, and the schedules that turn parameters into deliverables. Translating the printed PDF while leaving the model in the source language creates a fork that gets worse with every revision.

Our approach starts in the model, not the print. We export translatable content through schedules and DB Link or Dynamo-based extraction, translate it in a CAT environment where the terminology stays consistent, then return it in a structure your BIM manager can reimport. Family naming conventions are agreed up front, since "Puerta_Cortafuegos_90" and "Door_Fire_Rated_90" must map one-to-one for filters, view templates, and COBie exports to keep working. Where a client prefers hands-off delivery, our team works directly in a copy of the model under the supervision of the BIM coordinator. Either way, the geometry is never touched; only the words move.

IFC, openBIM, and multilingual data exchange

When a French practice models in ArchiCAD, the structural engineer works in Tekla, and the US contractor coordinates in Navisworks, the project speaks IFC. The buildingSMART schema gives every element a standardized class, but the human-readable content, property set values, material names, classification descriptions, and space labels, arrives in whatever language the authoring team used. A US estimator opening a European IFC file meets "Cloison de doublage" and "Trémie d'ascenseur" with no idea which quantities to price.

We translate IFC content at the data level, working on the property sets and name attributes rather than on screenshots or exported lists that cannot be reimported. Classification mappings get special care: if the source model is organized under Uniclass or a national system, we align descriptions with the US taxonomy the client uses, typically MasterFormat or OmniClass, and document the mapping so the model remains auditable. The same logic extends to CAD file translation for the 2D world that still surrounds every BIM project: DWG title blocks, layer naming, xref-heavy detail libraries, and the annotation buried in blocks. For sheet-based deliverables, our team handles translating annotated engineering drawings so notes, callouts, and revision clouds read correctly without shifting a single line of geometry.

Specifications and the discipline of MasterFormat

The project manual is where architectural intent becomes enforceable language. US specifications follow CSI MasterFormat's 50 divisions and the three-part SectionFormat structure, and foreign teams joining a US project must produce or consume specs in that idiom. The reverse is just as common: a US practice designing abroad needs its sections rendered into Spanish or French while keeping the numbering intact, because the general contractor's procurement team sorts bids by section number regardless of language.

Specification translation is mostly a war against drift. "Provide," "furnish," and "install" have distinct contractual meanings in US spec writing; a translation that collapses them into one verb quietly rewrites the contract. Our spec teams translate against a locked glossary of these operative verbs, keep article and paragraph numbering byte-identical to the source, and preserve every reference standard citation, ASTM E119, ANSI/BHMA A156.1, UL 10C, exactly as published. When you need full spec books translated, we deliver them in your office template with styles, headers, and tables of contents rebuilt, ready for the next addendum cycle rather than frozen as a one-time PDF.

LEED, WELL, and sustainability documentation across borders

LEED has certified projects in more than 180 countries, and the documentation stream runs through English at GBCI review. For international teams pursuing LEED on US projects, or US firms shepherding foreign projects through certification, that means translating product documentation, commissioning records, and policy documents into reviewer-ready English: EPDs and HPDs issued in German, cleaning policies drafted in Spanish, energy models annotated in French. WELL adds occupant-facing material that must read naturally in the building's own languages, since a wellness policy no one understands earns no points at audit.

The technical trap in sustainability translation is the credit language itself. Terms like "regularly occupied space," "previously developed site," and "demand response" carry precise USGBC definitions, and a casual synonym can turn a compliant narrative into a clarification request that costs a review cycle. We maintain a LEED v4.1 bilingual termbase in Spanish, French, and German, refined across dozens of submittals, and we translate manufacturer sustainability claims conservatively so the design team never certifies more than the source document actually says.

Scales, units, and sheet sizes: the quiet conversion problems

Some of the most expensive mistakes in international practice have nothing to do with vocabulary. US drawings are dimensioned in feet and inches at architectural scales like 1/8" = 1'-0"; the rest of the world draws in millimeters at 1:100. US offices plot on ANSI D or Arch D sheets; European partners expect ISO A1. A detail redrawn without care can end up at a scale no one's ruler matches, and a "2x4" translated literally becomes a 50 x 100 mm member that does not exist at a US lumberyard, since the actual section is 1-1/2 x 3-1/2 inches.

Our deliverables handle this explicitly rather than silently:

• Dimensions are never converted unless the client instructs it; when conversion is requested, we follow the project's rounding rules and flag every nominal-versus-actual case, such as lumber sizes, pipe diameters, and drywall thicknesses.
• Scale statements are restated for the target convention, with graphic scales recommended whenever sheets may be reprinted at a different size.
• Sheet size mapping (Arch D to A1, for instance) is documented in the delivery note so the print shop and the BIM manager stay aligned.
• Level references are checked against datum conventions, because a European "+3.50" story height and a US "EL. 111'-6"" describe the same slab differently.

Competitions, RFPs, and material libraries

International design competitions compress everything about this sector into two brutal weeks. A practice in Barcelona or Lyon entering a US competition must deliver boards, a design narrative, team qualifications, and compliance forms in flawless American English by a date that does not move. We have supported entries in both directions, translating jury-facing prose with a design-literate editor while a second translator clears the forms and certifications; our detailed guide to tender translation explains how we structure those sprints. The same machinery serves developer RFPs and university design-build shortlists, where qualifications packages recycle project sheets that we keep aligned in a bilingual library so each pursuit starts from polished text instead of from zero.

Between pursuits, the steady work is the material world architects specify from. European and Latin American manufacturers courting US specifiers need their finishes, systems, and furniture collections presented in specifier-ready English, and our product catalog translation for building materials keeps performance claims tied to the correct test standards while the marketing voice survives the crossing. Binder tabs, BIM object descriptions, and cut sheets all flow through the same termbase, so the object an architect drags into the model matches the catalog page the rep left behind.

Spanish, French, and German: where the work concentrates

Three languages dominate our architecture desk. Spanish leads on volume, driven by US-Latin American practice in both directions: Mexican and Spanish firms on US projects, US developers building in Mexico City and Bogotá, and jobsite documentation for Spanish-speaking construction crews, a need we cover jointly with our construction translation team. The regional split inside Spanish matters in architecture as much as anywhere; we cast translators by target country, and our Spanish technical translation group includes specifiers familiar with both peninsular and Latin American building vocabulary.

French follows, anchored by competitions, museum and cultural work, and Quebec projects where the Charter of the French Language makes documentation bilingual by law. Our French technical translation team handles both the Parisian design register and Quebec's construction terminology, which differ more than clients expect. German rounds out the trio through passive house and mass timber expertise flowing into US practice, along with fittings, facades, and door hardware from German-speaking manufacturers; learn more here about our German capabilities. Our process on all three follows ISO 17100, with independent revision on every deliverable, and as an ATA and GALA member firm we assign only translators with verified subject-matter credentials in architecture and construction.

What an architecture translation project looks like here

A recent engagement is representative. A German practice, shortlisted with a US architect of record for a university building in Texas, needed its design development package moved into English: a Revit model with German parameters, 140 sheets, a 490-page outline specification, and a sustainability narrative, in four weeks. We began with a two-day terminology sprint, agreeing on the family naming convention and the operative verbs with the AOR's spec writer. Model text was extracted and translated first so sheet exports would inherit English annotations, then the spec sections rolled out in daily batches, each revised by a second linguist before delivery. The package went to the owner on schedule, and the shared termbase now serves the same team on construction documents.

Every project gets that structure regardless of size: a named project manager based in our Texas office, a scoping pass that identifies where text actually lives in your files, an itemized quote within one business hour, and delivery back into the native format your team works in. Send a model, a spec book, or a competition brief, and we will tell you exactly what translating it involves before you commit to anything.