Licensed & insured Open today โ€” +1 000 000 0000
๐Ÿ“ž Call now

Smart Traffic Infrastructures

Transit signal priority: how buses and trams get a green light

Transit signal priority gives buses and trams preferential green time at signalised intersections, cutting delays without dedicating separate rights-of-way. Understanding how it works helps engineers and planners deploy it where it counts.

A city bus stopped at a traffic light during the night in an urban downtown setting.

Photo by Brett Sayles on Pexels

Transit signal priority (TSP) is one of the more cost-effective tools available to transport authorities trying to improve public transport reliability on existing road networks. Rather than building dedicated tram tunnels or bus rapid transit corridors, TSP uses communication between the approaching vehicle and the signal controller to extend a green phase, cut a red short, or insert a priority phase altogether. The result is measurable travel-time savings for passengers without the capital cost of grade separation.

What transit signal priority actually does

TSP works by modifying normal signal timing in response to a request from a transit vehicle. There are two main modes of operation. Passive TSP uses pre-set timing plans optimised around known transit schedules; it doesn't respond to individual vehicles in real time. Active TSP does: it detects an approaching bus or tram, checks whether the vehicle is running late or on schedule, and then adjusts the current phase accordingly.

The two standard responses are green extension (holding a green phase that would otherwise end) and early green (advancing the start of the next green phase). A third technique, phase insertion, creates a dedicated transit phase in the signal cycle. Phase insertion is used less frequently because it introduces more disruption to general traffic, but it's appropriate on high-frequency corridors where tram bunching is a persistent problem.

Crucially, TSP doesn't override the intersection. It works within the constraints set by the signal controller and, in networked environments, within the constraints of the broader adaptive signal control system managing corridor-wide progression. Priority is conditional, not absolute.

How the vehicle communicates with the signal

The detection layer is where TSP deployments vary most. Four technologies are in common use across Australian networks.

  • GPS with transit management systems. The vehicle's onboard GPS unit reports its position to a central transit management platform, which compares actual position against the timetable and sends a priority request to the traffic signal controller via a data network. Latency is the main limitation; requests must arrive early enough for the controller to act.
  • Dedicated short-range communication (DSRC) / V2I. A roadside unit mounted near the intersection exchanges data directly with a transponder on the bus or tram. Response is faster than GPS-based systems and doesn't depend on network reliability. This approach aligns with the broader V2X communication framework being deployed on smart corridors.
  • Infrared emitters. An emitter on the front of the vehicle triggers a detector mounted on the signal mast. Simple and proven, but limited to line-of-sight detection with no position or schedule data attached to the request.
  • Loop detectors in the road surface. Used on tram networks in particular, in-ground loops identify the tram as it crosses a detection zone. Reliable but inflexible; they can't carry schedule-adherence data, so the signal responds to every vehicle regardless of whether it's on time.

Conditional priority and schedule adherence

Unconditional TSP, where every approaching bus gets priority regardless of punctuality, creates two problems. It undermines the benefit: a bus that's already 5 minutes early doesn't need priority, and giving it one disrupts cross-traffic for no passenger benefit. It also degrades cycle-level performance across the intersection over time as compensatory phases accumulate.

Conditional TSP uses schedule-adherence data to filter requests. A vehicle that's on time or early receives no priority. A vehicle that's running late by more than a threshold (typically 60 to 90 seconds) triggers a request. The controller then evaluates the request against phase constraints before acting. This design requires the transit vehicle to carry real-time schedule comparison capability, which ties TSP implementation back to the quality of the transit management system feeding it.

For tram networks operating on mixed traffic corridors, schedule adherence is harder to enforce and bunching is a more common failure mode. In those cases, some operators set tighter thresholds and permit more frequent phase insertions during peak periods.

Integration with signal controller infrastructure

TSP doesn't operate in isolation. The signal controller at the intersection must be capable of receiving and processing a priority request mid-cycle. Older fixed-time controllers can't do this without hardware upgrades. Modern controllers running SCATS (Sydney Coordinated Adaptive Traffic System) or SCOOT (Split Cycle Offset Optimisation Technique) can accept TSP inputs, but the integration must be configured against each intersection's timing plan to avoid unintended phase conflicts.

Bob Panich Traffic Signals designs TSP integration as part of the signal controller specification, not as an add-on. Getting signal phase and timing plans right before layering in TSP logic is essential; a poorly structured base plan amplifies rather than absorbs the disruption that priority requests introduce.

On multi-intersection corridors, TSP coordination becomes a network-level problem. A priority request that extends green at intersection A may need to be propagated downstream to preserve the transit vehicle's progression through intersections B and C. This is sometimes called transit signal progression, and it requires the signal management system to hold a model of corridor timing rather than treating each intersection independently.

What TSP delivers in practice

Travel-time reductions from active TSP on Australian bus corridors have been reported in the range of 5% to 15% depending on corridor characteristics, fleet penetration, and the base reliability of the schedule. Tram networks in mixed traffic see larger gains where bunching is the dominant problem. Passenger experience improvements compound over time as reliability rebuilds ridership confidence.

The technology doesn't eliminate the need for good network design. TSP on a corridor plagued by poor bus stop placement or inadequate dwell-time modelling will underperform. Signal priority buys time at the intersection; it doesn't fix upstream causes of lateness.

For transport authorities and councils assessing TSP as part of a broader smart intersection design programme, the strongest deployments combine active priority with conditional logic, GPS-based schedule awareness, and controller hardware that can act on requests within a single phase cycle. That combination delivers consistent, measurable benefit without degrading general traffic flow beyond acceptable tolerances.

Bob Panich Traffic Signals supplies and integrates TSP-capable signal controller systems across Australian road networks, working with transport authorities and civil engineers from specification through to commissioning.