The Five-Minute Baton Pass: Closing the Gaps Between Shifts and Screens
Most teams have a meeting problem. They also have a gap problem. The meeting ends, the call drops, the shift changes, and the work sits in the space between one person's last update and another person's first question. In hybrid teams the gap is often invisible: a message sent at 17:30, read at 08:15, misunderstood by 09:00. In shift-based teams it is more obvious but no less costly. The answer is not another meeting. It is a relay.
The relay, not the review
A relay is short, purposeful and built for movement. A review looks backwards; a relay looks forwards. The five-minute baton pass is a deliberate handover at the boundary between people, shifts or working days. It is not a status report to the manager. It is a peer-to-peer transfer of the minimum context the next person needs to keep moving.
The distinction matters. Status updates tend to be organised around what the speaker has done. A baton pass is organised around what the next person needs. That shift in perspective is what keeps the ritual from becoming another meeting with a different name.
Four things to pass
Keep the pass to four fields. Anything more becomes a meeting.
- What I am passing on. Facts, decisions and context the next person needs. One or two lines.
- What I am dropping. Work that is no longer needed, paused or superseded. Saying this out loud prevents the next person from picking up a dead task.
- Who owns the next step. A named person, not a team. Include the action and the date.
- What to watch. Risks, dependencies or sensitivities that need a human eye.
A simple template to test next week
| Field | Prompt | Example |
|---|---|---|
| Pass on | What does the next person need to know? | 'Client has approved the revised scope; finance still needs the final figure.' |
| Drop | What should not be picked up? | 'The old supplier query is closed; no action needed.' |
| Next step and owner | Who does what by when? | 'Priya to send the figure by Tuesday 10:00.' |
| Watch | What could derail this? | 'Client contact is on leave from Wednesday.' |
The template is deliberately small. A handover that takes twenty minutes is a meeting. A handover that takes five minutes is a habit.
How to run it in five minutes
- Stand up, or use a dedicated channel if the team is remote.
- Use a timer. Five minutes is the whole point.
- Let one person speak at a time. The passing person leads; the receiving person asks clarifying questions.
- Resist problem-solving unless the issue is urgent and cannot wait.
- Capture the four fields in a shared note or channel.
- End with the next owner reading back the step they have agreed to take.
- If there is no next step, say so and close the loop.
The last point is important. Teams often invent work to fill a handover because silence feels like a gap in the process. A clean 'nothing to pass, no next step' is a valid outcome. It keeps the ritual honest.
Guardrails
A baton pass works when it stays small. Do not invite the whole department. Do not turn it into a round-robin of everything everyone has done. Do not use it to performance-manage, and do not let it replace a proper incident review when something has gone wrong. The ritual is for continuity, not for scrutiny.
It also helps to rotate who leads the pass. If the same person always runs it, the team may start to treat it as their meeting rather than a shared discipline. Rotation spreads ownership and makes it easier for quieter team members to hand over without feeling that they are interrupting a senior person's agenda.
Why it works
A five-minute pass does three things that a longer meeting often fails to do. It makes ownership visible, because every pass ends with a named person and a next step. It surfaces dropped work, because the 'drop' field gives people permission to stop carrying dead tasks. And it reduces repetition, because the next person hears the context before they start asking questions.
There is a cultural benefit too. A good handover assumes that the next person is competent and needs context, not supervision. That assumption is worth protecting. It tells the team that the gap between people is a design problem, not a performance problem.
Test it for a week
Pick one boundary: the end of the working day, a shift change, or a project handover between two colleagues. Run the five-minute pass for five days. At the end of the week, ask three questions. Did we repeat less? Did anyone pick up a task that should have been dropped? Did the next owner know what to do without chasing?
If the answer to those questions is mostly yes, keep the ritual and refine the template. If it has already become a status update, cut it back to the four fields and start again. The goal is not another meeting in the calendar. The goal is a cleaner handover between the people who do the work.
