skills/pitch-deck-builder/references/quality-checklist.md

# Quality Checklist

Run this before final delivery.

## Story and commercial judgment

- The client decision is explicit.
- The first three pages answer why this matters now.
- The recommendation is clear, even if the deck is framed as a discussion.
- The deck addresses likely CEO/CFO/Board/sponsor/lender objections.
- The deck includes next steps and the bank's role.
- There are no filler pages.
- Each section escalates the argument.
- Comparative rationale is not repeated after it has been proven unless the repeated page changes the decision, oversight action, or recommendation sensitivity.

## Slide quality

- Every slide has a conclusion-led title.
- Every slide has one primary message.
- Visuals are appropriate to the message.
- Tables are not overloaded with irrelevant metrics.
- Speaker notes include the intended talk track where helpful.
- Appendix pages are used for support, not to hide essential logic.
- For a native deck, the exported final `.pptx` is rendered and visually inspected, including its contact sheet and high-density pages.

## Evidence and citations

- Every material number is sourced, dated, scaled, and period-labeled.
- Market data and trading multiples are fresh or marked stale.
- Private-company data is labeled by source and period.
- Assumptions are separated from facts.
- Source conflicts are disclosed.
- Placeholder pages are clearly marked.
- QA results distinguish layout errors from visually adjudicated non-blocking warnings rather than stating `0` warnings when warnings were present.

## Banking-specific checks

- Valuation pages state methodology, basis, date, and key assumptions.
- Financing pages distinguish market capacity from theoretical capacity.
- Buyer/investor pages state selection logic and prioritization criteria.
- Strategic alternatives pages compare value, certainty, timing, control, and risk.
- Process pages include realistic milestones and dependencies.
- Credentials pages are relevant to the client and transaction type.

## Non-destructive checks

- Existing files/decks/data were not overwritten unless requested.
- Existing template/master/style was preserved unless requested.
- Source data was not deleted, hidden, or altered.
- Any suggested removals or replacements are clearly marked as suggestions.

## Final handoff

If not creating a native deck, output a complete storyboard with:

- deck metadata;
- MD-level storyline;
- deck architecture;
- slide-by-slide draft;
- source register;
- open items;
- QC status.

For HTML storyboard output, follow `../../../references/html-artifact-standard.md` and create a standalone HTML artifact rather than a dashboard-builder render contract.