# AI Pilot Acceptance Testing: Prove a Workflow Is Ready: worksheet

Prepared September 14, 2026. Adapt to your own process. Do not include secrets or private customer records.

## Working record

Complete the charter before tuning the workflow. Give the business owner a stable definition of a pass and preserve a separate evaluation set. The final decision should identify the exact input scope and permissions accepted. If the evidence supports only a supervised pilot, record that as the outcome rather than quietly broadening the meaning of production readiness.

| Field | Your working note |
|---|---|
| Workflow and business owner | Fill in for your business |
| Allowed inputs and sources | Fill in for your business |
| Permitted tools and actions | Fill in for your business |
| Prohibited actions | Fill in for your business |
| Required output and reviewer | Fill in for your business |
| Test categories and expected outcomes | Fill in for your business |
| Launch-blocking failures | Fill in for your business |
| Recovery and pause route | Fill in for your business |
| Operator and backup demonstration | Fill in for your business |
| Version and acceptance decision | Fill in for your business |

Use the notes to identify the next decision, not to create an appearance of completeness. Mark unknowns openly, assign an owner, and attach a safe evidence reference where appropriate. Do not put passwords, customer records, or private correspondence in a worksheet that will be shared widely.

Review the completed sheet with someone who actually performs the work. Ask them to walk through one ordinary example and one exception using only the recorded instructions. Update the unclear parts, then save a dated version. That small exercise turns a planning template into a practical operating artifact and gives future reviewers a clear starting point.