Blueprint Mapping Session — Terminology
Terms the Client Sees
These terms appear in client-facing deliverables (summary email, 90-day blueprint).
| Term | Meaning | Notes |
|---|---|---|
| Blueprint Mapping Session | The 90-minute paid session | Use the full name in the summary email header; "our session" in body text |
| 90-Day Blueprint | The action plan document delivered after the session | NOT the same as the ongoing client blueprint (progress dashboard) |
| Testable offer | The one offer the client will take to market within 90 days | "Testable" signals it's a first version meant to generate feedback, not a final product |
| Action plan | The structured 90-day timeline with monthly milestones | Interchangeable with "your plan" or "the plan we mapped" |
| First action | The single thing to do within 48 hours of the session | Prominently featured — this is the bridge from session to momentum |
| Milestone | A monthly checkpoint in the 90-day timeline | Not a build card. Not a deploy gate. A concrete marker of progress. |
Terms the Client Does NOT See
These are internal to the advisor's prep and kit documentation. Never use them in client-facing deliverables.
| Internal Term | What to Use Instead |
|---|---|
| Constraint | "challenge," "what's in the way," or just describe the situation |
| CPM / Constraint Priority Matrix | Don't reference — not part of BMS workflow |
| Deploy chain / deploy cycle | Don't reference — no ongoing builds |
| Build (in the AOS sense) | Don't reference — BMS doesn't produce builds |
| Upstream / downstream | Describe the cause and effect directly |
| GPS / Position-Direction-Speed | Don't reference — internal tracking |
| Mode 1 / Mode 2 / Mode 3 | Don't reference — internal kit structure |
| Advisory OS | Don't reference in deliverables (can use in session conversation if relevant) |
| Product ladder | Never mention |
| Conversion / upsell | Never mention |
| Focus paralysis | Describe the situation instead ("too many options," "hard to narrow down") |
BMS-Specific Vocabulary
These terms are used internally in the kit and facilitation SKILL. Some cross over to client-facing use.
| Term | Meaning | Client-Facing? |
|---|---|---|
| Session block | One of the 5 segments of the session arc (Ground, Clarify, Map, Build, Close) | No |
| Ground (Block 1) | 0–10 min: validate intake, surface changes | No |
| Clarify (Block 2) | 10–30 min: get specific on goals, identity, constraints | No |
| Map (Block 3) | 30–60 min: lay out viable paths, pressure-test, narrow to one | No |
| Build (Block 4) | 60–80 min: work backwards from testable offer to 90-day plan | No |
| Close (Block 5) | 80–90 min: confirm plan, name first action, explain deliverables | No |
| Prep doc | The advisor's session planning document — not client-facing | No |
| Written summary | The email sent within 24 hours recapping decisions and next steps | Yes (it IS the email) |
| 90-day blueprint | The HTML document with the action plan | Yes (it IS the document) |
Distinction from Ongoing Blueprint Terms
The ongoing client blueprint (kit-blueprint) uses terms that do NOT appear in BMS deliverables:
| kit-blueprint Term | BMS Equivalent |
|---|---|
| Build card | Monthly milestone |
| Deploy chain (8 stages) | None — no deployment process |
| Prework / "What We Need From You" | None — one-time session, no ongoing asks |
| "Questions We'll Work Through" | None — questions were resolved in the session |
| Status badge (Active/Queued) | None — not a living document |
| "Where You Are vs Where We're Going" (two-column grid) | "The Decision" (single narrative section) |