A board game rulebook has two jobs: help a new group learn the game and help returning players quickly answer questions. The most reliable way to test both is to give the draft and a prototype to people who did not design it, then observe where they stop, search, or make different interpretations.
This guide covers the rulebook itself and a print-proof workflow. It does not replace playtesting, and the final paper size, binding, and PDF settings must match the printer’s current specifications.
1. Inventory every component before writing rules
Lay out the prototype and create a checklist with component name, quantity, image or diagram, and any setup role. Use the same names in the rules, labels, player aids, and component list. If a piece is called a “marker” on the board but a “token” in the rules, choose one term and standardize it.
Ask a second person to pack and unpack the game using only this list. They should be able to tell whether anything is missing and identify each component without the designer explaining it.
2. Put the first-play path in a useful order
A practical structure for many games is:
- game goal and short overview;
- component list with labeled illustrations;
- setup steps, with a finished setup diagram;
- turn or round overview;
- detailed rules in the order players need them;
- game end and scoring conditions;
- examples, edge cases, glossary, and reference tables.
There is no single order that works for every design. The goal is to let readers follow a logical first session while keeping detailed exceptions easy to find later. Put variants and optional rules in a clearly marked section so they do not obscure the standard game.
3. Write each procedure as an action sequence
Use numbered steps for setup and phases. Begin each rule with the action players take, then explain its condition and result. For example: “Choose one card from your hand. Place it face up beside the board. Resolve its effect, then discard it.” If a step has alternatives, label them explicitly.
Define game terms before relying on them. Use the same capitalization and wording everywhere. Avoid pronouns such as “it” when several cards or pieces could be meant. When a rule refers to another section, include the section name or page reference, then recheck it after layout changes.
4. Draw examples for spatial or timing rules
If players need to understand adjacency, line of sight, movement, card orientation, scoring, or turn order, a diagram may be clearer than another paragraph. Give the image a caption, label the pieces, and use arrows or numbered steps to show what happens. Do not rely on color alone to distinguish important states; include symbols or labels that remain understandable in grayscale.
For an example turn, use a legal game state and show each action in sequence. Then compare every object in the diagram with the component list and the written rule.
5. Run a blind teach-test
Give the draft rulebook and prototype to a group with no designer present. Ask them to start and play a short section using only the materials. The designer should observe without correcting them. Record:
- the exact step or phrase where someone pauses;
- the question they ask and the page they consult;
- any rule interpreted differently by two players;
- any component they cannot identify;
- any game state where the group cannot determine what happens next.
After the session, revise the rule, diagram, or index that caused the confusion. Then run the same task with a fresh group. Do not treat a successful playtest as proof that every corner case is covered; separately audit the end condition, ties, simultaneous actions, and unusual component states that apply to your design.
6. Make the printed book easy to scan
Use descriptive headings, consistent terms, a clear contents page for longer manuals, and a glossary or index for frequently queried terms. Repeat table headings when a table spans pages. Keep examples beside the rules they explain when possible, and use running headers so players can tell which chapter they are in.
Ask a returning playtester to find five specific answers without reading from the beginning: how to set up, what a term means, how a common action resolves, how the game ends, and where a rare exception appears. If they cannot find these quickly, improve the navigation before adding more prose.
7. Export and proof the physical format
Keep book pages in normal reading order unless the print provider explicitly requests imposed printer spreads. Adobe notes that booklet imposition changes page arrangement for folding and binding; it also includes settings such as margins, bleed, and creep that depend on the booklet type. Confirm who is responsible for imposition before exporting so you do not rearrange the pages twice.
Make a short test PDF or a full-size print of representative pages. Check small component labels, diagram contrast, page numbers, tables, and the inside margin. Flip through the physical proof in reading order, then verify that each cross-reference still points to the right page.
Before you print
Prepare the interior PDF, cover if available, final trim size, page count, and destination country. Your Book Bound’s listed $99 offer includes one standard hardcover, manual file review, layout and cover support, proof revisions, and standard tracked worldwide delivery. Confirm special binding, paper, or other unusual requirements before ordering.
For a free file check, submit your rulebook files here. Include the intended size, page count, destination country, and expected date so the team can review the setup and confirm the next step.
Sources
- dV Games: How to Write a Standard Game Rulebook — discusses component lists, setup, victory conditions, and examples.
- Adobe InDesign: Print or export book files — book PDF export and consistency checks.
- Adobe InDesign: Impose documents for booklet printing — explains imposition and proof-related setup options.