Overview and components
The overview tells players what they are trying to do, how many people can play, and what the game asks them to manage. It does not replace the rules. The components list identifies every physical item and the terms used for it; the rulebook, labels, and player aids should use the same names.
Validation question: can a player locate every listed component and distinguish similar pieces without asking the designer?
Setup and turn structure
Setup must produce the correct starting state in order. It should say who takes the first turn, what differs by player count, and where random setup belongs. Turn structure then establishes the repeating rhythm: start-of-turn effects, choices, costs, resolution, cleanup, and what passes to the next player.
Validation question: can a new group set up and complete a first turn using only the page, components, and any named player aid?
Legal actions and resolution
Players need to know what actions exist, their prerequisites, limits, costs, timing, and outcomes. A rule such as “take a resource” is incomplete if the source, limit, timing, or conflict is unclear. Examples are valuable when they illuminate a hard choice or an exception, not when they merely repeat a simple sentence.
Validation question: when two players propose different interpretations, does the text provide a way to resolve the question?
Progress, ending, ties, and edge cases
Explain scoring or another progress measure before the ending if it affects decisions. State the exact end trigger, whether the current round completes, and how a winner is determined. Tie procedures, depleted supplies, impossible effects, simultaneous triggers, and conflicting card text are small sections with large blind-test consequences.
Validation question: can players explain why the game ended and determine the winner without designer confirmation?
Terminology and reference aids
A glossary is useful when a term carries a specific rule meaning. A player aid should compress recurring sequences and common reminders, not introduce rules that contradict or silently extend the main text. Keep version labels visible so a tester does not use an outdated aid with a revised rulebook.
Use the Rulebook Completeness Checker to mark the draft you have now. Then use the Blind Playtest Readiness Checker to review the complete packet and observation plan. Only a real blind session shows whether readers can apply these sections at the table.