SIDRA Traffic Modelling for Development Approval

A proposed development can appear straightforward until its additional vehicle movements meet a constrained intersection, a busy driveway or a peak-period queue. SIDRA traffic modelling gives the project team a structured way to test those conditions before they become an approval issue, design change or operational complaint.

For architects, planners and developers, the purpose is not simply to produce a level of service table. A properly scoped model helps determine whether a scheme can operate safely and acceptably within its surrounding road network, and what practical changes may be required to support an approval-ready outcome.

What SIDRA traffic modelling assesses

SIDRA Intersection is traffic analysis software widely used across Australia to assess the operational performance of intersections. It can model priority-controlled intersections, roundabouts, traffic signals, pedestrian crossings and other common intersection layouts. For a development application, it is generally used to compare existing conditions against future scenarios that include development-generated traffic.

The analysis typically considers measures such as average delay, level of service, degree of saturation, queue lengths and the 95th percentile queue. These outputs help identify whether traffic will clear efficiently through an intersection or whether queues may extend to a nearby driveway, roundabout, signalised junction or pedestrian crossing.

The model is particularly relevant where a proposal will add traffic during the morning or afternoon commuter peak, or during a site-specific peak. A childcare centre, supermarket, medical facility, school, hospitality venue or industrial development may have peak demand that does not align neatly with the standard road network peak. Selecting the correct assessment period is therefore as important as operating the software itself.

A SIDRA model does not replace engineering judgement. It is a decision-support tool based on defined inputs and assumptions. Its value lies in applying those inputs carefully, interpreting the outputs in the context of the site, and setting out recommendations that authorities and project teams can act on.

When a development needs a SIDRA assessment

Whether SIDRA traffic modelling is required depends on the scale and type of development, the characteristics of the surrounding network and the requirements of the consent authority. Councils may request it through pre-lodgement advice, development control plans, traffic impact assessment guidelines or a request for further information. For larger or more complex projects, it may form part of an environmental impact statement or State Significant Development application.

It is commonly warranted where development traffic will use an already constrained intersection, where a new access point is proposed close to an intersection, or where background traffic growth and committed development need to be considered. Modelling can also be useful for a rezoning or feasibility assessment, when the project team needs to understand whether the intended yield is likely to trigger road upgrades or access constraints.

A small proposal does not automatically avoid the need for analysis. A modest number of additional trips can matter on a narrow local road, at a poor-performing roundabout or near a school crossing. Conversely, a larger development may have limited impact where it is well connected to a higher-capacity road network and its traffic is distributed across several directions.

The question is not only how many trips the site generates. It is where those trips go, when they travel, how they enter and exit the site, and whether the surrounding intersections can accommodate them without an unacceptable safety or operational outcome.

Building a defensible SIDRA model

A reliable model begins well before the analyst enters traffic volumes. The assessment needs a clear understanding of the proposed development, the road network and the authority requirements. Early coordination with the architect and planner is useful because changes to access location, basement entry, loading arrangements or land use mix can materially affect the modelling scope.

Establish the right scenarios

Most assessments examine at least an existing scenario and a future scenario incorporating development traffic. Depending on the project, additional scenarios may include an opening year, a design horizon, approved but unbuilt developments, background traffic growth, changed road layouts or proposed mitigation works.

This is where a one-size-fits-all approach can create problems. Modelling only the current network may understate a future issue where nearby development is already approved. Equally, applying broad growth assumptions without evidence can overstate impacts and lead to disproportionate recommendations. The scenario framework should be proportionate, transparent and aligned with available strategic traffic data and authority guidance.

Use representative traffic data

Traffic counts should reflect normal operating conditions. Counts undertaken during school holidays, major events, wet weather or roadworks may not represent a typical weekday peak. The data also needs to capture turning movements at the relevant intersections, rather than relying solely on total road volumes.

For signalised intersections, signal phasing, cycle times, green splits and pedestrian phases need to be confirmed. For roundabouts and priority intersections, lane configuration, lane use, approach geometry, parking restrictions and observed driver behaviour can all influence performance. A desktop layout that differs from the built condition can produce misleading results.

Development traffic generation should be based on a credible source and tailored to the proposal. The consultant may apply recognised rates, survey comparable sites or review operational information supplied by the operator. For mixed-use developments, trips should be considered by land use and time period, with appropriate allowance for internal trips or pass-by trips where this can be reasonably justified.

Test access and network interactions

The nearest major intersection is not always the only location that matters. A proposed driveway can affect traffic flow through a nearby roundabout, while queues at a signalised junction can prevent vehicles from entering or leaving the site. In dense urban settings, kerbside activity, bus stops, loading zones, pedestrian movements and restricted turning movements may be equally important.

For this reason, SIDRA analysis is often undertaken alongside swept-path analysis, driveway grade assessment, parking and loading design review, and a broader traffic impact assessment. Each task answers a different question. SIDRA tests intersection operations, while swept-path analysis demonstrates whether the relevant design vehicle can physically manoeuvre through the access and servicing layout.

Reading results beyond level of service

Level of service is a familiar metric, but it should not be treated as a pass-or-fail test in isolation. A lower level of service at a constrained Sydney intersection may reflect established peak-period conditions rather than an impact created by the development. The key consideration is often the scale of change caused by the proposal, the practical ability to mitigate it and the consequences for safety and network function.

Queue results require the same care. A modelled queue may be acceptable where there is sufficient storage length, but problematic if it blocks a driveway, spills through a roundabout or interferes with a pedestrian crossing. Degree of saturation can indicate whether an approach is nearing or exceeding practical capacity, yet the interpretation should account for local conditions, signal operation and likely day-to-day variability.

Authorities will generally expect the report to explain what the results mean, not merely attach software output sheets. A clear assessment sets out the assumptions, traffic generation, distribution and assignment, model inputs, results and recommended measures. This allows the reviewing officer to follow the logic and assess whether the proposal has been properly tested.

Turning findings into workable project decisions

Where the model identifies an issue, the solution is not necessarily a major road upgrade. The response may involve refining the access arrangement, redistributing movements, adjusting parking supply, changing loading times, providing turn lanes, modifying signal operation or staging works to align with development delivery.

The appropriate response depends on land ownership, road authority requirements, available road reserve, cost, safety outcomes and the development's actual contribution to the issue. A recommendation that cannot be delivered through the planning approval or works programme has limited value. Practicality matters as much as technical performance.

Early SIDRA traffic modelling can therefore save substantial time later in the design process. It gives the team an evidence base for site planning decisions before drawings are fixed, supports informed discussions with council or Transport for NSW, and reduces the risk that a late traffic request will require redesign of access, parking or basement layouts.

Transport Strategies Alliance approaches modelling as part of the wider approval and delivery pathway. The relevant network conditions, development proposal, access design and authority expectations are investigated together so that the assessment supports a workable recommendation rather than a standalone set of numbers.

The most useful time to test an intersection is before the project becomes committed to an access arrangement that the network cannot support. A focused, site-specific model gives the project team room to make informed choices while those choices are still practical to implement.