How to Write a Project Handoff Note Nobody Has to Chase

You are leaving a project for two weeks, or for good, and the person taking over will spend their first three days messaging you on holiday unless you write a decent project handoff note. Most handoffs fail not because people forget the big things, but because the small, unwritten things live only in one head.

I have watched handoffs succeed and collapse across product, agency and operations teams. The good ones share a structure, and it fits on two pages. Here is how to write one, what to leave out, and how to hand it over so it actually gets read.

What a project handoff note is for

A handoff note has one job: let someone make the next three decisions without you. It is not a history of the project, and it is not a full documentation dump. If your colleague can answer "what is happening, what is next, who do I ask, and what might go wrong" after ten minutes of reading, the note worked.

That framing matters because it changes what you write. A note built to record everything runs to 15 pages and nobody finishes it. A note built to enable the next decisions stays short, because most of what you know is not needed this week.

The seven sections that cover almost every handoff

Use these headings in this order. Fill each one in plain sentences, not fragments.

1. Status in three lines. Where the project stands today, using a date and a number where you can. "Phase two is 70 percent done, launch is set for 3 December, and we are one week behind on design review."
2. Open decisions. Every decision that is pending, who owns it, and the deadline. This is the section people skip and the one that causes the most chaos.
3. Next five tasks. Specific actions, each with an owner and a due date. Not "follow up with vendor" but "confirm the revised quote with Lena at the print vendor by Thursday."
4. People map. Who matters on this project, what they care about, and how they like to be contacted. One line each.
5. Known risks. What could go wrong in the next month and what the early warning sign looks like.
6. Where things live. Links to the tracker, shared folder, key documents and recurring meetings.
7. Unwritten rules. The habits and sensitivities that never made it into any document.

If you already write clear briefs, much of this will feel familiar. The same discipline from briefing a team without writing a novel applies here: say what matters, then stop.

The unwritten rules section is where handoffs are won

Everything in sections one to six can usually be pieced together from trackers and email threads. Section seven cannot. It is the knowledge that took you months to collect, and it is what makes your replacement look competent or clumsy in their first week.

Examples of what belongs there:

• "The client's finance lead approves invoices only on Tuesdays. Send them Monday afternoon."
• "Marco says yes in meetings and changes his mind by email. Always confirm decisions in writing within 24 hours."
• "The weekly report goes to six people, but only the operations director reads it. Put her items first."
• "Do not mention the old launch date. It is a sore point after the delay in August."

Write these with care and keep them professional, because notes get forwarded. Describe behavior and what works, not personality. "Prefers a call before bad news lands in writing" is useful. "Gets defensive" is not.

A counter take on the full handover meeting

The standard advice is to schedule a long handover meeting and walk through everything together. I think that usually wastes the meeting. When you talk through a project live, the other person nods along, remembers maybe a third, and has nothing to return to later.

A better order is to send the note first, give your colleague a day to read it, and then hold a 30 minute call where they ask questions. Their questions show you exactly where the note is unclear, and you can fix it on the spot. The written note becomes the lasting record, and the meeting becomes a review instead of a lecture.

Take notes during that call and add the answers back into the handoff document. Our guide to writing meeting notes people actually read has a simple format that works well for this.

How long it should be and how to write it

For a typical project lasting one to six months, aim for 600 to 1200 words. Under 400 words, you are probably skipping open decisions or risks. Over 2000, you are writing history. Some practical habits:

• Write it over three days, not one evening. Start a rough draft early in your final week and add to it every time you answer a question or make a call. You will remember far more this way.
• Use names and dates. "Someone in legal is reviewing it" helps no one. "Priya in legal has the contract, expected back 18 November" does.
• Mark confidence. If you are unsure about something, say so. "I think the budget cap is 40,000, but confirm with finance" is honest and prevents a costly assumption.
• Put the most urgent thing first. If a decision is due in two days, it should sit in the opening lines, not in section five.

A short example

Status: Website rebuild is at content stage. 22 of 31 pages are drafted. Launch is fixed for 3 December and cannot move because of the trade show.

Open decision: Whether to cut the case studies page from launch. Owner: Daniel. Needed by 15 November, or design cannot finish on time.

Next task: Send the final homepage copy to Anna for legal review by Friday. She needs three working days.

Unwritten rule: Daniel decides faster when you give him two options and a recommendation, not an open question.

Notice what is missing: background, the story of how the project started, and who said what in July. None of it helps the next decision.

After the handoff

Offer one clear window for questions, such as "I am reachable by message until Friday at 5, then only for emergencies." That boundary protects your time and pushes your colleague to read the note instead of asking you directly. Then step back. Checking in every day signals that you do not trust them, and it delays the moment they truly own the work.

Finally, have the new owner send the first status update themselves, in their own voice. If you want that update to land well, point them to our piece on why status updates get skipped.

Frequently asked questions

What should be included in a project handoff?

Include current status, open decisions with owners and deadlines, the next few tasks, key contacts, known risks, links to where files live, and any unwritten working habits. The goal is that the new owner can act this week without contacting you. Leave out project history unless it explains a current decision.

How do you write a handover note when leaving a job?

Write one note per major project or responsibility instead of one giant document. Start it at least a week before you leave, add to it daily, and send it before your final handover call. Ask your manager to confirm who owns each item so nothing ends up without an owner.

How long should a handover take?

For most projects, plan for about three days of drafting alongside normal work, a day for the new owner to read, and one 30 minute question call. Complex projects with many stakeholders may need a second call. A handoff squeezed into your final afternoon almost always leaves gaps.