Automation register: 5 fields per step
In recent lessons you added a second automated step, paused one that drifted, restarted it and retired another. A year on, your steps sit in different states, each understood by a different employee. An automation register is one page listing them all: one row per step, with 5 fields for what it does, who owns it, its state, its metric, and the data it touches.
A case from the floor
A two-branch food distributor serving grocers and restaurants launched 7 WhatsApp steps in a year, including quotes, order confirmations, delivery times, statements and payment reminders. Then a restaurant owner wrote: "I paid that invoice two weeks ago. Why the reminder every two days?"
Nobody knew who owned the reminder step. Its builder and reviewer had left two months earlier, ownership passed to no one, and it kept sending from a receivables list nobody updated. One hour spent listing all seven steps in a single table surfaced three surprises: two steps with no owner, a step retired at one branch but live at the other, and a statement step, never counted as personal data processing, sending customers' names and balances to their mobiles.
Five fields for every step
- What it does. One line: when X happens, the system does Y. For example: when an invoice is 7 days overdue, the system reminds the customer. A label like "collections step" says neither when it fires nor what it sends.
- Owner. One named employee, not a department. They keep the row current; if they leave, the step changes hands on handover day, as in handing a role to a new employee.
- State and date. Parallel run, live, paused or retired, plus the date of the last change. Retired steps stay listed with their reason, so nobody re-pitches them.
- Metric and review date. One number, such as the share of replies sent unedited, with its value at the last review, and the next review date.
- Data it touches. What it reads, such as prices or balances, and whether it sends or stores personal data such as names and mobile numbers. This field ties the register to the law.
| Field | The payment reminder's row after the fix |
|---|---|
| What it does | 7 days past due with no payment: one reminder, then an alert to the accountant |
| Owner | Salem, first-branch accountant |
| State | Parallel run since its restart |
| Metric | Reminders sent to customers who had already paid; target zero |
| Data | Receivables list; customer name and mobile (personal data) |
A register nobody updates is worse than none: it lends confidence to stale facts. Update the row the day the state changes, not at month end.
When a step processes personal data
Once a step processes personal data, such as a customer's name and mobile number, the matter is no longer just housekeeping. Article 33 of the Implementing Regulation of the Personal Data Protection Law, published in the Umm Al-Qura Gazette on 7 September 2023, requires the controller, meaning your business, to keep a record of personal data processing activities while processing continues, plus 5 years from its end. It must be written, accurate, current and available to the competent authority on request, with minimum contents that include processing purposes and the categories of data, data subjects and recipients. Official text: https://uqn.gov.sa/details?p=23595
Your register does not replace that record, but it shows what belongs in it: every step whose fifth field lists personal data. Retiring a step does not end the duty; its entry stays for 5 years after processing ends. Confirm the details with your legal adviser.
Build it in an hour, keep it accurate
- Collect from 3 sources. System settings, each employee's answer to "what goes out automatically in your name?", and the last 50 outgoing messages; a step one source misses usually shows in another.
- Leave gaps visible. A field nobody can fill stays blank and highlighted, not guessed.
- Review monthly in 15 minutes. Which step has no owner, which is past its review date, and which changed state without its row changing?
Kept inside your system rather than on someone's laptop, the register can answer those questions over WhatsApp. You might send "Which steps are overdue or ownerless?" and the system replies: "Two: delivery times at the second branch, last reviewed 45 days ago, and order confirmation, ownerless since the month began." More in running your business from WhatsApp and invoicing over WhatsApp.