Project hand-offs are where things break. The original person knew the context, the history, the informal agreements. The new person has none of that — and often has a different approach entirely.
A good hand-off isn’t just dumping files. It’s a deliberate transfer of knowledge, expectations, and accountability. Here’s how to do it right.
Before the Hand-Off: Prepare the Package
Don’t hand off chaos. Gather the following before you pass anything to someone else:
- Current status — What stage is the project in? What’s done, what’s in progress, what’s blocked?
- Outstanding decisions — What decisions are still open? Who needs to make them? What’s the deadline for deciding?
- Known risks — What could go wrong? What’s already gone wrong? How was it managed?
- Contact map — Who are the stakeholders, vendors, and decision-makers? What’s their role?
- Why this matters — What’s the purpose of this project? What does success look like? What does failure look like?
The Hand-Off Meeting: Not a Lecture
A hand-off meeting should be a conversation, not a presentation. The new person needs to be able to ask questions, push back, and confirm understanding.
Structure:
- Walk through the project status together (not just present)
- Cover the outstanding decisions and risks
- Discuss any decisions you’ve already made that they might question — and explain why
- Agree on a check-in cadence for the first few weeks
Give them the “why” behind your choices. Not just what you did, but why you did it. That context prevents them from undoing work they don’t understand.
What to Document (Not Just Say)
Verbal hand-offs disappear. Document the following in a shared location:
- Project brief — What it is, why it exists, who requested it
- Current status — Stage, key milestones, what comes next
- Outstanding items — Decisions, approvals, or actions still needed
- Stakeholder list — Names, roles, contact info, their level of engagement
- Known issues — What has already gone wrong, how it was handled, what to watch for
Common Hand-Off Mistakes
Leaving it too late. Hand-offs take time. If you start the process when you’re already moving to a new role, you won’t have the bandwidth to do it well.
Assuming the new person will figure it out. They won’t. Not because they’re incompetent — because they don’t have your context.
Not confirming what’s been handed off. After the meeting, send a brief summary: “Here’s what’s been transferred, here’s what I’m still responsible for, here are the next steps.”
When You’re Receiving a Hand-Off
If you’re the person taking over:
- Ask for the project brief and contact map before the meeting
- During the meeting, confirm your understanding of each key item
- After the meeting, send a summary back: “Here’s what I understood — please correct anything I’ve missed”
- Set up your own tracking system early; don’t rely on the previous person’s notes
The Hand-Off Checklist
- Current status documented and shared
- Outstanding decisions listed with owners and deadlines
- Risks and mitigation approaches noted
- Stakeholder map provided
- Hand-off meeting held (not just files sent)
- Post-meeting summary sent confirming transfer
- Check-in schedule agreed for first month
Related
- How to Write a Project Brief in 10 Minutes — the starting point for any project worth handing off
- How to Escalate Problems to Your Manager — when a hand-off surfaces a problem you can’t solve alone
- How to Write a Weekly Status Update — keep stakeholders informed through any project transition
Office Email Templates Bundle — templates for handoff emails, time-sensitive follow-ups, and status updates.