Level 4 controls trap or detect fatigue-related errors before they cause harm. They are designed into equipment, tasks and procedures by others: we don’t supply or endorse them, and we can point you to providers. These are the types that apply in utilities & energy.
- Procedural cross-check
Two-person checks
A second qualified person checks critical actions so one tired person's slip is caught.
What it doesn’t do: Both people may be fatigued on the same roster, so it relies on fatigue-aware rostering behind it.
Examples: Rail: two-person crews and call-outs. Aviation: two-pilot cross-checks. Utilities: switching verification. Hospitals: double checks.
- Remove exposure
Scheduling critical tasks away from the early-morning low
Moves the highest-risk tasks out of the early-morning hours when errors are most likely.
What it doesn’t do: It reduces exposure but does not trap the error; it depends on planners knowing when fatigue peaks.
Examples: Maintenance: critical work scheduled off night shift. Hospitals: elective procedures in daytime.
- Remove exposure
Safe travel home after shifts
Buses, shuttles, taxis or rest rooms so tired workers do not drive home after night or extended shifts.
What it doesn’t do: It protects the commute only, not on-shift performance.
Examples: Mining: bus-in bus-out. Hospitals: taxi vouchers or rest rooms after night shift.
- Procedural cross-check
Structured shift handover
A fixed handover script and read-back at shift change catch what a tired outgoing worker forgets to mention.
What it doesn’t do: It covers the shift change only, not errors during the shift.
Examples: Hospitals: I-PASS or ISBAR. Ambulance: handover to emergency departments. Process plants and control rooms: structured shift logs.
- Trap the error
Control-room alarm management
Removes nuisance alarms and ranks the rest, so a night-shift operator sees the few that matter.
What it doesn’t do: It makes the right alarm visible; it does not make the operator respond correctly.
Examples: Refineries, gas networks, power generation and process plants.
- Procedural cross-check
Permit-to-work and isolation checks
Hazardous work cannot start until a permit is issued, isolations are proven and a second authorised person signs off.
What it doesn’t do: It controls whether work starts, not how well it is done.
Examples: Process plants: control of work. Utilities: access permits. Construction: isolation before maintenance.
- Procedural cross-check
Switching programme checks
Switching steps are written in advance, checked by a second person and read back step by step during execution.
What it doesn’t do: It does not catch errors in the network model the programme was built from.
Examples: Electricity networks: switching operations.
- Detect non-response
Lone-worker alarms
Raises an alarm when a lone worker falls, stops moving or misses a scheduled check-in.
What it doesn’t do: It responds after something has gone wrong and is not a fatigue measure.
Examples: Security patrols, utility field crews and home-care visits.
Most of the evidence for fatigue-detection technology comes from the vendors themselves. Ask for independent evaluation before you rely on it.