Traffic Calming Request Assessment Template for Councils
For Council officers and Traffic consultants
Use this template when someone asks for traffic calming—such as a speed hump, raised platform, kerb extension, road closure or another physical change. Define the location and problem first, then check existing evidence, road authority, access and network implications before selecting a response. A request is a reason to assess a location; it is not proof that a particular device is suitable or approvable. The responsible authority's current requirements, qualified design advice and approvals still determine whether any treatment can proceed.
When to use this template
Use it for a local-road or street request that proposes a physical traffic-calming measure, or when a concern about speeds, rat-running, crossing safety or amenity may need an area-based or street-based response. It is useful at initial triage, when preparing a brief for technical advice, and when documenting why an existing request should be progressed, combined with other work, monitored or referred.
Do not use it to design a device, issue construction instructions, approve traffic-control devices, replace a Road Safety Audit, decide a speed limit, or deal with an immediate emergency. A request on a state-managed road, a bus or freight route, or a road with complex access requirements may need an early referral to the relevant authority or specialist.
Why the treatment cannot come first
Traffic calming is usually considered as part of local area traffic management or a wider road-safety response. Austroads guidance describes local street management as considering the needs of all users while calming motor traffic; the NSW supplement points councils to approval and delegation material for local-area traffic-management schemes; and Main Roads WA notes that treatments need to account for larger vehicles and people cycling. The applicable jurisdictional guidance and approval route must be checked for each location. Austroads Guide to Traffic Management, Transport for NSW supplement to AS 1742.13, Main Roads WA Treatment Resource Guide
Copyable traffic-calming request assessment
Copy this into a request register, project brief or referral. Use unknown where the information has not been checked. Do not turn a suggested treatment into a committed outcome at this stage.
| Assessment item | Record | Status |
|---|---|---|
| Request and location | [Request ID, date, road, limits / cross streets, suburb, map or location-record link] | [ ] |
| Concern in plain language | [Reported speeding, through traffic, crossing issue, noise, near miss, access concern, other] | [ ] |
| Treatment requested | [Resident or stakeholder suggestion; record as a suggestion, not a decision] | [ ] |
| Road authority and ownership | [Council / state or territory authority / shared or unknown — verify] | [ ] |
| Road role and context | [Local street, collector, arterial, activity centre, school approach, industrial access, other] | [ ] |
| Who uses the street | [People walking, cycling, using mobility aids, public transport, freight, emergency services, waste collection, residents, other] | [ ] |
| Existing location evidence | [Data, observations, crash or incident context, prior requests, studies and dates] | [ ] |
| Evidence gap | [The specific unanswered question and whether targeted collection or professional review is needed] | [ ] |
| Physical and operational constraints | [Drainage, grades, driveways, crossings, parking, utilities, trees, property access, route needs, other] | [ ] |
| Network effects to consider | [Diversion, adjacent streets, intersections, public transport, freight and emergency access] | [ ] |
| Related projects or decisions | [Planned works, speed review, corridor plan, development, earlier outcome] | [ ] |
| Required process to check | [Authority policy, approvals, consultation, design review, funding or procurement pathway] | [ ] |
| Assessment question | [For example: “What response is proportionate to the documented issue at this location?”] | [ ] |
| Next step | [Refer / collect targeted evidence / engineering assessment / combine with area work / monitor / explain no further action now] | [ ] |
| Owner and review trigger | [Responsible officer, location record, date or changed condition] | [ ] |
Evidence and constraint prompt
The aim is to establish what is happening and what must be accommodated, not to create a universal threshold for action. Record sources, dates, extent and limitations.
| Question | Useful information to check | Caution |
|---|---|---|
| What is the problem? | Times, route, direction, behaviour, people exposed and exact road section | A broad complaint may hide several different problems. |
| Is there an existing record? | Prior requests, survey data, observations, projects, decisions and current site layout | Earlier evidence may not cover the reported time or current street condition. |
| Who could be affected by a change? | Walking and cycling activity, bus stops and routes, emergency and waste access, loading and property access | A treatment that addresses one issue can create a different access or safety issue. |
| Is this a street or area problem? | Adjacent-street conditions, alternative routes, origin–destination context and planned network changes | A single-device response can shift traffic or risk elsewhere. |
| What authority process applies? | Road ownership, current standards, delegations, design review and consultation requirements | Another jurisdiction's device, dimensions or approval process may not apply. |
Fictional worked example
The following fictional example shows how an officer could complete the assessment before choosing a response.
| Assessment field | Example entry |
|---|---|
| Request and location | CR-2047; Hakea Street, fictional suburb; Oak Avenue to station bridge; afternoon peak |
| Concern in plain language | Residents report vehicles using the street to bypass congestion on the signalised road. |
| Treatment requested | Speed humps requested by residents; recorded as a suggestion only. |
| Road role and users | Local street; bus route; childcare driveway; marked crossing near shops; delivery access. |
| Existing location evidence | Similar request assessed at the eastern end two years earlier; current traffic count available. |
| Evidence gap | The count does not cover the current afternoon diversion period or the full street section. |
| Constraints and network effects | Constrained drainage, frequent shop deliveries and potential diversion to adjacent local streets. |
| Assessment question | What local-street issue is occurring in the reported period, and what response should be assessed while maintaining access and considering nearby streets? |
| Appropriate next action | Link the earlier decision and current request to the location record; collect targeted evidence for the reported period; refer the completed assessment for qualified advice. |
The form does not select or promise an intervention. It records the request, the known context and the information still needed so the next assessment is proportionate.
Limits and approval caveats
This template does not prescribe treatment types, dimensions, spacing, warrants, costs, consultation steps or approval thresholds. Those matters depend on the location, road authority and current jurisdictional requirements. A physical treatment can require surveying, design, safety and accessibility review, utility and drainage checks, engagement, funding, authorisations and construction planning.
A completed template may support a decision to take no physical action at this time, particularly where the reported problem is not verified, is addressed by existing work, falls outside Council's authority or needs a different response. Record the rationale and a clear review trigger rather than closing the request without explanation.
Keep the request with the location
Retain the original concern, maps, evidence, specialist advice, approvals and outcome against the precise road location. Where your organisation uses XVision Command, follow its configured location-record and records-management practices; this template does not assume a particular data source, sensor coverage or product configuration.
Sources and further guidance
- Austroads, Guide to Traffic Management. National practitioner guidance, including Part 8: Local Street Management.
- Transport for NSW, Supplement to AS 1742 Manual of Uniform Traffic Control Devices. Current NSW references for local-area traffic management and council authorisation material.
- Main Roads Western Australia, Treatment Resource Guide. A road-authority resource describing local-area traffic-management considerations.
Related resources
- How to Investigate a Resident Speeding Concern — use when a reported speeding concern needs to be defined and investigated before considering any response.
- Speed Limit Review Request Checklist for Councils — use when the question is whether a signed speed environment should be reviewed.
Confirm current jurisdictional requirements and obtain the appropriate internal and road-authority review before using this material for a live decision.