What to Write Down Before You Step Away
TL;DR: Handoff notes before time off are a short written summary covering five categories, open jobs, pending decisions, who to call, where things live, and what can wait, so a team has answers instead of a reason to text. Skipping this step keeps the workload the same while you’re gone and simply moves the questions from a document to your phone. A one-page handoff note is the first real step toward a documented process.
Key Takeaways
- A handoff note is a short written summary of open jobs, pending decisions, contacts, locations, and deferred work, created before time away.
- Open jobs need a status and a next step written down, not just a list of names or project titles.
- Pending decisions need the decision itself stated plainly, along with who can make the call if you’re unreachable.
- “Who to call” only works if it names a specific person for a specific type of problem, not a general backup.
- “Where things live” means one written source of truth per item, not a guess about which folder or drawer holds it.
- Writing a handoff note once reveals which parts of the business depend on memory instead of a system that anyone could follow.
Why a Handoff Note Matters More Than a Text Chain
A handoff note before time off is a short written summary, created before you leave, that answers the questions your team would otherwise have to text you about. It covers five areas: open jobs, pending decisions, who to call, where things live, and what can wait. The point is removing yourself as the only working source of information for a day, a weekend, or a week.
Gaps in a handoff note trace back to one habit: information lived in a single person’s head, not on paper, and nobody noticed until that person was unreachable. This creates rework when the status of a job, the reason behind a half-made decision, or the name of a vendor contact was left unwritten. The team has to guess, wait, or interrupt time off to get an answer that should have taken two minutes to write down in advance.
A handoff note removes you as the only working source of information for a day, a weekend, or a week.
The five categories below are the actual questions that generate texts, calls, and stalled work when nobody wrote them down first.
Every text sent during time off points to something that was never written down.
The Five Categories to Write Down
Open Jobs
List every job or project in progress, its current status, and the next action, not just its name. A generic example: a landscaping crew has three properties mid-project, one needs a final walkthrough, one is waiting on a part, and one hasn’t started. Writing “three open jobs” tells nobody anything. Writing the status and next step for each means a team member can act without reaching you.
An open job with no written status forces someone to either guess at what’s done or wait for an answer, and guessing is how a customer gets billed for work that wasn’t finished.
Pending Decisions
Write down any decision that was in progress but not finalized, along with who is allowed to make the call in your absence. Example: a contractor was deciding between two suppliers for a material order, and the order needs to go out before you’re back. Leaving this unwritten means someone either freezes the order or picks a side without the context you had.
A pending decision without a named owner either stalls completely or gets made by whoever happens to be in the room, and neither outcome reflects the judgment you’d have used.
Who to Call
Name a specific person for a specific type of problem, not a general “call if needed” entry. Example: for a billing dispute, call the bookkeeper directly, not “finance,” and for a site emergency, call the lead technician, not “whoever’s free.” QuickBooks recommends setting a clear point of contact for staff and leaving emergency contact information before time away, which matches what a usable handoff note requires: a name tied to a problem type, not a department.
A vague contact list wastes time during the exact moment speed matters most, when a decision or a customer is waiting.
Where Things Live
Write down the source of truth for anything someone might need to find without you: passwords, contracts, the master schedule, supplier accounts. Example: a shop owner keeps the vendor pricing sheet in a shared drive folder, but the folder name isn’t obvious and nobody else has looked for it before. One line in the handoff note, naming the exact folder, file, or physical location, replaces a search that could eat an hour.
If the location isn’t written down, a team member either stops the task to search or skips a step that depended on that document.
What Can Wait
State plainly what doesn’t need action until you’re back, so the team isn’t guessing which fires are real. Example: a quarterly supply reorder is due in three weeks (example time frame) and doesn’t need to happen while you’re gone, so it’s fine to leave untouched. Separating what can wait from what can’t keeps attention on the handful of things that actually require a decision this week.
Without this line, a low-priority task can get rushed out of caution, using up time and attention that a genuinely urgent issue needed.
| Category | What to Write | Risk if Skipped |
|---|---|---|
| Open jobs | Status and next step for each | Guesswork on what’s done |
| Pending decisions | The decision and who can make it | Stalled work or wrong call made |
| Who to call | Specific name per problem type | Delay during urgent moments |
| Where things live | Exact file, folder, or location | Wasted search time, skipped steps |
| What can wait | Explicitly deferred items | Low-priority work rushed unnecessarily |
Each category follows the same rule: one clear action, one owner. A note that names a job by title alone leaves the reader guessing. A note that says “Morrison job needs final invoice sent, owner is the office manager, due before Friday (example date)” gives a team member everything needed to act.
I recommend treating the handoff note as a draft of a first real process document, not a one-time favor to a team. A five-category list rewritten every time someone leaves is still ad hoc. The same five categories, kept current between trips, start to look like a documented operation that doesn’t depend on memory.
A note that names the next step, the owner, and the deadline is a working handoff.
In Practice: Writing a One-Page Handoff Note
Situation: An office manager at a small service business is leaving for a long weekend and has never written a formal handoff note before, relying instead on being reachable by phone.
Steps:
- List every open job on a single page, noting status and next action for each.
- Identify any decision that’s in progress but unresolved, and name who can finalize it if needed.
- Write a contact name next to each likely problem type, not a general backup name.
- Note the exact location, file, or folder for anything a team member might need to find.
- Mark which pending items can wait until return, so they’re not mistaken for urgent.
- Hand the page to the person covering, and ask them to read it before the owner leaves.
Result: A one-page document exists that a team member could follow without calling the owner. The note worked if no question arrives that it already answers.
Common mistake: Writing vague entries like “check in on the Peterson account” instead of a specific status and action. Fix it by naming the exact next step and who owns it.
If it goes wrong: If questions still come in despite the note, the gap usually traces to a category left too general, and the fix is adding specifics the next time, not scrapping the format.
This is an illustration, not a record of an actual client or event.
FAQs
How do I write a handoff note before vacation?
Write down five things: open jobs with their status, pending decisions and who can make them, who to call for specific problems, where key documents or accounts live, and what can wait until you’re back. Keep each entry short and specific rather than general, since a vague note creates the same confusion as no note at all. A single page is usually enough for a short trip, and the format can expand for longer absences.
What should be included in a handoff note?
A handoff note should include the status of every open job, any decisions still pending along with a named decision-maker, specific contacts for specific problem types, the location of key documents or accounts, and a clear list of what doesn’t need attention until you’re back. Leaving any one of these out tends to produce the exact kind of question a handoff note is meant to prevent. The goal is completeness on these five points, not length.
Why do I keep getting texted while I’m away?
Texts arrive while you’re away because something your team needs to know wasn’t written down anywhere they could find it on their own. This is usually a status, a contact, or a file location that existed only in one person’s head. The fix is writing the missing piece down before you leave so the question never needs to reach you.
Who should write the handoff note, the owner or the team?
The owner or manager stepping away should write the note, since they hold the context the team doesn’t have yet. A team member can help by flagging which questions they’d be tempted to ask, which often reveals gaps the writer didn’t think to include. Either way, the person leaving should review the final version before walking out the door.
How detailed should a handoff note be?
A handoff note should be detailed enough that someone unfamiliar with the current status could act without guessing, but not so long that nobody reads it. One clear action and one owner per item is usually the right level of detail. If an entry takes more than two or three sentences to explain, the underlying job probably needs its own documentation, not just a mention in the note.
Does a handoff note replace a real process document?
A handoff note doesn’t fully replace a process document, but it’s the first draft of one. Writing the same five categories before every absence, and refining the entries each time, gradually builds a reference that works even when nobody is covering for someone else’s time off. Treating it as disposable paperwork wastes the pattern it reveals about where the business depends on memory.
What if something comes up that the handoff note didn’t cover?
Note it down for next time, and if it’s urgent, have the covering team member try the named contact for that problem type before reaching out to you. A note is never fully comprehensive on the first attempt, and the gaps it reveals are useful information for the next version. Treat each miss as a reason to add a line, not as proof the note failed.
Next Steps
A handoff note takes less time to write than one round of back-and-forth texts during time off, and it gets faster to produce once the five categories become habit. Save this list for the next trip, long weekend, or day off, and keep it where it will actually be found before walking out the door.
