posted 18th August 2026
When an engineering or architectural company develops a project in a Portuguese-speaking country, translating its documentation involves far more than converting words from English into Portuguese. The translator must select the appropriate terminology, understand the relevant technical discipline, and adapt the documentation to the linguistic and institutional conventions of the market in which it will be used.
This distinction is particularly important in international projects involving infrastructure, energy, transport, construction, architecture and urban development. Global engineering and design firms often work with multinational teams and produce project documentation in English, even when the project itself is being delivered in a country where Portuguese is the official language.
Translated documentation may include specifications, reports, tender documents, drawings, BIM models, metadata, manuals, engineering studies, contractual documentation and performance requirements. In such contexts, an inadequate technical translation can create far more than a linguistic problem: it can introduce inconsistencies into a workflow that depends on terminological accuracy.
The issue is not simply choosing between European and Brazilian Portuguese
One of the most common questions in technical translation into Portuguese concerns the choice of language variety.
European Portuguese and Brazilian Portuguese have genuine differences in vocabulary, syntax, orthographic conventions and technical terminology. However, treating them as though they were effectively separate languages is just as inappropriate as ignoring differences that can genuinely affect a project.
Civil engineering provides a straightforward example. In Portugal, betão armado is the standard term; in Brazil, the usual term is concreto armado. The distinction is not merely stylistic: terminology forms part of the way in which technical professionals identify and communicate concepts. The appropriate variety must therefore be determined by the context of the project.
It is not enough to ask: ‘Should this document be translated into European or Brazilian Portuguese?’
The relevant questions are:
- In which country will the document be used?
- Who will read it?
- What terminology does the client use?
- Which technical standards and regulations apply?
- What terminology appears in the project's existing documentation?
- Has the client or contractor specified any terminology requirements?
- Will the document be used within a BIM environment, a procurement platform or a regulatory approval process?
In Angola, for example, it is not sufficient to assume that documentation intended for the Angolan market should simply be translated into European Portuguese. Portuguese is the country's official language, but local linguistic and terminological usage must be considered alongside the specific requirements of the project, the organisations involved and the project's reference documentation.
The right question, therefore, is not ‘Which Portuguese variety is correct?’ It is:
Which terminology and linguistic conventions are appropriate to the context in which this document will be used?
Technical terminology: translating concepts, not isolated words
This is where technical translation differs most clearly from general translation. In engineering and architecture, translators rarely work with isolated words. They work with terminological units and technical expressions whose meaning depends on the relationship between their constituent elements.
Consider, for example, box culvert or expansion joint. A word-for-word translation may produce a linguistically plausible sequence that is nevertheless technically inappropriate. The translator must recognise the concept represented by the expression and identify the term used by professionals in the relevant field and target market.
Technical terminology is not static, either. Engineers, architects, manufacturers, standards organisations and other specialists create new terms, reuse existing words with specialised meanings, borrow terminology from other languages and form new terminological units through derivation and compounding.
Linguistic competence is therefore indispensable, but it is not enough. A translator may have an impeccable command of Portuguese grammar and still mistranslate an engineering document.
To translate a structural specification, for example, the translator must understand what is being specified, what function a particular element performs, and how that concept is normally designated by professionals in the target market.
A terminological error can become an operational problem
Consider the following illustrative scenario. An international engineering consultancy receives the documentation for a structural project in Rio de Janeiro and needs to translate into Portuguese the metadata associated with a BIM model.
The translator encounters reinforced concrete and uses betão armado, a perfectly valid and established term in Portugal. However, if the project is intended for Brazilian teams and the client's documentation consistently uses concreto armado, the choice may introduce an unnecessary terminological inconsistency.
In an isolated document, this difference may appear insignificant. In a BIM model containing thousands of elements, parameters and properties, however, terminological consistency can become an operational issue.
This is why engineering translation should be treated as part of a project's document workflow rather than as an isolated linguistic task. The same principle applies to tender documents, specifications, bills of materials, inspection reports, drawings, and operation and maintenance documentation.
Technical translation and the regulatory context
Localising a technical document can also involve more than terminology. Engineering and architectural projects are subject to standards, regulations and procedures that vary from one country to another and, in some cases, between the organisations responsible for delivering or approving a project. The terminology used in a document may therefore be linked to a particular standard, classification, construction system or administrative procedure. This should not be reduced to a simple question of ‘European Portuguese versus Brazilian Portuguese’.
Language is only one part of the issue. The other is understanding the technical and institutional context in which the document will be used. In Brazil, for example, construction documentation may be subject to standards issued by the Associação Brasileira de Normas Técnicas (ABNT), among other applicable requirements. ABNT maintains an extensive body of standards and standardisation work relating to the construction sector.
Likewise, international projects in Portuguese-speaking African countries may involve local legislation, public-sector requirements, client specifications and terminology established within the project itself.
A good technical translation does not alter these requirements. It makes them linguistically clear and terminologically consistent in the target language.
BIM, translation memories and terminology databases
Contemporary engineering and architectural projects also require translators to understand the digital environments in which documentation is used. BIM models, for example, can contain large volumes of textual information: component names, properties, parameters, classifications, descriptions, codes and other metadata. In these environments, consistency is no longer merely a matter of style.
Computer-assisted translation (CAT) tools, translation memories and terminology databases can help preserve previously approved translations and maintain consistency across large volumes of documentation. When properly configured, these tools can also flag inconsistent or unauthorised terminology during translation and review.
Technology, however, does not replace technical expertise. A translation memory can reproduce a previous solution; it cannot, by itself, determine whether that solution remains appropriate for a new project. Similarly, a terminology database is only as useful as the terminology it contains and the context in which that terminology is applied.
What about artificial intelligence?
Artificial intelligence can accelerate certain stages of the translation process, particularly when large volumes of documentation need to be processed. It can help produce an initial draft, identify terminological patterns, locate inconsistencies, and support research and document preparation. In engineering and architectural documentation, however, speed does not replace validation.
An automated system may identify a linguistic expression, but without specialist supervision it should not be regarded as the final authority on the meaning of an engineering concept, the terminology preferred by a client, or the suitability of a particular term within the regulatory context of a given market.
The question is not whether to choose between technology and human translators. It is to use technology where it adds efficiency while retaining human validation where specialist knowledge is indispensable.
What should you look for in a technical translation agency?
For engineering and architectural projects, the most important question is not how many languages an agency offers. It is *who will actually work on your project*.
A suitable agency should be able to demonstrate:
- Proven experience in the relevant technical discipline;
- Mastery of both the source language and the appropriate target-language variety;
- Knowledge of the terminology used in the target market;
- The ability to work with BIM documentation and other technical formats where required;
- Consistent use of translation memories and terminology databases;
- Robust review and quality-assurance processes;
- The ability to follow client-approved glossaries and terminology; and
- An understanding of the specific requirements of the project and the professionals who will use its documentation.
This is particularly important for international engineering and design firms operating in Portuguese-speaking markets.
Companies such as Dar Al-Handasah, for example, deliver engineering, architectural, water, energy, transport and other projects across a range of African markets, including Angola and Mozambique. Its portfolio includes, among other projects, electrification and solar-energy schemes in Angola and coastal protection works in Beira, Mozambique.
Mott MacDonald also works on infrastructure projects in Portuguese-speaking countries. In Mozambique, for example, the company has been involved in programmes relating to transport, infrastructure planning and urban development.
For companies operating in this international environment, translation is not an administrative step that takes place after the technical work has been completed. It forms part of the project's document infrastructure, enabling different teams to understand and implement the project consistently.
Engineering translation requires engineering knowledge
This is the approach we take at HaydockPolyglot.
We do not treat technical translation as an extension of general translation. We assign engineering and architectural projects to professionals with specialist knowledge of the fields in which they work, and we subject documentation to specialist review.
The objective is straightforward: to produce a translation that is not merely linguistically accurate, but that also works within the project itself.
That means understanding the terminology. Maintaining consistency. Respecting the appropriate language variety. Considering the technical and regulatory context. And, above all, recognising that behind every term lies a concept, component, process or requirement that must function in the real world.
When documentation describes a structure that will be built, infrastructure that will be installed, or a system that will have to perform, the translation must work too.