How to Run a Workload Risk Review Before Overtime Becomes a Safety Exposure

F2 | Psychosocial risk control for operations leaders

A schedule can look efficient in a planning meeting while becoming unsafe in the field. The warning appears when overtime, callouts, compressed recovery, and production pressure begin to change how people think, communicate, and decide. A workload risk review gives leaders a way to act before those changes are treated as normal.

A workload risk review tests whether the work system still gives people enough capacity, recovery, supervision, and decision support to perform safely under the current demand.

That definition matters because fatigue is often framed as an individual condition. The stronger question is what the organization has designed around the person. ISO 45003:2021 places psychosocial risk inside the occupational health and safety management system, where workload, working time, role clarity, resources, and leadership can be reviewed as connected conditions.

Step 1: Define the work period and decision

Start with a bounded decision, such as whether a team can safely complete the next shutdown, cover the next roster cycle, or accept another week of overtime.

A review becomes vague when it asks whether people are generally overloaded. Choose the period, team, operation, and decision that require evidence. State whether the review will authorize the plan, reduce the scope, add resources, change the sequence, or escalate the exposure.

Record the work that must be done, the work that can move, and the work that is being added because of an exception. This prevents the meeting from treating every task as equally urgent, even though the risk created by a missed inspection may differ from the risk created by delaying a low-criticality improvement.

Step 2: Map demand instead of counting hours alone

Map the demands that consume capacity, because two shifts with the same duration can create very different cognitive and operational exposure.

Review task volume, interruptions, night work, callouts, travel, handovers, emotional demands, high-consequence decisions, and the amount of work that must be completed under time pressure. Include planned work and the unplanned work that repeatedly displaces it.

The review should distinguish duration from intensity. A long shift with stable, well-supported work is not equivalent to a shorter shift that contains repeated alarms, conflict, emergency decisions, and incomplete information. The record should show when the demand peaks and which role carries the decision burden.

Step 3: Check recovery between work periods

Test whether the roster creates a real opportunity to recover rather than assuming that time away from the site equals recovery.

Look at the interval between shifts, quick returns, consecutive nights, commuting time, callout interruptions, and whether workers can use breaks without leaving critical work uncovered. Ask supervisors what actually happens when the plan meets production pressure, since a scheduled break that is routinely interrupted is not an effective control.

Recovery also depends on predictability. A roster that changes at short notice can make personal recovery harder even when the total hours appear acceptable. Where local law or collective agreements establish working-time requirements, use those requirements as a floor, not as proof that the workload is safe.

Step 4: Identify the decisions that become fragile

Find the decisions whose quality can deteriorate before a recordable event shows that capacity has been exceeded.

List the judgments that depend on attention, communication, memory, or willingness to pause. Examples include confirming isolation, accepting a permit, responding to an alarm, handing over a changing condition, recognizing a weak signal, and deciding whether a task should stop.

Then ask what evidence would show that the decision is becoming less reliable. Repeated rework, missed handover details, delayed escalation, increasing shortcuts, and unexplained variance can all justify a closer review. They do not prove that fatigue caused a failure, but they show why the workload decision cannot be based on hours alone.

Step 5: Compare staffing with the real work system

Compare the people available with the roles, interfaces, and controls that the work actually requires.

Do not count headcount without checking competence, supervision, contractor interfaces, lone work, relief coverage, and the authority to stop or resequence the job. A team can have enough people on paper while still lacking the person who can interpret a control, approve a change, or coordinate an emergency response.

Review vacancies, absences, new starters, temporary assignments, and repeated dependence on one experienced person. If a single individual carries the knowledge needed to keep the operation stable, the workload risk includes concentration of decision authority as well as total hours.

Step 6: Test the control options with the people doing the work

Ask the team which change would reduce exposure in the actual workflow, then test whether leaders can provide it before the next critical period.

Possible controls include reducing scope, adding relief, changing the sequence, extending recovery, removing low-value tasks, increasing supervision, creating a clearer escalation route, or moving high-consequence work to a better-supported period. The correct option depends on the demand and the decision it threatens.

Use direct questions that make the work visible. Which task is most likely to be rushed? Which handover is hardest to complete? What would make you stop? Which request arrives after the team has already lost capacity? A leader who hears the answers but cannot change any condition should escalate the decision rather than label the conversation as consultation.

Step 7: Set an escalation threshold before pressure peaks

Define the condition that will trigger a new decision before the team is forced to negotiate it while overloaded.

The threshold might involve a minimum staffing level, a sequence of consecutive night shifts, a critical role without qualified relief, repeated callouts, a failed handover, or a high-risk task scheduled after an unstable recovery period. Avoid presenting the threshold as a perfect biological limit. It is an operational trigger that tells the organization when the original plan no longer has enough evidence behind it.

Name the person with authority to change the work and the route for urgent escalation. A threshold without decision rights only creates another record. The practical test is whether a supervisor can use the trigger during a live shift without waiting for a meeting that will happen after the exposure has passed.

Step 8: Decide, communicate, and review the result

Close the review with a visible decision that changes workload, resources, sequence, or authority, and set a date to test whether the change worked.

Release the plan only when the evidence supports the work period and the critical decisions have usable controls. Restrict the scope when part of the work is supported but another part would depend on fragile capacity. Stop or escalate when the remaining exposure cannot be controlled with the resources available.

Communicate what changed, why it changed, and what condition will reopen the decision. Then return to the field and check whether the control survived real interruptions. A workload review is complete only when leaders can show that the work system, not just the meeting record, has changed.

Final checklist for the workload risk review

The review is useful when it connects demand, recovery, staffing, decisions, controls, and authority in one traceable decision.

• The review period, team, task scope, and decision owner are defined.
• Demand is mapped by intensity, interruptions, critical decisions, and unplanned work.
• Recovery is checked against the real roster, callouts, handovers, and break conditions.
• Fragile decisions and early warning signals are identified without claiming unproven causation.
• Staffing, competence, relief, supervision, and interfaces match the work system.
• Workers have identified practical changes that leaders can implement or escalate.
• Escalation thresholds and decision rights are clear before pressure peaks.
• The final decision includes an owner, a review date, and evidence that will show whether exposure changed.

Andreza Araujo’s work on safety culture treats leadership as visible in the conditions that shape decisions, not only in the messages leaders publish. That principle applies to workload. In a field shaped by more than 25 years of executive EHS experience and the practical framework in Safety Culture: From Theory to Practice, a schedule deserves the same discipline as any other safety control because it changes what people can reliably notice, communicate, and decide.

If your organization needs to connect psychosocial risk, safety culture, and operational decisions, Andreza Araujo helps leaders turn safety expectations into workable systems.