How to build a fatigue check for night shifts in 14 days

Night-shift fatigue is not a morale issue. On maintenance, warehouse, and production crews, it becomes a control problem the moment a supervisor lets a tired team keep moving because the job looks familiar.

A fatigue check only works when it changes the decision to start, continue, reassign, or stop the work. Across 25+ years leading EHS in multinationals and more than 250 cultural transformation projects, Andreza Araujo has seen that the useful question is not whether someone says they are tired, but what the supervisor will do next. In Make The Difference: Be a Leader in Health & Safety and Safety Culture: From Theory to Practice, the same idea shows up from two angles: a control that does not change behavior is paperwork, not leadership.

This routine fits ISO 45001, HSE fatigue guidance, and NIOSH shift-work guidance because all of them treat fatigue as a predictable operational risk, not a personal flaw. As Sorte ou Capacidade argues, repeated signals are rarely luck when the same pattern keeps returning on the same shift.

What you need before starting

Keep the first version simple. You need one owner, one page, one trigger, one escalation route, and one place to record the decision. If the form takes more than a minute to use, the night supervisor will skip it under pressure, which means the control never reaches the work.

The point is not to create a psychological test. It is to give the supervisor a practical gate that sits between fatigue and exposure. If your operation already runs a shift-start safety briefing, the fatigue check should sit inside that rhythm, because separate rituals tend to die on the same day they are launched.

Step 1: Define the fatigue signal your site will treat as real risk

Start by naming the signs that matter on your site, such as repeated micro-pauses, missed handovers, slow response to simple questions, and the habit of rechecking the same instruction. Verify the list with two crews, because the signal has to be visible to the supervisor before it can become a control. The common error is to treat fatigue as a mood, since mood changes and risk signals do not.

Step 2: Map the jobs that cannot absorb fatigue

List the tasks where one lapse can turn into a serious injury, a dropped load, a vehicle conflict, or a lockout failure. Keep the map narrow enough that the supervisor can actually use it, and verify it by asking which job would be unacceptable if the crew was short on sleep or already carrying overtime. The common error is to protect every task equally, because that leaves the site with a broad statement and no priority.

Step 3: Choose three questions that force a decision

Use three questions that do not invite polite answers. Ask what changed since the last rest period, which task needs the most precision, and what would happen if the next mistake were a small one that compounds. Verify the questions with a relief supervisor, because if a substitute leader cannot use them, the tool is not ready. The common error is to ask, "Are you okay?" and then act surprised when the crew says yes.

Step 4: Set pass, caution, and stop thresholds

Verify the thresholds with two realistic scenarios, because if different supervisors reach different decisions from the same facts, the rule is too vague to protect anyone. The common error is to make every answer land in caution, which sounds flexible but usually becomes permission to keep going.

Step 5: Assign who decides, who records, and who receives the escalation

The supervisor should make the first call, the planner should understand the schedule impact, and the EHS lead should see the pattern before it repeats. That division matters because fatigue often begins as a scheduling issue and only later becomes a field event. Verify the ownership by running one night without the EHS lead present and seeing whether the supervisor still knows what to do. The common error is to leave the supervisor alone with the burden and call that empowerment.

If you want the first five minutes of the shift to support this check instead of working against it, pair this routine with How to run a shift-start safety briefing in 12 minutes. The briefing sets the day, while the fatigue check decides whether the day should continue as planned.

Step 6: Pilot it on one crew for three nights

Do not launch across the whole site at once. Run the check with one crew for three nights, because a small pilot shows whether the wording is practical and whether the threshold changes decisions under real pressure. Verify the pilot by comparing the decisions made on each night, and check whether the same scenario leads to the same answer. The common error is to pilot the form without a baseline, since then nobody can tell whether the routine changed anything.

Step 7: Record exceptions in plain language

Write what actually changed, not a label that hides the work. If overtime compressed recovery, say that. If the crew came in after a split sleep pattern or a long commute, say that too. As Safety Culture: From Theory to Practice shows, the record matters only when the next person can read it and decide faster than the first person did. The common error is to write "operator issue" or "tired crew" and leave the real cause invisible.

Step 8: Close the loop at handover

Make the handover carry the fatigue decision forward. If the crew is on caution, the next shift needs to know why, what was changed, and what would trigger a stop. Verify the handover by asking the next supervisor to repeat the decision in one sentence without reading the form. The common error is to let the handover repeat the problem without ownership, which means the same fatigue is still there when the next shift starts.

Step 9: Review the pattern every week

Look at how often the check lands in caution or stop, which crews repeat the same pattern, and whether overtime, staffing, or schedule design is driving the result. If the pattern keeps showing up, move it into How to run a weekly leadership risk review in 30 minutes so the issue gets a decision slot instead of just another log entry. The common error is to review the record and leave the schedule untouched.

Step 10: Train relief supervisors and weekend leaders

The routine fails when only the permanent night supervisor knows how to use it. Train relief supervisors, weekend leaders, and any supervisor who may inherit the shift without warning, because fatigue often spikes when staffing is thin and the team is already adapting. Verify the transfer by having a substitute leader run the check without help. The common error is to treat the routine as a personal style instead of a site control.

What the final checklist should contain

• One page with a clear fatigue signal.
• Three questions that force a decision.
• Pass, caution, and stop thresholds.
• One named owner for the first call and one named recipient for escalation.
• A handover note that follows the decision into the next shift.
• A weekly review that shows whether the same pattern keeps returning.
• A relief-supervisor version that works without the original author present.

For supervisors who want the wider leadership layer, the closest next step is the book Make The Difference: Be a Leader in Health & Safety, and the operational companion is How to run a shift-start safety briefing in 12 minutes. If the same fatigue pattern keeps recurring across the week, move it into How to run a weekly leadership risk review in 30 minutes, because a night-shift fatigue check only matters when the next decision changes.