Fatigue Risk Management System (FRMS) is a data-driven, risk-based approach to identifying, measuring and controlling worker fatigue that goes beyond hours-of-service limits, combining policy, risk assessment, controls, reporting, training and monitoring.
A fatigue risk management system (FRMS) is a data-driven, risk-based process for identifying, measuring and controlling worker fatigue as an operational hazard, in the same way an organization manages any other hazard. Instead of relying only on fixed limits for hours worked, an FRMS asks a practical question: given this roster, this task and this crew, how tired are people likely to be, and what are we doing about it?
Hours-of-service rules still set an outer boundary. But two people working identical 12-hour shifts can carry very different fatigue loads depending on when the shift starts, how many nights they have worked in a row, their commute, and how much sleep they actually got. An FRMS is built to catch those differences. For background on the physiology behind it, see shift work fatigue.
Prescriptive limits are easy to audit. The weakness is that compliance with a cap says little about alertness at 4 a.m. on the third night shift.
An FRMS treats fatigue as a shared responsibility. The employer designs workable rosters and controls. The worker uses rest time to sleep and reports when they are not fit to work. Supervisors act on what they see. None of those pieces works on its own.
A written fatigue policy states who owns the system, sets roster principles, defines how fatigue reports are handled without punishment, and explains what happens when someone declares they are too tired to work safely.
Rosters, overtime records, call-out patterns and travel time are reviewed to find where fatigue is most likely. The output is a ranked list of high-risk roles, shifts and tasks.
Controls follow the usual hierarchy. Redesigning rosters, limiting consecutive nights and adding staff are stronger than relying on individuals to cope. Lower-level controls include task rotation, scheduled breaks, controlled napping where policy allows, the buddy system for critical tasks, and moving safety-critical work away from the early-morning low point.
Workers need a simple way to report fatigue and fatigue-related near misses. Incident investigations should ask how much sleep people had in the prior 24 and 48 hours, not just what rules were broken.
Workers, supervisors and schedulers each need different content: sleep hygiene and recognizing personal warning signs for workers, spotting impairment and having the conversation for supervisors, and roster design for planners.
Leading indicators such as excessive overtime, short rest breaks between shifts and repeated call-outs are tracked and reviewed.
The International Civil Aviation Organization (ICAO) built the modern FRMS model. ICAO Standards allow operators to use an approved FRMS as an alternative to, or alongside, prescriptive flight and duty time limits, provided they can show an equivalent or better level of safety. ICAO's Doc 9966 sets out guidance for regulators overseeing these programs.
API Recommended Practice 755, Fatigue Risk Management Systems for Personnel in the Refining and Petrochemical Industries, is the main reference for US process plants. The second edition, published in 2019 and designated an American National Standard, includes hours-of-service guidelines for normal operations and outages along with the broader FRMS elements.
Under the model Work Health and Safety laws, fatigue is a hazard that must be managed so far as is reasonably practicable. Safe Work Australia publishes a guide for managing the risk of fatigue at work, and state regulators such as WorkSafe add sector guidance, notably for mining and road transport.
There is no specific OSHA standard on fatigue. OSHA can still cite serious, recognized fatigue hazards under the General Duty Clause, and sector rules such as FMCSA hours of service for truck drivers apply in their own lanes. For most US employers, an FRMS is a matter of good practice and duty of care rather than a line-item legal requirement.
A mid-sized metals smelter ran a 4-on, 4-off pattern of 12-hour shifts. During a maintenance shutdown, contractors and some employees worked 14-hour days for 19 days straight. On day 17, a fitter on night shift fell asleep while driving a light vehicle back to camp and rolled it on an unsealed road. The investigation found the roster complied with the site's overtime cap because the cap only counted hours on the clock, not the 70-minute drive each way.
The site built an FRMS around the finding. Shutdown rosters are now scored before approval, with a maximum of 13 consecutive shifts and a mandatory 24-hour break. Drive time counts toward the daily limit. Workers complete a short fatigue self-check at the start of each night shift, and anyone scoring high is assigned non-critical duties or offered a bus back to camp. Fatigue reports are reviewed weekly by the shutdown manager. Sites that want to automate this kind of self-check and roster scoring often use dedicated fatigue management software.
Generally no, outside regulated sectors. Aviation operators, commercial drivers and nuclear plants face specific duty-time rules, and refiners commonly follow API RP 755 as an industry consensus practice. For other employers, OSHA has no fatigue standard, but a recognized fatigue hazard that causes or could cause serious harm can be cited under the General Duty Clause. An FRMS is the most defensible way to show you managed it.
A fatigue policy is one document. It states expectations, limits and responsibilities. An FRMS is the full working system around that policy: the risk assessment, the controls, reporting, training, data review and audits. A policy in a binder, with nothing measured and nothing changing, is not an FRMS.
No. Models that predict fatigue from schedule data can be useful for comparing roster options, especially in aviation and large shift operations. They estimate group risk, not individual alertness, and they can be wrong when inputs are poor. Many effective programs run on simpler tools: roster rules, overtime tracking, self-assessment checklists and supervisor observation.
Treat it as a hazard report, not a disciplinary matter. Ask about recent sleep, assess the planned task, and move the person to lower-risk work, pair them with a colleague, give a rest break or send them home with safe transport. Record the report so patterns show up. If workers are punished for speaking up, they will stop reporting and the system loses its main source of information.
Useful indicators include hours worked per week above a threshold, number of shifts with less than a set rest break between them, consecutive night shifts, call-out frequency per person, and the rate of fatigue self-reports. Track them by role and crew rather than only site-wide averages, because fatigue tends to concentrate in a few positions, such as on-call technicians and shutdown crews.
Part of SafetyIQ's EHS glossary: plain-English definitions of workplace health and safety terms.
> Keep learning
> See it in action
Capture hazards, run inspections, track training and close out corrective actions in one platform built for high-risk, field-heavy work.
Book my free demo
Get a demo built around your sites, your teams, and the way your people work.
EHS, journey, and fatigue management software for field-heavy teams.
.png){kind=logo}
.png)