Source: frameworks/kit-blueprint-mapping-session/04-blueprint-mapping-session-quality.md
Blueprint Mapping Session — Quality Checklist
Pass threshold: 90 / 100 points When to run: After every draft, before presenting to Kathryn for review. Applies to: Both client-facing deliverables (written summary email + 90-day blueprint).
Part A: Written Summary Email (50 points)
Structure (15 points)
| # | Check | Points |
| A1 | Opening references a specific moment or outcome from the session — not a generic "great session" | 3 |
| A2 | Decisions captured: the direction chosen and why are stated clearly | 3 |
| A3 | First action is restated with deadline | 3 |
| A4 | Deliverables listed: what the client will receive (blueprint, recording, resources) | 3 |
| A5 | Closing is warm, specific, and brief — not motivational or generic | 3 |
Content Accuracy (15 points)
| # | Check | Points |
| A6 | Every claim traces to what was discussed in the session — nothing fabricated | 5 |
| A7 | Client's name, company name, and any proper nouns are spelled correctly | 3 |
| A8 | Decisions attributed to the client are things they actually committed to, not the advisor's unconfirmed recommendations | 4 |
| A9 | No assumptions beyond what the client said (years in industry, revenue, team size — only include if stated) | 3 |
Voice & Boundaries (20 points)
| # | Check | Points |
| A10 | Reads as peer advisory — not coaching, not meeting minutes, not a transcript summary | 5 |
| A11 | Zero AI tells: no "That's exactly the kind of...", no inspirational reframing, no narrating behavior | 5 |
| A12 | Does not sell Advisory OS, Deploy Sprint, or any other offer | 4 |
| A13 | Does not promise ongoing support or imply a future relationship | 3 |
| A14 | Does not over-explain why the client's own decisions matter | 3 |
Part B: 90-Day Blueprint (50 points)
Structure (15 points)
| # | Check | Points |
| B1 | All sections present: Header, Opening Frame, The Decision, The Offer, 90-Day Timeline, First Action, Resources, Footer | 5 |
| B2 | Single-file HTML, self-contained (no external dependencies except Google Fonts) | 3 |
| B3 | Responsive — renders correctly on desktop and mobile | 3 |
| B4 | Footer includes advisor name, company, and session date | 2 |
| B5 | Doc type reads "90-Day Blueprint" — not "Client Blueprint" or "Blueprint" | 2 |
Content Accuracy (15 points)
| # | Check | Points |
| B6 | Opening Frame uses the client's own words or observable facts — not diagnosis or interpretation | 4 |
| B7 | The Decision section states the ONE direction chosen — not multiple options | 3 |
| B8 | The Offer section is concrete: name, audience, price range, delivery format | 3 |
| B9 | Timeline has specific named actions per month — not aspirational buckets like "define strategy" | 3 |
| B10 | First Action is a single concrete thing with a 48-hour deadline | 2 |
Design & Tone (10 points)
| # | Check | Points |
| B11 | Design language matches vault standards: Cormorant Garamond + Inter, warm/professional palette | 3 |
| B12 | Zero internal jargon in any section (constraint, CPM, deploy chain, build, GPS, Mode) | 3 |
| B13 | Warm and direct tone — not clinical, not casual, not motivational | 2 |
| B14 | Resources section contains actual useful items, not placeholder text | 2 |
Differentiation from Ongoing Blueprint (10 points)
| # | Check | Points |
| B15 | No build cards — uses monthly milestones instead | 3 |
| B16 | No deploy chain or 8-stage process | 2 |
| B17 | No prework / "What We Need From You" section | 2 |
| B18 | No status badges (Active/Queued) — this is not a living document | 2 |
| B19 | No "Questions We'll Work Through" — questions were resolved in the session | 1 |
Required-Revise Triggers
Any of these automatically fails the QC regardless of point total:
- Fabricated detail — any claim that doesn't trace to intake answers or session transcript
- Sells another offer — any mention of Advisory OS, Deploy Sprint, or "next steps together"
- Internal jargon in client deliverable — any use of constraint, CPM, deploy chain, GPS, Mode
- Wrong client name or company — factual error in the header or body
- Missing First Action — the most important element of the blueprint is absent or vague