---
name: deliverable-qa-checklist-builder
description: Build a tailored QA checklist that catches accuracy, scope, and quality issues in a client deliverable before it ships. Use this skill whenever a firm is about to send work to a client and says 'build a QA checklist for this deliverable', 'review this before it goes to the client', 'what should we check before we send this', or 'we keep sending work with mistakes'. Trigger whenever a client-facing deliverable needs a final quality pass before delivery.
---

# Deliverable QA Checklist Builder

## What this does and why it matters
The fastest way to lose client trust is a deliverable that goes out with an obvious error, a missing piece of scope, or the wrong client's name in it. This skill builds a QA checklist tailored to the specific deliverable, so the final review catches what actually goes wrong for this kind of work instead of a generic once-over. A consistent QA pass is what separates a firm that feels reliable from one the client has to double-check, and double-checked firms do not get referred.

## Inputs to gather
1. The deliverable type and its purpose for the client.
2. The scope or brief it is supposed to satisfy.
3. Who the audience is and how polished it must be.
4. Common mistakes this firm has made on similar work.
5. Any client-specific requirements or standards.

## Method
Build the checklist in layers, because different failures need different eyes. Check scope first: does the deliverable actually do what was promised, with nothing missing and nothing out of scope added. Then accuracy: are the facts, figures, names, and calculations correct and internally consistent. Then quality and polish: clarity, formatting, tone, and the small errors that signal carelessness. Then client fit: does it meet this client's stated standards and use the right names, dates, and details. Make each item a concrete yes/no a reviewer can actually check, and front-load the checks most likely to catch a costly mistake so a rushed review still catches the worst ones.

## Output format
ALWAYS use:

# QA Checklist: [Deliverable] | [Client]
## Scope check (does it deliver what was promised)
## Accuracy check (facts, figures, names, calculations)
## Quality and polish (clarity, formatting, tone)
## Client fit (their standards, right names and dates)
## High-risk items (the checks most likely to catch a costly error)
## Sign-off (reviewer, date, ready to send yes/no)

## Anti-patterns to avoid
- A generic checklist that ignores how this deliverable actually fails.
- Vague items a reviewer cannot objectively check.
- Checking polish while missing a scope gap or a wrong number.
- No named sign-off, so no one actually owns the review.

## Example
A QA checklist for a client-facing financial model verifies every requested scenario is present, that totals foot and the prior-year figures tie out, that formatting and labels are clean, that the client's fiscal year and entity name are correct, and flags the assumptions tab as the highest-risk item, ending with a named reviewer sign-off.