Workflow Automation Readiness Assessment

01 / METHODOLOGY

The score is transparent by design.

Each of the 12 dimensions is scored from 0 to 4 and weighted equally. Add the points, divide by 48, multiply by 100 and round to the nearest whole number.

TOTAL POINTS÷ 48× 100= READINESS SCORE

This is decision support, not an industry benchmark, certification or forecast. The result is only as reliable as the answers. Validate it against real workflow cases, system constraints and the people accountable for the work.

THE READINESS CAP

If rule clarity, ownership clarity or security/compliance readiness scores 0 or 1, the displayed score is capped at 54. A workflow should not be classified as ready for a pilot while one of those foundations is materially unclear, even if its volume and potential value are high.

0–34
Not ready yet
The workflow needs basic definition before automation design would be responsible.
35–54
Standardize first
There is an opportunity, but the operating rules or controls need strengthening first.
55–74
Good automation candidate
The workflow has enough repeatability, ownership and control for a bounded pilot to be reasonable.
75–100
High-leverage automation candidate
The workflow combines strong readiness with a clear opportunity for repeated operational value.

02 / ASSESS ONE WORKFLOW

Score the current state, not the aspiration.

Use one specific workflow — for example lead intake, document approval, customer onboarding or recurring reporting. Mixing several processes produces a score that describes none of them well.

JavaScript is off. The assessment still works manually.

Choose one 0–4 answer in each visible dimension, add the 12 numbers, divide by 48, multiply by 100 and round. Apply the published 54-point cap when rule clarity, ownership clarity or security/compliance readiness is 0 or 1. Match the result to the score bands above.

Choose one real workflow. Score its current state, not the state you hope to create.

0 of 12 dimensions answered.

01Repeatability

How consistently does the workflow follow the same path?

Stable patterns are easier to encode, test and explain than work that is reinvented each time.

02Frequency and volume

How often does this workflow run?

Repeated work gives a controlled automation more opportunities to repay its design and maintenance cost.

03Rule clarity

How clearly can the decisions and routing rules be stated?

If responsible people disagree about the rule, automation will encode the disagreement rather than resolve it.

04Data availability

Is the information needed by the workflow available and reliable?

Automation cannot compensate for missing identifiers, inaccessible records or inconsistent source data.

Unknown or unavailableMostly unstructured or unreliableAvailable with substantial cleanupMostly reliable and accessibleStructured, reliable and governed

05Handoffs

Are the workflow's handoffs frequent and understood?

Mapped handoffs create valuable automation opportunities; invisible handoffs create silent failure.

06Manual re-entry

How much information is copied or re-entered between systems?

Repeated, understood re-entry can be a strong connection opportunity when the destination and validation rules are clear.

07Error sensitivity and controls

Are the consequences of error understood and matched by controls?

A high-consequence workflow can be automated only when validation, review, audit and recovery are proportionate.

Consequences are unknownConsequences known, controls absentPartial checks existChecks and recovery are mostly definedConsequences, checks, review and recovery are explicit

08Exception frequency

How manageable are cases that do not follow the common path?

Exceptions do not prevent automation when they are recognisable, surfaced and routed to a named person.

Exceptions are unknownMost cases are exceptionalExceptions are frequent and loosely handledExceptions are identifiableExceptions are limited, classified and owned

09Integration availability

Can the systems involved exchange data responsibly?

APIs, exports, permissions and vendor constraints determine whether an apparent workflow is technically connectable.

Systems are unknownClosed systems or no accessManual exports or uncertain accessUsable APIs or controlled importsDocumented interfaces, access and test environments

10Ownership clarity

Is one person accountable for the workflow and its exceptions?

Automation needs an owner who can approve behavior, resolve exceptions and maintain the process after launch.

11Security and compliance readiness

Are access, data and approval constraints understood?

Known controls make a safe design possible; unknown obligations are a reason to pause, not to guess.

Requirements are unknownSensitive scope known, controls unclearSome controls and approvals identifiedControls and review path mostly definedData boundaries, access, logging and approvals are explicit

12Expected business value

Is the value of improving this workflow specific and observable?

A clear operational outcome supports prioritisation and gives the pilot an acceptance test.

Answer all 12 dimensions to calculate a readiness result.

03 / INTERPRET CAREFULLY

A score starts a decision. It does not make one.

Use the result to focus discovery. A technically connectable process may still be the wrong priority; a valuable process may still need ownership, security or rule work before automation.

CHECK THE EVIDENCE

Sample real cases. Confirm frequency, exception types, error consequences and system access rather than relying on memory.

KEEP JUDGMENT VISIBLE

Automate repeatable movement. Keep judgment, commitments and high-consequence decisions behind proportionate human review.

START REVERSIBLY

Prefer one bounded workflow, clear acceptance checks, an exception path and a named owner over a broad transformation programme.

Privacy: this tool runs entirely in your browser. It has no server submission, database, local storage, cookies, analytics or tracking script.

If the assessment reveals a good candidate, bring the workflow, the blockers and the evidence — not just the score.

Discuss the workflow

Workflow automation readiness assessment.