Many automations are built by one person, work for a while and then fail when that person changes role, because nobody else knows what they do or where they run.
A one-page runbook per automation
- Purpose and owner — what it does, which business process it supports and who is accountable.
- Inputs and outputs — systems it reads from and writes to, and the accounts it uses.
- Failure behaviour — what happens on error, who is alerted and how to restart.
- Dependencies — APIs, credentials and their expiry dates.
- Change history — what was changed, when and why.
Review the list of automations quarterly. Any without a named, current owner is a risk until one is assigned or it is switched off.