Is this workflow ready for AI?
Before adding AI to a process, score it on handoffs, exceptions, visible state, recovery and who may approve changes. A readiness checklist you can use as a worksheet.

A workflow is ready for AI help when handoffs are named, exceptions have owners, state is visible, recovery is defined and someone may approve changes. Score those operating facts with the TWIMCO readiness rubric—or run the free interactive assessment on the site—before you connect a model. If any dimension is blocked, fix the process first.
Score the process, not the pitch
A workflow is not ready for AI because a vendor said the model is good. It is ready when the operating facts are boring and visible. The handoffs have names. The exceptions have owners. The state can be seen. Recovery is defined. Someone may approve a change.
If any of those are blocked, fix the process before you connect a model. A model on a foggy workflow will be fluent about the fog.
Five questions
Score each ready, not yet, or blocked.
Handoffs. Can you point at what moves, and who receives it?
Exceptions. Is there an owner and a place for the case that cannot take the ordinary route?
State. Can a stranger tell whether the item is proposed, waiting, done, or failed without opening a chat?
Recovery. If the work stops halfway, is there a check before anyone retries, and a way back to a known state?
Authority. Is there a person who may approve what an agent is allowed to change, and a line it may not cross?
Ready means you could show it this week. Not yet means you know the gap. Blocked means two people would give different answers, or the fact lives only in someone's head.
You can run the same judgment on the free AI workflow readiness assessment. Eight questions, a few minutes, answers stay in your browser. The point of either path is the weak scores, not a badge.
How the work moves
Score five readiness dimensions
- Named handoffs
Who receives work, in what form, and what acceptance means.
- Owned exceptions
Unusual cases have an owner, evidence and a return path.
- Visible state
Proposed, in progress, waiting, done and failed are observable.
- Recovery
Incomplete work is findable; the next safe action is clear.
- Approval authority
A named role may change scope, prompts, permissions or agency.
Readiness is not a model score. It is whether the process can absorb help without hiding who owns the result.
How to use it
Walk one real workflow with the people who run it. Ask for an ordinary day, then for the last time something went sideways. Listen for unnamed transfers, unspoken exceptions, and moments when two people believed different states were true.
This is not a personality test for the company. A process can matter strategically and still be a bad place to put an agent. Importance is not readiness.
What you skip at your cost
Skip handoffs and the agent invents the transfer. Skip exceptions and the happy path becomes the whole product. Skip state and the agent summarizes a rumor. Skip recovery and the first partial write gets retried into a duplicate. Skip authority and a prompt change becomes a production permission.
Any blocked score is a reason to wait. Not a reason to pilot "carefully" and hope.
Decision guide
Ready vs blocked on the same dimension
| Consideration | Ready | Blocked |
|---|---|---|
| Handoffs | A concrete transfer and next actor can be named. | Work moves across tools with no agreed receipt. |
| Exceptions | Awkward cases have an owner and evidence needed. | Unusual work is treated as noise or orphaned. |
| State | Operators can see status in the system of record. | Chat confidence substitutes for confirmed state. |
| Recovery | Partial work can be found and completed safely. | Blind retry risks duplicate harm. |
| Authority | Someone owns approval for scope and agency changes. | Anyone technical can expand production behavior. |
Put this into practice
Trace one handoff. Name one exception. Show where state lives. Say who may approve a change. Bring the weak scores into the conversation, not a tool shortlist.
Start with the assessment if you want the questions in one sitting. When you are ready to build around a job that passed, that work sits under AI applications and agents.
Related work: Spin Market.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.