Handovers: Write Down What Actually Breaks

Someone covers your desk for a week and three things go wrong: a supplier order placed with the wrong reference, a customer credit never issued, and a recurring report skipped entirely. None of those are hard tasks. They failed because the trigger for doing them lived only in your habits, not on paper.

Document the exceptions, not the routine

Nobody needs a written guide to sending a standard invoice. Write down what happens when the invoice total is wrong, when the supplier ships a substitute, when the customer asks for a different address. Exception notes are short, specific and the only kind of documentation anyone reads on a busy morning.

Put each note beside the tool it refers to rather than in a separate manual. A note stored in a shared folder is invisible at the moment of need; a note attached to the order template appears when the work appears. Filing discipline rarely survives a bad week, so reduce the effort required to find the right page.

A checklist and a written process differ in use

Compare a checklist against a full process document. A checklist verifies that steps happened and takes a minute to use; a process document explains reasoning and takes twenty minutes to read, which nobody does mid-task. Keep both, but expect the checklist to carry the daily load and the document to serve training and audits.

Actionable step: next time you cover for someone, keep a running note of every question you had to ask. That list is a precise gap analysis, written by the person who needed the answers. Hand it back and ask them to fill the five biggest holes. Repeat quarterly and the unwritten fifth shrinks.

Over-documenting slows the team down

Every step you mandate adds a task to someone's day, and a ten-step approval for a fifty-dollar decision costs more than the error it prevents. Cap documentation at decisions where the cost of a mistake exceeds ten minutes of work. Below that line, let people use judgement and fix mistakes quickly.