Writing a Handover Note the Next Person Can Act On

A handover note works when the person covering for you can make a decision without calling you. Most handover notes fail because they list tasks instead of decisions. A task list tells someone what exists. It does not tell them what to do when something goes wrong, which is the only reason they are reading the note.

The fix is small. Write the note around three things: decisions that are pending, things that are stuck and why, and what you would do next. Everything else is already in your project tool.

Why task lists fail

Here is a real shape of a bad note, cleaned up:

Handover for two weeks leave.

- Client redesign: in progress, see board

- Vendor invoices: waiting on finance

- New starter onboarding: Tuesday

- Weekly report: due Fridays

Nothing here is untrue. All of it is useless. The person covering does not know whether the redesign is behind, who at the client to talk to, what "waiting on finance" means, or what happens if finance says no. They will find out by messaging you on holiday.

The same handover, rewritten

Handover for two weeks leave, back on the Monday after next.

>

Client redesign. We agreed to two rounds of feedback and we are in round two. If they ask for a third round, say yes but flag that the date moves by a week. The designer has the file history and knows what we already rejected in round one. Do not reopen the navigation question, it was settled, and reopening it costs about four days.

>

Vendor invoices. Three are sitting with finance and have been for a fortnight. If they are still unpaid by the end of next week, the vendor will chase and they are entitled to. Approve them yourself up to the usual limit. Anything above that goes to the finance lead.

>

New starter, Tuesday. Laptop is ordered, accounts are not created yet. If accounts are not ready by Monday evening, have them start on reading and the customer calls, not the codebase. Do not let them sit doing nothing on day one.

>

Weekly report. Skip it. Nobody has asked a question about it in months. If someone does ask, that is useful information.

Same four items. Completely different note. The second one lets someone act.

The template

Four lines per item, at most.

• What it is, in one sentence, assuming the reader knows nothing
• Where it actually stands, including anything already decided that should not be reopened
• What to do if it goes wrong, with a named limit on what they can decide alone
• Who to ask if it goes past that limit

If an item does not need all four, it probably does not need to be in the note.

Say what you will not do

A good handover also says what should stop. Not everything needs cover. If the weekly report can pause for two weeks, say so explicitly, because otherwise a conscientious person will produce it and you will have paid for something nobody reads.

The same goes for meetings. List the ones worth attending and the ones to decline on your behalf, and check whether the cover period lands on a public holiday somewhere else, because a covering person who is also off is no cover at all. Give permission clearly, because people covering for someone else are usually more cautious than the person they are covering for.

The two questions that make notes better

Before you send the handover, ask yourself two things.

What would make someone call me? Whatever that is, write the answer down. If your honest answer is "I do not know either", say that. "If the vendor pushes back on the deadline, I do not know what we should do. Ask the finance lead, they own the relationship" is more useful than silence.

What have I decided that is not written anywhere? This is where handovers leak most. You settled something in a corridor conversation three weeks ago. Nobody else knows. The person covering will happily reopen it, spend two days, and land where you already were.

Where this belongs

The best place for a handover note is next to the work, not in a chat message that scrolls away by Wednesday. If your leave dates and your project records live in different systems, the note becomes an orphan the moment you go. Enough warning helps too, which is what notice periods people will actually follow buy you.

This is one thing a workspace like SicherOne is built around: leave and project records sit together, so the board itself can show that a task owner is away and who is covering. That does not write the note for you. It just means the note is somewhere the covering person will actually look.

Write it two days early

The last practical point. Write the handover two days before you leave, not on the final afternoon, and put it on the checklist for the week before. Two things happen. You notice a decision you have not made and still have time to make it. And your colleague can read it while you are still there to answer the obvious question, which is almost always "what does this actually mean".

A handover note is a small piece of writing that saves someone a bad week. It deserves half an hour, and it works best when it is about judgement rather than tasks.