Key takeaways
- Mobile and static traffic management address different operating patterns. Describe how the task moves, pauses and affects road users, then have the competent team apply the relevant guidance. A vehicle travelling between jobs does not automatically make each worksite mobile, and a short stop does not by itself justify a simplified arrangement.
- Describe movement and expected pauses.
- The method fits when the competent team has assessed the actual operating pattern and the crew knows how to respond when that pattern changes.
Mobile and static traffic management address different operating patterns. Describe how the task moves, pauses and affects road users, then have the competent team apply the relevant guidance. A vehicle travelling between jobs does not automatically make each worksite mobile, and a short stop does not by itself justify a simplified arrangement.
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.
Describe movement during the work
Explain whether the activity progresses continuously, advances in stages or stays in one place. Include refilling, equipment changes and expected pauses. Naming the plant type does not explain its full work cycle. The designer or supervisor needs an accurate operating pattern to identify an appropriate arrangement and the points where different conditions or responsibilities need further assessment.
Plan the transition to a stationary situation
A fault or obstruction can turn a moving operation into a stationary occupation. Identify who assesses the transition and how the crew reports it. Avoid stretching the original description indefinitely because restarting is inconvenient. Foreseeable pauses should have an authorised decision route so the field team does not have to interpret technical requirements while managing an unexpected stoppage.
Review route-specific conditions
An approach suitable along one section may need review at intersections, accesses or places with different visibility and road-user needs. Mark stage boundaries and important interfaces clearly in the work pack. Do not ask the crew to infer operating limits or dimensions from a broad label such as mobile maintenance. The assessed environment must match the route and activity being delivered.
Keep travel and operations distinguishable
The office needs to know where the activity is scheduled and how material changes are communicated. Record meaningful transitions and unresolved issues for relief crews. Distinguish movement between work sites from movement during the managed operation. A GPS trail can support location enquiries, but it does not by itself prove that the correct arrangement was in place for each task or pause.
Practical preparation checklist
| Check | What to capture in the job record |
|---|---|
| Describe movement and expected pauses | Relevant location, stage and source reference |
| Identify the applicable worksite guidance | Responsible person and confirmed decision |
| Set transition and breakdown decision routes | Supporting document revision and status |
| Review route-specific interfaces | Open question, action owner and review point |
| Distinguish operational stages from travel | 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 moving operation stops for an equipment repair. The work pattern has changed even though the vehicle remains at the same road location. The responsible team should review the new occupation and determine the authorised response. Describing an indefinitely stationary task as mobile because it uses a vehicle would miss the important change.
Completion test and handover
The method fits when the competent team has assessed the actual operating pattern and the crew knows how to respond when that pattern changes.
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: Standard TGS Templates: When You Can Use One and When You Can't, What Is a Traffic Guidance Scheme (TGS)? Examples and When You Need One, Rural Road Works Traffic Control: Long Distances and High Speeds.
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 mobile vs static traffic management?
Explain whether the activity progresses continuously, advances in stages or stays in one place. Include refilling, equipment changes and expected pauses. Naming the plant type does not explain its full work cycle. The designer or supervisor needs an accurate operating pattern to identify an appropriate arrangement and the points where different conditions or responsibilities need further assessment.
What information needs to be confirmed?
A fault or obstruction can turn a moving operation into a stationary occupation. Identify who assesses the transition and how the crew reports it. Avoid stretching the original description indefinitely because restarting is inconvenient. Foreseeable pauses should have an authorised decision route so the field team does not have to interpret technical requirements while managing an unexpected stoppage.
Which responsibilities should be agreed?
An approach suitable along one section may need review at intersections, accesses or places with different visibility and road-user needs. Mark stage boundaries and important interfaces clearly in the work pack. Do not ask the crew to infer operating limits or dimensions from a broad label such as mobile maintenance.
When should the proposed approach be reviewed?
The office needs to know where the activity is scheduled and how material changes are communicated. Record meaningful transitions and unresolved issues for relief crews. Distinguish movement between work sites from movement during the managed operation. Confirm the current project requirements with the responsible person, retain the relevant evidence, and record any unresolved question before relying on the proposed arrangement.