How to Screen a 24/7 Roster Change for Psychosocial Risk in 9 Checks

A 24/7 roster change is a psychosocial-risk decision when it changes recovery, workload peaks, handover quality, night-work exposure, or the support available when work becomes difficult. A short screening process gives operations, HR, and EHS a chance to correct the design before the new pattern becomes normal.

A roster can look neutral in a spreadsheet because the same roles remain on the organization chart. The risk moves through the pattern. A different rotation can shorten recovery, place inexperienced people together on nights, increase split attention, or leave one supervisor carrying decisions across too many areas.

The practical thesis is that a schedule should be reviewed like a work-design change, not treated as an administrative update. ISO 45003, published in 2021 as guidance for managing psychosocial risks within an occupational health and safety system, supports that approach because it connects work organization, leadership, support, and worker participation to health and safety outcomes. In more than 250 cultural transformation projects, Andreza Araujo has seen that the hidden exposure usually appears in the gap between the planned pattern and the pattern people must invent to keep production moving.

What you need before starting

Bring the current roster, the proposed roster, shift lengths, planned overtime rules, absence and turnover trends, handover arrangements, escalation contacts, and the operational reason for the change. Do not begin with a generic well-being survey. Begin with the work pattern that is changing and the decision the organization needs to make.

Include at least one person who works the affected pattern, one frontline supervisor, one operations owner, and one HR or occupational-health representative. Their roles are different. The worker can describe the recovery problem, the supervisor can explain the decision load, operations can explain the production constraint, and HR or occupational health can help distinguish a work-design issue from a private clinical matter.

Keep the screen focused on foreseeable work-related exposure. It is not a diagnostic tool, and it should not ask employees to disclose personal medical information. The purpose is to improve the conditions under which work is organized.

Step 1: State what the roster change is meant to solve

Write the business problem in one sentence before comparing patterns. The purpose might be to cover a new production window, reduce agency dependence, improve weekend coverage, or respond to a customer requirement. Without that sentence, the team can reject every concern as resistance to change.

Test the statement with the affected supervisor and one worker from each shift. Ask what problem will remain if the change is approved and what new pressure the change could create. Their answers show whether the proposal solves a real constraint or simply moves the burden to a less visible part of the operation.

Verify that the change has a named operational owner. A common error is making HR responsible for a production decision that only operations can adjust, which leaves the psychosocial risk documented but not controlled.

Step 2: Map recovery across the full rotation

Lay out the complete rotation, including the transition between day, evening, and night work, rather than reviewing one shift in isolation. Mark the time between the end of one duty period and the start of the next, then account for travel, meals, family responsibilities, and the time needed to become ready for work.

Ask the people who live the pattern when they actually sleep and when they feel least able to make a careful decision. The answer may show that a nominal rest window does not function as recovery, especially after a late finish followed by an early start.

Verify the design against local working-time rules, collective agreements, and occupational-health requirements. The mistake is to treat legal compliance as proof of adequate recovery. A schedule can meet a minimum rule while still creating a predictable fatigue burden that the operation must address.

Step 3: Find the workload peaks the roster hides

Compare the roster with demand by hour, day, and week. Count the periods when call volume, changeovers, maintenance, loading, customer conflict, or emergency response overlap. A schedule with a balanced headcount can still create an unsafe peak if the hardest decisions arrive when the team is smallest.

Ask supervisors which tasks are delayed, combined, or informally transferred when demand rises. Those workarounds are evidence that the planned capacity does not match the real work. The screen should record the task that is compressed and the control that becomes fragile when it is.

Verify the proposal against the existing workload-risk review rather than creating a second disconnected document. The workload review can show whether the roster changes exposure, while the roster screen identifies the design decision that needs an owner.

Step 4: Test handovers and decision continuity

Follow one real handover through the proposed rotation. Note what information must travel, who receives it, how unresolved risks are marked, and who can make a decision when the outgoing supervisor is no longer available.

Night work often exposes a continuity weakness because support functions may be remote, delayed, or unavailable. Ask the incoming team what they would do if a critical condition changed at 2 a.m. If the answer depends on waking a person who is not formally on call, the roster has a decision-authority gap.

Verify the handover with a short rehearsal using a realistic exception. The common error is checking whether the form is complete instead of checking whether the next team can reconstruct the risk and act without guessing.

Step 5: Check supervision and escalation capacity

List the decisions each supervisor must make during the busiest and least supported periods. Include work stoppage, staffing changes, conflict, equipment failure, customer aggression, and requests to continue with a degraded control.

Compare that decision load with the number of people, areas, and contractors assigned to the supervisor. A new roster can increase risk when one person becomes the informal support line for several teams, because every interruption competes with the decision already in front of them.

Verify that escalation contacts, stop-work authority, and response expectations are written in plain language. The error is giving people a phone number without giving them permission to use it or a clear response standard once they call.

Step 6: Ask where people will compensate for the design

Invite the affected team to describe the shortcut they expect to take when the new roster becomes difficult. Do not ask whether they support the change in general. Ask what they will do when a break is missed, when a colleague calls in sick, or when the handover arrives incomplete.

People usually reveal the real risk when they describe how they will keep the operation running. One person may skip a check, another may accept extra hours, and a supervisor may absorb every unresolved issue until the next day. These are not character flaws. They are signs that the design is asking for private compensation.

Verify that each foreseeable workaround has a control response. The mistake is recording the workaround as an individual behavior problem and sending the person to retraining while leaving the roster unchanged.

Step 7: Separate support from surveillance

Define how employees can raise a workload, fatigue, conflict, or harassment concern without turning the screen into a monitoring exercise. Use a named route for urgent operational risk and a confidential route for sensitive concerns, with clear limits on what can remain confidential when someone may be in immediate danger.

Explain what leaders will do with the information. A survey without a response path can make people less willing to speak because it asks for exposure without demonstrating protection. The organization should be able to say who reviews the concern, when the person receives an answer, and what happens when the concern is disputed.

Verify the route with a small test case before launch. The common error is announcing support in general terms while leaving the night team unsure whether anyone will answer outside office hours.

Step 8: Set decision thresholds before the roster goes live

Agree on the conditions that require redesign, a temporary control, or executive review. Useful thresholds can include repeated missed recovery, unfilled critical shifts, unresolved handover failures, rising overtime, repeated workarounds, or a supervisor who cannot reach the required support.

The threshold should describe an action, not only a number. For example, if the proposed pattern repeatedly leaves a critical role uncovered, the response might be to pause the next expansion of the roster and restore the previous coverage until the gap is corrected.

Verify that the authority to act sits with a person who can change the roster. The error is creating an escalation threshold that only EHS can observe while operations retains the power to ignore it.

Step 9: Review the change after the first operating cycle

Set the review date before implementation and define the evidence that will be brought back. Combine worker conversations, overtime, absence, turnover, complaints, near misses, handover defects, and supervisor observations. No single measure can show whether a psychosocial risk has improved.

Ask whether people are sleeping, recovering, speaking up, and making decisions under the conditions the roster promised. Compare the planned pattern with the actual one, including swaps, extra shifts, informal support, and tasks that moved between teams.

Verify that the review can change the decision. The common error is scheduling a meeting after the launch while treating the new roster as permanent, which turns the review into a report rather than a control point.

Final checklist before approval

Approve the change only when the evidence answers these questions clearly.

• What operating problem does the roster solve?
• Where does recovery become difficult across the full rotation?
• When do workload and decision demand peak?
• Can the next shift reconstruct unresolved risk?
• Who can stop work and who answers after hours?
• Which workaround would people use first?
• How can sensitive concerns be raised safely?
• What trigger requires redesign or escalation?
• When will the actual roster be compared with the planned one?

For a broader plant review, the psychosocial-risk audit guide can extend this screen into a management-system check. If the main weakness appears during shift transition, use the shift-handover review routine to test the information and authority that move between teams.

Why this screen matters to safety leadership

A roster is not just a coverage table. It shapes attention, recovery, support, and the quality of decisions made when conditions are least forgiving. James Reason's work on latent failures is useful here because the unsafe outcome may appear in one person's action while the conditions that made that action likely were designed much earlier.

Andreza Araujo's work on safety culture reaches the same practical conclusion from the field. In Safety Culture: From Theory to Practice and Much More Than Zero, the work system matters because people cannot sustain safe decisions when the organization repeatedly asks them to trade recovery and support for output.

The strongest roster decision is the one that remains workable after the first difficult week. Screen the pattern before approval, assign the power to change it, and return to the people doing the work before a temporary compromise becomes the permanent system.