Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ANSI API RP 755-2010: Fatigue Risk Management Systems for Personnel in the Refining and Petrochemical Industries
A Comprehensive Guide to Implementing Fatigue Risk Management Systems to Enhance Safety and Operational Reliability
Scope and Purpose of API RP 755-2010
ANSI API RP 755-2010 is a recommended practice developed by the American Petroleum Institute (API) in collaboration with the American National Standards Institute (ANSI). It provides a structured framework for establishing, implementing, and continuously improving a Fatigue Risk Management System (FRMS) specifically for personnel in the refining, petrochemical, and chemical process industries. The standard addresses the growing recognition that fatigue—caused by shift work, long hours, and inadequate rest—is a significant contributor to human error, incidents, and catastrophic events in high-hazard environments.
The scope of API RP 755 encompasses all employees, contractors, and temporary workers whose tasks can affect process safety, operations, maintenance, and emergency response. This includes operators, maintenance technicians, engineers, supervisors, and anyone responsible for safety-critical functions. The recommended practice applies to both day-shift and rotating-shift schedules, as well as extended-duration shifts commonly found in turnaround and outage activities.
Key objectives of the standard include:
- Reducing fatigue-related incidents and near misses
- Promoting a positive safety culture where fatigue is openly reported
- Providing management with a systematic approach to assess and control fatigue risks
- Ensuring alignment with relevant occupational health and safety regulations
The standard is not intended to prescribe a one-size-fits-all solution; rather, it offers a risk-based approach that allows organizations to tailor their FRMS according to operational demands, workforce characteristics, and local regulatory requirements.
Technical Requirements and Core Elements
API RP 755-2010 defines a Fatigue Risk Management System based on the Plan-Do-Check-Act (PDCA) cycle. The FRMS must be documented, implemented, and maintained as part of the organization’s overall process safety management system. The following core elements are mandatory:
1. Fatigue Risk Management Policy
A clear policy that demonstrates management commitment to fatigue risk management. It assigns responsibility, sets performance objectives, and includes provisions for reporting fatigue without fear of reprisal.
2. Risk Assessment and Hazard Identification
Organizations must identify work schedules, tasks, and conditions that contribute to fatigue. This includes analyzing shift patterns, overtime, night work, and commute times, as well as evaluating tasks that demand high levels of alertness or involve repetitive monitoring.
3. Fatigue Mitigation Measures
Based on the risk assessment, appropriate controls must be implemented. These may include optimized shift design (e.g., forward-rotating schedules, maximum shift lengths), provision of adequate rest breaks, and strategies to mitigate fatigue during extended operations (e.g., planned napping, task rotation).
4. Education and Training
All personnel must receive initial and periodic training on fatigue awareness, the consequences of fatigue, and personal strategies to improve sleep hygiene and alertness. Managers and schedulers require additional training on fatigue-related risk indicators and FRMS design.
5. Incident and Near-Miss Reporting
A formal system to capture and analyze events where fatigue is suspected as a contributing factor. Root cause analysis should include a fatigue component.
6. Monitoring, Auditing, and Continuous Improvement
Performance indicators (e.g., unplanned overtime rates, number of fatigue reports, accident rates) are tracked. Regular internal audits and management reviews ensure the FRMS remains effective.
| Element | Description | Example Metrics |
|---|---|---|
| Policy & Accountability | Written policy, management responsibility | Number of shifts exceeding design parameters |
| Risk Assessment | Identification of fatigue hazards | Number of high-fatigue-risk shifts identified |
| Shift Design Limits | Maximum consecutive night shifts, shift duration | % of shifts within recommended limits |
| Training Completion | Fatigue awareness and mitigation training | % of workforce trained annually |
| Incident Investigation | Fatigue as a causal factor in events | Number of fatigue-related near misses reported |
Tip: When conducting a fatigue risk assessment, consider not only shift length but also the commuting distance and time. A 12-hour shift followed by a 1‑hour commute each way significantly reduces recovery time and increases cumulative fatigue.
Implementation Highlights
Successful implementation of API RP 755-2010 requires collaboration between operations, human resources, occupational health, and safety departments. The following practical steps can help organizations adopt the recommended practice effectively:
- Gather baseline data — Collect information on existing shift patterns, overtime usage, and incident records to identify areas with the highest fatigue risk.
- Engage the workforce — Involve shift workers and their supervisors in the risk assessment process. Their firsthand experience is invaluable for identifying hidden fatigue hazards.
- Prioritise high‑risk tasks — Focus mitigation efforts on activities that have the greatest potential for catastrophic consequences, such as critical operations, emergency response, and lone working.
- Design for recovery — Schedule adequate recovery days between shifts, especially after consecutive night shifts. The standard recommends at least two full nights of sleep after three or more night shifts.
- Monitor leading indicators — Track metrics such as unscheduled overtime, self-reported fatigue levels, and operator alertness readings to identify trends before incidents occur.
Warning: Simply reducing shift length from 12 to 8 hours does not automatically eliminate fatigue risks if the shift rotation pattern remains disruptive. Always evaluate the entire 24‑hour cycle, including back‑to‑back shifts and rest periods.
Another important aspect of implementation is the use of biomathematical models that predict human alertness and cognitive performance based on sleep history and circadian rhythms. While these models can be valuable aids, the standard emphasizes they should not replace direct observation and real‑world data collection.
Success Story: A major petrochemical plant implemented a fatigue management programme based on API RP 755, limiting night shifts to three consecutive nights. Within six months, the site reported a 30% reduction in human‑error‑related process deviations and a 40% decrease in absenteeism on the night shift.
Compliance and Auditing Notes
Although API RP 755 is a recommended practice rather than a mandatory regulation, many national and regional regulatory bodies incorporate its principles into their guidelines (e.g., OSHA’s process safety management). For organizations seeking to demonstrate due diligence, or those subject to internal corporate safety standards, adopting API RP 755 can serve as a robust defence when fatigue is alleged in an incident.
Key compliance considerations include:
- Documentation — All FRMS activities, from risk assessments to training records, must be documented and retained. A comprehensive management of change (MOC) procedure should address schedule changes.
- Audit frequency — Internal audits should be conducted at intervals not exceeding one year. A formal management review should evaluate audit findings and program performance.
- Third‑party verification — Some companies choose to have their FRMS certified by an independent body to demonstrate best practice. While not required by the standard, this can enhance credibility.
- Regulatory alignment — Where local regulations (e.g., EU Working Time Directive, Canadian Labour Code) impose stricter limits on working hours, those requirements must take precedence.
Important: API RP 755-2010 does not provide an exemption from any legal duty. Organisations must comply with all applicable occupational safety and health laws. The recommended practice should be viewed as a supplement, not a replacement, for legal compliance.
Auditors should verify that fatigue‑related incidents are tracked separately and that root‑cause analyses include a fatigue line of enquiry. They should also examine shift scheduling records to confirm no pattern of excessive overtime exists. The use of fatigue‑sensing technologies (e.g., eye‑tracking, wearable actigraphy) is permitted but must be part of a broader FRMS and not used as a standalone control.
Q: Is API RP 755-2010 applicable to small facilities or only large refineries?
A: The standard is scalable and intended for any organisation handling hazardous chemicals, regardless of size. Small facilities can adopt a simplified FRMS focused on the most critical risk factors; the framework remains the same.
A: The standard is scalable and intended for any organisation handling hazardous chemicals, regardless of size. Small facilities can adopt a simplified FRMS focused on the most critical risk factors; the framework remains the same.
Q: How does API RP 755 address fatigue caused by overtime versus normal shift work?
A: The standard treats all sources of fatigue cumulatively. Overtime must be factored into the total workload, and limits should be placed on both scheduled hours and voluntary extra hours to prevent excessive cumulative fatigue.
A: The standard treats all sources of fatigue cumulatively. Overtime must be factored into the total workload, and limits should be placed on both scheduled hours and voluntary extra hours to prevent excessive cumulative fatigue.
Q: Can an electronic rostering system ensure compliance with API RP 755?
A: Software can help design compliant schedules and flag violations of predefined limits, but compliance ultimately depends on management oversight, employee reporting, and a culture that discourages overwork. The system is a tool, not a guarantee.
A: Software can help design compliant schedules and flag violations of predefined limits, but compliance ultimately depends on management oversight, employee reporting, and a culture that discourages overwork. The system is a tool, not a guarantee.
Q: Is there a specific training requirement for supervisors regarding fatigue?
A: Yes. Supervisors and schedule planners must receive advanced training on fatigue physiology, shift design principles, and how to identify early signs of fatigue in the workforce. The standard recommends this training be refreshed biannually.
A: Yes. Supervisors and schedule planners must receive advanced training on fatigue physiology, shift design principles, and how to identify early signs of fatigue in the workforce. The standard recommends this training be refreshed biannually.
The adoption of API RP 755-2010 represents an industry‑wide acknowledgment that fatigue is a major process safety hazard. By treating it with the same rigor as any other operational risk, organisations can significantly reduce the probability of incidents and build a more resilient workforce.
© 2026 Technical Standards Publication. All rights reserved.