Skip to content
fatiguemanagement.co.uk

Planned vs actual fatigue

Fatigue risk is often assessed twice in practice — whether organisations label it that way or not.

First at planning: when rosters are designed, contracts are priced, or shifts are assigned against an expected pattern. Then again in operation: when overtime, overruns, call-outs, late finishes, changed travel, or different work content alter what actually happened.

Comparing planned and actual exposure can support governance, learning, and proportionate review. It does not measure individual alertness, predict incidents, or replace fatigue risk assessment or competent person judgement.

Planned fatigue: assessment at design stage

Section titled “Planned fatigue: assessment at design stage”

Planned fatigue (or planned exposure) is the fatigue risk considered when work is still on paper or in a planning system:

Planned assessment supports informed roster design. It helps organisations ask whether controls look adequate before work begins.

Planned controls alone are not enough if operations routinely diverge from the plan without review.

Actual fatigue: what happened in operation

Section titled “Actual fatigue: what happened in operation”

Actual fatigue exposure reflects what workers experienced in practice:

Deviation type Examples
Extended duties Possession overruns, late finishes, waiting on site
Overtime and cover Short-notice extensions, unfilled gaps filled ad hoc
Call-outs and on-call Disrupted sleep, unplanned starts
Changed travel Traffic, diversions, different origin (home vs accommodation)
Changed work content Higher workload than assumed, fewer breaks than planned
Consecutive patterns Repeated early starts or nights beyond what was assessed — see consecutive shifts
Swaps and roster changes Quick returns not visible on the base roster

ORR guidance on managing rail staff fatigue emphasises that organisations should measure performance and investigate whether plans have been implemented and risks controlled in practice — not only whether policies exist. Similar reasoning applies across shift-based and site-based work: what was planned and what occurred may differ.

Why deviations should trigger review

Section titled “Why deviations should trigger review”

A deviation may indicate that:

  • Rest windows were shorter than policy assumed
  • Cumulative load across the week exceeded what was assessed
  • Door-to-door time was longer than the roster reflected
  • A model score based on planned times no longer describes operational reality
  • Controls that looked adequate on paper were insufficient in practice

Deviations do not automatically mean harm occurred. They may indicate that fatigue exposure should be reviewed — especially when patterns repeat, affect safety-critical tasks, or coincide with reports of strain.

Organisations may choose to define triggers for review, for example:

  • Any duty exceeding planned end time by a defined margin
  • Overtime above a weekly threshold
  • A minimum number of quick returns in a roster period
  • Material change to travel duration
  • Credible worker fatigue reports conflicting with low model scores

Triggers should be proportionate to risk and documented — not used as automatic penalties.

Planned controls are not enough alone

Section titled “Planned controls are not enough alone”

Common gaps when only planned exposure is managed:

Gap Risk
Assessment uses nominal roster only Disruption and overtime invisible
FRI recalculated only at design stage Scores stale after operational change
Travel assumed, not recorded Duty and commute burden understated
“Compliant on paper” working time Fatigue exposure still elevated in practice
No feedback loop Same deviations repeat without learning

HSE shift work guidance stresses monitoring compliance with working hours arrangements and reviewing risk assessments when circumstances change. Compliance with working time rules alone does not automatically demonstrate that fatigue risk is adequately controlled.

How comparison supports learning and governance

Section titled “How comparison supports learning and governance”

A planned-vs-actual approach can support:

  • Assurance — checking whether fatigue controls work in live operations
  • Documentation — recording what was expected, what changed, and who reviewed it
  • Trend analysis — spotting recurring overrun, travel, or overtime patterns
  • Incident and near-miss learning — testing whether fatigue factors were present but missed in planning
  • Continuous improvement — adjusting rosters, resources, or controls based on evidence

This sits within wider fatigue risk management system (FRMS) monitoring and review — see fatigue records and audit for what to retain.

What this is not

Section titled “What this is not”

This page does not describe:

  • Real-time fatigue monitoring of individual alertness
  • Software products or automated sign-off
  • Legal conclusions about compliance
  • Mandatory review intervals for all sectors — requirements vary by role, contract, and context

Model outputs based on planned data remain probabilistic estimates. Reassessment after material change should involve competent review, not only recalculation.

Practical steps organisations may take

Section titled “Practical steps organisations may take”
  1. Define what “planned” means for your operation — roster version, assumptions, travel rules
  2. Capture actual end times, overtime, call-outs, and significant travel variance
  3. Compare periodically and after significant events
  4. Record reviews, decisions, and mitigations — see management accountability
  5. Engage workers on whether patterns feel sustainable — see worker fatigue reporting
Section titled “Related pages”

References

Section titled “References”