Photo: 2H Media / Unsplash
A stalled project is sometimes passed to another person with a collection of files and very little explanation. The recipient must then reconstruct the goal, work out which version is current and guess what prevented progress. A usable handoff reduces that uncertainty. It does not hide the project’s condition or assume that transferring ownership automatically solves its problems.
The first task is to describe the intended result. A folder name is not a goal, and an old deadline may no longer reflect the situation. Write a short statement explaining what the finished work needs to accomplish and who will use it. That statement helps the next person distinguish necessary work from material that was collected along the way.
Show the current state plainly
Separate completed work from work that is merely started. A draft may exist without having been reviewed. A supplier may have been contacted without having confirmed anything. A checklist that marks both as done can create problems for the person taking over. Use descriptions that explain the actual state rather than a reassuring color or vague percentage.
Identify the current working file and the location of supporting material. If several versions exist, explain which one should be used and why. Preserve required records, but avoid making the recipient inspect every old attachment before beginning. A simple index can be enough to distinguish the active document, background information and material kept only for reference.
Name the obstruction
State what is preventing the next meaningful step. The obstruction may be an unanswered decision, missing information, unavailable time or a dependency on another task. Describe it without turning the handoff into a judgment about someone else. The next owner needs to understand the obstacle, not inherit an argument about how frustrating it has been.
Then identify what has already been tried. A brief account can prevent repeated effort, especially when an approach failed for a reason that is not obvious from the files. Include relevant limits. A contact attempt that received no answer does not establish that a person has refused, and an untested idea should not be listed as a proven solution.
Make authority and responsibility explicit
A handoff can fail when the recipient receives responsibility without the ability to make necessary decisions. Clarify what the new owner may decide, what still needs approval and who can resolve a disagreement. For a small project, this may take only a few sentences. The important point is to avoid leaving those boundaries implicit.
Confirm that the person is actually accepting the work. Sending a document does not establish agreement about capacity or timing. If the handoff is part of a team process, use the team’s existing method for assigning ownership. A clear acceptance matters more than an elaborate document that arrives without context.
Offer a first action, not a complete script
Finish with one suggested next action and explain why it matters. The new owner should still be able to change the approach. A useful first action might be confirming a requirement or reviewing a specific draft. It should be small enough to begin without reconstructing the entire project history.
Arrange a brief check after the recipient has examined the material. That check is an opportunity to answer questions and correct omissions, not to retake control. A responsible handoff leaves the next person with a clear destination, an honest view of the current state and enough context to choose how to proceed.
Reflection: What would someone need to know to take over one current project without relying on its original owner’s memory?
A Handoff Note Template
A handoff does not need to be elaborate, but it helps to follow the same order each time so the recipient knows where to look. The outline below can fit on a single page for most small projects.
- Purpose: One or two sentences describing what the finished work must accomplish and who will use it.
- Status: What is complete, what is started but unreviewed and what has not begun.
- Working location: The current file or folder, with a short note on which version to use.
- Blocker: The specific thing preventing the next step.
- Already tried: Approaches attempted and what was learned from each.
- Authority: What the new owner can decide, what needs approval and from whom.
- Suggested first action: One small, concrete step and the reason it comes first.
- Check-in: When a short follow-up conversation will happen.
The template is a guide, not a form to be filled out mechanically. If one heading does not apply, it can be left out. If a project has a single unusual risk, it deserves its own line even if the template does not mention it.
What Gets Lost in Most Handoffs
Even careful handoffs tend to drop the same kinds of information. These are worth checking before the work changes hands.
- Informal agreements. A promise made in a hallway conversation or a quick phone call may never have been written down. If someone outside the project expects something, the new owner needs to know.
- The reason behind an odd choice. A decision that looks strange from the files may have been made for a good reason. Without that explanation, the next person may undo it and rediscover the problem the hard way.
- Relationships and preferences. Some contacts respond better to a short message, while others prefer a call. Sharing practical notes of this kind can save time, as long as they stay respectful and work-related.
- Upcoming dates that are not on any calendar. A renewal, a review or a follow-up that existed only in the previous owner’s memory can easily slip.
Receiving a Project Well
The handoff is a two-sided exchange, and the person taking over has a part to play as well. A few habits make the transition smoother for everyone.
Read before reacting
Go through the note and the main working file before forming a judgment about how the project was handled. First impressions of a stalled project are often harsher than the full picture warrants.
Write down the questions in one place
Rather than sending a stream of separate messages, collect questions and bring them to the agreed check-in. This respects the previous owner’s time and often reveals that several questions share a single answer.
Confirm the boundaries early
If the authority section is unclear, ask about it before making a significant change. It is easier to clarify a boundary at the start than to reverse a decision later.
Be honest about capacity
If, after reviewing the work, it becomes clear that the timeline or scope is not realistic, say so promptly. Accepting a project does not mean accepting every assumption that came with it. A clear conversation at the beginning protects both the work and the working relationship, and it gives the stalled project its best chance of moving again.
Quick check
How much did you catch? Tap a question to see the answer.
1. What should come before a file index in a handoff?
Answer: A clear statement of the intended result and who will use it.
2. How should completed and started work be described?
Answer: Separately, with factual descriptions of what has and has not happened.
3. Why confirm acceptance of a handoff?
Answer: Sending files alone does not establish agreement about responsibility, capacity or timing.

New messages, real moments from the road, and the All Is Well Project. Follow along and say hello.

The lessons behind everything Chris teaches. Start with three chapters, free.
Turn the lessons into your comeback.
Talk it through free with the Team Dorrity coach, or work with Chris one-on-one in The Better Than Back Experience.















Leave a Reply