Transferring responsibility.
WHEN HANDOVERS OCCUR
Shift changes Leave and absence Role changes Resignations Project transfers
WHY THEY MATTER
Most defects and omissions originate at handovers.
WHAT A HANDOVER MUST TRANSFER
Current status of everything in progress What is outstanding and by when Problems and their state Commitments made Anything unusual
WHY COMMITMENTS SPECIFICALLY
Promises made by one person and unknown to the next are how customers are failed.
WHAT TO ESTABLISH
A standard format.
WHY STANDARD
It ensures nothing is omitted and it can be read quickly.
WHAT A SHIFT HANDOVER SHOULD COVER
What happened What is in progress What needs attention Any safety matter Anything outstanding
WHAT TO RECORD
The handover, signed or acknowledged by both.
WHY BOTH
It confirms it actually occurred.
WHAT A ROLE HANDOVER REQUIRES
Time, allocated Documentation of tasks and their status Introductions to contacts Access transferred Overlap, where possible
WHY OVERLAP
Questions arise only once the person starts doing the work.
WHAT TO PRIORITISE IN A SHORT HANDOVER
Anything with a deadline Anything that would stop operations Relationships
WHAT TO AVOID
Leaving handover to the final day Verbal handover with no record
WHAT TO ESTABLISH
That handover is part of the role, not an addition to it.
