A Register of Your Automations: What to Document Before You Forget
Short answer: Write every automation your business runs into one register, with a row for each one: what starts it, which tools it touches, who owns it, what data passes through, which account it runs under and where failure alerts go. Ten columns cover most small operations. Review the register every quarter, and again whenever someone who built a flow leaves. It takes about an hour to start, and it saves a day of guessing the next time a password changes or a form field is renamed.
Why memory fails first
Most automations start small. A flow that copies web form entries into a spreadsheet gets built on a quiet Tuesday, then slowly becomes the way new customers reach your billing system. Eight months later the person who built it has moved to another role, a supplier has renamed a field in its API, and nobody can say which of the eleven flows touch customer phone numbers. The tools themselves do not help. Their dashboards list flows by the names their builders gave them, and those names usually describe the day the flow was created, not what it does today.
A register fixes that. It is one plain table that lists each automation once, with enough detail that someone who has never seen it can work out what it does, what breaks it and whom to call.
The ten columns
Keep the columns in this order so every review follows the same path.
| # | Column | What to write |
|---|---|---|
| 1 | Name | A purpose-based name, such as "Lead form to CRM" |
| 2 | Trigger | The event that starts it, for example "new form entry" |
| 3 | Tools | Each app and account it connects, in the order it uses them |
| 4 | Owner | The person accountable for changes |
| 5 | Backup owner | Someone who can pause or restart it when the owner is away |
| 6 | Data touched | Categories only, such as "name, email, order total" |
| 7 | Runs as | The service account or shared login it uses |
| 8 | Failure alerts go to | A shared address or channel, not a personal inbox |
| 9 | Last reviewed | A date |
| 10 | Notes | Known quirks, limits, and a link to the flow itself |
Three filled rows show the level of detail. The names and figures are made up for illustration:
| # | Name | Trigger | Tools | Owner | Backup | Data | Runs as | Alerts | Reviewed | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Lead form to CRM | New form entry | Web form, CRM, Slack | Dana | Omar | Name, email, enquiry text | ops shared account | ops-alerts channel | 2026-10-02 | Duplicates skipped by email |
| 2 | Invoice reminder | Daily at 07:00 | Accounting app, Gmail | Omar | Dana | Client name, amount due | billing shared account | billing inbox | 2026-09-18 | Skips paid invoices, sends on day 7 and day 14 |
| 3 | Weekly stock export | Every Monday 06:30 | Shop platform, Google Sheets | Dana | none yet | SKU, quantity | ops shared account | ops-alerts channel | 2026-07-30 | Export stops at 250 rows per run |
Row 3 already shows its own problem: no backup owner. The register makes that gap visible, which is the point.
Finding what you already run
Before you fill in the first row, list everything that currently runs. Work through each place where automations live:
- Open the automation dashboard and list every flow, including paused ones. A paused flow still matters, because someone may switch it back on.
- Check scheduled scripts, such as Apps Script triggers in a Google account or cron jobs on a server.
- Ask each team lead which steps feel automatic to them, such as a status change that sends an email. These are often built outside IT and never reach the dashboard you are looking at.
- Compare the list with your connected accounts. Any account with flows attached should appear in the register.
Keep the review honest. A flow that nobody can explain still gets a row. Mark its owner as "unknown" and set a deadline for deciding whether to keep it or delete it.
Check for personal logins
The most common weakness is a flow that runs under someone's personal login. When that person leaves, the flow either stops or keeps running on an account the business no longer controls. For each row, compare the "Runs as" column with the connected account inside the tool. If it shows a personal address, create a shared service account, reconnect the flow to it, and test with one sample record. Reconnecting can reset field mappings, so check them before you switch the flow back on.
Add two rules to your onboarding notes for new staff. New automations use shared accounts. Nobody deletes an account that has active connections until the register has been checked.
A quarterly review routine
A register that nobody opens is just a document. Put a calendar entry in the first working week of each quarter and work through it in about 30 minutes:
- Sort by "Last reviewed" and pick every row older than 90 days.
- Confirm that each owner still works in the business and has time for the flow.
- Trigger a test on any flow that has not run for a month, so you know it still fires.
- Remove rows for deleted flows and add any new flows you find in the tool.
- Update the alert address for any owner who has changed.
Run a short version immediately when someone with flow access leaves. The departing person names a backup for each of their rows before their last day, and the register changes that same day.
Where to keep it
A shared spreadsheet works well for most businesses. Give edit rights to two or three people, view rights to everyone else, and keep version history switched on. Do not store the register inside the automation tool, because it should survive if you change platforms. Link each row to its flow, and never paste API keys or passwords into the notes column.
FAQ
Do I need a register if we have only three automations?
Yes, although it can be short. Three flows that one person understands become a problem on the day that person is on holiday or leaves. Three rows take about ten minutes to write and give the next person a map.
Who should own each automation?
The person who relies on its output most, not necessarily the person who built it. A sales lead usually owns the lead form flow, because a broken flow shows up first in their work. The builder can be the backup owner, which spreads knowledge without moving responsibility.
How detailed should the data column be?
Name categories only, such as "contact details" or "payment amounts". Do not copy field values or sample records into the register. Otherwise the register itself becomes a store of personal data that needs protecting.
What if a tool changes its limits or pricing?
Update the notes column and check the trigger again. Plans and row limits change often, so confirm the current figures on the provider's help pages rather than trusting an old screenshot.
If your automations have grown beyond what a spreadsheet can track, tell us which tools you run and we will map them into a register with you: start the conversation.