Book a fit chat

What good handover documentation looks like

By Sam Kim · · 6 min read

What good handover documentation looks like

How do I write handover documentation that someone else can actually use?

Write it for a specific person doing a specific job while you are unreachable, then test it by having them run the job from the document while you watch and say nothing. Good handover notes cover what triggers the work, the steps in order, where everything lives, the decisions and who makes them, what normal looks like, and what to do when it goes wrong. Anything they had to ask you during the test goes into the document.

Why does most handover documentation fail?

Because the writer can't see what they know. Someone who has done the payroll run for six years writes "process the timesheets" as one step, when it is really eleven, three of which depend on knowing which manager always submits late and what to do about it.

It fails in a few predictable ways:

  • It describes the happy path only. The steps work when nothing is unusual. The document says nothing about the client who pays by cheque or the supplier who sends invoices to the wrong inbox.
  • It assumes access. "Log into the portal" is useless if the login is in your head or on your phone.
  • It was written once and never touched. The software changed, the form moved, and the document now describes a process that hasn't existed for a year.
  • It's buried. A perfect document in a folder nobody can find is the same as no document.

The underlying problem is the one behind the partner bottleneck: the knowledge lives with one person, and every workaround routes back to them.

What should a handover document actually contain?

Six things, in this order. If a section doesn't apply, say so rather than leaving it out, so the reader knows you checked.

  1. The trigger. What starts this job? A date, an email arriving, a client signing, a stock level. Someone covering for you needs to know when to act, not just how.
  2. The steps, in order. Numbered, one action per step, written as instructions. "Open the invoice register and filter by unpaid" beats "check outstanding invoices".
  3. Where everything lives. Every system, folder, inbox and spreadsheet the job touches, with how to get access. If a login is held by one person, that is a finding in itself.
  4. The decisions, and who makes them. Which steps need judgement, what the usual answer is, and who to ask when the usual answer doesn't fit. Name a person, not a role.
  5. What normal looks like. Roughly how long it takes, how many items usually come through, what a finished result looks like. Without this, the person covering can't tell whether something is wrong.
  6. What to do when it goes wrong. The two or three failures you have actually seen, and what you did. Plus the line nobody writes: who to call if it's something else.

Points four and six are where the real value sits. The steps are usually easy to reconstruct. The judgement and the failure history aren't.

How do you find what's missing?

Run a silent walkthrough. Pick the person who would actually cover the job, hand them the document, and have them do the real task, start to finish, while you sit beside them and say nothing unless they're about to break something.

Write down every moment they stop. Each one is either a missing step, a missing login, an unexplained decision or a term only you understand. Then fix the document and, where you can, run it again with someone else.

This takes an hour or two per job. It's the cheapest insurance in the business, because the alternative is discovering the gaps while you're actually away and someone is guessing.

Where does AI help, and where doesn't it?

AI is genuinely useful for the drafting, which is the part most people never get around to. It is not a substitute for the test.

It does well:

  • Turning a recording of you talking through a job into clean numbered steps.
  • Converting a messy checklist, a few old emails and some sticky notes into one consistent format.
  • Spotting steps that look vague and asking what you meant.
  • Rewriting a document once the process changes, if you tell it what changed.

It can't:

  • Know the exception you handle from memory and never mentioned.
  • Confirm a login works, a folder exists or a client still has that arrangement.
  • Decide who should make a judgement call. That's yours to set.

So the order is: talk it through, let AI draft it, then run the silent walkthrough with a person. The draft gets you to a document in an afternoon instead of never. The walkthrough is what makes it true. It's the same split that runs through what AI won't do: it assembles, a person checks.

Before you record anything, check your firm's rules on what client or staff information can go into an AI tool. If you don't have those rules yet, a one-page AI policy is the place to start.

Which jobs should you document first?

Not everything at once. Rank your jobs on two questions: how bad is it if this doesn't happen for a month, and how many people currently know how to do it?

Start where the answers are "very bad" and "one". In most small businesses that list looks something like:

  • Payroll and anything tied to a statutory deadline.
  • Invoicing and chasing payment.
  • Whatever keeps the phones and the inbox answered.
  • Anything a client would notice within a week.
  • Any automation that runs in the background, because when it breaks the person covering won't know it exists.

That last one is easy to miss. If you have workflows running on their own, the handover needs to say what they do, where they live, who owns the accounts and what the failure alerts look like. The detail on that is in who owns your automations and what happens when an automation breaks.

How do you keep it current?

Tie updates to change, not to a calendar. The moment a process changes is the only moment anyone remembers the old one well enough to write the difference.

Three habits do most of the work:

  • One owner per document, named at the top, along with the date it was last checked.
  • A rule that changing the process includes changing the document. New system, new form, new person on a step: the document gets opened before the change is called done.
  • A six-monthly skim of every document against what actually happens, to catch the drift nobody noticed.

Put the documents in one place everyone can find, organised by job rather than by person. When someone leaves, the job stays.

What to do next

  • List your jobs and mark the ones only one person can do. Pick the riskiest.
  • Record yourself talking through that job once, start to finish, including the exceptions you can remember.
  • Have AI turn the recording into the six-part structure above, then fix what it got wrong.
  • Run the silent walkthrough with the person who'd cover it. Add every question they ask.
  • Name an owner, date it, and move to the next job on the list.

General information, not legal, tax or financial advice · Drafted with AI tools to my written rules · Terms

Common questions

How long should a handover document be?

As long as the job needs and no longer. A weekly task might fit on one page; a month-end close might need five. The useful limit is that each document covers one job from trigger to finish. If it is trying to cover the whole business, split it, because nobody can find step four in a forty-page manual at 8am.

Can AI write our process documentation for us?

It can draft it. Record yourself talking through the job, or give it the emails and checklists you already use, and it will turn them into tidy numbered steps quickly. What it cannot know is the part you never said out loud: the exception you handle from memory, the client who gets treated differently. That is why the document still has to be tested by a person running the job.

How often should handover documentation be updated?

Whenever the process changes, which in practice means tying the update to the change itself. A new system, a new form, a new staff member taking over a step: each one is the moment to open the document. A scheduled review every six months catches the drift that nobody noticed.

Next step

Start with the job you'd pay most to stop doing.

It's the core question on the intake, and rough answers are fine. Or book a free 15-minute fit chat first. If the honest answer is "not yet", you'll hear that.

WhatsApp0450 253 297