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

Electronic Signalling Systems

Signal phase diagrams: how to read and draw them correctly

Signal phase diagrams are the primary documentation tool for describing how movements are grouped and sequenced at a signalised intersection. Reading and drawing them correctly is a foundational skill for anyone specifying or reviewing a signal design.

Detailed close-up of architectural blueprints with scale ruler, showing building plans and measurements.

Photo by John Guccione www.advergroup.com on Pexels

Signal phase diagrams sit at the centre of almost every traffic signal design package, yet they're frequently misread by people who didn't draw them, and poorly drawn by people who did. The diagram is a compact representation of which vehicle and pedestrian movements are permitted simultaneously, how those movements are grouped into phases, and in what sequence those phases run. Getting it wrong in documentation means the controller gets programmed differently from what the designer intended, and that gap doesn't always show up until commissioning.

What a signal phase diagram actually shows

A phase diagram depicts the intersection as a plan view, with approach lanes labelled by direction. Each phase is shown as a numbered or lettered block, with arrows indicating the movements that run during it. Solid arrows denote protected movements; dashed arrows denote permitted movements that run concurrently with conflicting traffic (typically a permitted right-turn across an opposing stream). The sequence of phases is usually shown left to right, in the order the controller cycles through them.

The diagram does not show timing directly. It doesn't tell you how long each phase runs. That detail lives in the timing plan, which references the phase numbers shown in the diagram. The two documents work together: the phase diagram defines the structure, the timing plan fills in the durations. Confusing the two is a common source of errors during design review, and it's worth understanding how timing plans are built and when they change alongside the phase structure itself.

Conventions for drawing phase diagrams in Australia

Australian practice follows conventions set out in state transport authority specifications, with Transport for NSW and its equivalents in Victoria and Queensland each publishing their own drafting standards. The core conventions are consistent across jurisdictions:

  • North is typically oriented to the top of the diagram, or the primary approach is placed at the bottom.
  • Signal groups are numbered sequentially, with vehicle phases typically using numbers and pedestrian phases using letters or separate numbering blocks.
  • Each phase block shows only the movements that are active in that phase, not the full intersection layout.
  • Intergreen periods are not shown on the phase diagram itself; they appear on the signal timing sheet.

One point that causes persistent confusion: a movement appearing in two phases does not mean it runs twice. It means that movement is served across multiple phases, usually because demand on that approach warrants split service, or because the movement is compatible with traffic in more than one phase. The diagram must make this unambiguous through consistent arrow styling.

How phase numbering connects to the controller

The phase numbers on a diagram aren't arbitrary labels. In most Australian signal controllers, phase numbers map directly to hardware outputs and software tables. Phase 1 in the diagram corresponds to Phase 1 in the controller configuration, which triggers specific lamp driver outputs. If the diagram labels a movement as Phase 3 but the controller programmer interprets it as Phase 2, the result can be conflicting movements running simultaneously, which is precisely what conflict monitoring hardware is designed to catch. Understanding how conflict monitoring works in traffic signal systems clarifies why accurate phase documentation is a safety issue, not just a paperwork one.

This is also why signal group numbering conventions matter. The labels used on the phase diagram must be consistent with the labels in every other design document: the wiring schedule, the controller software tables, and the as-built drawings.

Common errors in phase diagrams

Three errors appear repeatedly in design reviews.

First: missing pedestrian phases. Vehicle movements get carefully diagrammed, but the pedestrian signal groups are added as an afterthought or omitted entirely from the phase diagram, then specified separately in a pedestrian signal schedule. When the two documents don't align, the pedestrian phase timing ends up disconnected from the vehicle phase structure it depends on.

Second: unlabelled permitted turns. A dashed arrow on its own says a movement is permitted. It doesn't say which opposing movement it conflicts with, or what the assumed gap acceptance is. A reviewer seeing only the diagram can't assess whether the permitted movement is safe without cross-referencing the intersection geometry. Good practice is to annotate permitted turns with the conflicting flow reference.

Third: phase sequence shown as absolute rather than conditional. Many controllers run conditional phase sequences where phase B only runs if demand is detected on a particular approach. A static phase diagram shows phases as if they always run in the drawn order. If the diagram doesn't distinguish between mandatory phases and demand-dependent phases, the programmer may configure an unconditional sequence where a demand-activated one was intended.

Reading a phase diagram you didn't draw

When reviewing a phase diagram produced by someone else, start by confirming four things. Check that every approach lane has at least one phase serving it. Check that no two phases shown as simultaneous contain conflicting movements. Verify that pedestrian phases are shown and that their active periods align with phases that stop conflicting vehicle traffic. Finally, confirm the phase sequence is complete: that the diagram accounts for all turning movements, including U-turns where permitted, and doesn't leave any approach unserved in the cycle.

If the diagram shows an intersection with more than 4 phases, work through each pair of simultaneous phases explicitly. Complex intersections with slip lanes, right-turn arrows, and bus priority phases can generate 6 or 8 phases, and the number of potential conflicts grows quickly. A methodical check against the conflict matrix is faster than trying to visualise it from the diagram alone.

Keeping phase diagrams current through the project lifecycle

Phase diagrams produced at concept design are rarely identical to those produced at detailed design, and detailed design diagrams often differ from what gets installed. Changes to turning movement restrictions, lane configurations, or pedestrian crossing locations alter the phase structure. Each revision needs to be formally logged and re-issued, with the revision number marked clearly on the drawing.

At construction, any field change that affects a phase, even something as small as adding a pedestrian phase at a slip lane, must feed back into a revised diagram before commissioning. A phase diagram that reflects the designed intent but not the built outcome is an as-built documentation failure, and those failures surface during fault diagnosis and future modifications, often years later.

Bob Panich Traffic Signals prepares and reviews signal phase diagrams as part of detailed design documentation for traffic signal projects across Australia, ensuring the phase structure, group numbering, and sequence logic are consistent from design through to controller programming and handover.