The Handover
Why the handover decides the shift pattern more than anything else in the building, and how to tell a load-bearing overlap from an inherited one.
What one department found when it examined its handover, over four months
Nineteen paid hours a week came back and four minutes a shift went out, and the department kept a long overlap for the one handover where it was load-bearing. This is one employer's own result, not a recommendation about handover.
The handover determines the shape of the day more than any other physical arrangement. Its length sets the overlap between shifts, its location sets where shifts start, and its format decides whether the overlap has to be paid time at all.
The physical constraint in “The Handover” needs to be recorded alongside the people schedule rather than hidden inside it. Used carefully for small business time tracking, small business time tracking can provide current time and project context while the site, equipment and travel assumptions remain separately documented.
It is also the arrangement least likely to have been revisited, because it feels like part of the work rather than part of the schedule.
Teams documenting “The Handover” may use WorkSafe New Zealand fatigue guidance as an independent reference. Recheck current requirements before changing a live rota.
What the overlap actually buys
Three different things, usually bundled: the transfer of information, the physical continuity of a task that cannot stop, and a buffer against the outgoing shift overrunning.
- Information transfer, which can usually move to writing with a short verbal exception list.
- Physical continuity of a task that cannot stop, which sets a genuine minimum.
- A buffer against the outgoing shift overrunning, which is a scheduling choice.
Those have different costs and different solutions, and bundling them means the overlap is sized for the largest of the three on the worst day.
Separating the three
Information transfer can often move to writing, with a short verbal exchange for exceptions. Physical continuity cannot move at all and determines a genuine minimum. The buffer is a scheduling choice disguised as a requirement.
Pulling them apart on paper is a twenty-minute exercise per shift type and it is the whole of the analysis.
Where a long overlap is load-bearing
Where the work is continuous and risky — a patient, a process, a vehicle in motion — the overlap is doing real work and should be left alone or lengthened.
This is worth saying plainly because the rest of this page is about shortening them, and a handover examined without that distinction produces a saving and an incident.
The written handover and what it costs
Moving information to writing is not free: somebody writes it, somebody reads it, and the quality is variable in a way that a conversation is not.
Four minutes a shift of writing against fifteen minutes of overlap is a good trade arithmetically. Whether it is a good trade operationally depends entirely on what is being handed over, and that judgement belongs to the people doing it.
The room
Where handover needs a room, the room is a constraint: shifts start when it is free, and two teams handing over at once need two rooms or staggered times.
This is the most common hidden reason for a shift start time, and it frequently outlives the room. Changing the start time of every shift because a room was repurposed is a decision nobody has ever had to make consciously.
Staggering, which solves most room problems
Where several groups hand over at the same time, staggering by ten minutes removes the contention entirely and costs nothing.
It is rarely done because all the shift times were set at once, decades apart from each other, and nobody has looked at them as a set since.
The handover that is really a meeting
Some handovers have accumulated content that is not handover: notices, training points, operational updates, a safety message.
That content is legitimate and it does not need both shifts present at premium overlap rates. Separating it moves ten minutes of paid overlap into a channel that costs nothing, and the handover gets shorter and sharper as a side effect.
Measuring before changing
Three numbers over a fortnight: actual handover duration against planned, the proportion of content that was exception rather than routine, and the number of times the room or the previous shift delayed the start.
Collecting them takes somebody with a clipboard and a fortnight. Nobody regrets it, and the numbers usually settle the argument without anybody having to win it.
The overrun that nobody counts
If the outgoing shift routinely finishes late, the overlap is absorbing an overrun and the rota is not showing it. Shortening the overlap then moves the overrun somewhere else rather than removing it.
Fix the overrun first, or at least know that is what the overlap is for. This is the most common reason a handover change fails and is reversed within a month.
Who the handover is actually for
Worth asking directly, because the answer changes the design. A handover for the incoming shift should be short and exception-based. A handover that also serves as a record for somebody who was not there is a different document with different requirements.
Trying to make one event do both is what produces the long, thorough, expensive handover that nobody can shorten, and separating them usually takes ten minutes off it immediately.
What to hold for each shift change
For each shift change: planned overlap, what it is for in the three categories, where it happens, and the date it was last examined.
Four fields. The last one is usually blank and usually should be, which is a reasonable argument for examining one handover a year on a rotation.