Relief Shifts: The Roster Behind the Roster

A relief shift is worked by a floating employee — a reliever — who covers the gaps other people's absence creates: leave, sickness, training, vacancies. In continuous operations the relief layer is structural: without it, every absence becomes overtime or a hole.

Why it matters

Fixed patterns cover the plan; relief covers reality. A 24/7 roster needs every seat filled every shift, but every employee is absent 15-20% of working days once leave, sickness and training are counted honestly. That gap is the relief requirement, and mature operations size it with a relief factor: required staffing × (1 + absence rate). A site needing 20 on duty with 18% total absence staffs ~24 — the extra four are the relief pool.

Relief work itself is a distinct job shape: different crew each week, every daypart in turn, first call when the 5am sickness text arrives. Done badly it's the roster's dumping ground; done well it's compensated flexibility — schedule relievers' weeks in advance even when assignments float, give them first refusal rather than last-minute conscription for the worst slots, rotate them through full cycles so their pattern obligations (max nights, rest rules) stay intact, and pay the flexibility premium openly. Senior relievers who know every post are some of the most valuable people in any continuous operation.

A worked example

A four-crew processing plant staffs each crew of 12 with 2 relievers (a 17% relief factor). Relievers know their crew-attachment a month out and their precise assignments a week out; uncovered absence beyond the pool goes to a volunteer overtime list before anyone is called at home. Unplanned overtime fell by 60% in the first year.

✓ Do

Size the relief pool from measured absence (leave + sickness + training), not hope
Schedule relievers' work weeks ahead even when assignments float
Pay a visible flexibility premium or differential
Rotate relief duty fairly if it's shared rather than a dedicated role
Track relief utilisation — chronically idle or chronically exhausted pools are sizing errors

✗ Don't

Treat relief as free slack for projects, then have nothing left for absence
Give relievers systematically worse shifts than the crews they cover
Let relief assignments breach rest rules because "it's just cover"
Hire relievers last and train them least — they need the broadest competence
Use the relief pool to hide a permanent vacancy

Variations & alternatives

On-call scheduling Open shifts Skeleton crew scheduling 4-crew (A/B/C/D) rotation

Build this schedule in Tommy

Set the rotation once and Tommy fills the weeks ahead — shift swaps, leave and coverage gaps handled in one place, with your team always seeing the latest version.

Get Started

Frequently asked questions

What is a relief shift?

A shift worked by a floating employee to cover an absence or gap in the regular roster — the structural answer to leave, sickness and vacancies in continuous operations.

How big should a relief pool be?

Use the relief factor: required staffing × (1 + total absence rate). Honest absence accounting (leave + sickness + training) typically lands between 15% and 20%.

Is relief work worse than a fixed pattern?

It's different: more variety, less predictability. Compensated and scheduled respectfully it suits many people well; uncompensated and last-minute it becomes the roster's burnout role.

Relief shift vs on-call — what's the difference?

Relievers are rostered and working (assignment floats); on-call staff are off-duty unless summoned. Mature operations use both layers: relief absorbs known absence, on-call absorbs surprises.