A practical field guide from Automation Ace.
The short answer
A process is ready to automate when it is frequent, stable, standardized, rule-based, fed by reasonably clean data, has a low exception rate, runs on systems you can access, and has an engaged owner. Score each of those eight criteria from 1 to 3; a total of 20–24 means automate now, 14–19 means fix the weak spots first or automate part of it, and below 14 means the process needs work before any automation will stick.
For an interactive version, use the automation readiness score calculator. This checklist explains the reasoning behind each criterion and what to do about low scores. The calculator uses a finer 1–5 scale; the simple 1–3 scale below is designed for quick use in a workshop.
The readiness scorecard
Score each criterion 1, 2, or 3:
| Criterion | 1 (not ready) | 2 (partly ready) | 3 (ready) |
|---|---|---|---|
| Volume | Fewer than 10 a month | 10–100 a month | 100+ a month or daily bursts |
| Rate of change | Process changes monthly | Changes a few times a year | Stable for a year or more |
| Standardization | Different every time; judgment-heavy | Mostly consistent with variations | Same steps every time |
| Rules clarity | Rules live in someone's head | Partly documented | Written, unambiguous rules |
| Data quality | Free text, often missing or wrong | Mostly structured, some gaps | Structured, validated at entry |
| Exception rate | More than 30% of cases are exceptions | 10–30% | Under 10% |
| System access | No API or export; manual-only apps | Partial API or plan limits | APIs or native integrations available |
| Ownership | No clear owner | Owner, but limited time | Engaged owner with authority |
| Total | Verdict | What to do |
|---|---|---|
| 20–24 | Ready | Automate now; start with the happy path. |
| 14–19 | Ready with fixes | Fix the low-scoring criteria first, or automate the standardized portion and route the rest to people. |
| 8–13 | Not ready | Standardize, clean data, and document rules before building. |
Why each criterion matters
- Volume: automation pays back through repetition. Estimate it with the manual task cost calculator.
- Rate of change: if the process keeps changing, the automation needs constant rework. Stabilize first.
- Standardization: a process that is different every time is a judgment process; consider human-in-the-loop designs instead of full automation.
- Rules clarity: if nobody can write the rules down, nobody can automate them. The requirements doc forces this.
- Data quality: automation amplifies bad data. See handling blank and missing values and data hygiene.
- Exception rate: exceptions drive most of the build effort and most failures. See the exception inventory.
- System access: a plan tier without API access can block a project outright. See the systems and data inventory.
- Ownership: automations without an owner decay. See who owns what.
Red flags that mean “fix the process first”
- Two people describe the same process differently.
- “It depends” is the answer to most questions.
- Required data usually arrives by email or phone, not a form or system.
- A spreadsheet is the source of truth and anyone can edit it.
- The process exists to work around a broken upstream step.
- Nobody can say what “done” means.
How to fix low scores
- Standardize inputs with forms and required fields. See form automation.
- Write the rules down and get the owner to sign off.
- Split the process: automate the standardized 80% and route exceptions to people.
- Clean the data at the source, not inside the automation.
- Upgrade or replace tools that block access.
- Re-score after changes; scores should rise before you build.
Partial automation is still a win
A low-scoring process may still have automatable slices: collecting data, creating records, sending reminders, or preparing drafts for a person to approve. Map it first (see process mapping), then rank the slices with an impact vs effort matrix.
Frequently asked questions
How do I know if a process is ready to automate?
Score it on volume, rate of change, standardization, rules clarity, data quality, exception rate, system access, and ownership. Frequent, stable, rule-based processes with clean data, few exceptions, accessible systems, and an engaged owner are ready.
What makes a process a bad candidate for automation?
Low volume, frequent changes, judgment-heavy steps, undocumented rules, messy data, a high exception rate, systems without API access, or no clear owner.
What should I do if a process scores low on readiness?
Standardize inputs, document rules, clean data at the source, fix access blockers, automate the standardized portion while routing exceptions to people, and re-score before building.
Is there a tool to score automation readiness?
Yes. Automation Ace's automation readiness score calculator turns these criteria into an interactive score.
Disclaimer: Templates and checklists are starting points; adapt them to your process, policies, and tools. Product features, limits, and pricing mentioned here change over time, so confirm current details in each vendor's documentation. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.