Study
Connecting Traffic Assessment
Whether through-passengers justify a stop, a wait, or a change of vehicle — once dwell time and missed connections are counted.
Who it is for
Network planners and franchise teams who hear that ‘connections make the stop worthwhile’ and want the file to agree or disagree.
What you leave with
A count of true through journeys versus local boarders, with a caution on connections that look sold but arrive too late to be useful.
Scope
One hub or one timed connection (for example a rail arrival into a coach departure). Two hubs need a separate assessment.
Included
- Join of inbound and outbound records where a passenger or itinerary key exists
- Dwell-time bands and a miss-rate estimate from timed files
- A plain-English note on whether the connection is carrying the stop
- Sixty-minute briefing
Not included
- Timetable rewriting
- Union roster negotiations
- Passenger compensation calculations
Who does the work
Systemcraftpoint.
How the study runs
- Map the connection you care about and the keys in both extracts.
- Reconcile clocks and operating days.
- Count through versus local; flag implausible dwells.
- Brief the planning lead.
What to prepare
Two extracts with timestamps. If through tickets are a separate product, include them rather than only local singles.
Limits we will not paper over
Cash walk-up tickets with no itinerary key cannot be joined; we will say so rather than guess.
Next step
Name the hub, the two services, and whether through fares exist.