Translate Traffic Signal Phase Charts and Timings

To how to translate traffic signal timing plans, signal phase diagrams, pedestrian clearance intervals, vehicle movements, yellow change and red clearance labels, preserve the factual fields of the source document before polishing its language. a movement, a controller phase, an indication interval and an approved timing value are different objects, even when an informal sentence uses the same word for several. The practical solution is to separate observations, labels, numbers, status and commentary, translate the surrounding explanation, and check that a reader working in another language can still locate the same evidence. This complete guide explains how to do it using a repeatable document-to-document method, worked examples and quality tests.

The visible problem is that changing a number, reversing an approach direction or conflating WALK with clearance can communicate an unsafe or nonexistent control sequence. Transport documentation translators, infrastructure educators, municipal reviewers and multilingual road-safety communication teams need more than a natural-sounding sentence: they need a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation in which identifiers, quantities, distinctions and limits of confidence remain usable. A machine translation can be grammatically convincing yet factually misleading, particularly when a short code or a conventional label has a specialised meaning.

Quick summary: identify the document’s canonical job; separate recorded evidence from inference; lock names, codes and numbers; define terminology by field rather than by ordinary dictionary meaning; translate instructions and status without strengthening them; verify the target against diagrams or physical objects; retain uncertainty and revision history; and conduct a final read as the person who must use the translated result.

What this translation problem really is

A translation is not successful simply because readers understand its sentences. In signals materials, readers also need to perform retrieval: locate a row, reproduce a measurement, follow a sequence, identify a particular object, or distinguish what happened from what was expected. Every useful field has a relationship to other fields. If one field changes without its neighbours, the document can become internally contradictory. The translator must therefore protect relationships, not merely isolated nouns.

Begin with a small control sheet. Record the source title, creator, date, version, intended audience, units, coding system, any legend, and the current status of the information. List what is fixed evidence and what is explanatory language. Fixed evidence generally includes numeric identifiers, controlled codes, recorded measurements, and references that connect one file to another. Explanatory language can be reshaped, but its claims cannot become stronger or weaker by accident.

For example, a source may use ordinary words such as ”observed”, ”available”, ”side”, ”phase”, ”count”, or ”verified” with a precise technical sense. Those words can be deceptively easy. Instead of selecting the most common dictionary equivalent, ask what the field denotes, who produces that datum, and what consequences follow if a different sense is chosen. This field-first habit is the difference between attractive prose and trustworthy documentation.

First principles: the ten things that must remain true

Principle 1 — intersection identity and plan revision. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to green interval and minimum or maximum values. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 2 — vehicle and pedestrian movements. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to yellow change and red clearance. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 3 — phase number and controller terminology. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to WALK and flashing don’t-walk interval. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 4 — green interval and minimum or maximum values. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to countdown versus steady indication. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 5 — yellow change and red clearance. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to coordination timing and offsets. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 6 — WALK and flashing don’t-walk interval. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to detectors, actuations and phase calls. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 7 — countdown versus steady indication. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to temporary plan versus approved operational configuration. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 8 — coordination timing and offsets. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to intersection identity and plan revision. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 9 — detectors, actuations and phase calls. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to vehicle and pedestrian movements. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

Principle 10 — temporary plan versus approved operational configuration. Treat this as a separately testable claim. Identify its original column, symbol or sentence, and determine whether it is a label, an identifier, an instruction, an observation, or an interpretation. The distinction matters because a label can be translated while a reference code usually must remain stable. Check its relationship to phase number and controller terminology. If a target reader cannot reconstruct that relationship, the translation needs another pass even when the wording feels natural.

A twelve-stage method you can repeat

Step 1. Define the reader’s job

Determine what someone must actually do with a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation. A historian, learner, technician, collector or coordinator may use the same file differently. Note whether the reader’s next action is identifying, comparing, observing, purchasing, teaching or approving. Choose the register that serves that task without silently expanding the document’s authority.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about intersection identity and plan revision and one possible misreading involving WALK and flashing don’t-walk interval. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 2. Inventory the source

Make a field list from the original before translating. For this document, start with intersection identity and plan revision, vehicle and pedestrian movements, phase number and controller terminology, green interval and minimum or maximum values. Identify free text separately from marks, codes, tables and illustrations. A missing caption or a clipped spreadsheet column is a source-completeness issue, not a vocabulary issue.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about vehicle and pedestrian movements and one possible misreading involving countdown versus steady indication. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 3. Identify the authority of each claim

Ask who wrote each statement and whether it is a prediction, observation, instruction, suggestion or approved decision. Preserve those categories. a movement, a controller phase, an indication interval and an approved timing value are different objects, even when an informal sentence uses the same word for several. A translator should never convert a participant’s opinion into an official finding simply because formal target-language prose sounds more polished.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about phase number and controller terminology and one possible misreading involving coordination timing and offsets. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 4. Lock non-translatable values

Create a protected-value list covering identifiers, numerals, units, conventional codes, version strings, filenames, coordinates and any target-specific control labels. Keep a separate field for a translated explanation. Compare raw values by character when stakes are high, not by how familiar a string looks.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about green interval and minimum or maximum values and one possible misreading involving detectors, actuations and phase calls. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 5. Read any legend or diagram first

A label’s meaning depends on the key that accompanies it. Read tables, legends and visual relationships before drafting individual captions. Where the source is ambiguous, preserve the ambiguity and request clarification. Guesswork disguised as consistency is not a solution.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about yellow change and red clearance and one possible misreading involving temporary plan versus approved operational configuration. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 6. Draft the plain-language explanation

Rewrite sentences so that the target reader understands what the record says and does not say. Make causal relationships explicit where target grammar requires that, but do not add new measurements, events or permissions. The initial draft is a hypothesis to be verified, not the final release.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about WALK and flashing don’t-walk interval and one possible misreading involving intersection identity and plan revision. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 7. Check quantities and boundaries

Check each number against its qualifier, units, start/end status and date convention. A field labelled minimum, maximum, optional, predicted or estimated cannot lose that word. Always inspect decimal punctuation, leading zeros and signs after export to the target system.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about countdown versus steady indication and one possible misreading involving vehicle and pedestrian movements. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 8. Preserve uncertain information

Keep qualifiers such as possible, reported, illegible, approximate, planned and under review. They often carry more scientific or practical meaning than the surrounding narrative. An honest translation may be less elegant but more useful because it refuses to pretend uncertainty has disappeared.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about coordination timing and offsets and one possible misreading involving phase number and controller terminology. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 9. Perform a reverse retrieval test

Give another reader the target version and ask them to locate the original row, figure, symbol or physical marking. Can they recover intersection identity and plan revision and yellow change and red clearance without asking which source detail was silently omitted? Retrieval failure is a stronger quality signal than a general impression of fluency.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about detectors, actuations and phase calls and one possible misreading involving green interval and minimum or maximum values. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 10. Test with a concrete example

Pick one low-risk sample and follow the full chain: source statement, evidence, draft equivalent, checked equivalent and final reader interpretation. Explain why the tempting alternative fails. Practice with representative edge cases instead of assuming a single ordinary example proves the whole document is safe.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about temporary plan versus approved operational configuration and one possible misreading involving yellow change and red clearance. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Step 11. Run a target-only read

Hide the original and read for clarity, natural word order, internal consistency and navigation. Verify that headings lead to the sections they promise. Then reopen the source and check whether edits made for style altered any controlled fact. Good translation involves both fluency and source fidelity.

Step 12. Record review and release limits

Note the reviewer, version, unresolved questions and whether specialist sign-off is required. This is a documentary translation guide, not a method for designing, programming, approving or modifying road signal controllers. Licensed local specialists must review operational plans. Never label an unreviewed translated draft as an approved operative instruction. Store changes so future translators can distinguish an amendment from a fresh claim.

In practice, perform this step while the source a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation is open beside the target draft. Write down one checkable decision about vehicle and pedestrian movements and one possible misreading involving countdown versus steady indication. If you cannot state how the decision would be independently checked, it is not ready to become invisible in fluent prose. This procedure turns translation from a series of guesses into a documented sequence of small, reviewable judgments.

Worked examples: translate the record, not an invented story

The examples below are constructed teaching cases, not observations, products, live road plans or verified archival objects. Their purpose is to show a source fragment, a tempting misreading, a defensible target-language decision and a verification action. Replace them with authentic source material during a real translation job; do not copy the invented numbers into operational records.

Worked example 1: Movement is not a phase

Source evidence. Plan lists eastbound left turn movement and controller phase 3. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. The translator may replace movement with phase in every sentence. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Keep geometric movement separate from the controller’s assigned timing unit. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check arrows, movement labels and phase table against each other. Then apply to diagrams with multiple movements sharing a phase. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 2: Plan revision

Source evidence. Plan revision C is superseded by revision D; two sheets remain in the packet. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. An editor may combine values from both sheets into a fictional hybrid configuration. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Label each sheet with its effective revision and keep superseded values historical. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check the approval block and revision timestamp before release. Then apply to handover dossiers. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 3: Approach direction

Source evidence. Northbound through movement receives phase 2 in the example drawing. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. Northbound can be mistranslated as a movement heading north from the north approach. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Preserve the specified travel direction and clarify viewpoint where local terminology differs. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Trace vehicle arrows on the plan to confirm approach and destination. Then apply to four-leg intersection legends. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 4: Green minimum versus maximum

Source evidence. Controller schedule has minimum green 7 s and maximum green 30 s. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. Condensing both to green time 30 seconds states a fixed duration not present in the source. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Keep min and max qualifiers and the actuation context. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Compare each parameter with the original controller table. Then apply to public explanations of actuated control. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 5: Yellow change versus red clearance

Source evidence. Yellow change 4.0 s; red clearance 1.5 s in a sample plan. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translation may merge the two into one ‘yellow-red phase’. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Retain two separate intervals, values and their sequence. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. The target schedule must still show what is yellow and what is all-red. Then apply to technical review packs. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 6: Walk versus flashing clearance

Source evidence. Pedestrian WALK 7 s, flashing don’t walk 18 s, separate steady don’t walk afterward. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translator may interpret flashing hand as ‘walk now’ or as a general countdown. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Name the indications precisely and preserve each interval’s function. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check the pedestrian timing chart with the written explanation. Then apply to public information signs. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 7: Parallel concurrent movements

Source evidence. A vehicle through movement and adjacent pedestrian crossing can be served concurrently. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. The word concurrent may be mistranslated as consecutive. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Translate same-time operation explicitly without implying absence of turning conflicts. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Inspect both movement diagram and note about permissive turns. Then apply to intersection education leaflets. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 8: Pedestrian call

Source evidence. The controller has a pedestrian pushbutton input and a call waiting status. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translation may imply pressing the button instantly triggers WALK. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Differentiate request registration from actual service in a future phase. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Follow the source call state and logic diagram; do not promise a time. Then apply to accessible travel guides. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 9: No fixed cycle under actuation

Source evidence. The document describes variable phase length under detector calls. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A source diagram showing one illustrative cycle can be mistaken for a mandatory repeated schedule. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Keep the illustrative qualification and detector-dependent conditions. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Mark nominal values as examples rather than confirmed field settings. Then apply to classroom demonstrations. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 10: Offset in coordination

Source evidence. Offset is measured relative to a documented reference point in a coordinated network. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translation may describe it as a physical road distance or generic delay. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Keep timing offset and its reference definition intact. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check that all offset values use the same reference convention. Then apply to signal progression reports. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 11: Ring and barrier terminology

Source evidence. The controller diagram shows two rings separated by barriers. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translator may mistake ring for a circular road layout. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Retain controller-specific term with a concise explanatory gloss. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Trace stage compatibility and barrier line visually without redesign. Then apply to eight-phase controller illustrations. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 12: Permissive and protected turns

Source evidence. Left turn may operate protected in one interval and permissive in another. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. Translating both as ‘allowed left turn’ erases the distinction. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Name the right-of-way condition and any yield requirement exactly as written. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Compare arrow indications and movement legend. Then apply to bilingual training materials. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 13: Vehicle countdown confusion

Source evidence. The sheet has no vehicle countdown parameter, but includes a pedestrian countdown display. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A translation may assign the countdown value to all traffic lights. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Keep pedestrian display distinct from vehicular indication. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Locate the parameter’s target device in the source. Then apply to sign equipment inventories. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 14: Preemption and priority

Source evidence. The design document discusses emergency vehicle preemption separately from transit priority. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A generic translation of both as special treatment erases control logic distinction. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Preserve each term and its stated operating assumption. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check where the original describes interruption versus preference. Then apply to municipal procurement notices. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 15: Flashing operation

Source evidence. The controller can enter a flash mode for a specific contingency. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. An article may present flash mode as the normal pedestrian interval. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Distinguish the special operating mode from flashing don’t-walk during normal operation. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Verify the mode label in the plan set and public notice. Then apply to incident-response documentation. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 16: Timing units

Source evidence. A table shows 0.5, 5 and 50 seconds in separate columns. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A comma decimal convention can turn 0.5 into 5 or 5,000 if mishandled. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Preserve magnitude, unit and decimal interpretation. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Use source-to-target numeric column audit; no mental rounding. Then apply to multilingual spreadsheet exports. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 17: Temporary pedestrian diversion

Source evidence. Construction memo routes pedestrians to the west crossing while work occupies the east one. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. The translator might reverse west/east or imply the diversion is permanent. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Maintain location and time scope, and cross-check associated drawing. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Test the translated instruction as if a reader were approaching the site. Then apply to roadworks communications. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Worked example 18: Approved vs proposed parameters

Source evidence. Engineering note says proposed 20-second split pending local traffic authority review. This short fragment must be read inside the document’s actual field and the surrounding context. The translator’s first task is to decide which elements are data, which are descriptive labels and which are assertions. In this case the central content is not an invitation to embellish. It is a compact record whose parts must survive in another language, even where a normal conversational translation would prefer a smoother sentence.

Tempting mistake. A fluent translation might call the parameter approved or operational. This is more serious than a minor stylistic difference because a target reader may make a different inference or action from it. Before revising, explain precisely what would change: identity, sequence, quantity, confidence, authority, physical orientation or version. Being able to name the change helps a reviewer diagnose the failure instead of saying only that the sentence sounds wrong.

Better translation decision. Preserve proposed, pending and approval provenance; do not present it as a field instruction. Draft the surrounding sentence so that a reader unfamiliar with the source language can distinguish the actual fact from editorial explanation. Keep fixed signs, numerals and labels in a visible form, or supply a clearly marked translation key where the target document requires one. Do not conceal disagreement or fill an empty source field with a plausible value.

Verification and transfer. Check plan stamps, date and change control signatures. Then apply to tender documentation and public consultations. The important learning move is to repeat the check on a different real-world document, with a different layout or writer. The goal is not to memorise this particular fragment; it is to recognise the boundary between evidence and inference wherever it appears.

Failure modes that hide inside fluent translation

False certainty

An uncertain source becomes a confident target statement. Preserve confidence qualifiers and the evidentiary status of vehicle and pedestrian movements.

A useful prevention test is to have a second reader name the precise source detail that supports the translated claim. For signals records, compare the original field, the proposed equivalent and the reader-facing interpretation in three columns. If the third column promises more, less or something different from the first, revise the middle column. This catches meaning drift that ordinary proofreading often misses.

Silent unit changes

A value is converted, rounded or relabelled without authority. Use a documented conversion only when the audience needs it and the source value is still recoverable.

Code translation

A code is treated as an ordinary word and loses the lookup key that connects a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation to the original. Keep exact identifiers in a separate protected field.

Reordered sequence

The translator improves the flow while unintentionally changing the order of steps, time events or physical elements. Audit order against the original layout.

Status inflation

Pending, proposed or unreviewed becomes complete, accepted or approved. Keep every formal status and the person or institution responsible for it.

Scope drift

An article that should teach translation begins giving operational or professional advice. This is a documentary translation guide, not a method for designing, programming, approving or modifying road signal controllers. Licensed local specialists must review operational plans.

Unrecorded correction

A translator spots a possible source error, silently fixes it and removes the audit trail. Flag the issue and let the authorized source owner confirm a correction.

Poor extraction

Text is copied without diagrams, superscripts, symbols or footnotes. Recheck the PDF, image or physical object and its legend before declaring the source complete.

Practice: a progressive lesson for independent transfer

Exercise 1: Recognition

Take five sentences from a real a bilingual signal timing schedule, an engineering drawing legend, a road-works handover note or an educational explanation. Highlight codes, names, values, verbs of status and uncertainty markers in different colours. For each mark, write what would go wrong if it were guessed or generalized.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on intersection identity and plan revision and yellow change and red clearance. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Exercise 2: Pair comparison

Translate a short source fragment in two ways: a direct draft and an audience-friendly draft. List every factual difference. Keep the easier wording only where it leaves the source claims unchanged.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on vehicle and pedestrian movements and WALK and flashing don’t-walk interval. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Exercise 3: Number audit

Copy every measurement, date, unit and formal code into a separate table. Compare the target against this protected-value table in both directions. Note where a locale’s punctuation conventions could create ambiguity.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on phase number and controller terminology and countdown versus steady indication. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Exercise 4: Reader test

Ask another person to locate three items from the translated document in the original. Give them no hint about which column or symbol to use. Record time, confusion and the exact phrase that caused trouble.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on green interval and minimum or maximum values and coordination timing and offsets. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Exercise 5: Edge-case swap

Alter the practice source so that a key statement is only proposed, uncertain or incomplete. Watch whether your target language still signals that state. Then restore the original wording.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on yellow change and red clearance and detectors, actuations and phase calls. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Exercise 6: Final review

Read the target on its own, then compare field by field against the source. Write a one-paragraph release note stating what was checked, what remains unresolved and who must approve any technical use.

A strong answer does not merely sound polished. It contains a short evidence note: which original words, marks or values justified the decision, and how a second reader would verify it. For this lesson, focus especially on WALK and flashing don’t-walk interval and temporary plan versus approved operational configuration. A teacher can assess the response by whether it preserves the source’s meaning, retrieves the same object and acknowledges any ambiguity rather than concealing it.

Frequently asked questions

What is a traffic signal phase?

It is a controller timing unit assigned to one or more movements. The exact meaning should follow the agency and controller terminology used in the source. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Is a movement the same as a phase?

No. A movement describes the user’s path; a phase controls timing and may be associated with multiple movements. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Can I combine yellow change and red clearance?

Not as a documentary translation. They are separate intervals with different meanings and must remain separate in the source-to-target map. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Does flashing don’t walk mean a person should begin crossing?

No. Explain the indication according to the authoritative local guidance, especially when writing public-facing messages. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Can translation software reformat numeric timings?

It may reformat typography, but each number, unit and linked field needs a source-to-target check. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Should I adopt US phase numbers everywhere?

No. The source plan and local standard determine the controller convention; do not generalize example phase numbering worldwide. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Can the translated plan be used for programming?

Only after the relevant agency or qualified engineers have reviewed and approved it. Translation itself is not engineering authorization. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

What is the safest final review?

Combine numeric verification, visual diagram tracing, status and revision checking, and specialist sign-off. For a serious signals document, verify the decision against the primary source, the governing legend and any current authority that defines the field. If evidence is insufficient, state the limitation rather than choosing an answer only because it seems fluent. The principle is portable: preserve what is known, describe what is unknown and make review possible.

Final check: the translation should still support the same decision

Before release, ask five questions: Can the reader identify the same source object? Are all values, qualifiers, codes and dates intact? Does a diagram or chart still agree with the prose? Are the original approval state and remaining uncertainties unmistakable? Can someone trace each important target assertion back to evidence? The correct outcome is not the most elegant possible rewrite. It is a text that reads naturally while remaining accountable to the same facts.

This is a documentary translation guide, not a method for designing, programming, approving or modifying road signal controllers. Licensed local specialists must review operational plans. When uncertainty remains, report it clearly and seek relevant review. That restraint is a strength of careful educational writing: it gives the reader practical understanding without pretending that translation alone can replace observation, craft testing, archival verification or engineering authorization.

Top Ways to Translate Correctly | Translate Traffic Signal Phase Charts, Clearance Intervals and Pedestrian Timings Without Changing the Control Plan