Handover, Paid Twice or Not at All

Any operation that runs continuously has to transfer information at the boundary. A ward, a control room, a production line, a security post, a care home: the person leaving knows things the person arriving needs.

The practical lesson in “Handover, Paid Twice or Not at All” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring employee monitoring at tech companies, this workforce software resource can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

The transfer takes between five and twenty minutes depending on the complexity, it is required, and in a rota with no overlap it has nowhere to live.

For a separate benchmark relevant to “Handover, Paid Twice or Not at All”, consult the SHRM compensation resources. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

What happens when the rota has no overlap

The outgoing shift stays late, unpaid, because they will not leave a colleague without the information.

Or the incoming shift arrives early, unpaid, for the same reason.

Or it does not happen properly: a two-sentence version in the corridor, which is the version that produces incidents.

All three are common and only the third is visible, which is why handover quality is usually discussed as a professional standard rather than as a scheduling problem.

The overlap, and why it is removed

A paid overlap is the obvious answer and it costs real money: fifteen minutes twice a day across every shift is a meaningful share of a post per team.

It is therefore the first thing cut when establishments are reviewed, usually by somebody comparing rotas across sites and noticing that one has an overlap and another does not.

What follows is predictable and lagged: handover quality falls, incidents at shift change rise, and the outgoing shift absorbs the time informally. None of that appears in the saving.

Who the time belongs to

Both and therefore, in a badly designed rota, neither.

The clean framing is that handover is part of the outgoing shift's work — they are reporting on what they did — and the incoming shift's attendance at it is part of theirs. That implies both are paid for it, which is what an overlap does.

Where only one can be paid, paying the outgoing shift is usually the better choice, because the obligation to report is clearer than the obligation to listen, and because it is the outgoing shift who otherwise stays late.

Recording it

The punch tells you nothing here. The outgoing shift's punch is at the scheduled end whether they left then or not, and the incoming shift's is at the scheduled start.

Where there is an electronic handover record — a note signed by both, a system entry — its timestamps are the real boundary and should be compared with the punches periodically. A consistent gap is the measurement.

Where handover is verbal, ask. People will tell you exactly how long they stay, and the answers within a team are consistent.

The regulated cases

In healthcare, aviation, rail, nuclear and several other sectors, handover content and sometimes its duration are specified. Where that is so, the time is required by regulation and the argument that it is informal does not survive contact with an inspection.

It is also the sector group where the unpaid version is most dangerous, because a rushed handover has consequences beyond pay.

Making it shorter rather than unpaid

A structured handover is faster than an unstructured one by a wide margin. A fixed format — what changed, what is outstanding, what to watch — takes half the time of a free-form conversation and transfers more.

Written notes prepared during the shift rather than at the end of it move most of the work inside the day.

And handing over to one person rather than to a group, where the structure allows, removes the largest variable.

The question for a rota review

When an overlap is proposed for removal, the question to ask is where the handover will happen and who will be paid for it.

If the answer is that it will happen in the overlap that no longer exists, the saving is being taken from the outgoing shift's own time, and somebody should say so before the decision rather than two years later when the pattern is established.

Written handover, and its limits

A log, a shared screen or a structured note shortens the conversation and cannot replace it. The parts that transfer in writing are status and figures; the parts that do not are judgement, tone and the thing that is hard to describe.

Where a written handover is introduced as a substitute for the overlap, the conversation happens anyway, in the corridor, unpaid and unrecorded. Introduced as preparation for a five-minute overlap instead, it genuinely shortens it, and that is the version worth building.