# Automation requirements template and example

Ops Automators | Updated September 7, 2026

Complete the blank version with the process owner. The sample describes an illustrative deal-to-project handoff. Replace each example before using the document as approval to build.

Guide: https://www.opsautomators.com/guides/automation-requirements-template

## Worked example

| Requirement | Decision | Owner | Acceptance case / evidence |
| --- | --- | --- | --- |
| Outcome | One approved deal creates one linked project | Delivery lead | Normal and duplicate cases |
| Out of scope | Billing and staffing | Process owner | No billing actions |
| Trigger | Approval status changes to Approved | CRM owner | Unapproved edits do nothing |
| Required fields | Deal ID; account ID; scope; start date | Delivery lead | Missing date creates review item |
| Identity | Persist deal ID on project | Builder | Replay finds existing project |
| Timeout after write | Reconcile before retry | Operator | Simulated lost response |
| Exception ownership | Delivery queue | Delivery lead | Queue item assigned and visible |
| Acceptance | Evidence for every agreed case | Process owner | Signoff recorded |
| Volume and timing |  |  |  |
| Access and retention |  |  |  |
| Stop and recovery procedure |  |  |  |

## Blank brief

### Requirement

[Complete this field.]

### Decision

[Complete this field.]

### Owner

[Complete this field.]

### Acceptance case / evidence

[Complete this field.]


## Acceptance

- Owner:
- Date:
- Evidence:
- Open decisions: