What this rulebook checklist tests
A complete packet lets a first-time group identify the game objective, inventory the components, build the starting state, take legal turns, track progress, and finish and resolve a tie. It also gives readers consistent terms, representative examples, and enough exception handling to continue without the designer.
Completeness and clarity are different tests. A draft can contain every heading and still leave readers unsure about timing or permissions. A short prototype packet can be testable if it clearly supports setup, action, resolution, and ending. Mark only what the current draft supports.
Worked review example
Suppose setup is absent and the tie rule says only “most points wins.” Mark Setup as Missing and Ties as Unclear. The checker puts setup first, recommends a numbered sequence with the final ready-to-play state, and then asks for a complete tiebreak sequence. That is more actionable than a single completeness score.
How to interpret the result
Incomplete means at least one section is missing; finish those instructions before blind testing. Needs clarity pass means all sections exist but at least one requires a narrow reader test. Test-ready draft means this self-screen found no gap—not that the rules are proven understandable.
Turn a review into evidence
After revising, give the packet to a fresh group without teaching. Log their first questions, pauses, rule lookups, disagreements, and any place play stops. If readers repeatedly stop on a section marked clear, revise that exact passage and test it again. The Playtesting & Rulebook Validation workflow connects this review to packet readiness and issue prioritization.
Related resources
Use the Rulebook Sections Reference for the job each section performs. The Readiness Checker adds packet and observation concerns, while the Issue Log ranks observed failures after the session.