Key takeaways
- Review a traffic management plan when the work, site conditions or approval assumptions change, not only when someone notices an old date on the cover. Establish the applicable project review requirements and identify changes that need competent assessment. A current-looking document can still describe a work method that is no longer being delivered.
- Identify changed work assumptions.
- The plan remains usable when the actual work matches its reviewed assumptions and authorised changes are reflected in the current instructions.
Review a traffic management plan when the work, site conditions or approval assumptions change, not only when someone notices an old date on the cover. Establish the applicable project review requirements and identify changes that need competent assessment. A current-looking document can still describe a work method that is no longer being delivered.
This guide is for contractors, allocators and site supervisors preparing the decision described above. The examples are hypothetical planning situations, not reports of incidents or customer results. Use the current approved project documents and responsible authority's requirements for technical decisions. National guidance, local adoption and a particular permit condition are different references; confirm which applies to your work rather than assuming a rule from another project transfers unchanged.
Compare the plan with the actual method
Ask the contractor to identify changes in footprint, plant, sequence, access and operating periods. Compare these with the current plan and drawings. A revised programme can affect traffic arrangements even when the excavation location remains unchanged. Give the responsible reviewer enough information to assess the change, rather than requesting a new date on an otherwise unexamined document.
Use events as review triggers
Reports, inspection findings, recurring access problems and materially different conditions can reveal assumptions needing review. The competent project team should determine their significance and the authorised response. Avoid a universal trigger list that claims every event requires the same technical change. Record what prompted review and which decision is being requested so the outcome can be understood later.
Keep approval and revision status separate
A draft revision is not necessarily authorised for implementation. Track who prepared, reviewed and accepted it through the applicable process. Confirm whether related permissions and instructions also need amendment. Preserve the previous version for history while making the current operational version unmistakable. A file name ending final is not a reliable approval system.
Brief the change before relying on it
Identify every team affected by the revision, including relief crews, suppliers and the office. Explain the practical difference rather than simply resend the entire document. Record the communication and any outstanding question. Review is complete operationally only when the authorised outcome reaches the people whose work depends on it.
Practical preparation checklist
| Check | What to capture in the job record |
|---|---|
| Identify changed work assumptions | Relevant location, stage and source reference |
| Record the reason for review | Responsible person and confirmed decision |
| Track draft and authorised versions separately | Supporting document revision and status |
| Reconcile related permissions | Open question, action owner and review point |
| Brief all affected teams | Instruction issued and handover acknowledgement |
Use this as a preparation aid, not a declaration that a site complies with every requirement. Mark an item unresolved if the supporting information is missing. Ask the person responsible for the decision to confirm the outcome; a completed form should show what has been checked and what still needs attention. Keep the original record when an instruction changes so the next reviewer can understand the sequence.
Worked example: where the decision can go wrong
A hypothetical contractor replaces one delivery vehicle with a different configuration after the plan is issued. Reprinting the old drawing with today’s date would not address the changed access assumption. The coordinator should obtain competent review, reconcile affected permissions and communicate the authorised delivery instructions before dispatch.
Completion test and handover
The plan remains usable when the actual work matches its reviewed assumptions and authorised changes are reflected in the current instructions.
Before handing over, identify the current instructions, supporting evidence and any action still open. The receiving person should be able to locate those records without reconstructing a private conversation. If the work method, location, responsible person or conditions change materially, refer the affected decision for review through the project process. Recording a task as complete should not conceal a separate approval or technical acceptance that remains outstanding.
Sources, related guides and next steps
The primary published guidance for this topic is the reference behind the jurisdiction or subject discussed here. For national context, consult Austroads' guide and standard information. For workplace risk context, also read Safe Work Australia’s workplace traffic guidance. Check current local requirements before relying on an older document, a course description or a remembered procedure.
Related practical reading: Changing a TGS on Site: Who Can Approve It and How to Record It, What Is a Traffic Guidance Scheme (TGS)? Examples and When You Need One, Traffic Management Plan vs Traffic Guidance Scheme: What's the Difference?.
Keep your company's current job instructions, supporting records and assigned follow-up together. TrafWise can support operational record keeping; confirm the features and configuration your company uses rather than treating software status as independent technical approval.
Frequently asked questions
What should we check first for traffic management plan review?
Ask the contractor to identify changes in footprint, plant, sequence, access and operating periods. Compare these with the current plan and drawings. A revised programme can affect traffic arrangements even when the excavation location remains unchanged. Give the responsible reviewer enough information to assess the change, rather than requesting a new date on an otherwise unexamined document.
What information needs to be confirmed?
Reports, inspection findings, recurring access problems and materially different conditions can reveal assumptions needing review. The competent project team should determine their significance and the authorised response. Avoid a universal trigger list that claims every event requires the same technical change.
Which responsibilities should be agreed?
A draft revision is not necessarily authorised for implementation. Track who prepared, reviewed and accepted it through the applicable process. Confirm whether related permissions and instructions also need amendment. Preserve the previous version for history while making the current operational version unmistakable.
When should the proposed approach be reviewed?
Identify every team affected by the revision, including relief crews, suppliers and the office. Explain the practical difference rather than simply resend the entire document. Record the communication and any outstanding question. Review is complete operationally only when the authorised outcome reaches the people whose work depends on it.