How to run a workload-risk review in 8 steps

A workload-risk review fails when it counts hours and ignores decision load. Across more than 25 years in multinational EHS roles and more than 250 cultural transformation projects, Andreza Araujo has seen teams hide overload behind normal attendance, clean rosters, and polite silence. In Safety Culture: From Theory to Practice, the useful question is not whether the room sounds calm. It is whether the work itself is asking for more than the system can safely give.

This guide is for supervisors, HR partners, and operations leaders who need a practical way to review workload risk in rotating crews, overtime periods, and contractor-heavy settings. ISO 45003:2021 gives the management-system frame for psychosocial risk, while WHO guidance on mental health at work reinforces prevention, protection, and support. The point is not to turn normal pressure into a diagnosis. The point is to see where work design, recovery time, and decision load are drifting in the same direction.

The thesis is simple. You do not need a large survey to spot workload risk. You need one review that connects roster patterns, task mix, interruptions, recovery debt, and escalation rules before the strain becomes routine.

What you need before starting

Before you start, gather one roster, one week of overtime data, the open deviations, the recent complaints, and the jobs that still need extra approval or rework. If those five inputs do not live in the same place, that is already a signal. Workload risk usually hides in the gaps between systems, not in a single form.

Keep the review focused on one work unit at a time. A plant-wide conversation sounds impressive, but it usually blurs the place where pressure is actually building. If the problem sits in the night shift of one line, the weekend maintenance team, or a small group of supervisors carrying too many exceptions, start there. One clear unit gives you a better answer than five vague ones.

Step 1: Define the work unit

What to do: name the smallest group where the pressure is real. That may be one crew, one shift, one line, one route, or one function. Do not start with the whole site unless the whole site is truly exposed in the same way.

How to do it: write down who does the work, when they do it, and which decisions they own. A workload review becomes useful when it can point to a manager, a supervisor, and a work pattern. The review is not a mood check for the whole organization. It is a decision tool for one operating slice.

How to verify: ask whether the same group carries the same pressure every week. If the answer changes by day, shift, or season, your unit is still too broad.

Common error: using a generic wellbeing conversation to cover a specific operational overload.

Step 2: Collect the three workload signals

What to do: collect three signals at the same time, because workload rarely appears in one form only. Start with schedule pressure, then look at decision load, then check recovery debt. Hours matter, but hours alone do not explain why a team is draining its margin.

How to do it: compare planned time with actual time, count the interruptions that force a restart, and look at whether the team is making more exceptions than the standard work should require. A crew can have normal hours and still carry too many decisions. It can also work long hours and still be stable if the task is simple and the recovery is protected. The review works when you see all three signals together.

How to verify: ask one person to describe what made the shift harder than planned. If the answer is only "busy," the review has not yet reached the real signal.

Common error: treating overtime as the only sign of overload when the real issue is switching, interruptions, and rework.

Step 3: Look for drift in the schedule and the handoff

What to do: compare the planned schedule with what actually happened. The most useful workload review often starts with a simple question: where did the plan stop matching the work?

How to do it: check whether overtime was expected, whether a shift lost people to another job, whether maintenance or production changed sequence, and whether the handoff between crews became longer than it should be. James Reason's latent-condition lens fits here, because the pressure often comes from earlier decisions about staffing, sequencing, and expectation management rather than from the worker who is holding the line at the end of the shift.

How to verify: ask whether yesterday's plan still fits today's crew. If the same plan keeps being stretched to cover new demands, the workload problem is structural, not personal.

Common error: assuming that the roster is proof of control just because it was approved on time.

Step 4: Test decision load, not mood

What to do: ask what decisions the worker had to make before noon. That question is usually better than asking whether the person felt stressed, because people often normalize stress long before they normalize error.

How to do it: list the approvals, interruptions, exceptions, and rework cycles that the person had to manage. Then ask what had to wait while they were solving those problems. If a supervisor keeps solving exceptions that should have been handled by the system, the workload is no longer only on the person. It has moved into the way the work is designed.

How to verify: compare the number of decisions with the number of standard tasks. If the decisions keep rising while the tasks stay the same, the work is becoming harder without anyone saying so directly.

Common error: using a wellbeing score to describe a workload problem that is really caused by work design.

Step 5: Compare the evidence with one practical threshold

What to do: set one threshold that makes the review act. The threshold does not need to be complex. It only needs to be clear enough that the same situation triggers the same response next week.

How to do it: use a simple rule such as this. If the team is carrying overtime, unresolved deviations, and repeated interruptions at the same time, the workload review moves from observation to action. That action may be rescheduling, adding coverage, simplifying approvals, or removing a nonessential task. ISO 45003:2021 gives the organization the management frame, while WHO guidance on mental health at work reminds leaders that prevention is better than waiting for distress to become visible.

How to verify: ask whether the threshold would still work if the supervisor changed tomorrow. If the answer is no, the rule is too informal to protect the work.

Common error: waiting for absenteeism or a complaint line to prove the review mattered.

Step 6: Pick controls that change the work

What to do: choose controls that remove friction from the work itself. That may mean changing the sequence, reducing simultaneous priorities, adding coverage, tightening handoffs, or removing approvals that do not add value.

How to do it: connect each control to one owner and one due date. If the problem is decision load, do not answer with a poster. If the problem is recovery debt, do not answer with a lecture. If the problem is repetitive interruption, change the handoff or the access rule that creates the interruption in the first place. Andreza Araujo's experience across more than 250 transformation projects points in the same direction. The fastest improvement comes when leaders change the system, not when they explain the system more loudly.

How to verify: ask whether the control would still matter if nobody held a toolbox talk about it. If the answer is yes, it is probably a real control.

Common error: substituting awareness actions for operational changes.

Step 7: Close the loop with the next shift

What to do: pass the workload review to the next shift or the next leader in the same language you would use for a critical task. The point is not to announce that the team is tired. The point is to say what changed, what remains heavy, and what must be protected tomorrow.

How to do it: name the open pressure point, the control already chosen, and the check that will show whether the control worked. A workload review is complete only when the next owner can see the same risk picture and knows what to do if it worsens.

How to verify: ask the receiving supervisor to repeat the plan back in plain words. If they cannot explain the pressure without reading notes, the handoff is not yet solid.

Common error: closing the meeting before the operational owner knows what changed in the work.

Step 8: Recheck after 30 days

What to do: revisit the same unit after 30 days and compare the signal. If the review worked, the team should show less rework, fewer exceptions, better recovery, and fewer hidden delays. If the signals did not move, the controls were too weak or the root pressure was not the one you thought.

How to do it: use the same evidence set you used at the start, so the comparison stays honest. The point is not to produce a perfect score. The point is to see whether the work is becoming easier to run without requiring people to absorb the same strain every week.

How to verify: ask whether the next review would look different if you ran it today. If the answer is no, the first round may have changed the conversation but not the work.

Common error: treating a single conversation as a completed intervention.

Final checklist

• One work unit has been defined clearly enough to review.
• The review uses schedule pressure, decision load, and recovery debt together.
• The schedule drift and the handoff were checked against the plan.
• The controls change the work, not only the conversation.
• One owner and one due date exist for each action.
• The next shift knows what changed and what to watch.
• The same evidence set will be used again after 30 days.

FAQ

What is a workload-risk review?

It is a structured look at whether the work is asking too much from the people who must deliver it. A good review checks hours, interruptions, decision load, recovery time, and escalation rules, because stress often appears in the work before it appears in a complaint.

Who should lead the review?

A supervisor or operations leader should lead it, with HR and EHS supporting the evidence and follow-up. The person who owns the work needs to own the response, while HR and EHS help keep the review honest and action-oriented.

How is this different from a wellbeing survey?

A wellbeing survey tells you how people say they feel. A workload-risk review tells you what the work is demanding from them. Both can be useful, but the review is the better tool when you need to change the job, the schedule, or the handoff.

What data matters most?

Start with roster patterns, overtime, rework, interruptions, deviations, and recovery time. Those are usually enough to show whether the system is leaning too hard on people to absorb problems that should have been designed out.

Which Andreza Araujo book fits this topic best?

Safety Culture: From Theory to Practice fits because it treats repeated decisions as the real cultural signal. A Ilusao da Conformidade also fits because a calm surface can hide a work design that keeps asking people to carry more than they should.

If you want this review to become a repeatable management routine, start with Andreza Araujo's books at the official store and use Andreza Araujo to request a diagnostic that connects work design, workload risk, and decision rights.