Run a Shift-Schedule Psychosocial Risk Review in 14 Days

Shift schedules can create safety exposure before a worker reports fatigue, makes an error, or misses a control. A schedule review is useful when it changes staffing, handover time, recovery opportunity, or escalation rules rather than simply collecting another opinion.

This 14-day method is designed for an EHS manager, operations manager, or HR partner who needs a practical review of rotating, night, extended, or compressed shifts. It treats schedule design as a work condition that should be examined alongside workload, supervision, and critical-risk controls. ISO 45003:2021 supports this approach because psychosocial risk management belongs inside the occupational health and safety system, not in a separate wellness campaign.

What the 14-day review must produce

The review should end with four usable outputs. First, create a map of the schedules that place people under the greatest recovery pressure. Second, identify the work conditions that make fatigue more dangerous, such as driving, isolation, lifting, process alarms, or maintenance under time pressure. Third, assign an owner to each change. Fourth, define how the operation will verify whether the change improved the work rather than merely improving survey sentiment.

The review is not a medical diagnosis and it does not replace occupational health assessment. Its purpose is operational. The manager needs enough evidence to decide whether to change a roster, add a protected handover, adjust overtime approval, or escalate an individual concern through the appropriate clinical and HR route.

Step 1: Define the decision boundary

Start by writing the decision that the review must support. A useful boundary states which schedules are included, which work groups are affected, and which safety decisions cannot be delayed for 14 days. Include night work, early starts, split shifts, rotating patterns, overtime, call-outs, and travel if they influence recovery before safety-critical work.

Do not begin with a vague question such as whether people feel tired. Ask whether the current schedule gives a worker enough recovery to perform a defined task safely, and identify the leader who can change the schedule when the evidence shows that it does not.

Step 2: Map the schedule and exposure windows

Build one table with at least six columns: shift start, shift end, rotation direction, consecutive shifts, overtime, and safety-critical tasks. Add commute time when it is known to be material. A schedule that looks acceptable on paper can create a longer exposure when a two-hour journey follows a 12-hour night shift.

Mark the windows that deserve closer review. These may include the first shift after rotation, the final hours of an extended shift, the period after an unscheduled call-out, and the handover between a night team and a day team. The objective is not to label a person as fit or unfit. It is to show where schedule pressure meets hazardous work.

Step 3: Separate schedule risk from workload risk

Ask supervisors and workers to distinguish four conditions that are often collapsed into the word fatigue: insufficient sleep opportunity, excessive workload, emotional strain, and a medical concern. The first three require different management responses, while the fourth may need confidential occupational health support.

Use 10-minute conversations with a small sample from each shift, then compare the answers with absence, overtime, call-out, and incident-review information from the last 30 days. A pattern becomes more useful when several evidence sources point to the same work condition, which is why a single pulse survey should not decide the intervention.

Step 4: Test the high-risk tasks

List the tasks in which reduced alertness could weaken a critical control. Examples include vehicle dispatch, confined-space entry, energy isolation, crane signaling, process upset response, medication handling, and work at height. For each task, record the control that must hold, the person who verifies it, and the point at which the task must stop.

This step changes the conversation from general concern to operational consequence. If a roster creates a difficult recovery window before a task that depends on precise communication, the control plan may need a second verifier, a different start time, or a rule that prevents overtime from extending into the task.

Step 5: Review handovers and recovery protection

Examine whether the schedule protects the transition between shifts. A handover that takes place during the last 15 minutes of a long shift may transfer unfinished decisions without enough attention to changed conditions. Check whether the outgoing team can explain abnormal status, temporary controls, open permits, and unresolved alarms before leaving.

Then examine recovery protection outside the worksite. Look for short turnarounds, repeated night-to-day reversals, missed meal periods, and overtime approval that bypasses the supervisor who understands the task. ILO C155 places prevention within the organization of work, which means schedule design belongs in the same management conversation as equipment, procedures, and supervision.

Step 6: Agree on response thresholds

Set three response levels before the review becomes personal. A routine level triggers monitoring and a conversation with the supervisor. A control level requires a change to work allocation, overtime, handover, staffing, or task timing. An urgent level stops or defers safety-critical work and uses the established occupational health, emergency, or HR route.

Each threshold should name the decision owner, the evidence required, and the maximum response time. For example, a control-level signal may require a roster adjustment within 24 hours, while an urgent signal may require immediate removal from a safety-critical task until the responsible professional has assessed the situation.

Step 7: Pilot one schedule change

Choose one change that addresses the strongest evidence and can be tested without creating a new hazard. Options include reducing a repeated quick return, protecting a longer handover, changing the direction of rotation, limiting overtime before a critical task, or adding a second competent person during the highest-risk window.

Run the pilot for 7 shifts or another period that covers the relevant rotation. Record what changed, what did not change, and which operational constraints affected the result. A pilot is not successful because people report feeling better for two days. It is successful when the intended work condition changes and the critical control remains verifiable under normal production pressure.

Step 8: Verify, decide, and keep the evidence

On day 14, compare the original schedule map with the pilot evidence. Review overtime, late handovers, control-verification quality, task interruptions, worker concerns, and supervisor observations. Do not use the absence of an incident as proof that the schedule is safe, because a short review can contain no incident while still exposing weak controls.

Write a one-page decision record that states what will continue, what will change, who owns the change, and when the next review will occur. Keep the evidence with the occupational health and safety management system, protect confidential information, and link the decision to the relevant risk register or action tracker. If the review identifies a possible medical condition, refer it through the confidential process instead of attempting to resolve it through roster design alone.

What to do after the 14-day cycle

Use the result to set a monthly review cadence for schedules that combine night work, overtime, high-risk tasks, or frequent call-outs. A simple dashboard can track four signals: schedule changes, overtime before critical work, delayed handovers, and open concerns that have exceeded their response threshold.

Connect those signals to decisions. A metric that never changes staffing, sequencing, authorization, or escalation is only a record. The same principle appears in the psychosocial workload review and in the work-rest cycle check-in, which help leaders move from concern to a defined management response.

For a broader safety-management view, compare the result with the decisions that turn workload data into management action. The important question is not whether the organization completed a schedule assessment. It is whether the assessment changed the conditions under which people must make safety-critical decisions.

A schedule review earns its place in the safety system when it produces a visible decision, a named owner, and evidence that the work became more controllable. Andreza Araujo's approach to safety culture emphasizes that management systems become credible through repeated operating choices, which is why the final test belongs in the field rather than in the file.