The one-page handoff doc
The bus-factor question
An automation without documentation is a new kind of key-person risk: instead of depending on the employee who knows the process, you depend on whoever built the machine. If that is an outside consultant, you have traded one fragility for another, dressed up as progress.
The antidote costs one page. Not a manual, nobody reads manuals. One page, plain English, that any capable person in the building can act on.
The five headings
Every automation we ship carries the same one-pager, and it answers five questions:
- What it does: two or three sentences a new hire would understand
- When it runs: the schedule, and roughly how long it takes
- How you know it worked: what the normal output looks like and where it lands
- How to stop it: the kill switch, written for someone non-technical, usable at 7am without calling anyone
- Who to call: the person responsible, and what to tell them
Write it for the worst morning
The test of a handoff doc is not the calm day. It is the morning something looks wrong, the person who built it is on a plane, and whoever is standing there has to decide whether to pull the switch. If the page gets them to a safe decision in two minutes, it works. Jargon, links to dashboards, and anything longer than a page all fail that test.
Keep the pages where the team already looks, a shared folder, printed in a binder, taped inside a cabinet door. Findability beats elegance.
Ask for it up front
If you hire anyone to build automation, make the one-pager part of the definition of done. Builders who resist documenting in plain English are telling you something about the dependency you are about to create. It is half of how automation survives turnover, and all of how it survives the builder.
The audit answers this for your business
Two weeks, $2,500 flat ($1,000 for the first three clients), and you get the map of your own automatable work with dollars on it.