Fatigue Management Safety Talk: What Crews and Managers Need

Fatigue belongs on the safety agenda because it behaves like impairment. Sleep researchers found that after 17 to 19 hours awake, people performed some tasks as badly as or worse than at a 0.05% blood alcohol level, and a large US study found jobs with overtime carried a 61% higher injury hazard rate than jobs without it.

Key takeaways

Key takeaways

1. Fatigue works like impairment: 17 to 19 hours awake matched or beat 0.05% BAC on some tests in a 2000 study of 39 transport and army personnel.
2. Overtime jobs carried a 61% higher injury hazard rate in a US study of 10,793 workers (an association, not proof of cause).
3. WorkSafeBC puts duties on both sides: employers must not assign fatigued workers to risky tasks, and workers must report impairment.
4. Crews need recognition and a reporting script; managers need hours data and the authority to change schedules.
5. Pair the talk with a policy: hours limits, a reporting route, and a fatigue question on every incident form.
6. Measure reports, supervisor responses and hours exceedances, and expect reports to rise at first.

The harder part is making a talk change anything on Monday. A motivational hour on "getting more sleep" will not move a single number if your schedule still runs 14-hour days and nobody knows how to say "I'm too tired to run the lift." This guide covers what the evidence actually supports, what to teach crews versus managers, how to tie the session to a fatigue risk management policy, and how to brief and measure it.

Why is fatigue a safety issue and not just a wellness one?

The regulators in Canada already treat it as one. WorkSafeBC calls fatigue "a common cause of impairment in the workplace" and its fatigue page states that employers must not assign impaired workers to activities where fatigue may create an undue risk. Workers, for their part, must tell a supervisor if their ability to work safely is impaired for any reason. That is a two-way duty, and most crews have never been told the second half exists.

WorkSafeBC's own ergonomist describes fatigue as a contributory factor rather than the hazard itself. That framing works well for a safety audience. Fatigue does not fall off the scaffold. It makes the person on the scaffold slower to notice the unclipped lanyard. So the tasks done by tired workers need stronger protection, not a poster.

The Canadian Centre for Occupational Health and Safety (CCOHS) lists the safety effects plainly: slower reaction time, poorer decisions, more risk-taking and errors, and in the worst case falling asleep while driving or operating equipment. It also lists the organizational costs: absenteeism, turnover and higher incident rates.

The causes CCOHS names are mostly things a company controls:

• Shift work, extended hours and overtime
• Too little rest between shifts
• Long stretches of monotonous, physically heavy or mentally demanding work
• Heat, noise, poor lighting and vibration

Health factors and life outside work matter too, but a talk that only covers personal sleep habits leaves out most of these levers.

What does the research on fatigue and long hours actually show?

Three bodies of evidence are worth putting in front of a safety audience. Each has limits, and a good speaker says so.

Hours awake versus blood alcohol

Williamson and Feyer (Occupational and Environmental Medicine, 2000) tested 39 people, 30 from the transport industry and 9 from the army, through 28 hours without sleep and again after measured doses of alcohol. After 17 to 19 hours awake, performance on some tests was equal to or worse than at 0.05% BAC, with response speeds up to 50% slower on some tests. After longer without sleep, performance reached the level seen at 0.1% BAC.

CCOHS summarizes a comparison in the same range: roughly 17 hours awake compares to 0.05, 21 hours to 0.08 (Canada's legal driving limit) and 24 to 25 hours to 0.10. WorkSafeBC points out that 0.05 is the level at which driving becomes illegal in B.C.

The limits: this was a small lab study, the effect showed up on some tests and not all, and lab tasks are not a loader on a muddy site at 3 a.m. Use it to make the point land, not as a precise conversion chart.

Overtime and injury risk

Dembe and colleagues (Occupational and Environmental Medicine, 2005) followed 10,793 Americans in the National Longitudinal Survey of Youth from 1987 to 2000, covering 110,236 job records. After adjusting for age, gender, occupation, industry and region, they found:

• Jobs with overtime: 61% higher injury hazard rate
• Working 12 or more hours a day: 37% higher
• Working 60 or more hours a week: 23% higher

They also reported a dose-response pattern: the more hours, the higher the injury rate. The authors concluded that long-hours jobs were not riskier simply because they sit in hazardous industries.

The limits: it is observational, so it shows an association, not proof of cause. Hours and injuries were self-reported, and occupation and industry are rough stand-ins for how dangerous a given job really is. It is also US data from before 2001.

Long hours and long-term health

The WHO and ILO estimated in 2021 that working 55 or more hours a week was linked to 745,000 deaths from stroke and heart disease in 2016 across 154 countries, a 29% rise since 2000. Compared with a 35 to 40 hour week, 55-plus hours carried an estimated 35% higher risk of stroke and 17% higher risk of dying from ischemic heart disease. About 9% of the world's population works long hours.

This one is about slow, cumulative harm rather than the incident on Tuesday's shift, and it rests on pooled observational studies. For a safety audience I would use it to make one point: the people running the overtime (supervisors, project managers, operations leads) are often the ones carrying the most hours. I covered the productivity side of this in the 50-hour wall.

What the research does not tell you

CCOHS says it outright: fatigue is hard to measure, so its specific effect on injury rates is difficult to isolate. Canada's national claims data won't show it either. The Association of Workers' Compensation Boards of Canada (AWCBC) counts accepted lost-time claims (its 2024 fact sheet lists 348,747 across Canada, without stating the reference year), but those records do not code fatigue as a cause and leave out most injuries with no lost time. Your own incident data probably won't flag fatigue unless your investigation form asks about it. That gap is a good place to start.

What should a fatigue talk cover for frontline crews vs managers?

The most common mistake in a safety-talk brief is one message for everyone. Crews and managers have different jobs in a fatigue system, so they need different content. If you only get one session, split the last 15 minutes or run a short breakout.

For frontline crews

Keep it practical. Teach the warning signs CCOHS lists (microsleeps, irritability, poor concentration and memory). Make the reporting duty concrete: who they tell, what words to use, and what happens next. Cover the drive home after a long or night shift, because that risk walks off the site with them. Sleep advice for shift workers is useful, but it should be the smaller part of the session.

For supervisors and managers

This group needs permission and a script. A supervisor who receives a fatigue report needs to know which tasks to pull the person from and that doing so will be backed up. CCOHS recommends avoiding high-risk tasks between midnight and 6 a.m. and WorkSafeBC goes further, telling employers to "eliminate safety-critical work" in that window. Senior leaders need the hours data and the authority to change schedules. If they are in the room, ask the speaker to put your organization's own numbers in front of them.

A note on the manager side: as COO at Fitness Town during its growth years I worked 60 to 70 hours most weeks. By the thresholds in the research above, that is the long-hours group, and it is the conversation managers in your audience need to have with themselves.

How do you pair a fatigue talk with a fatigue risk management policy?

A talk without a policy behind it is a pep rally. Both WorkSafeBC and CCOHS describe the same basic structure, and a speaker should be able to point to each part of yours.

WorkSafeBC's three steps:

1. Identify work activities where fatigue could increase the risk of harm (complex decisions, working at heights, calculations, operating tools and machinery).
2. Assess the risk: how fatigue increases harm on each task and who could be affected, including other workers and the public.
3. Put controls in place, following the hierarchy of controls, then monitor them.

CCOHS adds the elements a fatigue management program should include: maximum hours of service, sensible shift rotation, consistent schedules and balanced workloads, rest facilities where needed, training on fatigue signs, a reporting procedure, access to medical screening and EAP, and fatigue as a standard question in incident investigations.

Here is how I would sequence it around an event:

• Before the talk, confirm your policy covers hours limits, a reporting route and what supervisors may do on receiving a report. If it doesn't, the talk can still run, but tell the speaker so they don't promise a process that isn't there.
• During the talk, the speaker walks crews through your actual reporting route and shows managers your actual hours data.
• After the talk, add a fatigue question to incident and near-miss forms within 30 days, and review overtime approvals for the highest-risk tasks.

This is general information, not legal advice. Your obligations depend on your province and industry, so confirm the details with your safety regulator or an employment lawyer.

How should you brief a speaker for a safety audience?

Safety audiences are sceptical, and rightly so. They have sat through plenty of talks from people who have never worked a night shift. The brief is where you protect them from a generic keynote. My full template is in what to put in a speaker brief; for a fatigue session add these:

• The work: shift patterns, typical day length, rotation, travel or fly-in schedules, and which tasks are safety-critical.
• The data you can share: hours worked, overtime trends, incident timing. CCOHS cites Alberta data showing most incidents fall between midnight and 6 a.m. and between 1 and 3 p.m., so check whether yours cluster the same way.
• Your policy: the reporting route, hours limits and what supervisors are authorized to do. Ask the speaker to teach your process, not a generic one.
• The room: crews, supervisors and executives in one session need a different talk from a leadership-only session.
• What you want people to do afterwards: one behaviour for crews, one for managers. Write them down.
• What the speaker must not do: give medical advice, diagnose sleep disorders, or shame people for working the hours the job demands.

On sleep, I would rather a speaker treat it as a shared problem than a lecture. I sleep 6 to 7 hours most nights myself. If your leadership group runs on short sleep, the six-hour sleep trap covers the evidence for executives.

Which of my talks fit a safety event?

I have spoken to trades and construction audiences and to healthcare teams, and these are the talks I would build a safety session from.

I don't list a talk called "fatigue management." Two of my signature talks on my speaking page are the closest fit, and keynotes are shaped to the event:

• The 2% Solution: Thirty Minutes to Transform Your Life splits a 30-minute daily window into moving, stillness and reading. For crews on long rotations, it gives a realistic floor of habit rather than an ideal routine.
• Smart, Driven, Burned Out is aimed at high performers running on empty. It suits supervisors and managers carrying the longest hours.

Keynotes typically run 45 to 60 minutes, with 20 to 30 minute versions for summits, and a half-day workshop format is available. For a safety audience I would recommend the workshop for supervisors, because the reporting conversation needs practice, not just explanation. My wellness keynote guide covers formats and planning in more detail.

How do you measure whether a fatigue talk worked?

Attendance and a satisfaction score tell you the room liked it. They don't tell you whether anyone is safer. Pick a few of these and set a baseline before the event:

Expect fatigue reports and fatigue-flagged incidents to go up at first. That usually means people are finally reporting what was already happening. Explain this to leadership in advance so a rising number isn't read as failure.

If you are planning a safety day, a trades association conference or a health-system event and want a session built around your schedules and your policy, request a speaking quote and send me the shift patterns along with the date.