How three published frameworks assess an automation opportunity
Three published frameworks for choosing which process to automate share volume, rules, exceptions and ownership, but one scores readiness only while another adds value, safety gates and weights. None cites evidence for its thresholds. Read on 2026-11-06.
Contents
An automation opportunity assessment is the step that decides which process to automate first. No standard defines it. This page reads three published frameworks: an eight-question screen from Yesautomate, an eight-criterion scorecard from AutomationAce, and the SCORE-20 model from MTF Institute. It sets out what each asks and how it turns answers into a decision. All three come from firms that sell automation work, consulting or training, and none cites evidence for its thresholds or weights in the pages read.
Yesautomate asks eight yes-or-no questions
A featured guide on its resources page poses eight questions about a process: repetitive, rule-based, high volume, digital inputs, stable, exceptions, human effort, and a measurable outcome.[1] Its rule: "HIGH REPETITION + HIGH VOLUME + DEFINED RULES" means a "STRONG AUTOMATION CANDIDATE".[1] It then matches the kind of input to a kind of tool: unstructured documents to "OCR + DOCUMENT AI", interpretation or prediction to "AI / ML", and a complex workflow to "RPA + AI".[1] The page gives no scores. The separate 15-question template is not covered.
AutomationAce gives a readiness score out of 24
AutomationAce scores eight criteria from 1 to 3: volume, rate of change, standardization, rules clarity, data quality, exception rate, system access and ownership.[2] Its bands are stated per criterion. Volume is 1 below 10 a month, 2 for 10 to 100, and 3 for "100+ a month or daily bursts"; the exception rate is 1 when "More than 30% of cases are exceptions", 2 for 10 to 30 percent and 3 for under 10 percent.[2] A total of 20 to 24 means "Automate now", 14 to 19 means "Fix the low-scoring criteria first, or automate the standardized portion and route the rest to people", and 8 to 13 means "Not ready".[2] It lists red flags that mean "fix the process first", among them "Two people describe the same process differently" and "Nobody can say what “done” means."[2] The score measures readiness. It has no value or risk dimension.
MTF Institute uses stop gates then SCORE-20
MTF Institute's guide separates two stages. The first is a set of stop gates: reject or redesign an opportunity "when any answer below is no", for example "Is there an accountable process owner authorized to approve the pilot?" and "Can harmful or irreversible actions be prevented or independently approved?"[3] Only opportunities that pass are scored, from zero to five, on four dimensions with fixed weights: "Priority = (Impact × 0.35) + (Feasibility × 0.25) + (Readiness × 0.20) + (Control strength × 0.20)".[3] The guide warns: "Do not let a high time-saving estimate compensate for an unacceptable failure mode", and "The best automation opportunity is not the task that looks most repetitive."[3]
Its worked example is hypothetical: an accounts-payable team with 4,000 invoices a month, 12 percent entering an exception queue (480 exceptions, 72 staff hours, a five-day median resolution, 8 percent routed wrongly).[3] A pilot on two low-risk exception types covering 180 cases scores Impact 4, Feasibility 4, Readiness 3 and Control strength 4. Weighted, that is 3.8, or 76 of 100: "The project qualifies for a bounded pilot, not a production rollout."[3] The arithmetic is correct: 4 × 0.35 + 4 × 0.25 + 3 × 0.20 + 4 × 0.20 = 3.8.
What the three have in common and where they differ
Synthesis, this page's own comparison and not any source's claim. All three ask about volume or repetition, defined rules, exceptions and a measurable outcome, and two of them ask about ownership. They differ on four points. AutomationAce and Yesautomate ask whether a process is suited to automation, while MTF Institute also asks whether the benefit is worth it (impact, 35 percent of its score) and whether it is safe (stop gates and control strength, 20 percent). Only AutomationAce gives numeric bands for volume and exception rate. Only MTF Institute weights its dimensions. Only MTF Institute says what the system may never do. A process that scores 24 on AutomationAce could still fail MTF Institute's first gate if no one is authorized to approve it.
Not yet proven
- That any of the thresholds are right. The pages read give no source for the volume bands, the 30 percent exception cut-off, the 20 to 24 verdict or the 35, 25, 20, 20 weights.
- That a higher score predicts a better automation. None of the three reports outcomes from projects scored this way.
- That a vendor-neutral standard exists. The three sources are firms that sell automation services or training, and no standards body is cited.
- That the worked example reflects a real project. MTF Institute introduces it with "Suppose".
If you have scored processes for automation and checked the score against what happened, I would like to compare notes: mackenzie@mackenziebowes.com.
Sources
- Yesautomate, Guides and resources: Is Your Process Ready for Automation? (the resources page that hosts the automation opportunity assessment template; the eight questions are from its featured guide), read 2026-11-06, undated. yesautomate.
com/ resources/ guides- and- resources/ automation- opportunity- assessment- template - AutomationAce, The Automation Readiness Assessment: Is This Process Ready to Automate?, read 2026-11-06; the search result dated it 2026-10-01. automationace.
com/ blog/ automation- readiness- assessment- checklist - MTF Institute Editorial Team, Process Automation Opportunity Assessment: Intake, Scorecard and Pilot Gates, published 2026-09-22. mtfinstitute.
com/ insights/ process- automation- opportunity- assessment- scorecard/