Knowledge Systems

Audit a Workflow for AI Automation

Assess one service workflow for bounded AI assistance using supplied operating evidence, transparent calculations, and explicit readiness dependencies.

Quick facts

Best for
Owners · Founder-operators
Prompt type
Effectiveness
Expected result
An evidence-based automation-fit audit with step-level classifications, scenario formulas and ranges, assumptions, uncertainty and confidence scores, Unknowns, readiness dependencies, a bounded validation plan, and named-human approval gates.
Time saved
Varies by workflow scope and evidence quality
Required inputs
WORKFLOW STEPS · WORKFLOW VOLUME · TIME PER STEP · ERROR AND EXCEPTION DATA · BUSINESS VALUE · DATA SOURCES AND ACCESS · CONSTRAINTS · WORKFLOW OWNERS · SUCCESS MEASURES
Works with
ChatGPT + Claude

What this prompt does

  • Maps supplied workflow evidence to bounded assist, automate-later, and keep-human recommendations.
  • Makes assumptions, calculation methods, uncertainty, privacy, security, access, and human approval dependencies inspectable.

When to use

  • Before selecting or buying an AI solution for a recurring workflow whose steps, volume, handling time, exceptions, and owner can be documented.

When not to use

  • Do not use it to authorize a priority, purchase, deployment, data-access change, permission change, or live workflow change.
  • Do not place unauthorized workflow data or unnecessary personal, sensitive, or confidential data in an AI system.

The prompt

#CONTEXT:
Create an automation-fit audit for one service workflow. This is decision support for a named human owner, not authorization to automate or change the workflow.

#INPUTS:
- Current workflow steps, decisions, handoffs, and stop conditions: [WORKFLOW STEPS]
- Observed case volume with period and source: [WORKFLOW VOLUME]
- Observed handling time per step with measurement basis: [TIME PER STEP]
- Error, rework, exception, and escalation evidence: [ERROR AND EXCEPTION DATA]
- Supplied customer, revenue, capacity, or quality value: [BUSINESS VALUE]
- Data sources, quality notes, access rights, and permission owners: [DATA SOURCES AND ACCESS]
- Operational, budget, technical, regulatory, and timing constraints: [CONSTRAINTS]
- Named workflow owners and documented decision rights: [WORKFLOW OWNERS]
- Supplied success measures, baselines, thresholds, and measurement owners: [SUCCESS MEASURES]

#INSTRUCTIONS:
1. Map each supplied workflow step, decision, handoff, exception, owner, and evidence source. Label missing facts Unknown.
2. For each step, assess standardization, judgment, exception rate, error consequence, data availability, privacy, security, data-access dependency, reversibility, and required human oversight.
3. Classify each recommendation as Assist now, Test with controls, Defer until dependency is resolved, or Keep human. Explain the evidence or source basis.
4. Distinguish every value as Supplied, Calculated, or Estimated. For a Calculated value, show the formula, units, and supplied operands. For an Estimated value, show a range, assumptions, uncertainty, and a confidence score with rationale.
5. Do not invent, infer, or fabricate ROI or return on investment, time savings, cost, feasibility, volumes, error rates, value, baselines, owners, access, or technical capability. Unsupported conclusions remain Unknown.
6. Treat time-savings calculations as scenarios, not forecasts. Example formula: supplied volume per period × supplied time per case × proposed bounded reduction. Show the resulting range and do not convert it to currency without supplied labor-cost evidence.
7. Create a privacy, security, and data-access dependency register. State the authorized source, approved purpose, current access, permission owner, retention constraint, required control, and stop condition.
8. Define a bounded validation test for any Assist now or Test with controls recommendation. Include baseline, sample, success measure, failure threshold, human review, rollback, and evidence to retain.
9. Do not infer authorization from a supplied owner, access record, priority, or recommendation. Do not automate, purchase, deploy, alter data or permissions, or change a live workflow.
10. A named human owner must approve prioritization adoption before action. A named human owner must approve purchasing before action. A named human owner must approve deployment before action. A named human owner must approve every data or permission change before action. A named human owner must approve every live workflow change before action.
11. Use only authorized workflow data in an approved AI workspace or approved AI vendor. Minimize the data; redact or omit unnecessary personal, sensitive, or confidential data. Follow company retention and vendor policy.

#RESPONSE FORMAT:
## Evidence and source basis
| Claim or input | State: Supplied, Calculated, Estimated, or Unknown | Source | Formula or assumptions | Uncertainty | Confidence score |
|---|---|---|---|---|---|

## Automation-fit audit
| Workflow step | Fit classification | Evidence basis | Human judgment | Exceptions and risk | Dependency | Stop condition |
|---|---|---|---|---|---|---|

## Privacy, security, and data-access dependencies
| Dependency | Authorized source and purpose | Permission owner | Required control | Status | Stop condition |
|---|---|---|---|---|---|

## Scenario calculations
| Scenario | Formula | Supplied operands | Estimated range | Assumptions | Uncertainty and confidence score |
|---|---|---|---|---|---|

## Bounded validation plan and human approvals

Input checklist

  • WORKFLOW STEPS
  • WORKFLOW VOLUME
  • TIME PER STEP
  • ERROR AND EXCEPTION DATA
  • BUSINESS VALUE
  • DATA SOURCES AND ACCESS
  • CONSTRAINTS
  • WORKFLOW OWNERS
  • SUCCESS MEASURES

Example input

Fictional example — WORKFLOW STEPS: Five documented intake stages. WORKFLOW VOLUME: 180 per month, Q2 CRM report. TIME PER STEP: Seven-minute median, ten-case sample; step-level timing Unknown. ERROR AND EXCEPTION DATA: 14% manager-review rate; five missing-location rework cases. BUSINESS VALUE: Response speed; revenue attribution Unknown. DATA SOURCES AND ACCESS: Authorized de-identified CRM field sample; customer message text excluded; Maya, access owner. CONSTRAINTS: $2,000 test ceiling; customer-facing automation prohibited. WORKFLOW OWNERS: Maya, operations; Omar, security. SUCCESS MEASURES: Missing-field rework rate; baseline and target Unknown.

Expected output structure

  • An evidence-based automation-fit audit with step-level classifications, scenario formulas and ranges, assumptions, uncertainty and confidence scores, Unknowns, readiness dependencies, a bounded validation plan, and named-human approval gates.

Customize this prompt

  • Replace broad averages with timestamped step observations before comparing options.
  • Keep customer-facing, financial, legal, employment, and safety-critical decisions human-owned unless separately governed.

Guardrails

  • Preserve the evidence or source basis for every material claim; unsupported facts remain Unknown.
  • Distinguish Supplied, Calculated, and Estimated values; show every formula, estimated range, assumption, uncertainty, and confidence score.
  • Do not invent, infer, or fabricate ROI or return on investment, time savings, cost, feasibility, volume, error rate, value, owner, access, or capability.
  • Make every privacy, security, and data-access dependency explicit before recommending a test.
  • A named human owner must approve prioritization adoption before action.
  • A named human owner must approve purchasing before action.
  • A named human owner must approve deployment before action.
  • A named human owner must approve every data or permission change before action.
  • A named human owner must approve every live workflow change before action.
  • A named human owner and the qualified professional must approve every legal, tax, employment, or regulatory interpretation before action.
  • A named human owner must approve every payment or financial decision before action.
  • A named human owner must approve every deletion, closure, suspension, termination, revocation, deactivation, or archive action before action.
  • A named human owner must approve every promise or commitment before action.
  • A named human owner must approve every policy exception before action.
  • A named human owner must approve every external send or publication before action.
  • Use only authorized workflow data in an approved AI workspace or approved AI vendor; minimize data, redact or omit unnecessary personal, sensitive, or confidential data, and follow company retention and vendor policy.
  • Do not infer authorization. Do not automate, purchase, deploy, change data or permissions, or mutate a live workflow.

Related articles

NEXT STEP

Next step

Find out what your company's knowledge is worth.