Fatigue

Fatigue is among the largest contributors to serious collisions and is almost entirely a scheduling problem rather than a behavioural one.

What causes it

Hours awake, which includes everything before the shift started.

Time of day. The circadian trough in the early hours affects everyone regardless of sleep.

Cumulative deficit across consecutive shifts, which a single night's rest does not clear.

Shift rotation direction and speed, where rapid backward rotation is worst.

And the commute, which is unpaid, unrecorded and adds to hours awake.

Four of these five are set by the rota, which is where the intervention belongs.

What monitoring detects

Eye closure and head position, on cab-facing systems with fatigue detection.

Steering micro-corrections, on some platforms.

Lane departure, from the vehicle's own systems.

All of which detect fatigue once it is present, which is late.

Useful as a last line, not as the programme.

The measures that work earlier

Shift design: limiting consecutive nights, forward rotation, adequate turnaround between shifts.

Schedule realism, because a route that cannot be completed in the hours available produces a driver pushing on.

Rest facilities, so a tired driver can stop without losing pay or a delivery slot.

And a stated right to stop, which is worth more than any detection system and costs nothing except the occasional late delivery.

The right to stop

A driver who is too tired to continue must be able to say so without consequence.

Which sounds obvious and is contradicted by most incentive structures: delivery windows, drop targets, pay by the job.

If stopping costs the driver money or standing, the policy is decorative and the detection system is measuring a pressure the organisation created.

Say it explicitly, and make the first person who uses it visibly fine.

Regulated hours

General orientation, not legal advice.

Where drivers' hours rules apply, they set a floor rather than a target, and a schedule built to the legal maximum every day is a fatigue programme in reverse.

The tachograph records compliance; it does not record tiredness.

Compliant and fatigued is an ordinary combination and is the one most operations never look for.

The measures

Consecutive nights worked, per driver.

Turnaround between shifts, distribution rather than average.

Incidents by time of day, which shows the circadian pattern clearly in any fleet with night work.

And use of the right to stop, which if it is never used is not a right.

Check use of the right to stop

The measure that tells you whether the policy is real.

If nobody has ever stopped, it is not a right.

Which usually means stopping costs the driver money, a delivery slot or standing.

Make the first person who uses it visibly fine, and say so, because that single instance establishes whether the rest of the policy means anything.

A practical configuration prompt

During configuration, use employee time tracking for fatigue-aware scheduling to prompt questions about purpose, ownership and output. Treat the page as a starting point and document each assumption.

Independent reference

For a thematic point of reference, see the Information Commissioner's Office. Consult the source directly because technical, operational and legal details change.