Work

Handoff Document Template

A handoff fails on the things nobody wrote down: the promise made in a hallway, the decision half made, the warning sign only the outgoing person knows. This handoff document template has a section for each, and ends with a read-back so you know the handover landed. Copy it, or start from the handover notes example closest to yours.

Updated 2026-10-27

Copy and adapt

The template

Handoff documentTemplate

Handoff: [what is being handed over], [outgoing] to [incoming]

Written: {{date}} Effective from: [date and time] Type: [permanent / leave cover / shift / account] Outgoing person reachable until: [date, and how] Related: [[Project, service or account]]

Status in three sentences

[Where things stand, what is going well, what is most at risk.]

Open items

[Item]: [current state]. Next step: [action] (@[incoming]) @due(YYYY-MM-DD)

Decisions in flight

[Decision]: who decides now: [name]. Deadline: [date]. My recommendation: [...] because [...]

Watch list

If [warning sign], then [first action]. Escalate to [name].

Open loops and promises

I told [person] I would [thing] by [date]. Status: [...]

People

[Name, role]: [why they matter, how they prefer to be contacted]

Where things live and access

[Document, repository or system]: [location]. Access: [granted on date / requested]

Recurring duties

[Duty], [how often], [where the how-to lives]

Read-back

Incoming person's summary of the top three items: [in their words]
Questions still open: [...]
Confirmed by [incoming] on [date and time]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.Software handoff when an engineer changes teams

When it fits: Use this when an engineer is moving to another team, ownership of a service changes permanently, and the outgoing person stays in the building but will soon be busy with other work.

Software handoff when an engineer changes teamsExample 1

Handoff: notifications service, Kenji Watanabe to Olivia Hart

Written: 2026-11-13 Effective from: 2026-11-16, 09:00 Type: permanent Outgoing person reachable until: 2026-12-18, chat any time, plus a 30-minute call every Thursday Related: [[Notifications service]]

Status in three sentences

The service is stable: 99.4 percent delivery over the last 30 days and no incidents since August. The biggest risk is the Apple push certificate, which expires 2027-01-14 and has never been renewed by anyone but me. The SMS fallback decision is half made.

Open items

Renew the Apple push certificate. Steps are in the runbook, section 4; it takes about an hour and needs the shared developer account. (@Olivia) @due(2026-12-15)
PR 2231, batching for digest emails. Reviewed once, needs a second review and a staging test. (@Olivia) @due(2026-11-27)
Flaky test in the retry suite, fails about 1 run in 20. Ticket 5120. (@Olivia) @due(2026-12-11)

Decisions in flight

Drop SMS fallback for password resets? Who decides now: Olivia with Dev (product). Deadline: Dec 4 planning. My recommendation: drop it; it costs about $1,900 a month and handles 0.3 percent of resets.

Watch list

If the delivery rate drops below 97 percent, check the push provider's status page first. Twice this year it was them, not us. Escalate to the on-call lead.
If the queue depth passes 50,000, the digest job is running during peak. Pause it from the admin panel.

Open loops and promises

I told the mobile team (Rosa) we would add a delivery-receipt webhook by Dec 1. Not started. Olivia to confirm or renegotiate the date with Rosa this week.

People

Rosa Jimenez, mobile lead: main consumer of the service, prefers written requests in the mobile channel.
Dev Patel, product manager: owns the SMS decision with Olivia.

Where things live and access

Repository, runbook and dashboards: linked from the service note. Access: Olivia granted admin 11-12.
Shared Apple developer account: access requested 11-12, pending.

Read-back

Olivia's summary: certificate by Dec 15, Rosa's webhook date needs an answer this week, SMS decision at Dec 4 planning.
Questions still open: whether the digest job can move to 03:00 UTC permanently.
Confirmed by Olivia Hart on 2026-11-13, 16:40

2.Parental-leave handover

When it fits: Use this when you will be out for months, the work is split between two or three people, and the hardest part is saying who decides what while you are away.

Parental-leave handoverExample 2

Handoff: marketing programs, Nadia Haddad to Chris Lam and Ellen Brooks

Written: 2026-11-30 Effective from: 2026-12-07 Type: leave cover, back 2027-04-05 Outgoing person reachable until: 2026-12-04. On leave, I will not check email or chat. For something truly urgent, Ellen contacts my manager, Tom, who decides whether to reach me. Related: [[Marketing programs]]

Status in three sentences

The Q1 product launch campaign is planned and briefed; it goes live Jan 19. The agency contract renews Feb 28 and needs a decision. Everything else is routine and documented below.

Who decides what while I am away

Campaign content and timing: Chris.
Budget, agency and anything over $5,000: Ellen.
If Chris and Ellen disagree: Tom.

Open items

Launch campaign live, assets approved by product (@Chris) @due(2027-01-19)
Agency renewal: renew, renegotiate or end (@Ellen) @due(2027-02-13)
Q1 budget report to finance (@Ellen) @due(2027-01-09)

Decisions in flight

Agency renewal: my recommendation is to renew for six months, not twelve, and ask for the paid social rate to match the 2025 rate. Their Q3 results were good; Q4 was average.

Watch list

If the launch date moves, the paid media booking ($18,000) can move once without a fee if we tell the agency 10 days ahead.

Open loops and promises

I told the sales team (Marcus) we would run a customer webinar in February. No date set. Chris to agree a date or tell Marcus it moves to April.
I promised the designer, Lucia, feedback on her portfolio by Dec 4. Done 12-02.

People

Tom Reyes, my manager: tiebreaker and only route to me.
Agency contact, Priya at the agency: answers same day, prefers calls for anything about money.

Recurring duties

Weekly newsletter, Tuesdays: Chris. Checklist is pinned in the newsletter note.
Monthly spend reconciliation, first Monday: Ellen.

Read-back

Chris: launch on the 19th is mine, webinar date or a message to Marcus by Dec 18.
Ellen: agency decision by Feb 13, budget report by Jan 9, anything over $5,000 is mine.
Confirmed by Chris Lam and Ellen Brooks on 2026-12-03

3.Clinical shift handover, night to day

When it fits: Use this for a nurse's end-of-shift handover worksheet on a hospital unit, where the receiver needs severity, the plan and the warning signs for each patient in a few minutes. The care record itself lives in your employer's system.

Clinical shift handover, night to dayExample 3

Shift handover: Unit 6B, beds 1 to 12, night to day

Written: 2026-11-21, 06:45 Effective from: 07:00 Type: shift. Night RN to day RN. Note: Handover worksheet only. The care record is in the hospital EHR and follows the unit's handover policy. No names, dates of birth or record numbers on this sheet; it is shredded at end of shift.

Unit status in three sentences

Nine patients, one discharge planned, one admission expected from the ED around 09:00. One nursing assistant short until 11:00. Beds 3 and 11 need the closest watching.

Bed 3, 78F (watcher)

Situation: community-acquired pneumonia, day 3 of IV antibiotics. On 2 L oxygen.
Background: COPD at home, independent before admission.
Assessment: sats 93 to 95 percent overnight, afebrile since 02:00, eating little.
Action list: blood cultures from yesterday pending; chase the lab at 09:00. Dietitian referral not yet seen.
Watch: if sats fall below 92 percent on 2 L, escalate to the medical team per the unit's escalation pathway.

Bed 7, 64M (stable)

Post-op day 1, knee replacement. Pain controlled overnight. PT to mobilize at 10:00. Watch for calf pain or swelling.

Bed 11, 85M (watcher)

New confusion from 01:00, pulled at his IV once. Bed alarm on, falls precautions in place. Medical team informed at 01:30 and reviewing on the morning round. Daughter visiting at 11:00 and asked to be told about any change.

Open items for the unit

Bed 9 discharge: pharmacy meds ready by 10:00, transport booked for 11:30.
ED admission around 09:00: bed 12 is clean and made.

Read-back

Day RN repeated: bed 3 cultures and sats threshold, bed 11 confusion and the daughter at 11:00, ED admission at 09:00.
Confirmed at the bedside for beds 3 and 11, 07:10

4.Account handover between account managers

When it fits: Use this when a client relationship moves to a new account manager, the renewal is months away, and the client will judge the change by whether they have to repeat themselves.

Account handover between account managersExample 4

Handoff: Harlow & Finch account, Grace Liu to Daniel Osei

Written: 2026-11-19 Effective from: 2026-12-01 Type: permanent (Grace moves to the enterprise team) Outgoing person reachable until: 2027-01-15, chat or a call booked through her calendar Related: [[Harlow & Finch]]

Status in three sentences

Harlow & Finch is a 42-store home goods retailer paying $186,000 a year, renewal on 2027-03-31. The relationship is good with operations and weak with finance. Their champion, Mia Torres, leaves the company on Jan 9, which is the biggest risk to the renewal.

Open items

Joint call with Mia and her successor before Jan 9 (@Daniel) @due(2026-12-18)
Support escalation on inventory sync delays, ticket 88213. Fix promised for the Dec 10 release. (@Daniel) @due(2026-12-12)
Quarterly business review deck (@Daniel) @due(2027-01-22)

Decisions in flight

Multi-year renewal: finance (Owen Pratt on their side) asked for a three-year price. Our deal desk has not approved anything. My recommendation: offer two years at a flat price, not three.

Watch list

If Owen asks for usage numbers, send the store-by-store report, not the summary. He found the summary misleading in September.

Open loops and promises

I told Mia "we will look at" a 5 percent discount for a multi-year deal. Nothing was approved or written. Daniel should say so plainly in the first conversation, not let it surface at renewal.
I promised operations a training session for new store managers in January. Not booked.

People

Mia Torres, VP Operations: champion, leaving Jan 9. Prefers short calls.
Owen Pratt, Finance Director: skeptical, wants numbers in writing before meetings.
Their successor for Mia: not named yet; Mia will introduce.

Where things live and access

Contract, renewal terms and call notes: linked from the account note. CRM ownership transfers Dec 1.

Read-back

Daniel's summary: meet Mia's successor before Jan 9, correct the discount expectation early, ticket 88213 fix on Dec 10.
Confirmed by Daniel Osei on 2026-11-20, after a joint call with Mia on the same day

5.Restaurant shift notes, close to open

When it fits: Use this when the closing manager will be asleep when the opening manager arrives, and the shift notes are the only conversation they will have.

Restaurant shift notes, close to openExample 5

Shift notes: Harbor Street, Saturday close to Sunday open

Written: 2026-11-28, 23:40 Effective from: Sunday open, 08:00 Type: shift. Closing manager Tanya to opening manager Rob.

Status in three sentences

Busy night: 214 covers, $11,350 in sales. Two things need you before brunch: the dish machine and the cash count. The private party at 18:00 Sunday is confirmed.

Open items

Dish machine rinse temperature running low. Technician booked for 09:00; hand-wash station set up as backup. (@Rob)
Drawer 2 was $12 short at close. Counted twice. Recount with the morning float and note it in the cash log. (@Rob)
Short rib 86'd at 21:15. Order placed for Monday; brunch menu unaffected. (@Rob)

Watch list

Walk-in cooler read 41°F at close, usually 38°F. If it is above 41°F at open, move dairy and fish to the reach-ins and call the refrigeration contractor.

Staffing

Kayla called out for brunch. Jen covers until 13:00. You are one server short from 13:00 to 15:00.

Open loops and promises

Promised table 14 (birthday, regulars) a free dessert next visit. Written in the reservation notes.

Read-back

Rob replied at 07:52: dish tech at 9, recount drawer 2, check walk-in first thing, one server short after 1.

What belongs in a handoff document

Every top-ranking handoff template covers the same ground: an overview, the current status, open tasks, contacts and where the files are. Those sections are necessary. They are also the parts that are already written down somewhere. A handoff document earns its place by capturing what lives only in the outgoing person's head.

Status in three sentences. What is going well, what is most at risk. If you cannot say it in three, the incoming person will not be able to hold it.
Open items with a next step. Not "pricing page" but "pricing page: copy approved, waiting on legal, chase Ana on Thursday."
Decisions in flight. Half-made decisions are the first thing to stall after a handoff. Say who decides now and what you would do.
Watch list. Warning signs as "if this, then that," with someone to escalate to.
Open loops and promises. What you told people you would do.
People, access, recurring duties. The practical layer.
Read-back. Proof the handover landed.

Open loops: the section most handovers miss

The most expensive failures after a handoff are promises the incoming person never heard about: a webhook a team was told to expect, a discount someone mentioned, a training session half agreed in a meeting. None of it is in the project tracker, because none of it was ever formal.

Spend twenty minutes going back through the last month of your email, chat and meeting notes before you write anything else, and list every "I'll get back to you" and "we'll look at that." For each one, say whether it is done, still owed, or should be withdrawn. The account handover example shows the hardest kind: an informal expectation that has to be corrected early rather than discovered at renewal.

Read-back: confirm the handover landed

Writing the document is half a handover. The other half is confirming that the incoming person understood what matters most. Healthcare formalized this years ago: in I-PASS, the last step is synthesis by the receiver, who restates the plan in their own words. It works everywhere. After you walk through the notes, ask the incoming person to summarize the top three items and write their summary into the Read-back section. If their top three are not yours, you have found the gap while you can still fix it.

Shift handovers are a different shape

A shift handover happens every day, is read in minutes, and is written by someone tired. Strip the template down to status, open items, watch list and read-back, and keep the order identical every shift so the reader's eye knows where to go. The restaurant example is about as long as shift notes should be.

For clinical handovers, use your unit's agreed format (SBAR and I-PASS are the common ones) and its own handover sheet. The record of care belongs in your employer's system, not in personal notes. The clinical example on this page uses bed numbers, age and sex only, with no names or record numbers, and is there to show structure, not to replace your unit's policy.

Handing over before leave

For parental leave, a sabbatical or a long absence, the question that matters is who can decide what. Name a decider per area, a spending limit and a tiebreaker, and say plainly how (and whether) you can be reached. Then hand over a few days early and let the cover run things while you are still around.

Common mistakes

A task list with no context. Twenty tickets and no word on which one is on fire.
Writing it the night before. Finish at least three working days before you leave, so there is time for questions.
No end date for questions. Either the outgoing person is pulled back for months, or they vanish on day one.
Credentials in the document. Link to where access is granted; never paste passwords or keys into a handover note.
Skipping the read-back. A handoff nobody confirmed is a document, not a handover.

When to use a different template

If the work you are handing over is a repeatable process, it deserves an SOP or, for systems, a runbook, and the handoff can link to it. Decisions you want to survive beyond this handover belong in a decision log. And if the person taking over is new to the company, pair this with an onboarding checklist.

Customization tips

Write the open loops section first
Before the status or the open items, list every promise you made in the last month: in email, in chat, in meetings, in passing. It is the section incoming people most often discover the hard way, from an annoyed colleague or client.
For leave, say who decides, not just who does
Splitting tasks across colleagues is the easy part. Write down who can make which decisions while you are away, with a spending limit and a tiebreaker. Without it, decisions wait months for your return, as the parental-leave example shows.
Keep shift notes to one screen
A shift handover is read in five minutes by someone about to start work. Cut the template to status, open items, watch list and read-back. Use a fixed order, the same every shift, so the reader knows where to look.
Use a structured format for clinical handovers
Most units already use a format such as SBAR or I-PASS. Use your unit's format and its handover sheet. The clinical example above follows SBAR with a watch line per patient, and the record of care stays in the hospital system.
Give the outgoing person an end date
"Reachable until" protects both people. The incoming owner knows they can ask questions for a while, and the outgoing person knows when they can stop answering. Two to six weeks suits most permanent handoffs.

In the app

How to do this in Scribelet

Open Desk Settings, then Templates, tap Add Template and paste the template above. Keep {{date}} in the Written line so every handoff is dated.
Before writing, ask the AI chat "what did I promise anyone about the notifications service since September?" It answers from your own notes with citations, which is the quickest way to fill the Open loops section.
Write open items as - [ ] Renew the push certificate (@Olivia) @due(2026-12-15). They appear in the Tasks view, and @remind(2026-12-10 09:00) sends a push reminder in your local time for the one item that cannot slip.
Link the handoff to the project or account note with [[Harlow & Finch]]. The backlinks panel then shows every handoff, meeting and decision about that account in one list for the next owner.
On the Team plan, write the handoff in a shared desk so the incoming person can add their read-back to the same note.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

What should a handoff document include?

Who is handing over to whom and from when, a three-sentence status, open items with owners and dates, decisions in flight, a watch list of warning signs, open loops and promises, key people, where things live and access, recurring duties, and a read-back from the incoming person. The last three sections are the ones most handover templates leave out.

How do you write good handover notes?

Write for someone who cannot ask you questions. Lead with the status and the biggest risk, list open items with a next step each, and write warning signs as "if this, then that" so the reader knows what to do, not just what to worry about. Then walk through the notes together and ask the incoming person to summarize the top items back to you.

What is a shift handover?

A shift handover is the short, structured transfer of responsibility between the person ending a shift and the person starting one, in a hospital, a control room, a kitchen or a support team. It covers what is in progress, what is at risk and what needs doing first. A shift handover template keeps the order the same every shift so nothing is skipped when people are tired.

What are SBAR and I-PASS?

Both are structured handover formats used in healthcare. SBAR stands for situation, background, assessment, recommendation. I-PASS stands for illness severity, patient summary, action list, situation awareness and contingency planning, and synthesis by receiver. That last step is a read-back, which is useful in any handover.

How far ahead should I write a handover before leave?

Start a draft two to three weeks before you leave and finish it at least three working days before your last day. Walk through it with the people covering, then let them run the work for a day or two while you are still there to answer questions.

Is a handoff document the same as onboarding?

No. A handoff transfers a specific body of work from one person to another. Onboarding brings a new person into the whole organization. When a new hire is taking over someone's work, use both: the onboarding checklist template for the company, and the handoff document from the person who did the job before.

Hand over the work without handing over a mystery

Write your handoff in Scribelet, ask your notes what you promised and to whom, and turn every open item into a dated task for the person taking over. Encrypted, free to start.

Write your handoff document

or get the app

Download on theApp Store

Free plan, no credit card. See pricing

Work

Onboarding Checklist Template

Most onboarding checklists list tasks. This one gives each task an owner and a due date, adds a Done when section so everyone knows when onboarding is over, and keeps open issues in one place. Copy it, or start from the filled-in checklist closest to the hire you are making.

Engineering

Runbook Template

A runbook is the page someone follows at 3 a.m. with no context. This template gives every step a literal command and the output to expect, and adds the two fields most templates skip: when the procedure was last verified, and what change would make it wrong.

Work

SOP Template (Standard Operating Procedure)

An SOP is only useful if a person who has never done the task can follow it and get the same result. This template puts the trigger, the checks and the escalation path next to the steps, and gives every procedure an owner and a review date so it does not quietly go stale.

Work

Decision Log Template

A decision log is a running record of what was decided, why, by whom, and what you expected to happen. This template adds the two fields most logs leave out: who disagreed, and a date to check whether the decision worked. Copy it for a team, or use the decision journal example for your own choices.

Projects

Project Status Report Template

A status report tells readers in thirty seconds whether the project is on track, what changed since last time, and what you need from them. This template defines green, amber and red up front, so the color means the same thing every week.

Article

Internal documentation

From the Scribelet blog