Skip to content
fatiguemanagement.co.uk

Fatigue assurance

Fatigue assurance is the ongoing process of checking whether fatigue controls are working as intended — in real operations, not only on paper. It complements initial fatigue risk assessment with monitoring, review, and improvement.

What fatigue assurance means

Section titled “What fatigue assurance means”

Assurance asks whether the organisation can demonstrate — to itself and competent reviewers — that:

  • Rosters and controls match actual working patterns
  • Workers can report concerns without inappropriate penalty
  • Repeated deviations are noticed and reviewed
  • Management decisions on elevated fatigue risk are documented
  • Learning feeds back into roster design and policy

ORR rail guidance describes checking performance and reviewing whether risks are controlled in practice — a theme that applies broadly to fatigue governance, though rail requirements are sector-specific.

Core assurance activities

Section titled “Core assurance activities”
Activity Purpose
Planned vs actual comparison Detect when worked hours, travel, or overruns diverge from the plan
Fatigue records Retain assessments, decisions, mitigations, and reviews
Worker reporting trends Surface patterns that models or planners miss
Management review Accountability for recurring issues
Periodic reassessment Update controls when roles, contracts, or demand change

HSG256 recommends monitoring working hours arrangements and reviewing risk assessments when circumstances change materially.

Records and decision documentation

Section titled “Records and decision documentation”

When elevated fatigue risk is accepted — for example to complete an outage or cover a gap — organisations may record:

  • What risk factors were identified
  • What mitigations were applied
  • Who approved continuation
  • What follow-up review is planned

The fatigue decision record template provides a structure for this. Records support review and learning — they do not prove a shift was safe, create automatic approval, or make processes “audit-proof.”

Learning without blame

Section titled “Learning without blame”

Effective assurance distinguishes:

  • System signals — recurring overruns, high cover rates, credible fatigue reports
  • Individual blame — which can suppress reporting and hide systemic problems

HSSIB investigation material into healthcare staff fatigue highlights that low reporting does not prove low risk — barriers to speaking up may indicate governance weakness.

Common misunderstanding

Section titled “Common misunderstanding”

“If we have records and FRI scores, fatigue is assured.”

Documentation and model outputs are inputs to assurance, not guarantees. Scores can be wrong for individuals, inputs can be outdated, and operations can diverge from the assessed plan. Assurance requires living review — see limitations of fatigue models.

Section titled “Related pages”

References

Section titled “References”