Key takeaways
- WHS laws require employers to manage fatigue risk; companies set their own hour limits from a risk assessment.
- SafeWork NSW's Code of Practice on managing the risk of fatigue at work commenced on 20 February 2026.
- A common starting policy is a 12-hour day, 50-hour week and 10 hours' rest between shifts, adjusted for night work and travel.
- Travel time, consecutive night shifts and short changeovers cause more fatigue problems than the length of any single shift.
- Limits only work if the roster enforces them automatically and workers can say they are not fit without penalty.
Fatigue management in traffic control means planning hours, breaks and shifts so no controller faces live traffic too tired to react. Employers must manage fatigue as a WHS risk, set limits from a risk assessment, build them into the roster, and give workers a safe way to say they are not fit for work.
This guide covers what the law expects, sensible hour limits, rest breaks, night work and travel, and a checklist for allocators. It is general information, not legal or safety advice, so check the current requirements with your state regulator and the award that applies to your workers.
Why fatigue is a serious risk in traffic control
A traffic controller's job is reaction: spotting the car that is not slowing, turning the bat at the right moment, hearing the radio call from the other end. Fatigue slows exactly those things. It also makes people irritable, which matters in a role that already attracts abuse from frustrated drivers.
Traffic control is unusually exposed to fatigue because of how the work is booked:
- Early starts and late finishes. Day shifts often start before sunrise to set up before peak.
- Night works. Many road occupancies are only granted outside traffic hours.
- Short notice. Jobs get extended, emergency call-outs come in, and shifts are filled late at night.
- Travel. Regional and outer-suburban sites can add hours of driving either side of a shift.
- Multiple employers. Casual controllers may pick up work with more than one company, so no single allocator sees the full week.
What the law expects
WHS laws in every state and territory require employers to eliminate or minimise risks to health and safety so far as is reasonably practicable, and fatigue is one of those risks. In NSW, SafeWork NSW's Code of Practice Managing the risk of fatigue at work commenced on 20 February 2026. Approved codes of practice describe how to meet your duties, and can be used as evidence of what is known about a hazard and how to control it, so read the current version from SafeWork NSW. Elsewhere, Safe Work Australia and your state regulator publish fatigue guidance.
There is generally no single legal cap on hours that applies to all traffic controllers. Instead, limits come from several places:
- your own risk assessment and fatigue policy
- the client's or principal contractor's site rules and contract
- the industrial award or agreement that applies, which sets ordinary hours, overtime, breaks and penalties (check the current award with the Fair Work Ombudsman)
- separate heavy vehicle fatigue laws, which may apply to staff driving certain heavy vehicles such as some TMA trucks (check with the National Heavy Vehicle Regulator)
Because traffic control on or next to a live road is high-risk construction work, fatigue should also appear in the SWMS for traffic control as a hazard with stated controls.
Setting hour limits: a sensible starting policy
Every company should set limits from its own risk assessment. As a starting point, many traffic control operators use something like the defaults below, then tighten them for night work, high-speed roads, heat and long travel. These are example settings, not legal limits.
| Rule | Example limit | Why it matters |
|---|---|---|
| Maximum per shift (including overtime) | 12 hours | Alertness falls away late in long shifts |
| Maximum per week | 50 hours | Fatigue accumulates across consecutive days |
| Minimum rest between shifts | 10 hours | Allows travel, food and a real sleep opportunity |
| Consecutive night shifts | Set a cap in your policy | Sleep debt builds quickly on nights |
| Switching nights to days | Longer break than standard | The body clock needs time to reset |
| Days off | At least one full day off in each week as a policy target | Prevents open-ended runs of shifts |
| Travel time | Count it in the fatigue assessment | A 12-hour shift plus 3 hours' driving is a 15-hour day |
Rest breaks during the shift
Breaks matter for two reasons: the award sets meal break entitlements and penalties, and controllers physically cannot stay sharp for hours on a bat without relief.
Practical rules that work on site:
- Plan relief in the crew size. If two controllers run stop/slow at both ends with nobody to relieve them, nobody gets a break without stopping traffic. Quote and roster for relief on long shifts.
- Schedule breaks at the briefing. Agree who relieves whom and roughly when, rather than leaving it to "when it quietens down".
- Rotate positions. Moving a controller from a busy stop/slow end to a quieter role resets attention.
- Make breaks real breaks. Out of the sun or rain, away from traffic noise, with water and food.
- Record them. Break times on the timesheet protect the worker's entitlements and the company in an audit or dispute.
Check meal break and rest entitlements in the award that applies; the traffic controller salary guide explains how awards, overtime and allowances fit together.
Night works, travel and call-outs
Night shifts
Night works are where fatigue planning earns its keep. Common controls include a shorter maximum shift, a cap on consecutive nights, a longer break when switching back to days, lit and safe break areas, and a supervisor who actively checks on alertness in the small hours. Avoid rostering someone onto a night shift after a full day shift on the same day.
Travel
Driving to and from site is often the most dangerous part of a fatigued worker's day. Include travel in the fatigue assessment, allow overnight accommodation for long regional jobs, and share driving where crews travel together. A controller who finishes a night shift and then drives two hours home is a real risk, even if the roster looks compliant on paper.
Extensions and call-outs
Jobs run over. Before agreeing to extend a shift, check how long the crew has already worked and whether the extension pushes anyone past your limits. For emergency call-outs, prefer workers who are rested over whoever answers the phone first, and record the decision.
Fit-for-work checks and speaking up
Hour limits do not catch everything. A worker can be within limits and still unfit because of a sick child, a second job or poor sleep. Build a short fit-for-work question into the traffic control pre-start checklist, and make sure the answer "no" leads to a calm, practical response: relief, a different role, or going home, without punishment. If saying "I'm too tired" costs people shifts, they will stop saying it.
Signs supervisors should act on:
- yawning, heavy eyelids, rubbing eyes
- slow or missed radio responses
- drifting from position or sitting down when they should be standing
- poor concentration, repeated mistakes, irritability
- a worker mentioning they drove a long way or slept badly
Fatigue roster checklist for allocators
Run through this before you confirm a roster, and again before you fill a late shift.
- Has the worker had the minimum rest since their last shift ended, including travel?
- Will this shift push them over the daily or weekly limit?
- How many consecutive shifts or nights is this?
- Is this a switch from nights to days, and has the longer break been allowed?
- How far is the site, and who is driving?
- Is there relief built into the crew for breaks?
- Does the worker have shifts with another employer that you have asked about?
- If you are overriding a limit, is the reason recorded and approved?
- Will the heat, speed environment or job length make fatigue worse on this job?
Common fatigue mistakes we see
- Counting only rostered hours. The roster says eight hours, but the shift ran to eleven and the drive home took another hour. Use actual timesheet hours, not planned ones, when checking limits.
- Ignoring the second job. Casual controllers often work for more than one company. Ask about other work when they join, and remind them they need to tell you if it affects their rest.
- Rewarding the person who always says yes. The most willing controller is often the most fatigued. Spread extra shifts and call-outs rather than leaning on the same people.
- Treating fatigue as a personal problem. Fatigue is a hazard the business creates through its rosters, so the business has to control it.
- No review. If limits are regularly overridden, either the limits or the staffing levels are wrong. Find out which.
Making it work in practice
The companies that manage fatigue well do three things. They write a short, clear policy based on a risk assessment. They make the roster enforce it, so the system blocks or flags a shift that breaks a limit rather than relying on an allocator's memory late at night. And they review it: near misses, incident reports and timesheets show where the policy is not holding.
Fatigue sits alongside the other big risks covered in our traffic controller safety guide, and many of the controls overlap with heat management on long summer shifts.
Next steps
Start by writing down your limits and checking last month's timesheets against them. If you want the roster to do the checking, TrafWise applies configurable fatigue limits (12-hour day, 50-hour week and 10 hours' rest by default) when shifts are offered and accepted, and the traffic control software buyer's guide covers what else to look for.
Frequently asked questions
How many hours can a traffic controller work in a day?
There is no single national cap that applies to every traffic controller. Employers must manage fatigue risk under WHS laws and set limits from a risk assessment, often around 12 hours a day including any overtime. Contracts, client rules and the relevant award can also set limits, so check each one.
How much rest should traffic controllers have between shifts?
Many companies require at least 10 hours off between the end of one shift and the start of the next, and more after night work. The gap should allow for travel home and back, not just time off the clock. Check your company policy, the client's requirements and the award that applies.
What are the signs of fatigue in a traffic controller?
Watch for yawning, heavy eyelids, slow reactions on the bat or radio, missed calls, poor concentration, irritability, drifting from position and microsleeps. A controller who says they are tired, or who drove a long way after little sleep, should be treated as a fatigue risk and relieved or moved.
Who is responsible for fatigue management on a road site?
Everyone with a WHS duty shares it. The traffic control company must plan rosters and policies, the principal contractor must not create pressure that causes fatigue, and workers must take reasonable care and report when they are not fit. Contracts often add specific limits that must be followed.
Do night shifts need different fatigue rules?
Yes, in practice. Night work disrupts sleep, so many companies set shorter maximum shifts, cap the number of consecutive nights, and require a longer break when switching from nights back to days. Base the rules on your own risk assessment and the regulator's guidance.