If you are preparing a Development Application in Sydney, the traffic report supporting it is a common place for avoidable delay to start. Councils rarely disagree with the traffic engineering itself. Far more often the report is missing something the reviewer expected to see, does not match the rest of the DA, or takes too long to make sense of. All three are fixable before you lodge.
What Councils Check in a Traffic Impact Assessment
As part of the DA process, a council reviewer is generally working through four questions:
- Does it cover the right ground? Existing conditions, traffic generation, parking, access and circulation, and pedestrian and cyclist safety.
- Does it match the rest of the DA? The same unit counts, the same parking numbers, the same site layout as the architectural and civil plans.
- Are the assumptions explained? Stated and justified, rather than asserted as bare figures.
- Can it be assessed quickly? Organised, clearly labelled, and easy to navigate.
A report that falls short on any one of these is the kind most likely to come back as a request for further information.
What the Report Needs to Cover
Formats vary between consultants, but the substance a reviewer looks for does not move around much. These are the categories that come up again and again.
Existing traffic and road network context
A reviewer wants to see that the report understands the site before it proposes anything: the surrounding road network, how traffic moves around the site today, and any known constraints such as nearby intersections, sight lines, or sensitive uses. Without it, the rest of the report has nothing to sit on.
Traffic generation and parking
This is the technical core. How much additional traffic the development is expected to generate, and whether the parking provided suits the proposed use. Reviewers are reading for the reasoning as much as the totals.
Access, circulation and vehicle movements
How vehicles get in and out, how they move once inside, and whether service and delivery vehicles can do both safely. For larger or more constrained sites this is usually supported with swept path or turning movement analysis.
Pedestrian and cyclist safety
A development needs to be assessed for how people move around and across the site frontage, not only for how cars do. This is one of the more commonly thin sections in an otherwise solid report.
Construction traffic, and where it belongs
Construction phase traffic is usually dealt with in a separate Construction Traffic Management Plan rather than in the traffic report itself. It is still worth a short cross reference, so a reviewer can see the construction phase has been considered even though the detail sits elsewhere.
What Gets a Report Sent Back
Three things decide how smoothly a report moves through review, and none of them are about whether the traffic engineering is correct. They are about whether a reviewer can confirm that it is.
Consistency with the rest of the DA
A reviewer will read the traffic report against the architectural and civil plans and expect the numbers to agree. The most common version of this problem is a parking count in the traffic report that does not match the count on the plans. It says nothing about the quality of the traffic work, and it is one of the most avoidable triggers for a request for further information.
Assumptions that are stated, not just asserted
A trip generation figure quoted with no indication of where it came from puts a reviewer in an awkward position: they cannot agree with reasoning they cannot see. A report that states an assumption and explains the basis for it reads very differently, even to a reviewer who might have chosen a slightly different assumption.
A report a reviewer can actually work through
Clear structure, labelled figures, and a logical order get a report through review faster than one that is technically sound but hard to follow. Two versions of this show up often: access and circulation described in prose but never shown on a plan, and a report that reads as a template rather than a response to this particular site.
Where a Traffic Engineer Fits In
A traffic engineer’s job on a DA is to turn the specifics of your site, the existing road network, the proposed use, the parking and access arrangements, into a report that covers the ground above and holds up against everything else you lodge. If you already have a draft report, or you are still briefing a consultant, it is worth checking it against these points while there is still time to change something. TTPA prepares and reviews traffic impact assessments for developments across Sydney and NSW.
Frequently Asked Questions
Does every DA need a full traffic impact assessment?
No. The depth of assessment generally scales with the scale and traffic intensity of the proposal, and with what the consent authority asks for in your case. A smaller or lower intensity proposal may only need a shorter traffic statement rather than a full assessment. It is worth confirming which applies before commissioning the work, because preparing the wrong one costs time either way.
Why would a council ask for further information on a report that looks complete?
Usually for one of the three reasons above rather than a disagreement about the traffic engineering: the report conflicts with another document in the application, an assumption is unexplained, or the reviewer cannot follow it well enough to sign it off.
Is construction traffic covered in the same report?
Generally no. Construction phase traffic is usually addressed in a separate Construction Traffic Management Plan. The traffic report should still cross reference it so a reviewer can see it has been considered.
Who prepares a traffic impact assessment?
A traffic engineer or traffic consultant, working from the architectural plans and the proposed use. On most DAs they also review the final report against the rest of the application before it is lodged.
If you are not sure whether your current report or brief covers what a reviewer expects, it is worth having it checked before you lodge, while gaps are still cheap to fix.
This article is general information about the DA process and is not legal or planning advice for a specific site or application.
Recent Comments