How do we document and hand over automations so they survive staff changes?

Most automation failures after staff changes are not technical. The person who built it knew which account it ran under, which field it depended on and what to do when a vendor changed its API. When they leave, that knowledge goes with them, and the first sign is a silent failure weeks later.

One spreadsheet or database for every automation across Zapier, Make, n8n and Power Automate.

1. What it does in one sentence.
2. The trigger and each step in plain language.
3. The fields it reads and writes, and which system owns each.
4. What success looks like, and how to check it.
5. Known limits: rate limits, time windows, manual steps.

Put a link to this page in the workflow's description or notes field so it is found from the workflow itself.

Connections built on an employee's personal login stop working when that account is closed. Use service accounts or shared admin accounts owned by the company, store secrets in the platform's credential store, and list them in the inventory.

Every workflow needs an error path that posts to a shared channel or mailbox with the workflow name, the record and the error. Our view: make the failure loud, and reliable automation must detect, escalate and recover.

Ask someone who did not build the workflow to fix a planted problem using only the documentation. Whatever they had to ask about goes into the documentation.

How much documentation is enough?

One page per workflow plus the inventory row. More is rarely read.

Where should documentation live?

Next to the workflow (a link in its notes) and in one shared place everyone can find.

Who should own an automation?

A role in the business that cares about the outcome, with a named person. The builder is not always the right owner.

How often should we review?

Whenever the workflow changes, and at least quarterly for business-critical workflows.

Octacer documents every workflow it builds and can audit and document automations someone else built. Our workflow best practices are a good starting point, and Engineering Capacity can provide an engineer to own them.

Create the inventory this week and fill in the owner and credentials columns first. Those two columns prevent most hand-over failures. Book a call if you want help.