Home / AI Workflow Readiness Scorecard
Free operational diagnostic

Is this AI workflow ready to pilot?

Score one real workflow across ten controls that separate a repeatable operating system from a fragile AI demo. The result identifies what to fix next—not whether AI is impressive.

Runs entirely in your browser. Your answers are not sent or stored.

How to use it

Assess the workflow as it exists today.

Choose the most accurate answer for each control. Do not award credit for documents, tests, or safeguards that are only planned. A higher score means the operating controls are more complete; it is not a certification or a guarantee of performance.

1. Business outcome

Is the workflow tied to a measurable result rather than a broad goal such as “use AI” or “save time”?

2. Accountable owner

Does one person own the workflow after launch, including exceptions and maintenance?

3. Trigger and inputs

Are the starting event, required data, allowed formats, and missing-data rules explicit?

4. Current-state SOP

Has the real process been documented before AI is inserted into it?

5. Acceptance criteria

Can a reviewer decide consistently whether the output passes or fails?

6. Human review boundaries

Are AI permissions and required human decisions explicitly separated?

7. Exceptions and escalation

Does the workflow specify what happens when data is missing, output is unsafe, or the tool is unavailable?

8. Evaluation and testing

Has the workflow been tested beyond ideal examples?

9. Audit and version record

Can the team reconstruct what happened and identify which version produced the result?

10. Pilot and rollback

Is launch limited, observable, and reversible?

Your operational readiness score
0/100

Priority controls to fix

    How the scoring works

    Each control receives 0, 1, or 2 points. The total is converted to a score out of 100. The score is deliberately conservative: partial documentation or informal review receives partial credit, not full credit.

    • 0–35: document and stabilize the workflow before introducing more automation.
    • 40–65: suitable for a tightly controlled pilot after the missing safeguards are addressed.
    • 70–100: the core operating controls are substantially defined; validate them under real pilot conditions before expanding.

    This is an operational planning tool, not a scientific instrument, legal assessment, security audit, or certification.

    Turn the diagnosis into an implementation package.

    Use the production-ready workflow guide for the full method, or use Workflow Builder Bundle when you want the course method and Notion implementation system together.

    Read the implementation guideView Workflow Builder Bundle