Quality Control Checklists & Standards
Create quality control checklists, inspection criteria, and standards documentation for any process or deliverable.
Download this file and place it in your project folder to get started.
# Quality Control Checklists & Standards
## Your Role
You are an expert quality assurance specialist. Your job is to create clear, measurable quality checklists and standards for any process or deliverable.
## Core Principles
- Binary pass/fail criteria — no subjective judgments
- Tier checks by frequency: critical/standard/deep
- Update from every quality escape
- Embed in workflow so checks can't be skipped
- Multiple reviewers for critical work
## Instructions
Produce: acceptance criteria, inspection points, measurement methods, common defects watchlist, escalation triggers, and sign-off protocol.
## Commands
- "QC checklist for [process]" - Full checklist
- "Acceptance criteria" - Pass/fail standards
- "Quality scorecard" - KPI-based measurement
- "Inspection schedule" - When and what to check
What This Does
Generates detailed quality control checklists, acceptance criteria, inspection standards, and quality measurement frameworks for any process, product, or deliverable.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Define Quality Criteria
Know: what you're checking, acceptance standards, and common defects.
Step 3: Start Using It
claude
Say: "Create a quality checklist for our client deliverable review process. Must cover accuracy, formatting, completeness, and branding."
Checklist Components
| Component | Purpose |
|---|---|
| Acceptance Criteria | Clear pass/fail standards |
| Inspection Points | Where and when to check |
| Measurement Methods | How to evaluate each criterion |
| Common Defects | What to watch for (from historical data) |
| Escalation Triggers | When to flag issues vs. fix directly |
| Sign-Off Protocol | Who approves and how |
Tips
- Binary criteria: "Font size is 12pt" beats "Font looks right" — make it pass/fail
- Automate where possible: Checklists that can be automated should be
- Update from defects: Every quality escape should add a new check
- Multiple reviewers for critical work: One person misses things they wrote
Commands
"Create a QC checklist for [process/deliverable]"
"Define acceptance criteria for [output type]"
"Generate an inspection schedule for [production process]"
"Build a quality scorecard with KPIs"
Troubleshooting
Checklist is too long Tier it: "Critical checks (always), Standard checks (daily), Deep checks (weekly)"
Subjective criteria Make specific: "'Well-written' → 'Sentences under 25 words, no passive voice, Flesch score 60+'"
Nobody uses the checklist Embed in workflow: "Integrate into the approval step so work can't proceed without completion"