To translate AGV and autonomous mobile robot warehouse safety instructions, operating-zone notices, operator interventions and maintenance handovers while preserving each driverless industrial truck’s safety status, begin by deciding what the reader must understand and what they are actually authorised to do. This practical guide to ISO 3691-4:2023 translation follows real document decisions, from terminology and record fields to readers’ questions. It shows how an apparently fluent sentence can be materially wrong when it changes an object, a limit, a role or the state of an action.
If you are searching for ISO 3691-4:2023 multilingual documentation, technical translation examples, translation quality checks or subject-specific localisation guidance, the central task is not to swap words in isolation. ISO 3691-4:2023 covers safety requirements and verification for driverless industrial trucks and their systems, including examples such as AGVs, autonomous mobile robots and automated carts. It addresses automatic modes and certain manual or maintenance modes, and notes the importance of preparing the operating zone. It is not a general standard for public-road robots or all types of mobile machinery. The source edition, diagram or interface must be checked before anyone treats a target-language explanation as operationally authoritative.
The method is straightforward: identify the relevant source version, freeze untranslatable values, resolve ambiguity with the owner, draft for the target reader, review with a subject specialist and test the finished communication in context. This article provides 8 connected chapters and 32 original worked cases. This guide explains translation decisions; it is not an operating manual, risk assessment or permission to override a safeguarding device. Site-specific safety instructions and authorised specialists control actual operations. The short answer and the detailed learning path follow.
Quick answer: what a reliable translation must preserve
- Identify the document, intended decision, audience, target language and locale.
- Keep classification codes, model identifiers, dimensions, dates and status signals distinct from human-readable names.
- Separate what was proposed, observed, approved, performed and independently verified.
- Mark source ambiguity for owner clarification rather than inventing a convenient answer.
- Keep necessary limits and conditional language even when a shorter sentence sounds more elegant.
- Test the translation in its final layout with a domain reviewer and a representative reader.
Who is this for? warehouse operators, multilingual EHS teams, robot integrators, commissioning engineers, logistics trainers and technical translators preparing safety-related communication. The aim is a working set of decisions that can be checked, corrected and applied across languages, not a declaration that a translated page complies with an entire technical standard.
What the standard covers—and what this educational guide does not claim
ISO 3691-4:2023 covers safety requirements and verification for driverless industrial trucks and their systems, including examples such as AGVs, autonomous mobile robots and automated carts. It addresses automatic modes and certain manual or maintenance modes, and notes the importance of preparing the operating zone. It is not a general standard for public-road robots or all types of mobile machinery. The official catalogue is the reference for scope and current edition: ISO 3691-4:2023 catalogue record. International standards are not reproduced here; the case notes below are constructed educational examples, not extracts from the licensed normative text. A project’s adopted local standard, contract, jurisdiction and actual operational procedure may impose further requirements.
A translator should therefore keep a boundary between explanation and authority. This guide explains translation decisions; it is not an operating manual, risk assessment or permission to override a safeguarding device. Site-specific safety instructions and authorised specialists control actual operations. In a high-consequence setting, request the current controlled source, technical drawings or system specification as appropriate, then ask a qualified domain reviewer to validate the rendered statements. A fluent paragraph cannot correct missing information, establish equipment suitability or supply approval that the source never gave.
Chapter 1: set up a translation brief before choosing terms
Start with a one-page brief recording source language, target locale, document owner, edition, required reading level and the specific choice the reader must make. Identify immutable fields such as part numbers, classifications, system states, measurements, thresholds and dates. Beside each field record whether it must be left untouched, transcribed according to an approved convention, translated as a term or explained in additional accessible language. This avoids the common mistake of treating all visible characters as interchangeable prose.
Create a decision log with five columns: exact source wording and location; proposed target wording; why it was selected; evidence or authority supporting that selection; and approval status. If two terms are plausible, both may belong in the log while neither should be released. Keep an issue open when a drawing, vendor promise or course rule is itself unclear. The translator’s obligation is to expose the ambiguity so the author can resolve it, not to make the source seem more complete than it is.
Use the following cases as translation-ready English bridge statements. They are intentionally not claimed to be French, Mandarin, Arabic, Tamil or another target language: actual grammar, word choice, formal address and culturally appropriate phrasing must be decided by a competent translator for the named locale. This distinction makes the examples reusable while avoiding pretend linguistic equivalence.
Chapter 2: What type of system is speaking
AGV, AMR, automated cart and robot may appear together in source records. Their labels do not automatically tell an operator which movements, safeguards or operating modes apply. A recurring difficulty in this chapter is that familiar workplace language compresses several decisions into a single phrase. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Test whether a worker can point to the exact machine and matching operating instruction. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 1: Fleet notice
Imagine a source-language note or loosely drafted English intermediate reading, “Robot 8 stopped”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Vehicle ID AGV-08 is stationary; reason and restart authorisation not established”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Stopped can mean planned stop, obstacle detection, fault or power loss. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. For the next revision, store this term with the relevant source image or record identifier, rather than saving the sentence without context.
Worked case 2: Asset type
Imagine a source-language note or loosely drafted English intermediate reading, “Autonomous forklift”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Driverless industrial truck of the identified model; load-handling configuration confirmed from asset record”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A nickname may imply forks or autonomous capabilities not fitted to the machine. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. In the final layout, confirm that headings and nearby labels do not change the meaning of this sentence.
Worked case 3: Control owner
Imagine a source-language note or loosely drafted English intermediate reading, “Robot chose route”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Controller requested route segment R4; routing decision and machine response logged separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Anthropomorphic wording can hide which subsystem issued a command. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. If local practice uses a shorter expression, retain the complete definition in the glossary and test whether the abbreviation remains clear.
Worked case 4: System boundary
Imagine a source-language note or loosely drafted English intermediate reading, “AGV is safe”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Safety verification applies to the stated truck and operating-zone configuration under specified conditions”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Safety is conditional on the system and environment, not a permanent trait. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Ask the language reviewer to describe the resulting action in their own words. Agreement on a word is weaker evidence than agreement on a decision.
Chapter checkpoint: Test whether a worker can point to the exact machine and matching operating instruction. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 3: Operating zones and access
Zones may be permanent, temporary, shared or affected by loading activity. Translated signs must preserve boundaries and the action expected of a pedestrian. The operational issue here is less about a rare dictionary word than about knowing exactly which thing the text refers to. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Walk the route with an authorised safety reviewer and compare signs with real entrance points. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 5: Entry notice
Imagine a source-language note or loosely drafted English intermediate reading, “Keep clear”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Pedestrians must not enter marked automated-vehicle operating zone while the identified mode is active”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Keep clear without a zone or active condition is too vague. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Make disagreement visible in the query log. An unresolved issue is not a reason to claim that the release has been verified.
Worked case 6: Crossing
Imagine a source-language note or loosely drafted English intermediate reading, “Use safe path”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Use the designated pedestrian crossing after following the site’s authorised crossing procedure”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Safe path cannot be guessed by a visitor unfamiliar with painted floor markings. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Check the example in both directions: would a reader translating it back recover the same referent and limits?
Worked case 7: Temporary barrier
Imagine a source-language note or loosely drafted English intermediate reading, “Area shut”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Access to zone Z2 temporarily restricted pending authorised clearance”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Shut may imply equipment shutdown instead of pedestrian access restriction. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Version the answer when the source changes, since a previously correct translation can become stale without a single typo.
Worked case 8: Loading station
Imagine a source-language note or loosely drafted English intermediate reading, “Wait here”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Remain behind the marked waiting boundary until the local authorised signal permits access”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Here depends on where the instruction is posted and whether the mark is visible. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Treat the safer wording as a proposed clarification until the source owner confirms it; linguistic confidence is not technical authority.
Chapter checkpoint: Walk the route with an authorised safety reviewer and compare signs with real entrance points. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 4: Modes, controls and commands
An automatic mode, manual mode and maintenance mode can involve different privileges and safeguards. Translation must not turn state labels into imperatives. Technical accuracy begins by distinguishing a displayed label from an observed state and an authorised decision. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Require a bilingual operator to distinguish observed status from an action they are authorised to perform. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 9: Auto state
Imagine a source-language note or loosely drafted English intermediate reading, “Auto ready”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Automatic mode available but not necessarily running; confirm actual active state separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Ready is often mistaken for moving or released to start. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. For the next revision, store this term with the relevant source image or record identifier, rather than saving the sentence without context.
Worked case 10: Manual control
Imagine a source-language note or loosely drafted English intermediate reading, “Take over”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Manual operation only by authorised personnel under the site-approved changeover procedure”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Take over sounds like an unrestricted permission to enter controls. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. In the final layout, confirm that headings and nearby labels do not change the meaning of this sentence.
Worked case 11: Maintenance display
Imagine a source-language note or loosely drafted English intermediate reading, “Service mode”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Maintenance mode indicated; access and motion restrictions remain governed by site procedure”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Service label does not mean the equipment is safe to approach. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. If local practice uses a shorter expression, retain the complete definition in the glossary and test whether the abbreviation remains clear.
Worked case 12: Emergency control
Imagine a source-language note or loosely drafted English intermediate reading, “Reset emergency stop”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Emergency stop has been activated; reset only under approved safety procedure after causes are resolved”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A translation should not present resetting as the immediate next step for everyone. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Ask the language reviewer to describe the resulting action in their own words. Agreement on a word is weaker evidence than agreement on a decision.
Chapter checkpoint: Require a bilingual operator to distinguish observed status from an action they are authorised to perform. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 5: Alerts and safety functions
An alert may describe an obstacle, a degraded component or a system failure. The translator must preserve its source, severity, uncertainty and effect on motion. A well-edited translation should not force readers to infer a missing unit, boundary or actor. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Replay sample alerts in a safe test environment with the responsible technician. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 13: Obstacle alarm
Imagine a source-language note or loosely drafted English intermediate reading, “Sensor saw person”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Obstacle detection event recorded in sector S3; object type not confirmed”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A sensing system may detect an obstruction without identifying a person. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Make disagreement visible in the query log. An unresolved issue is not a reason to claim that the release has been verified.
Worked case 14: Brake status
Imagine a source-language note or loosely drafted English intermediate reading, “Brake on”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Braking function indicated active by the specified status signal; verification state reported separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A screen icon alone may not be confirmation of measured stopping performance. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Check the example in both directions: would a reader translating it back recover the same referent and limits?
Worked case 15: Network loss
Imagine a source-language note or loosely drafted English intermediate reading, “No connection”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Communication link to fleet controller lost at logged time; machine response governed by configured safety behaviour”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: No connection is not proof that the vehicle is motionless. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Version the answer when the source changes, since a previously correct translation can become stale without a single typo.
Worked case 16: Fault banner
Imagine a source-language note or loosely drafted English intermediate reading, “Critical issue”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Fault category and error identifier retained; instructions refer to authorised fault-response procedure”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Critical without a code or clear action may increase panic while reducing utility. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Treat the safer wording as a proposed clarification until the source owner confirms it; linguistic confidence is not technical authority.
Chapter checkpoint: Replay sample alerts in a safe test environment with the responsible technician. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 6: Human roles and competence
Driverless does not mean responsibility-free. Operators, maintainers, pedestrians, system owners and emergency responders need distinct information and authorisations. These examples show why a controlled term must travel with its definition and its source. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Have a reviewer identify who must act, who may observe and who signs off completion. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 17: Operator instruction
Imagine a source-language note or loosely drafted English intermediate reading, “Anyone can restart”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Only designated authorised personnel may initiate restart according to documented procedure”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Removing the actor can create unauthorised behaviour. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. For the next revision, store this term with the relevant source image or record identifier, rather than saving the sentence without context.
Worked case 18: Visitor briefing
Imagine a source-language note or loosely drafted English intermediate reading, “Stay away from robots”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Visitors must follow site escort and marked pedestrian-route instructions in automated zones”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A generic fear message is less actionable than a route and role instruction. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. In the final layout, confirm that headings and nearby labels do not change the meaning of this sentence.
Worked case 19: Maintenance request
Imagine a source-language note or loosely drafted English intermediate reading, “Engineer called”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Maintenance team notified; attendance, diagnosis and corrective action are separate statuses”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Calling someone does not prove the fault has been inspected. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. If local practice uses a shorter expression, retain the complete definition in the glossary and test whether the abbreviation remains clear.
Worked case 20: Incident note
Imagine a source-language note or loosely drafted English intermediate reading, “Worker triggered alarm”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Alarm triggered during worker proximity event; causation remains under investigation”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: The wording should not blame a person before evidence establishes a cause. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Ask the language reviewer to describe the resulting action in their own words. Agreement on a word is weaker evidence than agreement on a decision.
Chapter checkpoint: Have a reviewer identify who must act, who may observe and who signs off completion. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 7: Loads and material flow
Loads introduce height, stability, identification and route hazards. Translate task constraints and change conditions, not marketing promises about throughput. At handover, ambiguity costs time because different teams may read the same sentence in different ways. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Compare the load note with engineering limits and the warehouse-management record. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 21: Load instruction
Imagine a source-language note or loosely drafted English intermediate reading, “Heavy load allowed”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Use only load types and masses approved for this truck configuration and route”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Heavy is subjective and omits load-centre and stability conditions. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Make disagreement visible in the query log. An unresolved issue is not a reason to claim that the release has been verified.
Worked case 22: Pallet label
Imagine a source-language note or loosely drafted English intermediate reading, “Pick item 204”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Transport pallet ID P-204 to designated location; verify item identity in warehouse system”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Pallet identity is not necessarily the stock-keeping-unit identity. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Check the example in both directions: would a reader translating it back recover the same referent and limits?
Worked case 23: Docking
Imagine a source-language note or loosely drafted English intermediate reading, “Dock complete”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Vehicle reported docked at station D5; load transfer completion must be confirmed separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Docking and successful transfer are separate stages. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Version the answer when the source changes, since a previously correct translation can become stale without a single typo.
Worked case 24: Queue
Imagine a source-language note or loosely drafted English intermediate reading, “Next robot ready”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Vehicle queued for dispatch; movement permission still depends on system conditions”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Queued is a planning state, not a start command. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Treat the safer wording as a proposed clarification until the source owner confirms it; linguistic confidence is not technical authority.
Chapter checkpoint: Compare the load note with engineering limits and the warehouse-management record. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 8: Maintenance and change control
Updating software, sensors, routes or floor layouts can affect a translated instruction. Communication needs version identifiers and a route to local safety validation. Translation becomes more reliable when a reviewer can connect the sentence back to a specific source field. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Make the technical team map every changed instruction to its affected zone and role. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 25: Firmware
Imagine a source-language note or loosely drafted English intermediate reading, “Software improved”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Controller firmware updated to specified version; safety verification outcome is documented separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Improved is evaluative and cannot replace evidence. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. For the next revision, store this term with the relevant source image or record identifier, rather than saving the sentence without context.
Worked case 26: Map revision
Imagine a source-language note or loosely drafted English intermediate reading, “New route active”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Map revision M7 loaded; activation and on-site verification must be confirmed in the release log”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Loaded is not the same as deployed safely. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. In the final layout, confirm that headings and nearby labels do not change the meaning of this sentence.
Worked case 27: Cleaning notice
Imagine a source-language note or loosely drafted English intermediate reading, “Robot cleaned”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Device cleaned in specified areas; any post-cleaning functional check is recorded separately”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Cleaning may disturb sensors and should not imply readiness. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. If local practice uses a shorter expression, retain the complete definition in the glossary and test whether the abbreviation remains clear.
Worked case 28: Repair closure
Imagine a source-language note or loosely drafted English intermediate reading, “Problem fixed”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Fault corrected by recorded work order; return to operation requires the applicable checks and approval”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Fixing a component does not necessarily release the system. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Ask the language reviewer to describe the resulting action in their own words. Agreement on a word is weaker evidence than agreement on a decision.
Chapter checkpoint: Make the technical team map every changed instruction to its affected zone and role. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
Chapter 9: Incident and multilingual handover
A useful handover describes who saw what, when it happened, what remains uncertain and which control is now in force. Translation should preserve uncertainty instead of assigning blame. A multilingual release is successful only if the intended reader can take the right action without the translator secretly deciding policy. As a working habit, isolate every noun that refers to a physical item, person, digital field or contractual deliverable; then underline modal verbs, exclusions and status words. Those small elements carry much of the difference between information and instructions. A glossary entry that says only “preferred translation” is insufficient when different contexts call for different referents.
Before writing, ask three separate questions. What precisely is known from the source? What part of the wording is an interpretation that needs confirmation? What could the reader reasonably do after seeing the translation? Conduct a tabletop review with logistics, safety and maintenance representatives. Where the answer has safety, money, accessibility or assessment consequences, involve the appropriate subject owner. Do not let a translation editor silently become the approver of a technical decision.
Worked case 29: Near miss
Imagine a source-language note or loosely drafted English intermediate reading, “Robot nearly hit staff”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Reported close-proximity event involving vehicle ID and pedestrian; measurements and circumstances subject to investigation”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Near miss is a safety-reporting category and should not be embellished into a confirmed collision. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Make disagreement visible in the query log. An unresolved issue is not a reason to claim that the release has been verified.
Worked case 30: Evacuation
Imagine a source-language note or loosely drafted English intermediate reading, “All clear”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “All-clear may be issued only by the site’s authorised source; source, time and area must be stated”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A translator cannot infer an all-clear from a stopped alarm. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Check the example in both directions: would a reader translating it back recover the same referent and limits?
Worked case 31: Shift report
Imagine a source-language note or loosely drafted English intermediate reading, “Everything normal”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “No unresolved alarms recorded for listed vehicles during the shift; exceptions and monitoring limits stated”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: Everything normal implies coverage beyond what a log demonstrates. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Version the answer when the source changes, since a previously correct translation can become stale without a single typo.
Worked case 32: Language signoff
Imagine a source-language note or loosely drafted English intermediate reading, “Signs translated”. It is brief and could easily survive an ordinary spellcheck. Yet the reader cannot necessarily tell whether it describes a capability, an instruction, an observation or a confirmed outcome. A better translation brief asks the author to approve this meaning-bearing formulation: “Translated safety notices checked on-site for legibility, placement and comprehension in named languages”. This formulation is a model for semantic clarification, not an automatic edit to a signed original.
Why this distinction matters: A correct sentence can still fail if posted at the wrong entrance. The translator should mark the object or condition that must remain stable across languages and note which supporting record resolves the doubt. If the source does not contain that evidence, put a question to the author and keep the choice provisional. A more natural-sounding target sentence is not necessarily a more faithful one, particularly when the adjective or verb expands the promise being made.
Practical review: compare the source field, proposed interpretation and any adjacent diagram, interface label, specification or contract clause. Ask the subject reviewer to identify what would be incorrectly bought, operated, taught, reported or approved if the weaker phrase were used. Then ask a target-language reader to paraphrase the narrower meaning without prompts. Treat the safer wording as a proposed clarification until the source owner confirms it; linguistic confidence is not technical authority.
Chapter checkpoint: Conduct a tabletop review with logistics, safety and maintenance representatives. A reviewer can now explain not only which expression is preferred but which misunderstanding it prevents. Record accepted formulations in the controlled terminology sheet and carry unresolved questions into the next chapter. A decision recorded once should be reused consistently, but it should never be copied to a materially different situation merely because the English looks similar.
A practical cross-language revision procedure
First, collect the issued source and any artefact needed to interpret it: drawing, code table, product sheet, operating-state record, learner agreement or equivalent. Second, mark names, quantities, dates, conditions, roles and claimed outcomes. Third, compile a short concept glossary and ask the owner to decide ambiguous source terms. Fourth, draft in the target locale using accurate technical vocabulary but accessible sentence structure. Fifth, have another linguist check meaning and a domain specialist check operational truth. Finally, test the finished page, sign, form or user interface in the context in which it will be read.
The tests are deliberately different. A linguistic review asks whether the sentence means the same thing. A technical review asks whether the referent and state are correct. A reader test asks whether a person can find and act on the necessary information. A release check asks whether the right edition and approval have reached the actual publication channel. Passing one does not imply passing all four; log the outcome of each instead of compressing everything into a single “checked” label.
Frequently asked questions
Can I translate ISO 3691-4:2023 without reading the licensed standard?
You can translate ordinary descriptive material when its meaning is fully supported by an authoritative source, but you cannot claim conformity to a copyrighted technical standard merely from an online summary. When a clause, symbol or formal classification controls the answer, consult the applicable authorised text and a qualified reviewer.
Should I translate codes or identifiers?
Usually preserve machine-readable identifiers exactly and translate the associated human-facing description. Confirm whether punctuation, character case and separators are meaningful. If a local script requires transliteration of a name, keep the original identifier alongside it so that later users can find the same record.
Can AI translation handle the first draft?
A machine-generated draft may help a qualified team, but it can invent a missing condition, overstate an outcome or smooth away uncertainty. It should not be treated as a final technical approval. Review source mapping, numbers, roles, control states and actual reader comprehension before release.
What if the source document is ambiguous?
Do not choose a meaning simply because one is more fluent. Record the ambiguity, propose alternatives, contact the author or technical owner and document the response. If publication cannot wait, identify the unresolved area and avoid an unsafe claim rather than silently deciding it.
How is an accessible explanation different from a literal translation?
Accessibility improves navigability and comprehension: explicit labels, readable structure, instructions that identify the actor and alternatives to colour-only information. It must not change a requirement, a right, an equipment limitation or an assessment rule. The accessible version should still be checked against the original.
What goes in a terminology record?
Store the source term, concept definition, intended audience, approved target term, disallowed near-synonyms, context sentence, authoritative source, locale, reviewer and update date. A record becomes useful when it teaches the next translator why a superficially similar alternative is wrong.
How should translation corrections be handled after publication?
Keep a version history linking the source change to affected target-language passages. Correct the web page, PDF, training material and any cached sign or notification where the error matters. Record who approved the correction and whether users require an explicit update.
When must a specialist review the result?
Use specialist review whenever mistranslation could affect safety, financial obligations, accessibility, qualifications, testing, contractual rights or technical operations. The linguist remains responsible for language quality while the appropriate technical owner confirms facts and authorised meaning.
Four-week learning and quality-control plan
Week 1 — observe and define
Choose eight source sentences from your real materials, identify the reader’s task and classify every protected element. Write down ambiguities that a dictionary cannot settle. Confirm which edition, drawing, record or service agreement controls each statement. The first deliverable is a brief and a concept table, not a polished translation.
Week 2 — draft and challenge
Translate the eight sentences into your selected locale. Ask a second linguist to propose the strongest alternative for every risky term, then explain why your preferred rendering better preserves the role, condition or referent. Submit unresolved technical questions to their source owner. Keep rejected alternatives in the decision log so they do not reappear next month.
Week 3 — test with a reader
Place the translation into a realistic form, instruction sheet, sign, drawing note, product catalogue or online interface. Ask a representative reader what they would do, what they believe is promised, and what remains uncertain. Compare their answer with the source owner’s intended decision. Repair meaning errors before polishing tone or layout.
Week 4 — approve and maintain
Freeze source and translation versions, record specialist and language approvals, publish only the checked version and create a correction route. Simulate a changed measurement, machine state, course rule or product classification. Trace every target-language sentence that would need revision. Keep the maintenance owner and review date visible in the release record.
How to know the translation is genuinely ready
A ready translation preserves the relevant object and its definition, the right action and authorised person, every protected measurement and condition, and the source’s exact level of certainty. It has been checked in context, not merely spellchecked. Its metadata points to the version it represents and its correction route is known. The underlying documentation remains the authority, especially where the consequences of misunderstanding are serious.
This specialist article fits below the established Master Art of Translation — EDKSG-TRANS-MASTER-WORLD-000, rather than replacing it. Readers who need to develop precise cross-language word knowledge can continue at the protected Vocabulary Learning Hub. Readers working on structure, audience and meaning can use How English Works: Translation and Meaning Across Languages. Those resources address the general architecture; the present article solves the narrower ISO 3691-4:2023 document problem.
Primary scope reference: ISO 3691-4:2023 official ISO record. Illustrative cases are original teaching examples. Verify the applicable edition, purchased standard, jurisdiction-specific rules and professional requirements before relying on any translation for regulated, contractual, medical or safety-critical action.