Project Plan — Context & Inputs
Required Inputs
1. Constraint Priority Matrix (Primary Driver)
The CPM is the single most important input. Every project plan section traces back to constraint analysis.
| Field | Priority | Description |
|---|---|---|
| Constraint name + ID | Required | Each constraint gets a unique ID (C1, C2, etc.) scoped to this initiative |
| Constraint tier | Required | Upstream/Co-Primary, Secondary, or Downstream |
| Pattern markers | Required | Recurring, Escalating, Same Root Cause, Solve Together |
| GPS data | Required | Position, Direction, Speed for the initiative |
| Recommended actions | Required | What the CPM says should happen — drives build design |
2. Session Transcript(s)
| Field | Priority | Description |
|---|---|---|
| Key quotes | Required | Direct quotes that serve as evidence for constraints and builds |
| Decisions made | Required | Any commitments, approvals, or direction changes |
| New information | Required | Facts about tools, team, processes not previously known |
| Prework received | If present | Items the client said they'd provide and did |
| Open questions | If present | Questions that surfaced and need resolution |
3. Client Reference Data
| Field | Priority | Description |
|---|---|---|
| Client name | Required | Canonical spelling |
| Company name | Required | Canonical spelling |
| Team members | Required | Names, roles, correct spellings — overrides transcript |
| Tools in use | Required | Software, platforms — correct names |
| Engagement details | Required | Rate, cadence, start date |
4. Master Plan
| Field | Priority | Description |
|---|---|---|
| Initiative listing | Required | Confirms this initiative exists and is active |
| Cross-initiative constraints | If present | Constraints that affect multiple initiatives |
| Engagement GPS | Reference | Master plan GPS provides broader context |
5. Existing Project Plan (Mode 2 only)
| Field | Priority | Description |
|---|---|---|
| Current build statuses | Required | Where each build stands in deploy chain |
| Outstanding actions | Required | What was due and what's still open |
| Prework status | Required | What's been received vs still needed |
| Timeline progress | Required | Which weeks are complete |
Input Priority Hierarchy
When inputs conflict:
- Reference data wins for names, spellings, tools (canonical source)
- Session transcript wins for decisions, new facts, client quotes
- CPM wins for constraint classification and priority
- Master plan wins for cross-initiative context
- Previous project plan provides continuity — update, don't discard
What Drives Each Section
| Section | Primary Input | Supporting Inputs |
|---|---|---|
| Header | Reference data | Master plan (initiative scope) |
| Matrix Validation Banner | CPM | Session transcript |
| GPS | CPM + session | Previous GPS (for trajectory) |
| Current State vs Target | CPM + session | Previous state items |
| Deployment Plan (builds) | CPM recommendations + session decisions | Previous build statuses |
| Constraints | CPM | Session (new evidence) |
| Themes | CPM + session patterns | Previous themes |
| Stakeholders | Reference data + session | Previous stakeholder cards |
| Prework | Session + project plan | Previous prework status |
| Evidence | Session transcript | Previous quotes |
| Product Constraints | Session observations | Previous coaching notes |
| Notes | Session + reference data | Previous notes |
| Actions | Session decisions | Previous outstanding actions |
| Timeline | Build statuses + session | Previous timeline |
Validation Rules
- Every constraint referenced in a build card MUST exist in the Constraints section
- Every build referenced in a target state item MUST exist in the Deployment Plan
- Every stakeholder with an owner tag MUST appear in at least one build card
- Every "Still Needed" prework item MUST reference which build it blocks
- The deploy chain for each build MUST show exactly 8 steps
- GPS must be scoped to THIS initiative, not the overall engagement
- All dates must be internally consistent (timeline vs build cards vs header)