Swaps and Cover

A schedule that cannot be adjusted by the people working it will be adjusted anyway, informally, and the record will be wrong.

Why swaps matter

They absorb the changes a fortnight's notice cannot anticipate: an appointment, a family event, a bad week.

They keep coverage without the employer paying a premium, because a worker-initiated change is not an employer change in most rules.

And they are the single thing people most want from a scheduling system, ahead of everything a vendor leads with.

The minimum process

Both parties agree, in writing. A message thread is writing.

A manager confirms — checking skills, certifications and hours, not vetoing on preference.

The rota is updated the same day.

Three steps. Anything longer produces informal swaps that never reach the record.

What the manager is checking

Can the person do the role? A till-trained person cannot cover a keyholder shift.

Does it create a rest problem? A swap can produce a clopening that the original rota avoided.

Does it push someone into overtime or past a contracted maximum?

Does it breach minor-employment rules, where under-18s are involved?

Four checks, thirty seconds, and they are the reason confirmation exists rather than approval.

Where it goes wrong

Swaps allowed but not recorded, so the clock data, the payroll and the fire list all disagree.

Approval used as control — refusing swaps to enforce the original rota — which produces informal swaps and a record that is fiction.

Swap burden concentrated: two people covering everyone, which is visible in the data and invisible to management.

A swap that becomes a permanent change without anyone updating availability.

Reading the pattern

Swaps per person per month.

Repeated swaps out of the same slot mean the rota does not fit that person, which is an availability update rather than a discipline matter.

Repeated swaps into shifts means someone wants more hours, which is an allocation finding.

A site with high swap volume has a rota problem, not a workforce problem.

What not to do

Do not require a form where a message would do.

Do not make the person find their own cover for sickness, which is the employer's job and is covered in its own note.

Do not penalise swap requests, which turns a release valve into a pressure gauge.

Confirm, do not approve

The distinction that keeps the record honest.

Check capability, rest, hours and minor limits. Four checks, thirty seconds.

Do not refuse on preference, which is using confirmation as control.

Because a refused swap does not stop the swap; it stops the swap being recorded, and then the rota, the clock data and the fire list all disagree.

Reproduce the workflow

For another way to make this requirement testable, review the request-mapping example. Treat it as a starting point, then reproduce the case with real roles, sites and exceptions.

Independent reference

For a thematic point of reference, see the CIPD. Use this established source as an outside check before turning the principle into a workplace rule.