A handover meeting agenda for a useful 30-minute review
Use this 30-minute handover meeting agenda to review priorities, watch a successor practise a real task and assign owners to remaining gaps.
You have half an hour with the employee leaving, the person taking over and their manager. The handover document is open. It would be easy to spend the whole meeting reading it aloud and finish with “Any questions?”
A handover meeting agenda should help the group establish what the successor can take on, what still needs work and who will resolve the gaps. Reserve time for the successor to attempt something they are about to do. Their questions will be more specific once the work is in front of them.
The agenda below is designed for one role or workstream with a draft pack already prepared. For a complex role, run several focused sessions rather than expecting one meeting to cover everything.
Prepare the meeting before people join
Send the pack and agenda in advance, ideally at least one working day before the meeting. Ask the successor to mark unclear passages and choose a task they expect to perform soon. Confirm that the people attending can open the relevant materials.
Use the job handover checklist to prepare the pack. This meeting is the point where the group checks whether the material is usable.
Give each participant a clear job:
- The manager facilitates, resolves ownership questions and records the review outcome.
- The outgoing employee explains the current position and corrects missing or misleading detail.
- The successor works through the example, asks questions and describes remaining limitations.
Choose a note-taker if the manager cannot facilitate and capture actions comfortably. For a remote meeting, share the working document and let the successor share their own screen during practice.
Atlassian's Inclusive Meetings guidance recommends clarifying roles and the agenda and assigning people to follow-up actions. Apply those basics here so the meeting ends with owners, rather than a list of unattributed concerns. Atlassian Team Playbook
The 30-minute handover meeting agenda
Keep this running order beside the shared notes:
- Minutes 0-5: confirm the scope and transfer date.
- Minutes 5-12: inspect the next week's priorities and risks.
- Minutes 12-22: run a successor dry run.
- Minutes 22-27: decide what can transfer and what needs work.
- Minutes 27-30: read back owners, dates and follow-up arrangements.
These time boxes are a starting point. If the review reveals a material blocker, record it and arrange the work needed to resolve it. Reaching minute thirty does not make the handover ready.
Minutes 0-5: confirm what is changing hands
Start with one sentence describing the transfer: “From Monday, Sam will own the weekly client update and the outstanding interview schedule.” Name anything excluded, such as approving additional scope or negotiating fees.
Confirm the effective date and the manager who can resolve questions after it. If the successor is covering temporarily, state which decisions they can take and which should wait or go to the manager.
Ask the successor what they most need to leave the meeting able to do. Choose one achievable task for the dry run. The group should agree what success looks like before starting it.
Minutes 5-12: inspect the next week
Review the next three consequential actions, using the actual dates and owners in the pack. For each, ask what could stop progress and who needs to be involved.
A fictional example might be a client update due Thursday. The draft is ready, but a revised delivery date still needs sponsor approval. The successor needs to know which date can be communicated and who will confirm the revision.
Open the supporting material when the distinction matters. Do not resolve a disagreement about approval status by choosing the most confident recollection. Mark the point as unconfirmed and assign someone to verify it.
Park background detail that does not change the next action. Keep any urgent uncertainty visible for the review decision later in the meeting.
Minutes 12-22: run a successor dry run
Give the successor control of the document or screen. Ask them to use the pack as they would after the transfer. The outgoing employee should observe before helping, so the group can see where an instruction depends on an explanation that has never been written down.
The Association for Project Management's research summary recommends operational dry runs as part of project handover. Here, the exercise is adapted to a successor's immediate work rather than a complete project launch. APM project handover research
For the client-update example, use this prompt:
“Prepare the opening points for Thursday's update. Find the current delivery position, identify what you can state confidently and show where you would escalate the unapproved date.”
Watch for three things: whether the successor can locate the current source, choose a sensible next action and identify the boundary of their authority. Ask them to explain their reasoning briefly.
If they get stuck, capture the exact gap. “Could not distinguish the accepted schedule from the proposal” gives someone a correction to make. “Needs more confidence” leaves the problem unclear.
Use a draft or safe practice case. Do not send a client message, change a live system or make a financial commitment merely to demonstrate readiness. The exercise should preserve the same approval requirements as the real task.
Minutes 22-27: decide what can transfer
The manager reviews the observed result and the unresolved questions. Separate the responsibilities that are ready from those with a limitation or blocker. One successful exercise does not establish that every part of the role is covered.
For each gap, record an action, owner, due date and interim arrangement. In the fictional example:
“Outgoing lead will identify the accepted schedule and add the approval source by Tuesday, 10 a.m. Manager will review the correction. Until then, Sam will use the currently approved date and route change requests to the manager.”
Check that the named people agree to those responsibilities. If a blocker cannot be resolved before departure, the manager needs to assign continuing ownership. Do not leave the outgoing employee as the assumed fallback indefinitely.
Minutes 27-30: read back the agreement
Close by reading out the transfer date, the responsibilities accepted, remaining limitations and the owner of each action. Ask the successor to state their first next step in their own words.
Agree where corrections will be recorded and who will check them. Set a follow-up review only where an unresolved issue or upcoming first task warrants one. For example, the manager might review the first client-update draft before it goes out.
Your meeting record can be short: review date, attendees, task attempted, result, transfer decision and open actions. Keep it beside the current pack so the successor can see what was agreed.
After the meeting, update the material rather than leaving corrections only in personal notes. The useful outcome is a successor who can proceed and a manager who can see exactly where support is still required.
