Automation Specification Template: Trigger, Rules, Actions and Exceptions

Two people drawing on whiteboard

An automation specification is a one or two page description of what an automation should do, written before it is built. It records the trigger, the rules, the actions and what happens when something goes wrong. Writing it takes twenty minutes and saves hours of rebuilding, because most automation problems come from cases nobody thought about in advance.

When to write one

  • Before building any automation that touches customers, money or records.
  • When someone else will build or maintain it.
  • When you return to an old automation and nobody remembers how it works.

For a five-minute personal shortcut it is unnecessary. For anything the business depends on, it is the cheapest insurance available.

The template

AUTOMATION SPECIFICATION

Name:
Owner (person responsible):
Version and date:

1. PURPOSE
   What problem does this solve?
   What is done manually today, and by whom?
   Expected benefit (time saved, errors avoided):

2. TRIGGER
   What event starts the automation?
   In which system does it occur?
   How often is it expected (per day / week)?

3. INPUTS
   Field              Source            Required?     Example
   
4. RULES AND CONDITIONS
   IF ...              THEN ...
   IF ...              THEN ...
   OTHERWISE ...

5. ACTIONS (in order)
   Step   System        Action                    Output
   1
   2
   3

6. EXCEPTIONS
   Situation                              What should happen
   Required input missing
   Duplicate trigger
   Connected service unavailable
   Unexpected value

7. HUMAN CHECKPOINTS
   Which steps need review or approval, and by whom?

8. NOTIFICATIONS AND LOGGING
   Who is alerted on failure, and how?
   Where is the run history kept?

9. ACCESS AND DATA
   Accounts and permissions used:
   Personal data processed:
   Where data is stored or sent:

10. TEST CASES
   Case                    Input                 Expected result

11. MANUAL FALLBACK
   How is the task done by hand if the automation is down?

12. HOW TO PAUSE OR SWITCH OFF

13. REVIEW DATE

How to fill in each part

Purpose

State the problem and the expected benefit in numbers where you can. This is what you will compare against later. If the benefit is unclear, question whether to build it; the Automation ROI Worksheet helps.

Trigger

Name one precise event: a new row in a specific sheet, a form submission on a specific form, an order reaching the status Paid. Avoid vague triggers such as when a customer contacts us.

Inputs

List every piece of data the automation uses, where it comes from and whether it is always present. Missing optional fields are a frequent cause of failures.

Rules

Write conditions as if-then statements and always include what happens otherwise. A rule without a default leaves some cases unhandled.

Actions

Number the steps in the order they run and name the system each one happens in. Note what each step produces, since later steps often depend on it.

Exceptions

This is the section that distinguishes a reliable automation. For each situation, choose a response: stop and alert, skip the step, retry, or pass to a person. Consider in particular what happens if the trigger fires twice for the same item.

Human checkpoints

Mark where a person must review before the automation continues: messages to many recipients, payments, anything where an error would be costly or embarrassing. Business Automation Strategy discusses where to draw this line.

Access and data

Use a shared business account, not a personal one, and give it only the permissions it needs. Record which personal data passes through which services, so that it matches your privacy policy.

Test cases

Write them before building. Include the normal case, each branch of the rules and each exception.

A filled-in example

  • Name: New enquiry routing
  • Trigger: Submission of the contact form on the website
  • Inputs: Name (required), email (required), topic (required, dropdown), message (required), phone (optional)
  • Rules: If topic is Billing, assign to accounts. If topic is Support, assign to support. Otherwise assign to the office manager.
  • Actions: 1. Add a row to the enquiries sheet. 2. Email the assigned person. 3. Send a confirmation to the customer.
  • Exceptions: Email address invalid: skip step 3 and flag the row. Sheet unavailable: retry after five minutes, then alert the owner.
  • Human checkpoint: None. Replies to customers are written by a person.
  • Fallback: Form submissions are also emailed to the office inbox.

From specification to working automation

  1. Review the specification with the people who do the task today.
  2. Build it step by step.
  3. Run every test case and record the results.
  4. Switch it on, with error alerts active.
  5. Store the specification where the team can find it, and update it whenever the automation changes.

How to Turn a Repetitive Manual Task into an Automation Workflow walks through the building stage.

Common mistakes

  • Writing only the happy path.
  • No named owner.
  • Rules without an otherwise.
  • Using a personal login that disappears when someone leaves.
  • No description of how to switch it off.
  • A specification that is never updated after changes.