Stagger the Timetables
Where two bus routes share a corridor, DTP frequently schedules them to arrive at the same time instead of staggered, halving effective frequency for free. Mandate a statewide audit and correction of every shared-corridor timetable clash.
Adopted by the Fusion Victoria executive before this record was imported into Engage. Source: the original published policy ↗.
- Doubles effective frequency for free
- Statewide, not just Melton
- Zero cost, ministerial fix
DTP is running two buses on the same corridor at the same time and calling it two services. Melton commuters get the frequency of one.
Where two bus routes share a corridor, DTP frequently schedules them to arrive at the same time instead of staggered, halving effective frequency for free. Mandate a statewide audit and correction of every shared-corridor timetable clash.
What it does
- Doubles effective frequency for free — Staggering two routes that already run the same corridor turns two simultaneous 40-minute services into one effective 20-minute corridor, no new buses required.
- Statewide, not just Melton — Melton's 457 and 459 are the clearest example, but DTP has never audited how many other shared corridors have the same clash.
- Zero cost, ministerial fix — This is a scheduling correction, not a service increase, deliverable by ministerial direction without a budget line.
Design Rationale
A mandated audit is chosen over a service-by-service fix because the Melton case is unlikely to be the only instance. Wherever two routes share a corridor for even part of their length, unstaggered timetables silently halve the effective frequency residents experience. It costs nothing to correct once identified, but nobody is currently checking for it.
System Interaction
DTP already sets and publishes timetables for every metropolitan and regional bus route; this requires no new systems, only a cross-referencing audit of shared-corridor timing across the existing timetable dataset, followed by rescheduling directives issued through the same process DTP already uses to publish timetable changes.
Economic & Institutional Logic
Because the buses, drivers, and routes are already funded, staggering is a pure efficiency gain: the same operating budget delivers double the effective frequency on affected corridors. It is the cheapest frequency improvement available anywhere in the network, because it requires no new expenditure at all.
Risk & Failure Modes
The main risk is that DTP treats the audit as a one-off exercise rather than an ongoing check. Timetables change regularly, and a new clash can be introduced at the next reschedule just as easily as an old one is fixed. The audit and correction process should be a standing compliance check, not a single pass.
Evidence & Precedent
Pulse or clockface scheduling, deliberately staggering services that share a corridor so combined frequency is even rather than bunched, is standard practice in mature transit networks internationally. Melton's 457/459 pairing is a documented case where this basic principle was not applied despite both routes being run by DTP-contracted operators on published timetables.
Implementation Outline
Sequence 1: Mandate a DTP audit of every shared-corridor pairing statewide, cross-referencing published timetables for services that overlap in time on shared sections. Sequence 2: Publish the audit findings, including every clash identified. Sequence 3: Issue rescheduling directives to correct each clash. Sequence 4: Make the audit a standing annual compliance check, not a one-off.
What it costs
Timetable audit and changes need operational assessment
Paid for by
Use DTP planning capacity, then cost any fleet, driver or connection changes identified by the audit.
Supporting research
Imported wording revision: rev-vic-stagger-the-timetables-49e6ce43e7fe
Adoption record and sources
- Policy identifier
vic-stagger-the-timetables- How it was adopted
- Imported from Imported from Fusion Party Victoria; adopted by the branch executive.
- Source proposal
- No source proposal recorded.
- Ballot result
- No Engage ballot recorded
- Authority
- Fusion Victoria
- Decision event
- Not recorded
- Ratified
- Not ratified through Engage
- Effective
- 22 July 2026
- Published
- 15 November 2026
- Provenance
- Imported from Fusion Party Victoria
- Import basis
- Adopted by the Victorian branch executive. Confirmed by the Engage maintainer on 2026-11-15 that all live Victorian branch policies are ratified and adopted.
- Imported
- 15 November 2026
- Source record
stagger-the-timetables- Adopted amendments
- None recorded
- Published wording revisions
rev-vic-stagger-the-timetables-49e6ce43e7fe