Automation Readiness Assessment
Check whether a process is stable, repeatable and clear enough to justify automation instead of adding software to a moving target.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Frequency | Count how often the task occurs during a defined period. Distinguish a typical workload from a peak. | The frequency record, its source and the person responsible for resolving missing evidence. |
| Inputs | Retain the original source and state its format, unit and period. Mark assumptions separately from measured values. | Source values, conventions and missing details. |
| Outputs | Show a concrete example of the result the receiving person or system needs. Check fields, format and next action. | Expected output fixture and receiving owner. |
| Exceptions | Document the cases the normal process cannot complete and who should resolve them. | The exceptions record, its source and the person responsible for resolving missing evidence. |
| Ownership | Name the person who can approve the decision and the person who carries out the next action. A team name alone can leave the handoff unclear. | Named decision owner, action owner and review date. |
Review the decision
Check whether a process is stable, repeatable and clear enough to justify automation instead of adding software to a moving target. Keep frequency, inputs, outputs attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
The Real Cost of Adding Another SaaS Tool · How to Decide What Business Work Should Be Automated.
Calculation and source notes
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026