How to Build a Work-Rest Cycle Check in 14 Days

A work-rest cycle check is the operating review that tells you whether a shift gives people enough recovery between exposures, not just enough hours off the clock. In psychosocial risk terms, it sits where ISO 45003, the HSE Management Standards and daily roster decisions meet the real work that a night-shift supervisor has to manage.

This guide is for night-shift supervisors, maintenance leaders and EHS partners who need a practical routine, because fatigue controls fail when the site stops at awareness and never changes pace, handover quality or decision rights. Across 25+ years leading EHS in multinationals, Andreza Araújo has seen that pattern repeat in plants, distribution centers and contractor-heavy operations. In Muito Além do Zero, she argues that the system produces the result, not the slogan, and that is why recovery has to be managed like any other control.

A supervisor who treats the roster as the whole system will miss the fact that a worker who finishes at 6 a.m., drives home for forty minutes, sleeps in fragments because of heat or noise, and returns to the same pattern has not recovered, even if the schedule still looks compliant on paper. That is not a personal weakness. It is a work design problem that becomes visible only when the operation stops pretending that the clock alone can tell the truth.

What you need before starting

You need four inputs before you touch the first shift: roster history, overtime data, critical task list and one person who can answer when the trigger fires. Without those inputs, the check becomes a calendar exercise that looks organized while missing the actual exposure.

The primary audience is the night-shift supervisor, although the method also helps plant managers and EHS leads who have to see whether work-rest pressure is built into the schedule or hidden inside the operator's effort. Andreza Araújo's Safety Culture Diagnosis: Learn how to do your own is useful here because the method starts with visibility. If the organization cannot see the pattern, it cannot manage it.

Step 1: Define who is inside the work-rest cycle

What to do: define which people, tasks and hours are inside the check. Include the workers who carry the exposure, not only the people whose names appear on the roster. That means contract workers, floating operators, maintenance crews, cleaners and any role that can be pulled into night work without a stable rhythm.

How to do it: list the shift pattern, the actual start and finish time, the expected overtime window, the handover time and the tasks that cannot slip to morning. Then compare that list with the people who actually do the work, because a title on paper does not tell you who carries the fatigue. ISO 45003 treats workload and recovery as system factors, which is why the boundary has to be operational, not decorative.

How to verify: ask three workers to describe the last time the shift changed at the last minute. If they give different answers, the boundary is not clear enough yet.

Common error: using job title as the boundary and assuming that recovery can be measured by the published schedule alone.

Step 2: Map the real recovery window

What to do: map the actual recovery window after the shift ends. Ask about sleep opportunity, commute time, split sleep, family interruptions, second jobs and call-backs. A 12-hour break on paper is not the same as 12 hours of recovery in real life, because life keeps happening after the turnstile.

How to do it: collect one week of self-reported recovery notes from the same crew and compare them with overtime, absences and repeated mistakes. You are not diagnosing a clinical condition. You are checking whether the organization has left enough room for the body and the mind to reset. The HSE Management Standards are useful here because they treat workload and recovery as part of the work system, not as a side conversation.

How to verify: look for the same person reporting different sleep quality on different nights, especially after back-to-back shifts or a late change in task scope.

Common error: treating free time as recovered time and asking the worker to absorb the mismatch silently.

Step 3: Choose the signals that matter

What to do: choose the signals that tell you the cycle is breaking. Use a small set that leaders can read in one minute: overtime above plan, missed breaks, repeated micro-errors and near misses that cluster at the same hour. Those are leading indicators, which means they tell you the system is stretching before the injury rate rises.

How to do it: review the same four signals every day for two weeks, then compare them with shift changes, busy nights and staffing gaps. Andreza Araújo's Safety Culture: From Theory to Practice fits this step because culture shows up in repeated choices, not in a one-time feeling that the site is fine.

How to verify: if one signal rises twice in a row, treat it as a system pattern and not as a one-off complaint. In practice, a repeated short pause, the same error at the same time and the same worker falling behind are all the same message in different forms.

Common error: hiding behind lagging indicators, then acting surprised when the dashboard looks calm while the crew is already stretched.

Step 4: Set trigger levels before the shift starts

What to do: set trigger levels before the shift starts. A simple version has three levels. Level 1 means the task continues with a pause and a second check. Level 2 means the scope is reduced, the task is reassigned or relief is added. Level 3 means the work stops until the supervisor and the area owner agree on the next move.

How to do it: write the trigger in plain language and tie it to the role, not to the mood of the manager on duty. ISO 45003 and the HSE Management Standards both make more sense when they change work design, because a framework without a trigger becomes a poster that nobody uses at 3 a.m.

How to verify: ask the crew to tell you what happens when the trigger fires. If they cannot answer in one breath, the rule is still too vague.

Common error: making the trigger so high that it only fires after the operation has already borrowed too much from recovery.

Step 5: Assign ownership across the system

What to do: assign one owner for the check, one owner for the roster, one owner for the correction and one owner for the audit. The supervisor can run the daily check, but the planner, area owner and EHS lead each have to own their part of the system. Broad responsibility with narrow ownership is how fatigue becomes everyone's concern and nobody's decision.

How to do it: write the names, the back-up names and the escalation path on one page. Across 250+ cultural-transformation projects supported by Andreza Araújo, the same failure has appeared many times: leaders say the problem is shared, then the shift keeps waiting for someone else to act. Shared language is not shared control.

How to verify: the person at the front line should be able to say who answers, who approves the change and who closes the loop before the next night begins.

Common error: handing the whole issue to HR, because workload and recovery belong in operations first and in support functions second.

Step 6: Pilot the check on one high-risk shift

What to do: pilot the check on one high-risk shift before scaling it to the rest of the operation. Pick the task with the clearest fatigue exposure, such as maintenance after midnight, line changeover or a contractor-heavy turnaround. This is where the check becomes real, because the work-rest problem shows up fastest when the pace is high and the margin is thin.

How to do it: run a five-minute start-of-shift review, one mid-shift verification and one end-of-shift handover note for seven consecutive nights. Then compare the notes with the actual work outcome, looking for the same deferrals, the same confusion and the same jobs that keep slipping because nobody has enough recovery to stay sharp.

How to verify: if the pilot reduces rework, short pauses and last-minute improvisation, keep it. If it only creates more paperwork, the check is too far from the field.

Common error: asking every department to adopt the tool at once, which turns a practical control into another program that nobody fully owns.

When the same pattern keeps returning, connect it to the fatigue risk escalation trigger so the signal goes somewhere instead of dissolving into informal talk.

Step 7: Close the loop with worker voice

What to do: close the loop with worker voice at the end of the shift. Ask three questions: what became harder tonight, what needs a pause before tomorrow, and what should I carry to the next crew. Those questions matter because silence at the end of the shift is often mistaken for agreement.

How to do it: answer every concern within 24 hours, even when the final fix takes longer. If the answer is only "we are looking at it", the worker hears delay. If the answer includes the interim control, the owner and the next update date, the worker hears that the report changed something.

How to verify: the same concern should not have to be reported three times before someone reacts. Andreza Araújo's article on the speak-up follow-up loop shows why follow-through is the part that protects trust.

Common error: thanking people for speaking up and then letting the issue vanish into the next meeting.

Step 8: Review weekly and tighten the cycle

What to do: review the cycle weekly and tighten the roster, the break rules and the escalation path where the evidence says to change. If the same signal repeats, do not ask the worker to be more careful. Change the condition that keeps producing the same exposure. That is where Andreza Araújo's Liderança Antifrágil is practical, because leadership proves itself when it changes the system, not when it admires the problem.

How to do it: compare the week against the baseline: overtime, missed breaks, first-hour errors, rework, sleep complaints and delayed handovers. If the numbers improve but the crew says the pace is still unsustainable, keep listening, because the human signal may be ahead of the dashboard.

How to verify: the weekly review should end with one concrete change, one named owner and one date for checking whether the change worked.

Common error: celebrating a cleaner report while the same fatigue pattern keeps moving from one team to the next.

Safety is about coming home, and a weekly review only matters when it protects the people who have to repeat the shift tomorrow night.

• The roster, handover and trigger are on one page.
• Each trigger has a named owner and a back-up.
• Workers can explain what happens when the trigger fires.
• The weekly review compares signals, not opinions.
• The check is linked to workload triage and speak-up follow-up.

For teams that want the broader diagnostic lens, Safety Culture Diagnosis: Learn how to do your own and the books at Andreza Araújo's store give the next level of structure. If you need help turning this check into a leadership rhythm, Andreza Araújo's Safety School is the natural next step. Safety is about coming home.