Human–AI Workflow
Readiness Check

An AI agent can produce a plausible answer while the team still has no shared decision. Use these seven questions on one real workflow before adding another agent, approval step or automation.

Seven questions for one workflow

Select “Clear” only where the answer already exists. Your selections stay in this browser and are not sent to me.

01 Who owns the exact decision?

Name the accountable person and the action they can accept, reject or return for review. “The team” is not an owner.

02 What context is the decision based on?

Can the reviewer find the input, source, version and applicable policy without reconstructing a chat?

03 What may the agent do, and what stays human?

Separate suggestions, system actions and irreversible decisions. Define permissions and the engineering boundary.

04 What evidence is sufficient to proceed?

Specify a representative test set, failure types and an acceptance threshold before the workflow goes live.

05 Where does the accepted state live?

Identify the record that says what was approved, by whom and when. A successful agent run is not acceptance.

06 When does approval expire or need revalidation?

Name changes to evidence, policy, prompt, data source or destination that reopen the decision.

07 What happens on an exception, and how will you know it worked?

Define the human escalation route and measure accepted outcomes, rework and recovery cost.

What a decision record can look like

Illustrative example. This is a sample format, not a claim about a client or a production system.

KYB document triage · bounded pilotExample decision record
Owner and action
Sofia, the illustrative Head of Compliance, approves an agent to sort incoming KYB documents into “review first” and “ready for human check” queues. Only a human reviewer may accept or reject a case.
Context and evidence
Checklist KYB-v3, sample set PILOT-50 and evaluation note EVAL-01 are the versioned inputs in this example. Sofia reviews missing-document and false-complete cases before the pilot starts.
Accepted state
Sofia records “Pilot approved for triage only” on 28 September 2026 against KYB-v3 and EVAL-01. No automatic case approval is permitted.
Expiry and revalidation
Reopen approval if the checklist, model or prompt, document schema, source, routing destination or human review rule changes; review again after 30 days.
Escalation and outcome
Uncertain or conflicting cases go to Sofia's assigned compliance reviewer. Track accepted classifications, missed mandatory documents, rework and reviewer time, not just successful agent runs.

Take one workflow from ambiguity to an agreed next step.

If several answers are still implicit, we can map the current process, define decision rights and controls, and agree what would make a bounded implementation ready.

Bring one live workflow for a Product / System Discovery conversation

This opens an email draft to [email protected]. You choose what to send.

Back to top