AI Agent Readiness Audit

Step 1

Start with the workflow, not the tool.

Use this audit when you want to diagnose one recurring workflow before a call. It maps the sources, owners, decision rules, evidence, handoffs, and review gates that decide whether the next step is Agent, Automation, Operating System, Cleaner Context, or Park.

Privacy note:

Do not include passwords, secrets, customer records, regulated data, confidential client details, payment details, medical, legal, HR, employment, or security-sensitive information.

Step 2

Workflow basics and quick diagnostic.

Workflow name Business owner

Who receives the workflow output and owns the next action?

Recurring trigger What happens if this goes wrong?

Current pain

Step 3

Score the workflow.

1 = not true yet. 3 = partly true. 5 = clearly true and repeatable. Higher scores do not all mean "build an agent"; they show which path is safest to explore next.

RecurrenceProblem pressure 3 The workflow happens often enough to justify designing it. Business importanceProblem pressure 3 A bad handoff creates meaningful rework, customer friction, operational risk, compliance risk, or leadership drag. Source clarityContext readiness 3 Named sources of truth exist and are usable. Ownership clarityContext readiness 3 Each step has a named owner, reviewer, or escalation path. Decision rulesContext readiness 3 Routing, prioritizing, approving, rejecting, escalating, or pausing rules are written down. Evidence qualityContext readiness 3 Outputs can show what evidence was used and where assumptions remain. Handoff qualityContext readiness 3 A new person could understand state, next action, owner, deadline, and open questions. Automation fitAutomation readiness 3 Triggers, inputs, outputs, and low-risk actions are structured enough for automation. AI fitAI/agent fit 3 AI would help with drafting, summarizing, extracting, classifying, researching, or triaging. Agent fitAI/agent fit 3 The workflow needs coordinated multi-step action, stable context, permissions, auditability, and escalation. Risk controlControl and maintenance 3 Wrong outputs are caught before they create external, customer, legal, financial, or reputational consequences. Maintenance ownerControl and maintenance 3 Someone owns source, rule, template, exception, and quality-check updates.

Step 4

Minimum context map.

Trusted sources

Inputs required Output required

Decision rules

Evidence to preserve Human review gate

Allowed automatic actions Actions that require human approval

Known exceptions Escalation path

Maintenance owner

Step 5

Your audit result.

Step 6

Send the audit report request.

With your consent, this sends your contact details, workflow answers, scores, and rules-generated report text to the audit endpoint. The next screen gives you a booking link with the report details attached.

First name Last name

Email I agree to be contacted about this audit and understand I should not include confidential or sensitive information here. I would like to discuss this audit result in a workflow audit conversation.

Step 7