
What a Good Handoff Document Actually Contains
TL;DR: A handoff document works when it contains five specific parts, the trigger that starts the task, the steps in order, the decision rules for judgment calls, the exceptions that break the normal pattern, and who to ask when none of that covers the situation. Without all five, the person running the task has to guess, and guessing is where delays and errors start. The test is simple: hand it to someone new and watch whether they stop to ask a question that the document should have already answered.
Key Takeaways
- A complete handoff document contains five parts: trigger, steps, decision rules, exceptions, and who to ask.
- An incomplete document forces a new person to guess at decisions the writer made automatically and never wrote down.
- Decision rules and exceptions are the two parts often left out, because the original owner stopped noticing them as decisions.
- A before and after comparison of the same task shows the practical difference between a task list and a document someone else can run.
- Documenting a task before automating or hiring for it prevents the new hire or new tool from inheriting the same gaps.
- The test for a working handoff document is whether a new person can complete the task without asking a basic question.
What Belongs in a Handoff Document
A handoff document is a written description of a task detailed enough that someone with no prior exposure to it can complete the work correctly on the first attempt. A handoff document needs five specific parts, and a document that fails is usually missing one or two of them, not all five. The gaps tend to be the parts the original owner stopped noticing, because the decisions became automatic over time.
The five parts are the trigger, the steps, the decision rules, the exceptions, and who to ask. Each one answers a different question a new person will have, and each one, left out, forces a guess.
- Trigger: what starts the task. A specific event, date, or signal, not a vague sense that it’s “time.”
- Steps: the actions in the order they happen, specific enough to follow without interpretation.
- Decision rules: the judgment calls the task requires, written as if-then logic rather than left to instinct.
- Exceptions: the situations that don’t fit the normal pattern, and what to do when one comes up.
- Who to ask: the name or role to contact when the document doesn’t cover the situation in front of them.
The U.S. Chamber of Commerce advises testing a standard operating procedure by having someone new complete the task using only the document, then revising it until they can finish without asking questions, and including troubleshooting guidance where the task requires it. That test, run honestly, exposes which of the five parts is missing faster than any review meeting.
Why Handoff Documents Fail
A document that lists only the steps looks complete but describes what happens when everything goes right. The real cost of a thin document shows up at the first decision point or the first exception, and that’s where a new person stalls out and starts asking questions the document should have already answered.
A handoff document that lists steps but skips decision rules works right up until the first judgment call, and then it stops being useful.
The failure points cluster in two places: the moment a decision has to be made with incomplete information, and the moment something happens that falls outside the normal pattern. A document that only covers the straight-line case leaves both of those moments uncovered, and the person running the task has no way to tell whether they’re handling an exception correctly or making it up.
The person who wrote the steps stopped seeing the decisions as decisions, which is why the risk sits in what got left out.
This matters most during handoffs, when a task moves from the person who built it to someone new. The person handing off the work tends to skip the parts that feel obvious to them, because years of repetition turned a judgment call into a reflex they no longer notice making.
Before and After: The Same Task, Two Documents
The difference between a thin document and a complete one is easiest to see side by side. The example below is an illustration, not a record of an actual task, and the numbers are placeholders.
| Element | Before | After |
|---|---|---|
| Trigger | “When an order comes in” | “When a customer submits an order through the online form, timestamped automatically” |
| Steps | “Process the order and ship it” | Numbered steps from confirmation email to tracking number sent |
| Decision rules | None stated | “If the order total exceeds $500 (example amount), route to the owner for approval before shipping” |
| Exceptions | None stated | “If the shipping address is outside the standard delivery zone, hold and contact the customer before processing” |
| Who to ask | Not listed | “For payment disputes, contact the office manager. For shipping zone questions, contact the warehouse lead.” |
The before version reads like a summary someone could nod along to in a meeting. The after version is a document someone else can run, because it answers the three questions a new person actually has: what counts as normal, what counts as an exception, and who to call when it’s neither.
A handoff document works when a new person can finish the task without asking a basic question.
Naming Who to Ask
The “who to ask” section gets added last, if it gets added at all, because the original owner has never needed it themselves. That’s exactly why it matters most to someone new. A new person doesn’t know which questions are worth escalating and which ones they’re expected to answer on their own, and a document that names a specific person for specific categories of question removes that guesswork entirely.
At an airline’s front ticket counter and gate, too few staff could perform the primary or secondary agent functions during flight operations, and that caused delays on a daily basis. I wrote a checklist of expectations and duties for both roles, organized by the countdown to departure, and trained the employees on it. It helped, set clearer expectations, and organized the team better. If I were doing it again, I’d onboard new employees in both roles from the start, including codeshare flight operations.
That checklist assigned specific duties to specific roles at specific points in the countdown.
Document Before You Automate or Hire
Writing the handoff document first, before bringing in a new hire or a new tool, keeps the gaps from getting baked into whatever replaces the current process. A task handed to a new employee with no document forces them to reconstruct the decision rules by trial and error, which costs time and produces inconsistent results until they catch up. The same problem shows up when a business tries to automate a task it never fully wrote down, because the software only repeats what the task description told it to do.
Writing the document before automating or hiring prevents rework. If the exceptions and decision rules aren’t written down first, the new hire improvises and the automation tool executes the wrong default, and both outcomes create rework that a complete document would have prevented.
In Practice: Writing One Handoff Document
Situation: An office manager needs to hand off a recurring task, such as processing weekly vendor invoices, to a new employee without being available to answer every question in the first few weeks.
Steps:
- Write down the trigger using the invoice tracking system or inbox where the task actually starts.
- List the steps in the exact order they happen, naming the specific screen, field, or form involved at each one.
- Identify every point where a judgment call is required, such as approval thresholds, and write each as an if-then rule.
- List the exceptions that have come up before, such as a missing invoice number or a mismatched amount, and what to do for each.
- Name the specific person or role to contact for anything the document doesn’t cover.
- Hand the document to someone unfamiliar with the task and watch where they pause or ask a question.
- Revise the section that caused the pause, and repeat until no question comes up.
Result: A written document that lists the trigger, steps, decision rules, exceptions, and who to ask, confirmed by a test run with someone new. The reader can tell it worked when that person completes the task without interrupting anyone.
Common mistake: Writing only the steps and skipping the decision rules, because the original owner no longer notices they’re making a judgment call. Fix this by watching yourself do the task once and flagging every point where you paused to decide something.
If it goes wrong: If the new person still has to ask a basic question after the test run, the gap is almost always a missing decision rule or an uncovered exception, not a missing step.
This is an illustration of the method, not a record of an actual client result.
FAQs
What should a handoff document include?
A handoff document should include five parts: the trigger that starts the task, the steps in order, the decision rules for judgment calls, the exceptions that fall outside the normal pattern, and who to ask when none of that applies. Leaving out any one of these forces the person running the task to guess, which is the point where errors and delays start.
How do I know if my handoff document is good enough?
A handoff document is good enough when someone unfamiliar with the task can complete it correctly using only the document, without asking a basic question along the way. Hand it to a new person, watch where they hesitate or ask for clarification, and treat every pause as a sign that section needs more detail.
Why do handoff documents usually fail?
Handoff documents usually fail because they describe the steps for the normal case but skip the decision rules and exceptions, which are the parts the original owner stopped noticing as decisions over time. The gaps don’t show up until someone hits a judgment call or an unusual situation the document never addressed.
What’s the difference between a task list and a handoff document?
A task list names what needs to happen, while a complete handoff document also covers what to do when a decision is required or something falls outside the normal pattern. A task list works for someone who already understands the judgment calls involved, but a new person needs those calls written out as explicit rules.
Should I write a handoff document before hiring someone new?
Yes, writing the document before the new hire starts keeps them from having to reconstruct the decision rules through trial and error on the job. It also gives the business a reference for training going forward, instead of relying on the new hire’s memory of what they were told once.
How detailed should the steps section be?
The steps section should be detailed enough to name the specific screen, field, form, or action involved at each point, not just a general description of the activity. A step like “process the order” leaves room for interpretation, while a step naming the exact fields to fill in does not.
What are decision rules in a handoff document?
Decision rules are the if-then statements that cover the judgment calls a task requires, written out instead of left to the instinct of whoever is doing the work. An example is a rule stating that any order above a set dollar threshold routes to a specific person for approval before processing continues.
Next Steps
A handoff document that’s missing its decision rules or its exceptions will look complete right up until someone runs into the gap. If you’re not sure which of your recurring tasks carries the most risk from an incomplete handoff, see how a Systems Review ranks which handoffs to document first: https://qualify.greatlakesbusinesssupport.com/systems-review
