AI-Assisted Business System QA Checklist

Define the business use case

1. Name the workflow, team role, input source, expected output, and decision that the AI-assisted asset should support.
2. Decide whether the output is a checklist, SOP, prompt library, QA report, or review note.
3. Keep sensitive customer or account data out of prompt examples unless a safe access path is agreed.

Create reviewable inputs and outputs

1. Use redacted examples, public URLs, screenshots, safe exports, or sample data where possible.
2. Write acceptance criteria for what a good answer, SOP, prompt, or QA note should include.
3. Mark anything that requires human review before sending to a customer or changing a live system.

Build a handoff trail

1. Document the prompt, source context, assumptions, output location, owner, review step, and next action.
2. Avoid claims that AI will guarantee accuracy, deliverability, rankings, revenue, or compliance.
3. Keep the asset reusable by naming what to update when the workflow changes.

Choose the next gig

1. Use AI-095 for an AI-assisted CRM SOP pack.
2. Use AI-096 for a business prompt library setup.
3. Use AI-097 for a Codex-assisted website QA report.