Skip to content
fatiguemanagement.co.uk

ORR rail fatigue reporting

Effective fatigue reporting helps organisations understand operational strain before incidents occur. ORR appendix material on fatigue reporting explains why reporting routes and culture are central to rail fatigue governance.

This page describes reporting themes from ORR guidance. It is not medical advice and does not address fitness-for-duty assessment or disciplinary processes.

Why worker fatigue reporting matters

Section titled “Why worker fatigue reporting matters”

Workers often notice fatigue precursors first — poor sleep, unsustainable patterns, long travel, disrupted rest, or pressure to work when alertness is low. Formal and informal reports can help organisations:

  • Identify patterns that roster scores or compliance checks miss
  • Learn from near-misses and credible concerns
  • Adjust rosters, travel, or workload before harm occurs
  • Demonstrate engagement as part of a fatigue risk management system (FRMS)

Reporting supports review and improvement. It does not, by itself, prove that fatigue risk is controlled or that a worker is fit for duty.

What fatigue reports can help organisations understand

Section titled “What fatigue reports can help organisations understand”

Reports may cover:

  • Subjective fatigue or alertness concerns before or during shifts
  • Long travel, poor lodgings, or noisy rest environments
  • Over-running work, late-notice changes, or missed breaks
  • Patterns that look acceptable on paper but feel unsustainable in practice
  • Discrepancies between planned rosters and actual worked time

ORR guidance encourages proactive reporting of precursors — not only reports after someone feels unable to continue safely.

Organisations should define what to report, how, and to whom — and train managers to respond proportionately.

Why low reporting does not prove low fatigue risk

Section titled “Why low reporting does not prove low fatigue risk”

ORR guidance states that a lack of fatigue reports is not evidence that fatigue is not a problem. It may indicate:

  • Reporting routes are unclear or unused
  • Workers fear blame, penalty, or loss of favoured shifts
  • Fatigue is normalised (“everyone is tired”)
  • Supervisors discourage reporting

Conversely, high reporting — if handled well — can indicate a healthier safety culture, not necessarily worse underlying risk.

See worker fatigue reporting for wider UK guidance on barriers and management response.

Barriers to reporting

Section titled “Barriers to reporting”

Common barriers include:

  • Fear that reporting will affect pay, promotion, or shift preferences
  • Belief that nothing will change
  • Stigma around tiredness in safety-critical roles
  • Unclear routes or slow management follow-up
  • Reports being treated as individual weakness rather than system signals

ORR appendix material on positive safety culture discusses features that support open reporting — including leadership commitment and learning from reports without inappropriate blame.

Management response and learning

Section titled “Management response and learning”

When reports are received, proportionate response may include:

  • Reviewing the specific shift, travel, or roster pattern
  • Checking whether planned vs actual operations diverged from assumptions
  • Considering mitigations — rest, transport, roster change, or workload adjustment
  • Recording decisions in fatigue records
  • Escalating to competent persons when elevated risk is accepted

Management response should focus on system improvement, not on proving whether an individual should have worked. See management accountability for fatigue.

Section titled “How reporting links to FRMS and safety culture”

Within ORR’s Plan-Do-Check-Act framing, reporting supports the Check and Act phases:

  • Monitoring whether controls work in practice
  • Identifying when policy and reality diverge
  • Feeding learning back into roster design and travel planning

Reporting is one indicator among many — alongside overtime trends, absence, incident data, and roster assessments. No single metric tells the whole story.

What reporting is not

Section titled “What reporting is not”

Fatigue reporting arrangements should not be presented as:

  • Automatic proof that a worker is unfit or fit for duty
  • A substitute for medical occupational health assessment where that is required
  • A disciplinary trap for workers who raise concerns
  • Guarantee that reported issues will be resolved — though organisations should respond seriously

Workers should not be discouraged from reporting because they fear inappropriate penalty.

Section titled “Related pages”

References

Section titled “References”