Every shift change is a small transfer of responsibility. Done well, nobody notices it. Done badly, a customer waits overnight, a pallet sits unscanned or a patient follow-up is missed. This guide answers the questions teams ask most about running a handover that does not drop tasks, whether you work in operations, support, a warehouse or a clinic.
Why do handovers fail?
Most failures are not carelessness. They come from the way the moment is set up:
- Memory instead of records. The outgoing person “just knows” where things stand, and that knowledge walks out of the door with them.
- Rushed timing. The handover is squeezed into the last five minutes, when the outgoing person is already thinking about leaving.
- No fixed shape. Each person shares what they happen to remember, so what gets passed on depends on who is talking.
- Unclear ownership. “Someone should chase that” usually means no one does.
- One-way delivery. The incoming person nods politely and asks nothing, then discovers the gaps at 3 a.m.
What should a handover include?
- Open items. Everything started but not finished, with its current status.
- Risks and warnings. Anything that might go wrong in the next shift: a fragile customer, a failing machine, a short-staffed hour.
- Decisions pending. What is waiting for an answer, who must decide and by when.
- Owners. A named person for every open item, not a team name.
- Deadlines. The actual time something is due, not “soon”.
- What changed. New instructions, workarounds or exceptions the incoming person would not otherwise know.
Add a short line on what is finished, so the next shift does not repeat it. Leave out the rest of the history; a handover is a briefing, not a diary.
Is there a simple template?
Yes. Five headings fit on one page and work in almost any team:
- Done this shift: a few lines, only what the next shift needs to know is complete.
- Still open: item, status, next step, owner, deadline.
- Risks & watch-points: what to keep an eye on and why.
- Waiting on a decision: the question, who decides, by when.
- Contacts & access: who to call, where the keys, logins or files are.
The rule that matters most: every open item answers three questions. What is the next step? Who owns it? By when? If any answer is missing, the item is not ready to be handed over.
Should a handover be written or verbal?
Both, because they do different jobs.
Why written alone fails
Notes get skimmed. Tone, urgency and nuance disappear, and the reader cannot ask what “check the usual way” means.
Why verbal alone fails
Conversation is quickly forgotten and leaves nothing to look back at. It also fails completely when shifts do not overlap.
The combination that works
Write the note first, then walk through it together for ten minutes. The document is the record; the conversation is where the incoming person asks questions and the outgoing person adds the things that did not fit on the page.
When should the handover happen?
Plan for an overlap of 10 to 15 minutes, and up to 30 for complex or high-risk work. Start drafting the note during the last hour, adding items as they arise, rather than writing it from memory at the end. Avoid doing it at the exact minute the shift ends; the outgoing person should still be on the clock and focused.
If your operation runs around the clock with no overlap, post the written note before the outgoing person leaves and agree a fallback, such as a phone number reachable for the first hour.
How does this apply to different teams?
- Support: open tickets with promised reply times, angry customers and pending escalations.
- Warehouses: unfinished picks, late trucks, blocked locations and equipment faults.
- Clinics: patients awaiting results, medication timings and follow-up calls, within your privacy rules.
- Operations and IT: running incidents, scheduled changes and vendor promises.
How do you audit handover quality?
- Count surprises. Ask the incoming person each week how many things they learned about from someone other than the handover.
- Track dropped items. When a task is missed, check whether it appeared in the handover note.
- Spot-check notes. Read one or two a week and ask whether a stranger could act on them.
- Ask the receiver. They are the customer of the handover, and their feedback is the most honest measure.
Keep these reviews free of blame. The aim is to improve the template, not to catch people out.
Common handover mistakes
- Writing a diary. Long narratives bury the three things that matter.
- Vague owners and deadlines. “The team will follow up” is not an assignment.
- Skipping the bad news. Risks left out to look tidy come back as incidents.
- Different formats every time. Without a template, people cannot find things quickly.
- Never reviewing it. A template that is never improved slowly turns into a formality.
A shared document is enough to start. If you already track tasks and projects in FulcrumGrid Command Center, you can keep open items, owners and deadlines in the same place the next shift opens first, instead of in a note that lives in someone’s inbox.
Make the handover short, structured and two-way, and tasks stop falling between shifts.
Frequently asked questions
How long should a shift handover take?
Usually 10 to 15 minutes of conversation, plus a written note prepared during the last hour. Complex or high-risk work may need up to 30 minutes.
What is the most important thing to include in a handover?
Open items with a next step, a named owner and a deadline. If those three are clear, the next shift can act without guessing.
How do we hand over when shifts do not overlap?
Post a structured written note before the outgoing person leaves, and agree a way to reach them for questions during the first hour of the next shift.
How can we tell whether our handovers are working?
Count how often the incoming shift is surprised by something, and check whether any missed task was mentioned in the note. Review a few notes each week.
FulcrumGrid Command Center
Keep every open item in view
FulcrumGrid Command Center helps you track tasks, owners and deadlines in one place, so the next shift starts with the full picture.