Work messages6 min read

How to write a handover note a colleague can act on

A handover note fails when a colleague has to read it twice to find out what is actually done. The fix is structural, not stylistic: sort the same facts into finished, in progress, blocked, and who to ask. This guide shows how to reorganize a narrative brain dump into a note someone can act on, without inventing owners, dates, or commitments.

Start by sorting facts, not by writing better prose

Most handover notes are written in the order things happened. That feels natural to the writer and is slow for the reader, who needs to know what still needs doing. Before you touch the wording, list every fact in the draft and label it: finished, in progress, blocked, or a person to contact.

The labels do the work. A sentence like "I've been going back and forth with the vendor about the invoice" contains a status (in progress), a topic (the invoice), and a contact (the vendor). Once you see those parts separately, the note almost writes itself. Keep the original wording for anything uncertain; do not upgrade "waiting to hear" into "confirmed".

Before

Hi Sam, picking up from where I left off. I've finished the Q3 report and sent it to Priya. The vendor invoice is still going back and forth, I'm waiting to hear from them. The new dashboard is blocked because I still don't have access to the analytics account. If anything comes up, Dev is the one who knows the client history.

After

Hi Sam, here's where things stand. Finished: the Q3 report, sent to Priya. In progress: the vendor invoice, still going back and forth; I'm waiting to hear from them. Blocked: the new dashboard, because I still don't have access to the analytics account. Who to ask: Dev knows the client history. Picking up from where I left off.
The facts are identical, but the reader can now scan for status instead of reconstructing it from a paragraph. The greeting and closing line are kept so the note still sounds like the same person.

Keep the status words the original used

The most common damage in a handover rewrite is a status that drifts. "Waiting to hear" becomes "pending approval," which implies someone is actively deciding. "Blocked" becomes "in progress," which hides that the work cannot move. When you reorganize, copy the status wording rather than paraphrasing it.

This matters most for blockers. A blocker should say what is stopped and why, using the cause the original gave. If the original says access is missing, the note says access is missing. Do not add a workaround, a person who might help, or a date by which it will be resolved unless the writer said so.

Before

The onboarding pack is basically done, I just need to check the last section. The client call notes are blocked until legal gets back to me. I haven't started the training slides yet.

After

Onboarding pack: nearly done, I just need to check the last section. Client call notes: blocked until legal gets back to me. Training slides: not started yet.
Each item keeps its original status word (nearly done, blocked, not started) and its original cause. The edit only separates the items so a reader can see three different states at a glance.

Name the person to ask, not the department

A handover note is only actionable if the reader knows who to contact. If the original names a person, keep that name attached to the specific topic. If it names a team or says "someone in finance," keep that too; do not promote a team into a named individual.

Put the contact next to the thing it relates to, not in a separate list at the bottom. A reader looking at a blocked item should see the contact in the same line. This is where a scattered draft usually improves most, because the names are already there, just far from the work they belong to.

Before

I've asked Marcus about the contract renewal and he's looking into it. The budget sheet needs someone in finance to sign off. Also Dana has the login for the shared drive if you need it.

After

Contract renewal: with Marcus, who is looking into it. Budget sheet: needs sign-off from someone in finance. Shared drive login: Dana has it.
Each contact now sits beside the item it belongs to. Marcus stays a named person, finance stays unnamed, and Dana's login is tied to the shared drive rather than floating at the end.

Separate what you promised from what you did

Handover notes often mix completed actions with commitments. "I said I'd send the summary by Friday" is not the same as "I sent the summary." Keep commitment wording intact, including any day or date the writer gave, and place it under in progress or open rather than finished.

If the original hedges, keep the hedge. "I should be able to finish the review tomorrow" is a soft commitment, and rewriting it as "review finishes tomorrow" turns an intention into a promise the reader may rely on. The reader needs to know how firm each item is.

Before

I told Ravi I'd get him the revised figures by Thursday. I should be able to finish the review tomorrow. The slides are done.

After

Done: the slides. Open: revised figures for Ravi, which I said I'd get to him by Thursday. Open: the review, which I should be able to finish tomorrow.
The promise to Ravi and the soft estimate for the review are kept as commitments, not reported as completed work. Thursday and tomorrow stay exactly as written.

Check the note against the original before sending

After restructuring, read the new note beside the old one and compare item by item. Look for names, numbers, dates, weekday names, and any word like today or tomorrow. Then check negations and conditions: "don't send until" and "only if" must survive the rewrite.

A rewrite tool can help with the mechanical part of this, but the comparison is yours. If you use Lightphrase to retone or restructure a selected draft, treat the output as a proposal and check it against the original before pasting it into the handover message. The tool works on the text you select in an editable field; it does not know which facts are load-bearing.

  • Read the finished, in progress, blocked, and contact lines against the original draft.
  • Confirm every name, number, and date appears exactly as the writer gave it.
  • Check that no hedge became a promise and no blocker became progress.
  • Make sure any condition or negation is still attached to the same action.

Take it into your next draft

Before you send a handover note, sort every fact into finished, in progress, blocked, or who to ask, and keep the original status words, names, dates, and hedges attached to the right item. Then read the new note beside the old one and confirm nothing was added, upgraded, or dropped. The structure is yours to change; the facts are not.