Signal group numbering is the structured labelling system that traffic engineers use to identify every distinct vehicle and pedestrian movement at a signalised intersection. Without it, describing a right-turn phase from the northbound approach, or a pedestrian crossing on the southern leg, becomes a string of words that is open to misinterpretation between design, commissioning, and maintenance teams. The numbering convention turns those descriptions into a compact, unambiguous reference that survives handover documentation, controller firmware, and field audits.
Bob Panich Traffic Signals works with signal group numbering on every project Bob Panich Traffic Signals designs or delivers. Getting the numbering right at the design stage prevents configuration errors that show up later as conflict faults or rejected timing submissions.
What a signal group actually is
A signal group is a collection of signal heads that always display the same indication at the same time. All heads serving the northbound through movement, for example, operate identically: they turn green together, they go amber together, and they go red together. They form a single group regardless of how many heads are physically installed on the approach.
This distinction matters because a controller doesn't think in terms of individual lamp heads. It thinks in groups. Each output channel in the controller hardware corresponds to one signal group, and the timing plan specifies which groups are active during which phase. Understanding that relationship is part of understanding what signal controller hardware actually manages inside a traffic cabinet.
Pedestrian movements are signal groups too. They sit alongside vehicle groups in the numbering scheme rather than in a separate system. That matters when a pedestrian phase is interlocked with a turning vehicle phase: both appear on the same conflict matrix, using the same numbering convention.
The standard numbering convention
Australian practice follows a convention derived from the Austroads signal design guidelines, where vehicle signal groups are numbered sequentially and pedestrian signal groups are numbered separately. The specifics vary by jurisdiction. In Victoria, for instance, the convention used by VicRoads (now absorbed into the Department of Transport and Planning) allocates vehicle groups in the range of 1 to 32 and assigns dedicated numeric ranges or alphanumeric labels to pedestrian groups. Queensland Transport and Main Roads uses a similar structure with minor labelling differences.
The numbering typically starts from the northbound approach and proceeds clockwise around the intersection. So on a standard four-leg intersection:
- Group 1: northbound through and left
- Group 2: northbound right turn
- Group 3: eastbound through and left
- Group 4: eastbound right turn
- Group 5: southbound through and left
- Group 6: southbound right turn
- Group 7: westbound through and left
- Group 8: westbound right turn
Pedestrian groups typically follow, using P1 through P8 (or equivalent) mapped to the corresponding crossing. A T-intersection drops two vehicle approaches, so it carries fewer groups. A complex multi-leg intersection may push well past Group 12.
Why the starting point and direction matter
The clockwise-from-north convention is a shared assumption. When a controller configuration file, a timing plan, and a signal design drawing all use the same convention, any engineer reading one can immediately cross-reference the others. When they don't, a Group 3 in the design becomes an ambiguous reference in the controller, and the first time that matters tends to be during a fault callout at 2 am.
North is defined by the orientation of the intersection layout drawing, not true magnetic north. On a skewed intersection, the "north" leg is whichever leg the designer nominates as north on the plan. That nomination has to appear explicitly on the drawing and in the handover documentation. If it's left implicit, someone will assume differently.
The same convention governs how signal phase and timing plans are built and adjusted. Timing plan software references groups by number, and every constraint, minimum green, and intergreen interval is expressed in terms of those group numbers. A mislabelled group at the design stage propagates into every subsequent document.
Conflict matrices and the group numbering link
The conflict matrix is where signal group numbering has the most direct safety consequence. The matrix records which groups cannot be simultaneously active because the movements they serve physically conflict. Group 2 (northbound right turn) conflicts with Group 5 (southbound through) because those vehicles cross each other's paths. The matrix captures that as a prohibited simultaneous pair.
A controller reads this matrix at runtime. If a phase sequence attempts to activate two conflicting groups together, the controller rejects it. This is the core logic that conflict monitoring relies on, and it's discussed in detail in the article covering conflict monitoring in traffic signal systems. The key point here is that the matrix is only as reliable as the numbering it references. A transposed group number means the conflict check is applied to the wrong movement.
Intergreens and the numbering system
An intergreen period is the minimum time between one group going red and a conflicting group going green. It gives vehicles time to clear the intersection before opposing traffic enters. Intergreen values are stored in a table indexed by group pairs. Group 2 to Group 5 might require 5 seconds of intergreen; Group 1 to Group 6 might require a different value based on the geometry.
That table has a row and a column for every group. On a large intersection, that's a matrix with hundreds of cells. Accurate group numbering is what makes the table auditable: an engineer reviewing the controller configuration can trace every intergreen value back to a specific pair of movements and verify it against the design geometry.
Maintenance, upgrades, and numbering continuity
Signal group numbers should not change when a controller is replaced or upgraded. They're not internal to the hardware. They're part of the intersection's identity. When a maintenance crew replaces a controller card or loads a new firmware version, the group numbering must carry through unchanged. If it doesn't, every piece of documentation referencing the old numbers is now incorrect, including timing plans, fault logs, and as-built drawings.
This continuity requirement is why group numbering belongs in the design documentation rather than being left to the installation team to assign on site. It needs to be fixed early, agreed by the authority, and protected through every subsequent change. On upgrade projects, Bob Panich Traffic Signals reviews existing group assignments before any controller work begins to confirm the numbering is consistent with both the current design drawings and the jurisdiction's current standard.
Non-standard cases: slip lanes, shared phases, and complex geometry
Not every intersection fits the standard numbering template. Slip lanes that operate under give-way control rather than signal control don't get a signal group, because there's no signal head to control. But if a slip lane is subsequently signalised in a future upgrade, it needs a new group number that fits consistently into the existing scheme.
Shared phases, where two approaching movements (typically left turn and through) are served by the same green indication, are captured as a single group. The design drawing has to make clear which movements are combined, because the conflict matrix implications differ from a phase that only serves one movement.
On complex multi-phase intersections with overlap phases, two groups may operate identically during some phases but differ during others. These are handled through phase logic in the controller firmware, but the group numbering itself remains stable. Each group still has one number, regardless of how its timing varies across the signal plan.
Getting this right at the design stage, before the controller is configured and before the timing plan is submitted for approval, is the point where errors are cheapest to fix. Once a group number is embedded in approved documentation, changing it requires a formal amendment across every document that references it.