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

Smart Traffic Infrastructures

Turn-phase sequencing: how signal controllers order competing movements

Turn-phase sequencing governs the order in which a signal controller serves competing movements at an intersection, and getting it wrong costs more delay than almost any other timing decision.

An aerial view of a bustling urban intersection with vehicles and people crossing.

Photo by CK Seng on Pexels

Turn-phase sequencing is the engineering decision that determines the order in which a traffic signal controller grants right-of-way to competing movements at an intersection. Where signal timing plans set how long each phase runs, sequencing decides which movements run together and in what order. It's a distinction that matters: two intersections with identical phase durations can perform very differently depending on how their sequences are arranged.

What turn-phase sequencing actually controls

At any signalised intersection, movements fall into three categories: through traffic, turning traffic, and pedestrian crossings. The controller must serve all of them without creating conflict. Sequencing is the logic that resolves which movements are compatible enough to run simultaneously and which must be separated by an intergreen period.

Right turns (in Australian practice, turns across opposing traffic) receive particular attention. A right-turn movement that conflicts with oncoming through vehicles cannot run concurrently with the opposing through phase. The controller must either protect the turn with its own exclusive phase, permit it on a permissive basis after the opposing green has cleared, or run it in a lead or lag arrangement relative to adjacent phases. Each option carries a different delay penalty and a different safety profile.

Left turns are generally compatible with adjacent through movements, but not always. At high-pedestrian-volume locations, a left turn that conflicts with a pedestrian crossing phase requires its own sequencing decision. Bob Panich Traffic Signals designs sequencing arrangements that account for pedestrian demand data, not just vehicle counts, to avoid under-serving crossings at busy urban intersections.

Protected, permissive, and protected-permissive arrangements

The three standard sequencing arrangements for turning movements each carry distinct trade-offs.

A protected phase gives the turning movement an exclusive green period with no conflicting traffic. It is the safest arrangement and the most capacity-expensive: the intersection must serve one movement at a time, consuming green time that could otherwise be shared. Protected phasing is appropriate at intersections with high turning volumes, poor sight distances, or a history of right-turn conflicts.

A permissive arrangement allows turning vehicles to move through gaps in opposing traffic during a shared green phase. It consumes no additional cycle time but creates exposure to conflict. Drivers must judge gaps correctly under time pressure, and peak-hour conditions often reduce usable gap frequency to the point where turning queues build despite having notional green time available.

Protected-permissive sequencing combines both. The turning movement receives an exclusive protected phase, then continues on a permissive basis during the opposing through phase. This arrangement recovers some of the capacity lost to exclusive phasing while maintaining a safety margin during the period of highest opposing volume. The sequencing challenge is deciding whether the protected phase leads the opposing through movement (a leading phase) or follows it (a lagging phase), since each produces different gap characteristics and queue dissipation patterns.

Leading versus lagging protected phases

The lead-lag question is one of the more consequential sequencing decisions at a multi-lane intersection, and it doesn't have a universal answer.

A leading protected right-turn phase clears the turning queue before opposing through traffic arrives. Drivers waiting in a dedicated right-turn bay move first, the bay empties, and then the opposing green releases. This arrangement works well when right-turn queues are long and the bay is short: it prevents overflow back into the through lane. It also benefits from having the turn complete before opposing vehicles build speed through the intersection.

A lagging phase runs the protected turn after the opposing through movement. Opposing traffic has already cleared when the turn phase begins, which can improve the permissive window if the protected phase follows. Lagging arrangements can cause driver confusion at intersections where the display sequence is unfamiliar, particularly where dual-turning bays exist. Bob Panich Traffic Signals evaluates both options during the sequencing design stage using turning-movement count data to identify which arrangement minimises total intersection delay rather than just right-turn delay.

Split phasing is a third option used at T-intersections or locations with severe geometry constraints. Each approach receives its own exclusive phase, with no concurrent movements. It resolves sequencing complexity at the cost of significantly longer cycles and higher average delay across all movements.

How sequencing interacts with adaptive control

Fixed sequencing applies the same movement order every cycle. Adaptive signal control introduces real-time variation: the controller can extend or shorten individual phases based on detector data, but in most deployed systems the sequence order itself remains fixed. The controller adjusts durations within a predetermined sequence rather than reordering movements dynamically each cycle.

Some advanced adaptive systems do alter sequencing in response to demand. If right-turn demand drops below a threshold, the controller may skip the protected phase entirely for that cycle, serving the movement on a permissive basis instead and reclaiming the saved time for through movements or pedestrians. This phase skipping requires careful configuration to avoid displaying unexpected signal sequences to waiting drivers, which creates its own safety risk.

Coordinated corridor timing adds further constraints. A signal that runs as part of a green wave corridor must maintain a fixed offset relationship with its neighbours. Changing sequencing at one intersection can disrupt band integrity across multiple signals, meaning sequencing decisions rarely exist in isolation on an arterial route.

Sequencing at complex intersections

Multi-leg intersections with five or more approaches, staggered crossings, or significant pedestrian flows require sequencing schemes that go beyond standard four-phase arrangements. Bob Panich Traffic Signals works through these configurations using phase compatibility matrices: a structured tool that maps every movement pair against its conflict status, and then derives the minimum number of phases needed to serve all movements without conflict.

The matrix approach makes explicit which combinations are physically safe to run simultaneously and which cannot be. It also surfaces opportunities to combine movements that engineers might otherwise sequence separately out of caution. At a complex intersection, discovering that two movements previously run in separate phases are actually compatible can cut cycle length by 10 to 15 seconds, which compounds significantly across a peak-hour period.

Sequencing also interacts with saturation flow rate in a way that affects capacity calculations directly. A protected right-turn phase that discharges at a lower saturation flow rate than the adjacent through movement will take longer to serve the same number of vehicles. Engineers who treat saturation flow as a single intersection-wide constant risk under-designing turn bays and over-estimating throughput on restricted movements.

Common sequencing errors in practice

The most frequent mistake Bob Panich Traffic Signals encounters in existing installations is the use of protected phasing where turning volumes don't justify it. Protected phases installed as a conservative default consume green time that produces no measurable safety benefit at low-volume locations, extending cycle times and increasing average delay for all movements. The opposite error also occurs: permissive-only arrangements at high-speed, high-volume locations where gap acceptance becomes unreliable during peak periods.

A second common error is failing to revisit sequencing after land use changes. A residential-area intersection sequenced for predictable commuter flows may develop significant right-turn demand as surrounding land is redeveloped for retail or mixed use. Sequencing that was appropriate at commissioning may be actively counterproductive three years later. Periodic turning-movement surveys, not just timing reviews, are the mechanism that catches this drift before it manifests as congestion or conflict.

Documenting the rationale for sequencing decisions is a step that gets skipped on compressed project timelines. When a future engineer reviews an installation without that documentation, they're left inferring intent from the configuration itself. Adaptive signal control systems in particular accumulate sequencing logic across software updates, and without a clear design record the original intent can be obscured by incremental changes.

What good sequencing design looks like

Bob Panich Traffic Signals approaches turn-phase sequencing as a system-level decision rather than an intersection-level one. Movement compatibility matrices, turning-count data, pedestrian crossing demand, corridor offset requirements, and saturation flow estimates for each turning movement all feed the design before a sequence is confirmed. The result is a configuration that serves peak demand without over-provisioning phases during off-peak periods, and that can be adjusted efficiently when demand patterns shift.

Sequencing documentation covers the rationale for each phase arrangement, the turning volumes that informed the protected or permissive decision, and the conditions under which the sequence should be reviewed. That record is as much a deliverable as the configuration file itself.