To translate ISO 19650-2 BIM documentation, information requirements, common data environment status, project information exchanges and handover records correctly, start with the particular record and its intended reader. This practical guide explains delivery-phase information exchanges for building and civil-engineering assets, rather than general BIM modelling tutorials. It is written for appointing parties, project information managers, design teams, main contractors, specialist suppliers, translators and bilingual reviewers. The central translation challenge is to make technical language understandable across borders without changing an underlying observation, a controlled term, an identifier, a permitted use or the status of evidence. A natural sentence can still be seriously wrong when it changes what the reader is entitled to conclude.
The ISO catalogue identifies ISO 19650-2:2018 as a published delivery-phase information-management standard, confirmed in 2024; a revision is being developed. This guide discusses practical translation decisions without restating the protected standard or asserting that a particular project complies. A bilingual information exchange is not merely a drawing with translated annotations. A recipient must still recognise which organisation requested information, which team is authorised to provide it, which revision was exchanged, how its suitability is recorded, and whether the information is for coordination, review or an agreed delivery. Translation must keep those decisions visible even when project teams use different languages, software and contractual vocabulary.
Quick summary: identify the applicable ISO 19650-2:2018 edition and the exact document; confirm the specimen, asset or project scope; retain identifiers and approved codes; translate purpose, measurement conditions and authority precisely; do not invent numbers, test results, approvals or legal conclusions; preserve uncertainty and missing information; review all tables against the source; obtain competent bilingual subject review before operational use. A mistranslated information requirement can cause the team to submit the right file at the wrong milestone. A mistranslated status can make an unapproved model look suitable for construction. Neither error is cured by fluent prose. The translator’s job is to retain record identity, requirements, status and responsibility, while the project’s appointed decision-makers remain responsible for the actual acceptance.
- Identify the reader and the real decision the translated record will support.
- Preserve the actual source revision, entity, units, conditions and data origin.
- Use a controlled bilingual glossary and keep stable machine identifiers unchanged.
- Separate observed evidence from proposed actions, approvals and interpretations.
- Release the target text only after a source-to-target technical evidence check.
Definition lock: what translation means in this specialist field
For this article, delivery-phase translation means preparing target-language versions of project information requirements, exchanges, approvals and handover records while retaining the original operational distinction among requested, submitted, reviewed, accepted and superseded information. A clear translation does not replace the common data environment or create permission to use a model.
The expression "construction information management" must not become a blanket claim of quality or conformity. Here, a correct translation is a faithful representation of the source’s meaning under a clearly described set of conditions. A related technical discipline may have its own validation rules. For example, a reviewer can confirm that the source says "pending" without deciding whether the underlying activity should be approved. This distinction lets language specialists and technical decision-makers collaborate without confusing their responsibilities.
Why technical translation is an evidence problem, not only a language problem
The most expensive translation mistakes often preserve ordinary grammar but destroy relationships. A number loses its unit; a conclusion loses its qualification; a file loses its version; an actor loses the responsibility attached to an action. Those mistakes are hard to notice if reviewers compare sentences only for elegance. A better review asks what practical decision a reader could make after reading each sentence and whether the original author actually authorised that inference. This is especially important in construction information management, where the same noun can appear in a laboratory worksheet, a supplier declaration, a contract and a public-facing explanation.
Before touching the target language, build a source map. Record who produced the material, its publication or revision date, the unit or project to which it belongs, the fields that are controlled by a system, and the source references for each essential claim. Decide whether you are translating for operational action, document understanding, training, a customer response or formal filing. Each use may have a different approval route. If the use is not specified, preserve limits rather than assuming the broadest permission.
Twenty-six specialist decisions that protect meaning
1. Delivery phase is not operation
Delivery-phase records concern designing, constructing and handing over the asset; operation-phase maintenance and asset management have different decisions and lifecycles. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that calling a commissioning deliverable an ongoing asset inspection record moves its business meaning into the wrong stage. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A bilingual handover pack can include future operations data, yet its present exchange still belongs to a named construction milestone. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
2. Appointing party and appointed party
The party commissioning an information exchange is not interchangeable with the organisation contracted to prepare it; project-specific terminology and appointment documents control the labels. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that replacing both roles with a vague word for owner conceals who has the obligation to provide information. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A requirement issued by the client and a response submitted by the design team must remain different records. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
3. Information requirements
A requirement describes what information is needed, when, in what form and for which decision; it does not necessarily describe what has already been delivered. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that translating required as completed changes a future obligation into an accomplished result. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A fire strategy model requested for design coordination is not automatically evidence of statutory acceptance. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
4. Exchange information requirements
Requirements attached to an appointment can include expected formats, milestones and review rules; each belongs to a specific work scope. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that an abbreviated EIR cannot be expanded into a universal legal obligation without checking local project usage. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A steelwork package might require a schedule and model at separate gates, even if they share a subject. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
5. Project information requirements
Project-wide information objectives must be distinguished from asset-level needs and specific exchange requirements. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that the translator should not merge a project register heading with a deliverable list simply because both mention information. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A flood-resilience design study may require different evidence from routine structural drawings. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
6. Information exchange milestones
A milestone is a planned point for exchanging specified information, not necessarily the date the construction work physically ends. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that confusing submission for approval may give a false impression that a contractual gate was satisfied. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A model uploaded on Tuesday for Friday review remains submitted until the right review decision is recorded. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
7. Project roles and review authority
Author, coordinator, reviewer, approver and recipient can be different people or organisations, and the translation must preserve their separate actions. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that a polite target-language passive voice sometimes erases who is accountable for reviewing a file. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A contractor can upload a document while only an authorised representative can accept it for the contractual purpose. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
8. Common data environment
A CDE is a managed approach for storing and exchanging information, with access, status and traceability; it is not simply any shared folder. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that using a target-language expression meaning public cloud drive may hide permissions and version controls. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A file visible to internal coordinators is not necessarily a published deliverable to the client. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
9. Work in progress and shared information
Internal working material differs from information shared for coordination, and both differ from information formally delivered. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that a translation that calls every shared item approved invites unsafe reuse of developing design. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A team may share a developing clash model to coordinate without allowing it to be used as a construction instruction. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
10. Published and archived states
A published information container has a defined communication purpose; archived records preserve the historical trace and should not be treated as current. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that old revisions can look authoritative when a translation removes archived or superseded metadata. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A previous revision retained for audit is not the live drawing that field crews should consult. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
11. Status and suitability codes
Project CDE codes can indicate why a file was issued and what it may be used for; code dictionaries must come from the specific project. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that do not translate a two-character status code into an invented universal ISO meaning. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A status mapped locally to coordination must not be recast as final approval after localization. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
12. Revision and version history
Revision identifiers, dates, transmittal numbers and issue descriptions establish a chain through which recipients know what changed. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that replacing a revision index with an ordinary page number breaks the record’s identity. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A revision B note may describe drawing changes while version 03 records the third issue under an internal workflow. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
13. Information container naming
Project naming conventions can encode originator, zone, level, type, role and number; preserving tokens is often more important than translating them. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that machine-readable identifiers should not be silently transliterated or reordered to sound natural. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: The target-language description of a file may change while its contractual container ID remains identical. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
14. Classification and asset identifiers
System codes, object classes and asset identifiers often connect schedules to drawings, models and maintenance registers. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that a natural-language equivalent of pump does not authorise changing the registered equipment code. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: The bilingual model property label can be localized while the stable asset reference stays untouched. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
15. Information model versus file format
An information model may combine several structured datasets and views; PDF, IFC and native authoring files are not interchangeable evidence. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that a translator should not promise editability after a format conversion that only preserves appearance. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A coordination model exported as IFC can differ in properties from its native authoring source. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
16. Federated models and discipline ownership
A federated view brings information from multiple disciplines together, without automatically transferring authorship or review responsibility. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that one combined screenshot must not be presented as a single fully approved design deliverable. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: Electrical and mechanical models can be combined for clash inspection while each discipline controls its own source. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
17. Clash issues and coordination notes
A detected clash is an observation pending interpretation, not proof of an engineering defect or evidence of resolution. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that the word resolved must not replace reviewed, acknowledged or assigned unless the source records actual closure. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A duct passing through a beam in a coordination check may be an unresolved issue or an intentional opening awaiting confirmation. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
18. Task information delivery plans
A task team plan records its own deliverables and anticipated exchanges; a master plan consolidates across teams. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that translating task-level commitment as a project-wide promise changes who is responsible. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: An architectural door schedule and a structural opening model can have separate planned dates and dependencies. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
19. BIM execution planning
An execution plan describes how people intend to produce, verify and exchange information, not a certificate that every practice has been completed. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that a strategy drafted for tendering should not be translated as confirmed implementation in the live project. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A proposed naming scheme becomes an approved project rule only after the relevant decision. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
20. Data quality and model checking
A check might assess geometry, attributes, naming, coordinates or completeness; the target language must identify which test was performed. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that model checked does not imply every property or regulatory obligation was verified. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A successful file-open test cannot be described as a complete engineering review. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
21. Security and access permissions
Different recipients may have varying access rights to sensitive site layouts, asset records and contractual information. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that the translation must not turn limited permission into public distribution or alter a confidentiality statement. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A subcontractor allowed to view a floor plan may still lack authority to download all asset data. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
22. Approval records and transmittals
Transmittals tell recipients what was issued; review records tell them the outcome. A transmittal alone is not necessarily acceptance. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that approved with comments and rejected are not interchangeable statuses; preserve both the decision and its qualifications. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: An attachment can be received successfully but fail its technical review. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
23. As-built and record information
A design intent, a contractor’s record of installed conditions and a verified as-built dataset have different evidential bases. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that adding verified where the source says submitted turns a contractor claim into independent confirmation. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A field change noted in a mark-up may await validation before it can be reflected as a final handover attribute. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
24. Handover and information acceptance
A handover exchange may include documents, asset identifiers, warranties and operating information, but acceptance depends on recorded checks. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that file transfer, document receipt and contractual acceptance must remain separately traceable. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: A facilities team can receive an O&M manual without certifying that all asset serial numbers match. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
25. Local contracts and national practice
The ISO reference cannot resolve every local contractual definition, legal duty, language requirement or local naming convention. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that copying a foreign project’s approvals vocabulary can be misleading when the current agreement uses other roles. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: For cross-border delivery, the reviewer should read the actual appointments before settling critical role labels. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
26. Machine-readable multilingual metadata
Parallel descriptions, language fields and references can be localized, but controlled keys and source-target links must remain stable. In a multilingual construction information management record, this distinction changes how the next person interprets the entry. Read the entire field group, not just an isolated heading: the field label, neighboring values, source notes and document status may all constrain the appropriate expression. When two English terms appear similar, ask what operation or measurement would be different if one were substituted for the other. The answer is often the reason both terms exist.
A frequent translation trap is that do not use translation software to replace an element identifier just because it resembles a translatable word. The wording may sound professional while relocating an observation, changing a limit or implying more certainty. Mark the affected phrase in the bilingual glossary and give it one approved explanation suited to this specific document. If the source is contradictory or incomplete, preserve that condition and record a query instead of repairing the underlying facts in translation. Accuracy sometimes means leaving an unresolved question visible.
Imagine the working record in context: The bilingual display name can differ while a data element’s identifier and revision stay the same. A useful quality check asks the reviewer to identify the actual source field behind the target phrase, locate the same identifier and unit in both versions, and explain what the recipient is allowed to infer. If that explanation changes between languages, revise the translation or escalate the source ambiguity. Keep the reason for the choice in a short decision log so a later revision or another language version does not silently reverse it.
Twelve worked translation cases — fictional learning examples
The following miniature cases are invented teaching examples. They show the difference between a fluent but misleading rendition and one that protects the evidence. They are not quotations from ISO 19650-2:2018, samples of an authorised standard, measured test data from a real site or official advice about what a project should approve. The numbers and names, where present, are illustrative only.
Case 1: Coordination is not construction
Source situation: A model is shared for design coordination. A misleading target version would imply: "It is approved for site installation." A safer meaning-preserving rendering is: "It may be reviewed for design coordination only." The target version must not grant permission the source never granted. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 2: Issue date versus acceptance date
Source situation: A package was transmitted on 4 June. A misleading target version would imply: "The client accepted it on 4 June." A safer meaning-preserving rendering is: "The package was submitted on 4 June." The record has an event date but no acceptance decision. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 3: Task plan ownership
Source situation: The ventilation task team plans a schedule. A misleading target version would imply: "Every contractor commits to that schedule." A safer meaning-preserving rendering is: "The ventilation team plans the stated exchange." Responsibility remains with the named team. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 4: Superseded drawing
Source situation: A previous revision is stored in the archive. A misleading target version would imply: "This is the latest current drawing." A safer meaning-preserving rendering is: "Previous revision retained for reference." History and current authority are different. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 5: CDE suitability label
Source situation: Local code means suitable for coordination. A misleading target version would imply: "Suitable for building work." A safer meaning-preserving rendering is: "Suitable for coordination under project code dictionary." Status codes have project-specific use. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 6: Model federation
Source situation: Architectural and structural files are federated. A misleading target version would imply: "The merged model has one author." A safer meaning-preserving rendering is: "Discipline models are combined for coordination." Combining views does not merge accountability. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 7: Pending clash
Source situation: A clash has been raised for review. A misleading target version would imply: "A structural defect is confirmed." A safer meaning-preserving rendering is: "Coordination issue raised, disposition pending." Observation is not an engineering conclusion. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 8: Receipt of transmittal
Source situation: An information package is received. A misleading target version would imply: "All information is technically approved." A safer meaning-preserving rendering is: "Transmission received; review outcome not yet recorded." Receipt and acceptance are separate. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 9: As-built claim
Source situation: Installer supplies its record drawing. A misleading target version would imply: "Engineer verified built condition." A safer meaning-preserving rendering is: "Installer-submitted record drawing." Source attribution protects evidential scope. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 10: Security designation
Source situation: Restricted drawing is accessible to assigned team. A misleading target version would imply: "Drawing is publicly available." A safer meaning-preserving rendering is: "Drawing accessible to authorised recipients." A reader’s right to view is conditional. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 11: Asset tag
Source situation: Asset ID AHU-04 appears in register. A misleading target version would imply: "Change the ID to a translated abbreviation." A safer meaning-preserving rendering is: "Keep AHU-04; translate explanatory label." Stable IDs connect bilingual records. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
Case 12: Incomplete delivery
Source situation: Required property was not populated. A misleading target version would imply: "Property confirmed absent in constructed asset." A safer meaning-preserving rendering is: "Required field not completed in submitted data." Missing data is not proof of physical absence. The task is not to turn the author’s technical judgment into a new judgment by the translator. In a real assignment, the approved expression would depend on the full source sentence, its referenced tables, the current revision and the receiving organisation’s terminology. Retain the source evidence and seek a technical reviewer when the difference affects action, acceptance or comparison.
A controlled twelve-stage translation and checking workflow
1. Intake
Identify the requested language pair, audience, intended use, owner and version of the source record. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
2. Source boundary
List which documents, attachments, tables, images, fields and external data sources belong to the translation assignment. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
3. Edition check
Record the cited ISO 19650-2:2018 edition and verify the title and status using the official catalogue; do not replace a published edition with a draft. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
4. Evidence map
Mark every identifier, unit, threshold, date, decision, uncertainty phrase, actor and condition that carries technical meaning. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
5. Terminology lock
Create a scoped glossary for construction information management; record the intended concept, its excluded near-synonyms and source field. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
6. First translation
Translate for the intended reader while preserving clause structure when it is necessary to protect conditions and obligations. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
7. Numbers and units
Compare every source and target number, separator, measurement unit and calculation basis cell by cell. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
8. Status and authority
Check that observed, proposed, submitted, pending, accepted, tested, rejected and superseded are not silently interchanged. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
9. Tables and graphics
Inspect every header, legend, axis, diagram label and footnote against the values that it qualifies. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
10. Subject review
Ask a competent bilingual specialist to verify physical, operational or analytical meaning rather than grammar alone. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
11. Resolution
Record ambiguities, obtain source-owner answers, and prevent unapproved editorial repairs from entering the final text. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
12. Controlled release
Preserve a bilingual version pair, approvals, change log, distribution scope and revision link for later updates. Record how the step was carried out, what evidence was inspected and which questions remain. A future reviewer should be able to repeat the check without depending on the translator’s memory. This matters because translations are often reused months later in a different system, where a missing note about context may become an incorrect operational assumption. Do not treat the step as complete merely because the language is fluent; ask whether the recipient can correctly reconstruct the source’s meaning and limits.
How to build a bilingual terminology and decision register
A useful terminology register includes the source expression, target expression, definition in plain language, unit or code where relevant, actual field or passage, a short example, the type of ambiguity to avoid, who approved the mapping and the date. The definition should state the concept rather than simply reverse-translate the chosen words. One target-language phrase can be appropriate for a marketing summary and inappropriate for a technical record. The register must therefore attach an approved term to its intended use, not claim that the translation works everywhere.
Keep a separate decision log for unresolved terms and source defects. The log can say that a source table contained a missing value, the owner was asked for confirmation, and the release retains the blank pending clarification. That is more trustworthy than a visually tidy table with made-up zeros. For changed or corrected source material, issue a new translation revision only for the affected material, check dependencies and preserve the link to the previous bilingual pair. Reproducibility is part of readability in specialist documentation.
What not to promise in a translation
Do not promise that a translated record proves regulatory compliance, test-method conformity, performance in every operating condition or acceptance by a particular authority unless the source actually establishes that claim and the applicable reviewers have approved the language. Standards describe scopes and methods; translation explains what the record says. A laboratory result, design file or maintenance event does not automatically become a legal certificate when translated. Keep forecasts, measurements, estimates, advice, decisions and unresolved reports in their original categories.
A useful final question is: If the target-language reader takes the most decisive reasonable action from this sentence, does the source text support that action? If not, the translation needs a qualifier, an owner query or a correction. That question is more reliable than asking only whether a paragraph sounds like it was written by a native speaker.
Frequently asked questions
Can a BIM model be translated without editing the model?
Yes. A separate localized transmittal, explanation or property glossary may be enough, but the translator must check how the recipient identifies and uses the original model. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Should CDE status codes be translated?
Usually retain the controlled code and provide its approved project-specific explanation in the target language; never invent a universal expansion. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Is the published model always suitable for construction?
No. Purpose, stage, contractual conditions and suitability still govern use. Published is not an unrestricted guarantee. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
What is the difference between a milestone and an approval?
A milestone records a planned exchange point; approval records a decision under a defined process. They may occur on different dates. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Does an IFC export preserve every detail?
Not necessarily. Compare properties, relationships and model versions before asserting equivalence between exports and authoring files. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Can translation correct inaccurate original data?
Not silently. Flag the source problem, seek the responsible party’s correction and keep an audit trail linking versions. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Who should approve bilingual technical records?
Usually a competent bilingual subject expert plus the authorised project reviewer, under the actual information-management process. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
What if a contract uses different role names?
Follow the approved contract and document the mapping rather than forcing an international vocabulary onto a specific project. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Can a filename be localized?
Only when agreed and when links, CDE conventions and machine identification remain valid. Often a translated display title is safer. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Does this guide certify ISO compliance?
No. It teaches the translator how to preserve meaning; formal conformance depends on requirements, competent assessment and project evidence. For a live document, compare the relevant source field, referenced edition and intended reader before settling the final wording. A terminology choice should be backed by the evidence actually in the file, not by general familiarity with a similar product or process.
Primary reference, editions and further learning
ISO 19650-2:2018 is a copyrighted international standard. Consult the authoritative catalogue and an authorised edition for formal requirements. This educational explanation describes practical translation pitfalls; its fictional examples do not quote requirements and must not be mistaken for instructions that supersede competent assessment.
ISO catalogue: ISO 19650-2:2018
For foundational translation decisions, use the existing Master Art of Translation guide. For learning the English vocabulary that carries technical distinctions, use the established Vocabulary Learning Hub. For grammar, meaning, register and cross-language communication, continue with How English Works. Those resources retain their broader subject ownership; this page remains a narrow specialist application.
Master Art of Translation — complete system
How English Works — Translation and Meaning Across Languages
Conclusion: make the evidence readable without changing the evidence
The goal of translating construction information management is not to add confidence or remove complexity. It is to let a reader in another language identify the same item, follow the same distinction, see the same measured or recorded conditions and understand the same limits. Good translators make the meaning easier to use while leaving technical decisions with the qualified owners. That combination—clear language, stable records and careful review—is what makes a specialist translation useful across borders.