Read a sample: 1. What a Successful Handoff Makes Clear
At the end of a busy afternoon, Maya sends her colleague Jordan a message:
> “Can you take over the client update? Everything is in the folder. Thanks!”
Maya has transferred a link and made a request. She may even feel relieved that the work is covered. Jordan, however, opens the folder to find a draft update, several background documents, and comments from different people. The client is expecting something soon, but the message does not say what has been completed, which version to use, or what Jordan is supposed to do next.
Jordan might be able to work it out. That effort, though, is part of the handoff. The less Maya explains, the more Jordan must investigate, guess, or interrupt someone else.
A successful handoff is not simply the movement of a task from one person’s list to another’s. It is a transfer of enough understanding and responsibility for the next person to act. The sender makes the work’s current state visible. The recipient has a chance to ask questions, confirm what they understand, and agree to take the next step.
That does not mean every transfer needs a long document or a formal meeting. A familiar, routine task may need only a few sentences. A complex project or an ongoing responsibility may need a conversation and a written record. The measure is whether the new owner can find their footing without relying on assumptions that matter.
This chapter introduces four elements that make that possible: the current status, unresolved questions, the next action, and confirmation. We will follow Maya and Jordan’s client update to see how each element changes an ordinary request into a workable handoff.
People often say they have “handed something off” when they have forwarded an email, shared a file, or mentioned the work in a meeting. Those actions can begin a transfer, but they do not necessarily establish who is doing what.
Suppose Maya forwards Jordan the client’s original request with the note, “For you.” Jordan now has the original request, but not Maya’s knowledge of what has happened since it arrived. Maya knows which sections of the update are drafted, which information still needs review, and who can answer a remaining question. None of that knowledge automatically travels with the email.
The reverse can happen too. Maya may provide a thorough explanation but never ask whether Jordan can take the work. Jordan reads the message as background information; Maya assumes Jordan has accepted ownership. Both may leave the exchange feeling informed, while the task remains unclaimed.
A useful distinction is:
- Sharing information gives someone material to read.
- Requesting help asks someone to contribute.
- Handing off ownership asks someone to take responsibility for an identified part of the work, with an understood next step.
These can overlap, but they are not interchangeable. If Maya wants Jordan only to review a paragraph, she should say so. If she wants Jordan to finish and send the update, she should make that request just as clear—and give Jordan an opportunity to accept it.
Ownership also has a scope. Jordan might own preparing the next draft while Maya remains responsible for the client relationship. Or Jordan might take over the update through delivery. Neither arrangement is inherently better. The problem is leaving the boundary unstated when it affects who acts, who decides, or who follows up.
The first question a recipient usually needs answered is: Where does this stand now?
Status is not the full story of how the work arrived here. It is a current picture that helps someone enter the work. For Maya’s client update, that picture might include:
> “The draft is written, and the delivery timeline has been checked with the project team. The section on the support transition still needs review. Nothing has been sent to the client yet.”
In a few sentences, Jordan can distinguish finished work from work that remains open. The final sentence matters because it prevents a consequential misunderstanding: a polished-looking draft is not necessarily an approved or delivered update.
Compare that with:
> “We’ve been working on the update since the client asked for more detail. I started a draft, then the project team had some comments, and I moved a few things around.”
The second version describes activity, but Jordan still has to infer the present state. Is the draft ready? Have the comments been resolved? Has anyone sent an earlier version? The history may be useful later, but it does not yet orient the recipient.
A status summary can be brief without being vague. Try naming what is complete, what is underway, and what has not happened when those distinctions affect the next action. You do not need to fill every category for every task. You do need to say enough that the recipient does not mistake a draft for a final version or assume an unfinished item has already been handled.
If the status is uncertain, say that too:
> “The draft is ready for review. I believe the timeline was checked, but I have not confirmed whether the latest change was included.”
That is more useful than presenting the timeline as verified. Jordan can now decide what to check rather than unknowingly building on an assumption.
A handoff often occurs precisely because work is unfinished. That is not a flaw. An unfinished item becomes difficult when the recipient cannot see that…