Purpose: Use this checklist to score the quality of a playbook before publishing or reusing it with a customer.
Scoring:
✅ Pass = 2 points
⚠ Minor Issues = 1 point
❌ Major Issues = 0 points
Pass Threshold: 19/24 or higher
General (Max 6 pts)
Check | Pass/Needs Fix | Notes |
Playbook title follows standard (Product – Tier – Implementation Type) | ⬜ |
|
Duration and # tasks align with scope (no overruns) | ⬜ |
|
Clear customer-facing descriptions, no jargon | ⬜ |
|
Module Level (Max 6 pts)
Check | Pass/Needs Fix | Notes |
Modules use format: Gerund + Object (“Preparing Database”) | ⬜ |
|
Module sequence reflects journey (Kickoff → Data → Training) | ⬜ |
|
Role Restrictions applied (Customer/Internal) | ⬜ |
|
Task Level (Max 8 pts)
Check | Pass/Needs Fix | Notes |
Task names are action-oriented (no “your/our”) | ⬜ |
|
Task Type correctly set (Customer vs Internal) | ⬜ |
|
Dependencies in place (no orphans) | ⬜ |
|
Start/Due Dates set (relative offsets, not blank) | ⬜ |
|
Visibility correct (Customer tasks visible, Internal tasks hidden) | ⬜ |
|
All links validated (no broken links) | ⬜ |
|
Task descriptions are concise (≤ 2 lines) | ⬜ |
|
Subtasks or guides used for detail | ⬜ |
|
Visual & UX (Max 2 pts)
Check | Pass/Needs Fix | Notes |
Screenshots/visuals used appropriately | ⬜ |
|
Consistent color palette & alt-text applied | ⬜ |
|
Automations & Data (Max 2 pts)
Check | Pass/Needs Fix | Notes |
Automations configured & tested in Sandbox | ⬜ |
|
Required data fields linked to CRM | ⬜ |
|
Totals
General: ___ / 6
Module: ___ / 6
Task: ___ / 8
Visual/UX: ___ / 2
Automations/Data: ___ / 2
Overall Score: ___ / 24
✅ Next Step: Anything below 19/24 requires revision before publishing.