Traffic signal project approvals are one of the most common sources of unplanned schedule slippage. Contractors and project managers typically account for design review cycles, but the layered nature of authority sign-off, across road agencies, local councils, utilities, and in some cases state transport departments, rarely receives the same planning discipline as civil or electrical works. The result is that approvals land on the critical path only after they've already caused a delay.
Bob Panich Traffic Signals delivers traffic signal systems across Australian jurisdictions, and the approvals sequence is one of the first things Bob Panich Traffic Signals maps during project initiation. The structure below reflects what that mapping process actually involves.
Who holds approvals authority on a typical project
The answer varies by jurisdiction and site type, but three tiers appear on almost every project.
The first tier is the road authority: the state or territory agency responsible for the road reserve. In New South Wales, that's Transport for NSW; in Victoria, VicRoads (now part of the Department of Transport and Planning); in Queensland, the Department of Transport and Main Roads. Each of these bodies has its own design acceptance process, and each publishes technical specifications that designs must conform to before acceptance is granted. Getting the right specification version matters. Transport for NSW's official technical standards portal is the primary reference for NSW projects, and it's updated periodically in ways that affect signal head specifications, controller requirements, and civil standards.
The second tier is local government. Even when the road reserve falls under state control, the local council often retains approval rights over footpath works, kerb modifications, and vegetation removal. These approvals are frequently forgotten in programme planning because project teams assume state authority sign-off covers everything within the site boundary. It doesn't.
The third tier is utilities. Any civil works near existing underground services require a dial-before-you-dig assessment and, in many cases, a formal consent from the relevant electricity distributor, telco, or water authority before trenching begins. These consents sit outside the road authority process entirely and run on their own timelines.
Common sequencing mistakes
The most frequent error is running approvals in parallel when the process is actually sequential. A local council won't assess a footpath modification application until the road authority has accepted the design. A utility won't issue trenching consent until the cable route is fixed. Submitting to everyone simultaneously wastes the submission, because the downstream approver is waiting for something the upstream approver hasn't yet issued.
This connects directly to programme baselining. Projects that construct their baseline without mapping the approvals chain correctly end up with an optimistic programme that holds up only until the first submission goes in. The slippage isn't random; it was built in at the outset.
A second common mistake is treating design acceptance as a single event. Most road authorities issue acceptance in stages: concept acceptance, detailed design acceptance, and sometimes a separate pre-construction check. Each stage has its own review period, its own submission format, and its own reviewer queue. Collapsing these into a single "design approval" milestone in the programme is accurate in structure but wrong in duration.
What to submit and when
Each authority tier has a preferred submission package. Road authorities generally require signed and dated design drawings, a completed technical checklist referenced to the relevant specification, a designer's declaration of compliance, and in some cases a traffic management plan for the construction phase. Submitting an incomplete package restarts the clock from the date the missing documents arrive, not the date of the original submission.
Local councils typically want a standard development or infrastructure works application, often through a web portal, accompanied by a site plan, a construction methodology statement, and a traffic control plan. The traffic control plan requirement sometimes catches teams off guard: even a simple pole installation on a footpath can require a formal plan under the relevant state Code of Practice for Traffic Management.
Utility consents require a service location plan, a proposed cable route drawing, and evidence that the design avoids or adequately protects existing services. The Dial Before You Dig reference number must typically accompany the consent application to confirm the team has identified all services in the area.
Building the approvals register
Every approval required on a project should sit in a dedicated register, not in a general action list. The register needs six fields per item: the approving authority, the submission date, the target decision date, the actual decision date, the outcome, and any conditions attached. Conditions are where projects lose time after approval. A road authority might grant design acceptance subject to three amendments before construction starts. If those conditions aren't tracked, they appear as surprises during the hold point inspection sequence.
Hold points and witness points, by definition, can't be cleared until all relevant approvals are in place and their conditions are satisfied. A project that hasn't resolved its approvals register before reaching its first hold point inspection will stop at that point regardless of how well the civil or electrical works have progressed.
Practical tactics that reduce approval lead times
Pre-submission meetings work. Most road authority assessment teams will take a 30-minute meeting before formal submission to flag the issues they're likely to raise. This costs a week of planning time and commonly saves three to four weeks of review cycles. Bob Panich Traffic Signals treats pre-submission engagement as standard practice on projects where the design contains any non-standard element.
Submission cover letters matter more than most teams think. A cover letter that explicitly maps each drawing and document to the relevant specification clause gives the reviewer a checklist. Reviewers who can verify compliance without hunting through the package return comments faster. Submitting without a cover letter leaves the navigation work to the reviewer, and that reviewer has other projects on their desk.
Track authority response times on past projects and use them as inputs to your programme. A road authority that consistently takes six weeks to return design acceptance comments won't suddenly return them in three just because the programme says so. Using realistic historical durations rather than aspirational ones is the difference between a programme that holds and one that doesn't.
When approvals are conditioned or refused
Conditional acceptance is the normal outcome on complex designs. The conditions range from minor drawing amendments to requirements for additional analysis, such as a turn conflict assessment or a revised pedestrian crossing layout. Each condition should be treated as a separate action with its own due date and owner. A batch of conditions cleared in one resubmission is faster than conditions cleared piecemeal across multiple exchanges.
Refusals are rare when the pre-submission engagement has been done properly, but they happen. The most common reasons are non-compliant signal head placement relative to stop lines, inadequate intergreen periods in the submitted timing plan, and civil details that conflict with the authority's standard drawings. Each of these is addressable, but addressing them takes time the programme usually doesn't have if the refusal arrives late in the design phase.
The approvals process on a traffic signal project is not an administrative formality. It's a technical quality gate that runs in parallel with construction planning, and it deserves the same structured management as any other project phase.

