Fatigue Risk Coordinator in 60 Days: First Decisions

A new fatigue risk coordinator often receives an unclear mandate. Leaders want fewer fatigue-related errors, employees want schedules that can be lived with, and the EHS team wants a process that does not turn every tired person into a case file. The first 60 days should focus on decisions rather than awareness slogans.

Fatigue risk is a work-design issue when working conditions reduce alertness, recovery, attention, or judgment at the moment a task matters. The coordinator does not diagnose sleep disorders or make clinical determinations. The coordinator identifies how schedules, workload, staffing, handovers, commuting, overtime, and supervision interact, then makes the operational owner visible.

What does the role need to understand before starting?

Fatigue is not one signal with one cause. A worker may report poor recovery, a supervisor may observe slower decisions, and an incident review may show that a critical task was scheduled at the end of an extended shift. These observations require different evidence and different owners.

ISO 45003:2021 treats psychosocial risk as part of the occupational health and safety management system. Fatigue should not be isolated in a wellness campaign when the work system is producing the pressure. Connect the issue to planning, staffing, supervision, task design, reporting, and change management.

Use the first 7 days to map shift length, consecutive shifts, overtime, night work, recovery opportunities, commuting demands, workload peaks, task criticality, handovers, and authority to pause work. These prompts help find conditions that deserve verification.

First week: establish the evidence boundary

The first week should answer four questions. Where could fatigue affect a safety-critical decision? Which work conditions make that exposure more likely? Who can change the condition? What evidence would show that the change worked?

Start with one operating area. Choose a work cycle that includes a meaningful transition, such as a night shift, maintenance window, seasonal production peak, or contractor handover. Follow the work from schedule creation to task completion and compare what the roster promises with what the operation demands.

Build an evidence register with 5 columns: condition, possible effect, decision owner, current control, and verification date. If a concern has no owner, it is not yet in the management system. If it has an owner but no verification date, it is only an intention.

Protect confidentiality from the beginning. Aggregate workforce information where possible, keep clinical information with occupational health, and explain what the coordinator will record. Trust disappears when employees believe that a fatigue conversation will become a performance label.

Days 8 to 14: trace one high-risk work cycle

During the next 7 days, trace the decisions that shape fatigue exposure. Review the roster, staffing plan, overtime approvals, pre-job brief, handover, task sequence, break opportunities, and closeout. The question is whether the policy changes work when capacity is tight.

Do not treat a self-report, near miss, or absence record as proof of one cause. Each is a signal that needs context. James Reason's work on active and latent failures helps explain why a visible event can be separated from the conditions that made a decision fragile.

Days 15 to 30: convert signals into work-design decisions

By day 15, identify 2 or 3 priority conditions. Keep the scope narrow. A program that names every possible fatigue factor avoids the hard decision about which roster, staffing rule, task sequence, or escalation practice must change first.

Write each decision in operational language. “Improve fatigue awareness” is not a decision. “Move the critical inspection away from the final hour of the extended shift unless the supervisor verifies capacity and a second competent person is available” can be reviewed.

Use a 30-day action horizon with an owner, interim control, permanent option, and verification method. An interim control may be a second-person check, task resequencing, temporary staffing adjustment, or supervisor review. It should not become a permanent substitute for correcting the design.

Make trade-offs visible. A roster change can affect output, a staffing adjustment can affect budget, and a new handover can affect time. Andreza Araujo's Safety Culture: From Theory to Practice reinforces the practical point that culture is experienced through repeated decisions, not declared in a campaign.

Days 31 to 45: test the controls under pressure

Controls that work only on a normal day are not ready for fatigue-sensitive work. Between days 31 and 45, test the chosen controls during a night shift, unplanned absence, production surge, late maintenance handover, or contractor interface.

Ask supervisors to demonstrate what happens when a worker raises a fatigue concern before a critical task. Who receives the signal? Who decides? Can the task be delayed, reassigned, resequenced, or supported? How is the decision recorded without exposing private health information?

Record what was expected, what happened, what barrier weakened, and what decision must change. Three useful measures are time from signal to owner assignment, fatigue-sensitive tasks with a verified control, and age of unresolved work-design actions. Measures matter only when they change work.

Days 46 to 60: establish the operating rhythm

The final 15 days are for repeatability. Set a monthly review for priority conditions, a 90-day deeper review of schedules and work design, and a clear escalation route for urgent exposure. Define which information stays local, which themes reach senior leadership, and which decisions require occupational health input.

Create a one-page dashboard with no more than 8 decision fields: priority exposure, current control, owner, verification date, unresolved barrier, escalation status, workforce feedback, and next decision. The dashboard should help a leader decide what to change, not reward the coordinator for collecting more fields.

Review the rhythm after 60 days. If meetings discuss scores but not schedules, staffing, task timing, or authority, the process has drifted toward reporting. If leaders can name the exposure, owner, interim control, and next verification date, the role is beginning to work.

Common mistakes new fatigue risk coordinators make

The first mistake is treating fatigue as an employee resilience problem. Personal sleep education has value, but it cannot repair an unstable roster or a workload plan that assumes recovery will happen by itself.

The second mistake is collecting sensitive information before defining the decision. If the organization cannot explain what it will change, more personal data will increase anxiety without improving control.

The third mistake is giving EHS ownership of every response. The coordinator should protect evidence quality and challenge weak assumptions, while the operational leader owns the conditions that create the exposure.

The fourth mistake is accepting a policy as evidence of readiness. A written rule can be useful, although readiness is demonstrated when a supervisor can apply it during pressure and a worker can raise a concern without losing control of the task.

Resources to deepen the role

ISO 45003:2021 provides a management-system reference for psychosocial risk. The UK Health and Safety Executive's Management Standards approach offers another lens for examining demands, control, support, relationships, role, and change. Apply the relevant legal and occupational-health requirements for the countries where the organization operates.

For leadership practice, Safety Culture: From Theory to Practice connects work conditions with the culture employees experience. Make The Difference: Be a Leader in Health & Safety supports the move from visible activity to decisions that protect people when production pressure rises.