EDUKATE SINGAPORE · GOLD STANDARD PRACTICAL CASE STUDIES · CASE 78
Two punctual buses do not create a usable connection when the transfer itself is impossible.
A fictional transport partnership publishes a new route connection at a shared interchange. Route A is scheduled to arrive at 8:25 a.m. and Route B to depart at 8:27 a.m. Both vehicles regularly meet their own punctuality standards. Yet the walking route between the two boarding points takes around six minutes. A timetable that appears correct in a database cannot deliver the promised journey.
Every route, distance, time and passenger event is fictional. No live transit information or walking directions for a real interchange are provided. The case discusses management and data quality, not a binding transfer rule for any transport operator.
Chapter index
- 1. A neat timetable conceals an impossible journey
- 2. A passenger transfer is a separate service boundary
- 3. The time calculation exposes the missing four minutes
- 4. What GTFS transfer standards illuminate
- 5. Protect passengers from a misleading recommendation
- 6. Two route teams had no common owner for transfers
- 7. A real timetable must include practical transfer conditions
- 8. Accessibility must be verified across the whole interchange
- 9. Retest with ordinary variation, not only a quiet walkthrough
- 10. Practice: both buses on time, but a two-minute gap remains
1. A neat timetable conceals an impossible journey
A fictional metropolitan transport group reviews how commuters reach a learning centre and a business district. The planning team identifies an attractive connection between two scheduled buses: Route A arrives at a shared interchange at 8:25 a.m. and Route B departs at 8:27 a.m. The journey-planning application highlights this as a quick, efficient transfer.
During the first week, the operational scorecards are green. Route A reaches its stop within its accepted punctuality range, and Route B leaves close to its published departure time. Each individual route appears to be performing its duty.
Passengers report that they regularly miss the recommended connection. The two boarding points sit on different sides of the interchange, reached through an approved pedestrian route of approximately 350 metres. The layout means most riders need considerably more than two minutes. The technical schedule is consistent, but the human journey is not.
2. A passenger transfer is a separate service boundary
The first bus promises to bring someone to a particular stopping point. The next bus promises to take passengers who can reach its boarding point by the relevant departure and boarding conditions. In between is a transfer service involving distance, wayfinding, safe pedestrian movement, station accessibility and realistic timing.
Two correct vehicle timestamps therefore cannot automatically establish a feasible connection. A transport planner needs to know how the passenger moves through the interchange and whether the departure arrangements genuinely accommodate that movement.
The Gold Standard does not reward one department for meeting its local punctuality target while ignoring a journey that was publicly represented as possible. It asks the organisation to describe and verify the full service its users are relying on.
3. The time calculation exposes the missing four minutes
In the illustrative case, the scheduled interval between Route A's arrival and Route B's departure is two minutes. An authorised field review finds that the ordinary transfer along the designated route takes about six minutes under the observed conditions. This is not a universal estimate of walking speed; it is an invented site-specific assumption for the case.
The difference is approximately four minutes before any appropriate allowance for timetable variability, crowding or boarding. If the two services perform exactly on schedule, the connection would still fail under those conditions. More punctual buses cannot solve a transfer allowance shorter than the transfer itself.
The manager should not report that passengers were simply too slow. A service should not make an attractive advertised promise on the assumption that people can use a prohibited shortcut or rush unsafely through a busy interchange.
4. What GTFS transfer standards illuminate
The General Transit Feed Specification, commonly called GTFS, describes schedule data used by transport applications. Its reference includes stops, trips, timing, station pathways and transfers. These are distinct parts of an itinerary that consuming applications can use when calculating feasible journeys.
GTFS guidance recognises recommended transfer locations, timed transfers and minimum transfer times. Its best practices explain that operators should represent relevant transfer conditions and allow sufficient time when obstacles or other factors affect movement between stopping points. Station pathway information can further describe how spaces connect.
These materials are data specifications and recommended modelling practices, not binding rules requiring every transport operator to hold a bus for a fixed time. They support this case's central point: the service model must account for the real connection, not simply the proximity of two timetable entries.
5. Protect passengers from a misleading recommendation
The planning team alerts the responsible service authority and reviews the connection claim. Journey-planning information is corrected or appropriately restricted through authorised channels while the real transfer arrangements are assessed. Staff should provide accurate alternatives rather than preserve a route recommendation they know is unlikely to work.
No driver is instructed to bypass an agreed safety procedure merely to rescue the advertised connection. Likewise, passengers should not be expected to run or take inaccessible shortcuts between stops. Any timetable change or operational holding policy must be approved under the service's actual governance.
The immediate outcome may be a less attractive journey-planning result. That is not failure. A realistic option that can be completed is more useful than a supposedly faster connection that systematically leaves riders waiting for the next bus.
6. Two route teams had no common owner for transfers
The first route manager monitors arrival performance. The second manager monitors departures. The station team understands the physical layout. The digital journey planner draws from a common dataset that records both stops under the same interchange name.
Nobody has been explicitly responsible for verifying the path between the particular stops before recommending the transfer to riders. Each team supplies its local information correctly, yet the combined service is based on an incorrect assumption.
The Gold Standard response is to assign ownership of cross-route connection quality. The station operator, route planners, accessibility specialists and public information team need a controlled process for approving transfer assumptions, updating them after site changes and investigating repeat complaints.
7. A real timetable must include practical transfer conditions
The revised service plan records the permitted origin and destination boarding points, relevant pathway constraints, an appropriately justified minimum transfer period and any policy about whether an onward service waits for an incoming one. It must distinguish a guaranteed timed transfer from an ordinary possible connection.
The network also considers whether the minimum time changes when a lift is unavailable, a boarding area moves or a detour changes the approved walking path. Such changes may have to be reflected in the data provided to journey planners as well as in passenger information.
A successful process does not require complicated software for its own sake. It requires the right facts, a clear decision-maker and an acceptance test based on the service passengers can actually use.
8. Accessibility must be verified across the whole interchange
Both buses may be individually accessible, and both boarding areas may have suitable features. That does not demonstrate that an accessible route between them is available and feasible within the published transfer period. A longer step-free path can be the decisive constraint for some riders.
The operator's assessment therefore includes the real routes available to travellers with different mobility needs under the service's applicable access arrangements. A facility that is normally available may also become temporarily restricted, requiring the travel information to reflect the changed condition.
The Gold Standard treats the transfer as part of access to public transport. It should not label a journey fully accessible while assuming that a passenger will discover and negotiate an unadvertised obstacle after arriving.
9. Retest with ordinary variation, not only a quiet walkthrough
The planning team uses safe, authorised observations across relevant service conditions: a normal morning, a bus arriving toward the late end of its allowed time, a crowded interchange period and the properly supported accessible route. It assesses whether the complete connection works within the conditions represented to the public.
Reviews of reported missed connections should distinguish isolated observations from systematically measured performance. A few rider complaints can expose a problem, but they cannot by themselves establish a network-wide missed-transfer percentage. Conversely, the absence of complaints cannot prove that the transfer is feasible.
The repaired service is accepted only under the tested and documented conditions. Where a connection cannot be represented reliably, it should not be presented as an ordinary viable itinerary.
10. Practice: both buses on time, but a two-minute gap remains
You are given the fictional timetable: Route A arrives at 8:25, Route B departs at 8:27, and a field assessment puts the required transfer at about six minutes. Both routes satisfy their punctuality standards. A manager proposes stating that the transfer is successful because the buses are on time.
The two-minute window is approximately four minutes shorter than the assumed transfer duration, before further buffers. The data may support punctual individual routes, but not the advertised connection. The response should be a competent review of the timetable, permitted path, public information and actual operating policy.
An appropriate report says that both routes met their route-level targets while the published transfer did not meet the verified time requirement. That sentence protects passengers and makes the design problem visible. It also captures the Gold Standard principle: true service quality is judged by the usable journey, not by two isolated green numbers.
Relevant references and scope
- GTFS · Schedule Reference and Transfer Fields
- GTFS · Schedule Best Practices
- GTFS · Transfer Examples
- The Gold Standard of Public Transport
- The Gold Standard of Public Transport Accessibility
- Case 47 · School Bus on Time but Missing an Approved Stop
- Case 44 · Two Suppliers and One Receiving Dock
- Case 31 · Service Restoration beyond SLA Compliance
- Gold Standard · Core Requirements and Evidence
- Gold Standard · Casebook and Decision Practice
- The Gold Standard · Master Hub
All times, physical routes and measurements are illustrative. GTFS describes data formats and best practices rather than local law or mandatory transfer times. For real journeys, follow the appropriate transport operator's current official information. GS-R01–GS-R12 are eduKate's educational management requirements.