If the preview is blank or blocked, use Open in New Tab. Some external servers do not allow embedded PDF display.
Traffic Impact Assessment
database-integrated directional traffic, queue metrics, and capacity checks
Quick start guide
Search and apply a site/address first, then confirm the auto-filled parameters.
Review user-input fields marked with red labels before calculating.
Use Calculate All Metrics to refresh all tables/charts together from one source of truth.
Optional modules are exploratory; validate outputs with engineering judgement before reporting.
Search Address
Enter an address or road and use Search to find matching counters. Exact road matches are prioritized; otherwise nearest reference counters are used.
No session file loaded
Current database: Queensland (QLD)
Tip: Include suburb/city to improve geocoding reliability and speed.
Searching suggestions...
Last Searched:
Direction of travel (D1 / D2) *
D1 = Direction 1 (Gazettal / primary stream). D2 = Direction 2 (Against Gazettal / opposing stream).
Select the compass direction each stream travels — Eastbound, Westbound, Northbound or Southbound.
Required for two-way and one-way roads. On two-way roads D2 is set to the opposite of D1 automatically.
Set this once here after address search; AM Peak and one-way labels below stay locked to these values.
Which way does Direction 1 traffic travel?
Opposing stream (auto-opposite of D1; editable)
D1 = Eastbound · D2 = Westbound
TWO-WAY detected, confirm below.
Confirm Road Operation Mode
Choose ONE-WAY or TWO-WAY for this road before using calculated values.
Confirm Selection (always required)
Analysis Results
Match Type:- Search Address:- Geo Source:- Road/Location:-
All Nearby Roads
Streets within 0.2 km of the searched address:
0.2 km3.0 km
Site Location
Select a site from search or click a marker to auto-fill inputs. Numbered map badges match the reference cards below.
Map Status:Waiting for site data...
Exact Data Found
AADT:- vehicles/day
D1 AADT:-
D2 AADT:-
Using 3+ Reference Points (within 5km)
Road-level weighting with suggested road volume
Each road now shows a suggested AADT and one road-level % slider set (no duplicate sliders). Reference cards stay interactive for Use/Remove and show informative weighting context. Final traffic volume is a weighted average, not a sum.
Choose Calculation Method
Manual Traffic Generation
Select a land-use scenario to show the published rate citation.
Share of gross trips already on the frontage road (retail, fast food, service stations). Apply per RTA/RMS Guide practice; 0 = none.
Standards: Default daily / peak rates come from the RTA/RMS Guide to Traffic Generating Developments (v2.2, Oct 2002) §3, with office / high-density peaks updated per RMS TDT 2013/04a where noted. State GTIA / Austroads documents set the assessment framework (LOS, DOS) — they do not replace these land-use trip-rate tables. Peak % = peak-hour trips ÷ daily trips. Always verify rates with the approving authority before lodgement.
ℹ️ Direct AADT Entry — Use this when you already have an AADT figure (e.g., from a traffic count, council data, or another study). Enter the total daily volume and the directional/peak splits will be calculated automatically.
Calculated AADT (Weighted Average of References)
Detected Area Type:- • Type%:100%
Weighted Avg AADT:- vehicles/day
AADT to use:- vehicles/day
Calculated D1 AADT:-
Calculated D2 AADT:-
No matches found Try searching by different road name or manually select from database below.
Input Guide
🔴 Red input boxes require user entry/review and are editable.
🟢 Green input boxes are auto-filled or read-only. If marked editable, they can still be adjusted.
1. Select Site from Map or Manual Entry (Site ID)
Use either the database search or map marker selection. Once a site is selected, values below are synchronized automatically.
🧭 Directional Orientation (relative to road survey direction)
➡
D1 — Gazettal
-
⇄
⬅
D2 — Against Gazettal
-
Analysis Parameters
🔴 User Input | 🟢 Auto-filled
All manual entry fields are shown in red. All auto-filled fields are shown in green, and each editable auto-filled field is explicitly marked.
Confirm road classification & capacity factors above before calculating.
This updates directional summary, queue, VCR/LOS, optional diagnostics, and charts in one pass.
📊 Traffic Data Visualization
Source: Selected traffic profile
Hourly Traffic Profile
Peak Hour Analysis
Direction 1, Eastbound Peak Hours
Direction 2, Westbound Peak Hours
Grouped Directional Summary
Compares AM/OP/PM/EV directional splits and totals used by downstream queue and VCR calculations.
🔴 Direction 2, Westbound
Year
AM
OP
PM
EV
Total
LV
HV
RT
LV
HV
RT
LV
HV
RT
LV
HV
RT
🟢 Direction 1, Eastbound
Year
AM
OP
PM
EV
Total
LV
HV
RT
LV
HV
RT
LV
HV
RT
LV
HV
RT
Development Impact Screening AGTM Part 12 · TMR GTIA
Adds the development's trips to the background traffic on the frontage link and compares with / without: 5% rule by impact type (TMR GTIA Table 6.4), LOS change and the adopted DOS / V/C criterion. Mid-block screen only — intersection delay needs SIDRA (TMR GTIA Pt.C §11), pavement needs SARs (§13).
Auto from Trip Generation (net of pass-by) when blank.
Residential ≈ 25 in / 75 out; office ≈ 80 in. PM mirrors AM.
Enter development trips (or run the Trip Generation calculator) to screen the development against the background traffic.
Queue Length EstimationAustroads AGTTM
Toggle between table and chart views. Stop/Go hold queues use the AGTTM Part 3 Table 4.3 method: the 5-minute arrival count times the stopping-time multiplier (2 min ×2.4 cars / ×8 oversize; 5 min ×6 / ×20; 10 min ×12 / ×40; 15 min ×18 / ×60, i.e. 6 m per car and 20 m per heavy vehicle of zero-discharge queue). Above 60 km/h this app uses 7 m per car as a conservative adoption; road trains are given 63 m. Lane closure shows after-merge and including-merge concentration on the remaining lane(s). AGTTM merge-taper checks are advisory for advance-warning placement — they do not inflate queue length.
🔴 Direction 2, Westbound
Queue Duration
AM
OP
PM
EV
Max Queue
🟢 Direction 1, Eastbound
Queue Duration
AM
OP
PM
EV
Max Queue
🟠 SWT Queue Summary
Direction
AM
OP
PM
EV
Max SWT Queue
🔴 Direction 2, Westbound
🟢 Direction 1, Eastbound
VCR / LOS AnalysisDoS / VCR LOS
LOS from Degree of Saturation (VCR): A ≤ 0.60 free flow; B 0.61–0.70 stable minor delay; C 0.71–0.80 acceptable; D 0.81–0.90 approaching capacity; E 0.91–1.00 at capacity; F > 1.00 oversaturated.
Work VCR assumes: Single Lane Closure (default)
🔴 Direction 2, Westbound
Metric
AM
OP
PM
EV
Capacity with factors (AGTM03-20)
— Calculate All Metrics to show the factor breakdown for this direction.
🟢 Direction 1, Eastbound
Metric
AM
OP
PM
EV
Capacity with factors (AGTM03-20)
— Calculate All Metrics to show the factor breakdown for this direction.
🔴 Direction 2, Westbound
🟢 Direction 1, Eastbound
Design capacity with AGTM03-20 factors (both directions)
Design capacity = class base × terrain (fT) × lane width (fW) × lateral clearance (fLC) × side friction (fSF) × HV/RT (fHV), minimum 500 vph/lane.
Per-direction breakdowns also appear directly under each VCR / LOS table above.
— Run Calculate All Metrics, or adjust capacity factors above, to refresh this breakdown.
* Design capacity uses Austroads AGTM03-20 practical per-lane capacity (Table 6.1 / §§5.2–5.4 & 6.2.1), adjusted for terrain, lane width, lateral clearance, side friction and HV/RT mix, with a minimum of 500 vph/lane. Adopted in Queensland via QGTM / TMR GTIA.
Analytics Dashboard
Consolidated 24-hour performance view — is the road healthy, where is the bottleneck, what changed?
Worst VCR
—
LOS —
D1 Peak Queue
—
metres
D2 Peak Queue
—
metres
24-Hour Traffic Profile
Hourly vehicle volumes — D1 vs D2 (opening year)
Volume-to-Capacity Ratio by Hour
Work VCR per direction — target 0.85, capacity 1.00
Queue Length by Hour
Peak queue estimate per direction — watch 200 m, high 400 m
Preview not generated yet.
HOURLY ESTIMATE
Bucket Definition: AM (07:00-09:00, MORNING PEAK), OP (09:00-16:00, MORNING OFF PEAK), PM (16:00-18:00, EVENING PEAK), EV (18:00-07:00, EVENING OFF PEAK).
⚠️ Use red time per cycle, NOT total hourly accumulation. Temporary work-zone stop/go commonly uses around 120s in a 240s cycle.
Max Back-of-Queue Calculator
Auto-filled from calculated VPD/hourly profile and direction settings.
Estimated Max Queue: --
1. QUEUE LENGTH (Hourly Basis)
min
Direction 1
Hour
Hour Type
Volume (vph)
AGTTM Queue (m)
SWT Queue (m)
Max Physical Reach (m)
Direction 2
Hour
Hour Type
Volume (vph)
AGTTM Queue (m)
SWT Queue (m)
Max Physical Reach (m)
2. VCR (Hourly Basis)
Direction 1
Hour
Base VCR (LOS)
Work VCR (LOS)
Direction 2
Hour
Base VCR (LOS)
Work VCR (LOS)
🔄 Detailed Detour Route Capacity
Merges the 24-hour hourly profile of the primary site with selected detour roads to identify specific peak-period failures.
Detour Route Scenarios
Configure how many detour routes need separate analysis. Each route keeps its own selected path, weights, and detour inputs.
1 route configured.
User-defined diversion percentage (e.g., keep local/emergency access on the primary road).
Choosing "series" for parallel routes double-counts the diverted traffic; choosing "alternatives" for a series route under-loads every segment.
Primary-road queue length above which the report states a detour is warranted. No published value — set from the site's storage / advance-warning envelope and record the basis.
Confirm bridge load limits, low-clearance structures, and swept-path suitability before adopting detour capacity outputs.
The attestation is printed in the report as a limitation: this tool does not compute bridge loads, clearances or swept paths (AGTTM Part 2 §3.2.3).
Select one or more streets to define the traffic detour path.
Choose a Road VPD method for each road: 📡 Nearby Datapoints calculates a weighted current-road VPD from the selected reference counters; 🚗 Trip Generation uses calculated AADT. Datapoint mode is read-only and updates from the selected weights below.
Route-level summary: the cards above show each selected detour road separately. The table below shows the worst directional capacity result across the selected detour segments for each period.
Physical per-lane capacity for V/C — same classes as the assessment form
These factors adjust per-lane capacity for detour V/C on every selected street (same AGTM03-20 chain as queue / VCR). Values stay synced with the assessment form until you edit them here. Override per street in each road’s capacity panel if needed.
Design capacity: —
The closed section drivers would otherwise have used. Required for delay — delay is the extra time, not the whole detour trip.
Estimated delay per diverted vehicle: -
Detour road summary: each selected road is assessed separately, with D1 and D2 LOS shown for every period.
Road
Metric
AM (7–9)
OP (9–16)
PM (16–18)
EV (18–7)
🛣️ Road Status After Diversion (Existing Road)
Shows the remaining traffic on the work zone road after diversion, with separate D1 and D2 LOS for each period.
Metric
Formula Trace
Analysis Assumptions
DTCA Path
-
HV Source
-
RT Source
-
Growth Source
-
Lane Source
-
Profile Source
-
Design hour (K / D)
-
Acceptability criterion
-
Capacity basis
-
Count / AADT accuracy
-
Works duration class
-
Trace Item
Applied Value / Rule
🧪 Internal Diagnostics (Hidden, Click to Expand)
Run diagnostics to check formula consistency.
Check
Status
Details
Hidden panel: open with Ctrl+Shift+D or add ?debug=1 to URL.
Detour preview not generated yet.
🖨️ Print Customization (All Sections & Tables) (Click to Expand)
Toggle any section or table to fully customize what appears in the printed report.
Sections Card/Details
Tables Table/Table Wrap
Section Summaries & Titles Fully Editable
Edit the report heading, the informative summary shown above each section, and the descriptive summary shown below each section.
Beta Features (Click to Expand)
Trial Features — Use for exploratory assessment only. Always validate outputs with independent manual engineering checks before reporting.
🔴 In Beta Features, editable input boxes are red and should be reviewed before use.
🟢 Auto-filled/read-only boxes are green. If a field is auto-filled but marked editable, you can still adjust it.
Intersection Queue & Capacity Calculator
Volume/Capacity Ratio0.83
Level of ServiceLOS D
Dynamic Spacing (m/veh)7.25m
Estimated Queue Length90.6m
💾 Multi-Stage Scenario Manager
Save your current calculated metrics as a distinct project stage (e.g., "Phase 1 - NB Lane Closed"). Build a comparison matrix for your final report.
Stage / Scenario Name
D1 Config (Lanes)
D2 Config (Lanes)
Max D1 Queue
Max D2 Queue
Worst Network VCR
Action
📐 AGTTM Layout Geometry & Cross-Section
Ref: Austroads AGRD Part 3 / AGTTM Part 3 (Static Work Sites)
Advance sign spacing, taper lengths and taper separation from the Austroads Guide to Temporary Traffic Management Part 3 (Static Worksites).
Source: AGTTM Part 3 Table 2.2 (advance sign spacing), Table 5.7 (traffic-control, lateral-shift and merge taper lengths for a 3.5 m closed lane, scaled to the entered lateral shift), Table 5.8 (distance between tapers), Table 4.4 (additional signs ahead of PREPARE TO STOP) and Table 2.5 (minimum lane width). Values are identical in AGTTM03-21 (Ed 1.1) and AGTTM03-26 (Ed 1.2, May 2026); QGTTM Part 3 (TMR, Nov 2025) records no Queensland departure on these tables. The lane-width badge reports only whether the width meets the Table 2.5 minimum for the approach speed — it is not a compliance statement for the TGS.
AGTTM COMPLIANT
Default = closed lane width.
Min 0.5m for urban, 2.0m for rural highway.
Distance to kerb/barrier (AGRD Part 3 Table 4.6). For worksite staging, also check AGTTM Part 3 Section 3.2.1 clearances (typically 1.2 m desirable, 0.3 m absolute minimum with approved barriers).
Advance sign spacing (Table 2.2)
-
Merge taper (Table 5.7)
-
Lateral shift taper (Table 5.7)
-
Distance between tapers (Table 5.8)
-
Traffic control taper (Table 5.7)
-
Extra signs before PREPARE TO STOP (Table 4.4)
-
👁️ Approach Sight Distance (ASD)
Calculates the safe stopping distance required for approaching traffic based on speed, reaction time, and road gradient.
Reference note: Stopping sight distance per Austroads Guide to Road Design Part 3 §5.3: SD = RT·V/3.6 + V²/(254·(d + 0.01·G)), with the coefficient of deceleration d from Table 5.3 (car 0.36 general, 0.46 absolute minimum; truck 0.29) and reaction time from Table 5.2 (2.5 s desirable, 2.0 s, 1.5 s constrained). The truck case governs end-of-queue warning on heavy-vehicle routes.d (sealed road, passenger vehicle).
Reaction Dist.
-
Braking Dist.
-
Total Required ASD
-
Truck SSD (d 0.29)
-
⚠️ Warning message here
🧠 Road Type Sensitivity (Quick Search)
Tune how the model classifies residential vs busy roads and applies traffic scaling in quick search estimates.
📉 Speed Reduction Travel Time Impact
Calculates the baseline time penalty added to every vehicle passing through the work zone due to reduced speed limits, assuming free-flowing conditions (no queuing).
Added Delay Per Vehicle
-
-
Total Daily Network Delay
-
Lost hours per day
💸 Economic Delay Cost (Road User Cost)
Calculates the estimated daily economic impact of the traffic delay using standard Austroads Value of Time (VoT) rates. Translates network delay hours into financial cost to the community/freight industry.
Total Daily Economic Cost to Community
$0
LV: $0 | HV/RT: $0
⏱️ Work Window Optimizer (Auto-Scheduler)
Displays permitted working hours based on hourly traffic volumes. Calculates Single Lane Closure (SLC) for multi-lane roads, or Single Lane Reversible Flow (SLRF) for single-lane roads.
00:0006:0012:0018:0023:59
Waiting for calculation...
Stop/Go Shuttle Simulator
Calculates signal timings and queues for single-lane reversible flow operations (portable traffic lights or Stop/Go). Based on the peak hourly volume of your selected profile.
D1 Green Time
-
Base Queue: -
SWT Queue: -
All-Red Clearance
-
Applied twice per cycle
D2 Green Time
-
Base Queue: -
SWT Queue: -
⚠️ Warning message here
🗺️ AustRoads Management Visualization
Select a generic temporary management template to visualize the work zone layout and estimated queue impact based on your calculated traffic volumes.
Estimated Queue Overlay
-
Pedestrian Detour Impact
Choose whether pedestrians walk a separate detour route, or are simply redirected across the carriageway onto the opposite footpath (no street detour).
0.20.2 km
Selected path: -
Scan map to choose pedestrian detour streets.
Other side of road — opposite footpath
Pedestrians are not sent on a street detour. They cross to the opposite footpath at the start of the closed section, walk past the works, then (usually) cross back.
Delay = opposite-path walk time + road-crossing walk + crossing wait delays − existing path time.
Use Mixed where pedestrians cross at a signalised / controlled point one way and give way at the other.
Calculates estimated maximum pedestrian delay using route distances, walking speed, and controlled/uncontrolled crossing delays.
Estimated Maximum Added Delay
-
Existing time + detour time + crossing delay model
-
Vulnerable-user checklist (AGTTM Part 3 §3.10; AS 1428.1) — confirm and record in the TMP:
Continuous, safe pedestrian path with no dead-end at an uncontrolled arterial crossing; desire line respected so people do not cross through the worksite.
Accessible: kerb ramps at every kerb, gradient and cross-fall within AS 1428.1, path width ≥ 1.2 m, firm surface, tactile indicators, no trip edges.
Cyclists: separated facility maintained or a signed alternative; not forced into a live lane at higher speed.
Public transport: relocated stops accessible and within reasonable walking distance; bus turning paths on the detour checked.
School zones, aged care and health facilities on the detour identified; emergency and property access maintained.