Translate GTFS Service Alerts and Moved Stops

How do you translate a GTFS Realtime Service Alert without sending riders to the wrong stop? Identify which agency, route, trip, direction or stop is affected; distinguish a closure from a detour, a reduced service from a significant delay, and an inaccessible lift from the loss of the entire station. Then translate the passenger-facing message without changing the structured `effect`, the entity selectors or the time interval. This guide owns the alert-message problem, not ordinary timetable translation.

Readers looking for GTFS Realtime service alert translation, `informed_entity` route and stop IDs, `NO_SERVICE` versus `DETOUR`, moved-stop notices, accessibility alerts, multilingual `header_text`, `description_text`, and `communication_period` versus `impact_period` need more than a readable announcement. When a message says ‘only route 12 at platform B’, an inaccurate translation can tell passengers the whole network is closed. The canonical task is preserving which service is affected, when, and what a person should actually do.

Did you know that an overbroad entity selector can change journey planning even if the notice itself sounds correct? The GTFS specification describes how combined route and stop selectors narrow the scope, while the community guidelines warn against ambiguous `NO_SERVICE` effects. Our hypothetical examples demonstrate backtranslation and route-identity checks. For real travel, riders should follow the transport operator’s current authoritative notices.

The one-minute answer

The rule is simple to remember: identify the kind of record, lock its authoritative identifiers and values, preserve every boundary of meaning, then make only the reader-facing language more natural. For GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language, first ask what the original evidence actually permits the recipient to conclude. If that answer changes after translation, revise before release. Accuracy is not measured by how elegant the words look in isolation; it is measured by whether a careful reader can retrieve the same practical information from both versions.

The visible problem: a fluent translation can still change the decision

Imagine an employee, researcher, healthcare professional or ordinary reader being given two descriptions of the same technical record. Both seem fluent. One, however, silently replaces a source qualifier with a stronger assertion. The reader acts on the stronger assertion and the document no longer means what its issuer recorded. This is why the translator has to compare the source, the structured field and the intended reader action, instead of approving a sentence solely because it sounds natural.

This article concentrates on the Service Alerts entity of GTFS Realtime, including localized rider messages, entity selectors, impact and communication periods, effects and accessibility information, not the separate TripUpdates feed or general transport fare policy. It deliberately does not pretend to take over neighboring guides. Each case is invented for teaching, not a live operational record, a substitute for professional compliance work or an instruction to take action with a real patient, passenger, payment or product. The method is useful because it makes omissions visible, especially when the source contains codes, abbreviations, dates, statuses or incomplete evidence.

First principles: preserve the meaning before rewriting the language

1. Service Alert versus TripUpdate

Service Alerts describe network disruptions and rider messages while TripUpdates supply specific trip timing and stop updates. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Do not republish a delay timestamp as a station-closure command. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

2. Selector scope

An informed entity identifies an affected agency, route, trip, stop or combination. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

A narrower route-stop pair must not become a whole-network statement. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

3. Combined selector fields

Fields combined inside one informed_entity are interpreted together as an AND condition. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Applying the result to every route at a stop changes scope. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

4. Multiple informed entities

Multiple selectors can represent several separately affected entities. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Do not read separate entries as one impossible combined requirement. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

5. Cause and effect

Construction or weather may describe cause; no service, detour or moved stop describes operational effect. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Knowing why a disruption happened does not tell you exactly what riders must do. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

6. No service

NO_SERVICE can change routing behavior and requires careful affected-entity selection. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Avoid falsely closing an entire route because one platform is unavailable. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

7. Reduced service

Reduced service is not necessarily full cancellation. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Do not ask every rider to abandon all trips. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

8. Moved stop

A temporarily relocated stop must retain its exact named destination and access directions. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

A vague ‘nearby’ can misroute passengers. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

9. Accessibility issue

A broken lift or step-free route change may affect only some journeys. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Do not represent station inaccessibility as cancellation of all trains. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

10. Time windows

Communication period and impact period address display and actual service effect respectively. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Announcements can appear before disruption starts. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

11. Multilingual fields

GTFS can carry translated header and description text with language identifiers. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

Do not alter IDs while localizing user-visible words. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

12. Official operator primacy

The feed may be updated or corrected rapidly during disruptions. This is the first distinction to identify when reading a record about GTFS Realtime Service Alerts translation, informed_entity selectors, stop moved notices, accessibility issues, impact periods and passenger routing language. A writer might treat the label as decoration, but a translator must ask whether it assigns a role, names an observation, defines a condition or restricts how a conclusion can be used. Write the answer in a short source-side note before selecting a phrase in the target language.

A translation should retain issue time, source link and refresh expectation. The practical test is to remove the proposed translation and ask a reviewer to reconstruct the original field from the remaining wording. If the reviewer cannot recover who or what the statement describes, when it applies and what is still uncertain, the translation has lost information. Restore the exact qualifier, identifier or relationship and check the record again, rather than adding a reassuring sentence unsupported by the source.

The repeatable ten-step translation workflow

Good professional translation does not rely on remembering every special term in one sitting. It relies on a small sequence that works when the record is long, unfamiliar or machine-readable. Apply these ten steps to one document, then repeat them on a second document from the same source system. The second run should be quicker without being less careful: you will have separated reusable terminology from document-specific facts.

Step 1: Identify GTFS Realtime entity

Confirm the source is an Alert rather than a TripUpdate or VehiclePosition. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Before moving to the next step, do a two-way check: read the target-language version back into a short neutral description of the original. Ask whether it still says what happened, to whom or to what, at which place or time, under which stated condition, and with what level of certainty. A mismatch is a reason to revise or ask an authorized subject reviewer, not a cue to guess.

Step 2: Read the alert’s affected entities

Copy route, stop, trip, agency and any specified direction selectors. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 3: Interpret selector logic

Check whether fields are combined within one entity or across multiple entities. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 4: Read the effect enumeration

Distinguish NO_SERVICE, DETOUR, STOP_MOVED, SIGNIFICANT_DELAYS and ACCESSIBILITY_ISSUE. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 5: Read the cause separately

Avoid deriving a stronger operational conclusion merely from maintenance or weather. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 6: Interpret both time concepts

Record display and actual impact intervals according to the current feed version and guidance. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 7: Extract passenger actions

Translate the usable instruction about where to board, transfer, wait or seek step-free access. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 8: Protect identifiers and destinations

Keep exact stop, route and platform labels where the operator depends on them. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 9: Build localized header and description

Place the urgent affected-service statement first; make the route action clear without inventing it. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Step 10: Run rider-path verification

Ask a reviewer to follow the translated message on a map and compare the original selector scope. Begin with the original record and identify the exact source field or sentence that supports the action. Record its function in plain English. If it is a value or a code, preserve its literal form; if it is explanation, preserve the condition and implied actor. This prevents the common error of treating a business rule, a clinical status or an operating notice as interchangeable general prose.

Worked examples: translate the claim, not a convenient imitation

The following mini-cases are fictional and language-neutral. ‘Source’ represents a short original-language field after a literal English gloss; the ‘unsafe rendering’ shows an error that could appear in any language pair. The suggested wording is a faithful English backtranslation test, not a universal legally approved phrase for every language. A local specialist must approve legally or clinically controlled terminology where applicable. Read the reason after each example; it is the transferable lesson.

Worked case 1: Route-stop combined scope

Illustrative source: “informed_entity route 12 and stop B”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Every route at stop B is cancelled”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The two fields form one qualified entity selector. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Only route 12 service at stop B is affected”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Audit and transfer: Compare the suggested version with the original and point to the words that preserve the actor, attribute and scope. Ask a second reviewer to answer, without seeing the original, what is known and what is not known. If their answer is stronger, broader or differently timed, revise the sentence. For the next document, deliberately alter one qualifier and explain how that would change the translation. This last exercise turns recognition into independent judgement.

Worked case 2: Separate selectors

Illustrative source: “One selector route 7; a second selector stop K”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Only route 7 at stop K”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Two entries do not automatically become an AND condition. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Route 7 and stop K are separately affected as indicated”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 3: No service

Illustrative source: “NO_SERVICE for route 4, specified segment”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “All city buses are unavailable”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The effect must not extend beyond the affected segment. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “No service for the stated portion of route 4”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 4: Reduced service

Illustrative source: “REDUCED_SERVICE on route 8”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Route 8 is cancelled”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Fewer trips is different from no trips. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Reduced service on route 8”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 5: Significant delay

Illustrative source: “SIGNIFICANT_DELAYS for a train line”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “The line is closed”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Delay and closure have different rider consequences. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Significant delays are reported for this line”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 6: Detour

Illustrative source: “DETOUR around Central Street”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Boarding impossible across the line”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. An alternative path may exist rather than a full stop. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Service is diverted around Central Street”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 7: Moved stop

Illustrative source: “STOP_MOVED from Pine Road to Oak Road”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Wait at Pine Road as usual”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The passenger action must name the new location. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Temporary boarding point: Oak Road, not Pine Road”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 8: Temporary location

Illustrative source: “Temporary stop 300 m north of original”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Stop 300 m south”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The directional relationship is operationally essential. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Temporary stop approximately 300 m north”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 9: Affected platform

Illustrative source: “Platform 2 closed; platform 1 operational”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Station closed”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Closing one platform is not equal to closing the station. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Platform 2 is unavailable; follow instructions for platform 1”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 10: Lift outage

Illustrative source: “ACCESSIBILITY_ISSUE: lift between concourse and platform unavailable”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “No trains operate at this station”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Accessibility and train operation require separate language. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Lift unavailable on specified connection; rail service status unchanged”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 11: Step-free alternative

Illustrative source: “Use accessible entrance on West Lane”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Use stairs at East Lane”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The destination must remain navigable for users relying on the instruction. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “For step-free access use the West Lane entrance”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 12: Cause construction

Illustrative source: “Cause CONSTRUCTION, effect DETOUR”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Major accident cancels all services”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Cause and effect should both reflect the source. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Construction is causing the listed detour”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 13: Cause unknown

Illustrative source: “UNKNOWN_CAUSE with service interruption”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Emergency police closure”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Uncertainty about the cause must remain visible. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Service interruption; cause not yet confirmed”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 14: Effect unknown

Illustrative source: “UNKNOWN_EFFECT”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “No service for the whole day”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. An unknown status is not authorization to invent a closure. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Service effect not yet confirmed”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 15: Display timing

Illustrative source: “Communication period begins Friday 09:00”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Construction begins Friday 09:00”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Communication may precede the event itself. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Notice displayed from Friday 09:00”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 16: Impact timing

Illustrative source: “Impact period Saturday 02:00–05:00”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Alert permanently in force”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The actual disruption window is distinct from the period that the notice is shown. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Disruption affects services Saturday 02:00–05:00”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 17: UTC time

Illustrative source: “Impact starts 2026-10-29 01:00 UTC”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “01:00 local time worldwide”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Time zones can shift a date in local display. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Impact starts at 01:00 UTC on 29 October 2026”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 18: Language tag

Illustrative source: “header_text language en”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “route_id must become en”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Localized text and structural IDs belong to different fields. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “English-language header text, identifier unchanged”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 19: Short header

Illustrative source: “Route 6 stop closed”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “All buses disrupted indefinitely”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The header must communicate effect and scope before contextual detail. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Route 6: specified stop temporarily closed”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 20: Detailed description

Illustrative source: “Use temporary stop on Market Lane after 18:00”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Market Lane opens at 18:00 for everyone”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. The condition binds the instruction to riders and time. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “From 18:00, affected riders use the temporary Market Lane stop”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 21: Link to operator

Illustrative source: “Official operator URL provided”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Third-party map is definitive”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Authoritative destinations should remain traceable. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “See the transport operator’s current notice at the supplied link”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 22: Route identifier

Illustrative source: “route_id R-017”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Route seventeen only, change internal ID”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Machine identifiers should not be localized into unverified alternative IDs. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Route R-017 (retain machine identifier)”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 23: Direction selection

Illustrative source: “Only inbound trips affected”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “All directions affected”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. Directional qualifiers matter even when the public route name is the same. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Inbound trips only are affected”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 24: Trip-specific alert

Illustrative source: “Alert selector names trip T-09”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “All trips on this route cancelled”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. A trip selector narrows scope below the route level. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Only trip T-09 is subject to this alert”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 25: Scheduled disruption

Illustrative source: “Planned stop closure on Sunday”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Unplanned emergency closure now”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. An announced future event is not evidence that it is already happening. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Planned stop closure on Sunday as announced”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Worked case 26: No confirmed end

Illustrative source: “Closure notice has no confirmed restoration time”. The original fragment may be short, but the field belongs to a larger record. Before translating, note which real-world object, party, time, value or status it refers to. Do not silently assume that all neighboring fields carry the same qualifiers; in structured information each field has its own declared purpose.

Unsafe rendering: “Service resumes in ten minutes”. This is attractive because it reads smoothly or seems to simplify specialist language. It is nevertheless misleading here. A precise invented reopening time harms passenger planning. Even a single substitution can change a user’s decision, especially when the statement will be displayed beside a number, identifier, alert or action button.

Faithful working rendering: “Restoration time not yet confirmed”. This wording explicitly preserves the relevant boundary rather than asking the reader to infer it. The objective is not to copy the source word order. It is to convey the same accountable claim, including any limitation or unresolved status, and to retain the exact value or named field if one is present.

Failure modes: how mistakes appear, and how to repair them

Failure mode 1: Service Alert versus TripUpdate becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Do not republish a delay timestamp as a station-closure command. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Service Alerts describe network disruptions and rider messages while TripUpdates supply specific trip timing and stop updates. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 2: Selector scope becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. A narrower route-stop pair must not become a whole-network statement. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. An informed entity identifies an affected agency, route, trip, stop or combination. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 3: Combined selector fields becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Applying the result to every route at a stop changes scope. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Fields combined inside one informed_entity are interpreted together as an AND condition. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 4: Multiple informed entities becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Do not read separate entries as one impossible combined requirement. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Multiple selectors can represent several separately affected entities. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 5: Cause and effect becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Knowing why a disruption happened does not tell you exactly what riders must do. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Construction or weather may describe cause; no service, detour or moved stop describes operational effect. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 6: No service becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Avoid falsely closing an entire route because one platform is unavailable. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. NO_SERVICE can change routing behavior and requires careful affected-entity selection. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 7: Reduced service becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Do not ask every rider to abandon all trips. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Reduced service is not necessarily full cancellation. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 8: Moved stop becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. A vague ‘nearby’ can misroute passengers. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. A temporarily relocated stop must retain its exact named destination and access directions. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 9: Accessibility issue becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Do not represent station inaccessibility as cancellation of all trains. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. A broken lift or step-free route change may affect only some journeys. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 10: Time windows becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Announcements can appear before disruption starts. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. Communication period and impact period address display and actual service effect respectively. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 11: Multilingual fields becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. Do not alter IDs while localizing user-visible words. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. GTFS can carry translated header and description text with language identifiers. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Failure mode 12: Official operator primacy becomes an assumption

A rushed translator sees a familiar phrase and replaces it with a familiar target-language term. The visible symptom is usually an unexplained shift of certainty, coverage, date, party, instruction or numerical category. A translation should retain issue time, source link and refresh expectation. To repair it, return to the governing record, reread the field next to its identifier, and restore the missing boundary. The feed may be updated or corrected rapidly during disruptions. A final reviewer should be able to describe that distinction in one sentence without appealing to intuition.

Practice and transfer: test your judgement without a glossary

Use these practice prompts as a short training circuit. Cover the suggested rendering in each worked case, translate the source independently into the language you know, and then compare the operational meaning. On a second pass, translate your own answer back into English. A successful response retains the facts and makes any unresolved matter explicitly unresolved. Do not measure success by matching our English wording character for character.

Practice 1: Separate selectors

Task: A colleague hands you the fictional record “One selector route 7; a second selector stop K” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Route 7 and stop K are separately affected as indicated”. An answer that implies “Only route 7 at stop K” fails because Two entries do not automatically become an AND condition. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 2: Reduced service

Task: A colleague hands you the fictional record “REDUCED_SERVICE on route 8” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Reduced service on route 8”. An answer that implies “Route 8 is cancelled” fails because Fewer trips is different from no trips. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 3: Detour

Task: A colleague hands you the fictional record “DETOUR around Central Street” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Service is diverted around Central Street”. An answer that implies “Boarding impossible across the line” fails because An alternative path may exist rather than a full stop. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 4: Temporary location

Task: A colleague hands you the fictional record “Temporary stop 300 m north of original” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Temporary stop approximately 300 m north”. An answer that implies “Stop 300 m south” fails because The directional relationship is operationally essential. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 5: Lift outage

Task: A colleague hands you the fictional record “ACCESSIBILITY_ISSUE: lift between concourse and platform unavailable” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Lift unavailable on specified connection; rail service status unchanged”. An answer that implies “No trains operate at this station” fails because Accessibility and train operation require separate language. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 6: Cause construction

Task: A colleague hands you the fictional record “Cause CONSTRUCTION, effect DETOUR” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Construction is causing the listed detour”. An answer that implies “Major accident cancels all services” fails because Cause and effect should both reflect the source. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 7: Effect unknown

Task: A colleague hands you the fictional record “UNKNOWN_EFFECT” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Service effect not yet confirmed”. An answer that implies “No service for the whole day” fails because An unknown status is not authorization to invent a closure. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 8: Impact timing

Task: A colleague hands you the fictional record “Impact period Saturday 02:00–05:00” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Disruption affects services Saturday 02:00–05:00”. An answer that implies “Alert permanently in force” fails because The actual disruption window is distinct from the period that the notice is shown. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 9: Language tag

Task: A colleague hands you the fictional record “header_text language en” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “English-language header text, identifier unchanged”. An answer that implies “route_id must become en” fails because Localized text and structural IDs belong to different fields. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 10: Detailed description

Task: A colleague hands you the fictional record “Use temporary stop on Market Lane after 18:00” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “From 18:00, affected riders use the temporary Market Lane stop”. An answer that implies “Market Lane opens at 18:00 for everyone” fails because The condition binds the instruction to riders and time. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 11: Route identifier

Task: A colleague hands you the fictional record “route_id R-017” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Route R-017 (retain machine identifier)”. An answer that implies “Route seventeen only, change internal ID” fails because Machine identifiers should not be localized into unverified alternative IDs. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 12: Trip-specific alert

Task: A colleague hands you the fictional record “Alert selector names trip T-09” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Only trip T-09 is subject to this alert”. An answer that implies “All trips on this route cancelled” fails because A trip selector narrows scope below the route level. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

Practice 13: No confirmed end

Task: A colleague hands you the fictional record “Closure notice has no confirmed restoration time” and asks for a shorter multilingual public-facing explanation. Write the sentence without seeing the original’s technical heading. Decide which word or number cannot move, which qualifier must remain and whether professional review is needed before a reader acts on it.

Model answer and feedback: A safe backtranslation is “Restoration time not yet confirmed”. An answer that implies “Service resumes in ten minutes” fails because A precise invented reopening time harms passenger planning. For harder practice, state the smallest extra source fact that would make the unsafe rendering valid; if the missing fact is not present, leave it out. This exercise tests controlled inference, not memory of specialist jargon.

A practical bilingual review checklist

First review the document without editing: locate every code, amount, date, direction, time interval, party role, permitted action and unresolved condition. Next read only the translation and write down what a new reader would believe. Compare those two descriptions line by line. Underline places where your translated sentence becomes more certain, more general, more immediate or more directive than the original. Those are potential meaning-changing edits even when the grammar is excellent.

In a second pass, test retrieval. Could a reader using the translated document locate the same field in the underlying record, follow the same official link, identify the same entity and distinguish the same status? If a source has an explicit unknown, unavailable, pending, excluded, estimated or provisional state, give that word an equally visible job in the translation. For numerals, verify the original digits, separator conventions, units, rounding, reference dates and time zones. Never let a presentation change quietly become a new source fact.

In the final pass, assign responsibility. Ordinary language polishing can be completed by a translator; rule-dependent classification or legal consequences must be reviewed by an authorized subject specialist. Record who reviewed the terms, which official version was used and whether an issue remained open. That modest audit trail is more useful than a declaration that the work is “perfect,” because a reader can see how to verify it when the underlying rules are updated.

Frequently asked questions

How does a GTFS Service Alert differ from a TripUpdate?

Service Alerts describe disruptions and rider guidance; TripUpdates communicate actual trip-level arrival and departure changes. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

What does informed_entity mean?

It specifies the service entities a particular alert applies to, including agencies, routes, trips or stops. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Do route_id and stop_id inside one selector mean AND?

Yes; their combination narrows the alert to the specified route at the specified stop. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Are two separate informed_entity entries the same as one combined entry?

No; separate entries can represent separate affected entities. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Does NO_SERVICE always close the full route?

No; the practical scope depends on entity selectors, which should be as granular as possible. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

What is a STOP_MOVED alert?

It tells riders a boarding or alighting stop has moved; the new location and applicable service must remain precise. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Does an accessibility alert mean no trains run?

Not necessarily; an elevator or step-free route can be affected while rail operation continues. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

What is the difference between communication and impact periods?

The first covers when to present the notice and the second describes when service is affected, under current guidance. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Can I translate route IDs and stop IDs?

Keep their machine identifiers exact; only localize approved visible display names. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

Where should passengers verify an alert?

Use the operator’s latest official channels, particularly when an incident is developing. The cross-language test is whether the reader’s answer to the practical question would be the same before and after translation. Preserve evidence that limits the claim, and do not fill gaps with attractive but unsupported certainty. When the choice depends on current official rules or an individual record, consult the issuing authority and qualified reviewer rather than treating this educational guide as approval.

What to practise next

Choose one short real-world public sample from an authoritative source, remove personally identifying information and produce a field map before translating a sentence. Write three lines for each difficult term: what it refers to, what it does not refer to, and how a reader could verify it. Then practise a second language or domain without changing that method. This is the point of transfer: the same discipline that protects one kind of record should help you recognize a different kind of boundary in an unfamiliar text.

For general language foundations, use the eduKateSG Vocabulary Learning Hub to practise precision, meaning and word choice, and How English Works for how sentences, instructions and evidence are interpreted. The present guide is deliberately narrower: it is about the Service Alerts entity of GTFS Realtime, including localized rider messages, entity selectors, impact and communication periods, effects and accessibility information, not the separate TripUpdates feed or general transport fare policy.

Contextual next routes

GTFS TripUpdates and cancellations — read this linked owner when your next question shifts from the specific record type treated here to a related, but distinct, translation or English-learning task. Do not merge the two jobs; compare the boundaries before following the new route.

CAP public emergency alerts — read this linked owner when your next question shifts from the specific record type treated here to a related, but distinct, translation or English-learning task. Do not merge the two jobs; compare the boundaries before following the new route.

Vocabulary Learning Hub — read this linked owner when your next question shifts from the specific record type treated here to a related, but distinct, translation or English-learning task. Do not merge the two jobs; compare the boundaries before following the new route.

How English Works — read this linked owner when your next question shifts from the specific record type treated here to a related, but distinct, translation or English-learning task. Do not merge the two jobs; compare the boundaries before following the new route.

Source standards and authoritative reference routes

GTFS Realtime Service Alerts specification — consult the issuing body’s current edition, changes and definitions. Technical and legal terms should be checked against the effective source version, not inferred from an example or copied from an older secondary summary.

GTFS community implementation guidance and period terminology — consult the issuing body’s current edition, changes and definitions. Technical and legal terms should be checked against the effective source version, not inferred from an example or copied from an older secondary summary.

GTFS Realtime worked examples — consult the issuing body’s current edition, changes and definitions. Technical and legal terms should be checked against the effective source version, not inferred from an example or copied from an older secondary summary.

Educational scope and disclosure: All worked fragments and names in this article are invented. They illustrate translation decisions, not current operational instructions or individual-case advice. Refer to the competent issuer, current standards and qualified domain professionals for real-world approval. Last reviewed for source context: 29 October 2026.

Top Ways to Translate Correctly | Translate GTFS Realtime Service Alerts, Moved Stops and Accessibility Notices Without Misrouting Riders