Board game rulebooks

How to write rules people can actually use

Everyone complains about rulebooks. Almost nobody teaches how to write one. This is a handbook synthesised from 106 primary sources, with every claim linked back to where it came from.

Continue with Google

Free, always. Sign in once to unlock the full handbook, the research database, the checklist and every download.

106primary sources
127findings, each with a citation
68rulebooks studied
14topic areas

What you unlock

The full handbook

17,000 words across seven parts — foundations, architecture, craft, production, process, evidence and templates.

All 127 findings

The research database, filterable and searchable, with a source link on every row.

68 real rulebooks

What the community praises and condemns — named games, specific reasons, linked sources.

Pre-print checklist

46 checks across 8 phases, plus style rules, metrics and structure templates.

106 sources

Every document harvested for the project, with clickable URLs.

Word & Excel downloads

The handbook as .docx and the 10-sheet research database as .xlsx, in English and Thai.

Free sample

Chapter 1 — Why the rulebook is not paperwork

1.1 The rulebook is the game

Strip the rulebook out of the box and what remains is a set of tokens. Attractive tokens, perhaps, but not a game. The rules are the only thing that converts components into the specific experience a designer built. Punchboard puts it plainly: "Without the rules, all you're left with is a box full of tokens and pieces."

There is a second, less obvious reason the rulebook carries disproportionate weight. Board games have no shared interface. Every video game has a controller and a screen; every website has a browser. Board games have nothing in common except the manual. That makes rulebooks the one universal surface of the hobby — and, as accessibility writer Michael Heron observes, its one universal point of inaccessibility.

1.2 The commercial case

A bad rulebook is not a cosmetic problem. It is a business risk with documented casualties.

  • A professional editor names games killed by their rulebooks. Paul Grogan — who has edited roughly a hundred rulebooks, including Vital Lacerda's heaviest designs — was asked directly whether a poor rulebook has ever damaged a game's success. His answer: "There are a number of examples of how a poor rulebook killed a game. First Martians, Batman Gotham City Chronicles, and many more."
  • Awards juries now reject games over rulebooks. The Spiel des Jahres jury issued a public statement that it had ruled out otherwise-strong games purely on rulebook quality: "We jury members no longer wish to see ourselves in the role of beta-testers for rulebooks, which are only made adequate on the second printing run."
  • Buyers filter on it. BGG users state directly that they are less likely to buy a game when reviews complain about the rules, and reviewers defend covering rulebooks on the grounds that a game you cannot learn is a game you cannot evaluate: "How can you even tell the gameplay is good without at least a decent rulebook telling you how to play the game?"
  • It is an accessibility gate. One player's response in the 1 Player Guild thread is worth keeping on your desk: "My eyes aren't great. If a rulebook doesn't have a readable layout, a clear hierarchy of information, adequate diagrams and an index, then it's useless to me. If I can't find another way to learn the game, I won't be able to play it."

Eight things that matter most

Distilled from all 127 findings. The handbook explains each one, with sources.

01

State the goal before the rules

Readers who know the objective can attach every later rule to a purpose.

02

Never use a term before you define it

The single most-cited reader irritation across fifteen years of forum threads.

03

One concept, one word, forever

Synonyms make readers hunt for differences that don’t exist.

04

Conditions before effects

“If you roll a 5 or higher, draw a card” — skimmers skip effects whose condition isn’t met.

05

Examples resolve ambiguity, not the obvious

Illustrate the move that would otherwise become a forum thread.

06

Never hide a rule in an example

Re-readers skip examples by design. A rule placed there is invisible.

07

Put rules where a confused player will look

Organisation is a retrieval problem, not only a teaching one.

08

Blind test — and do not help them

Intervening trains testers to look at you instead of the page.

Rulebooks the community praises

Fantasy Flight Games (Marvel Champions, Arkham Horror LCG, Descent 3E)

Dual-document model

Condensed 'Learn to Play' to get started + an extensive alphabetical 'Rules Reference' with a detailed index; users report finding anything 'in seconds'.

Root (Leder Games)

Walkthrough / Learning-to-Play book

Ships a scripted walkthrough book alongside a formal rules reference; the reference explicitly tells you which book to read based on your learning style.

Arcs (Leder Games)

Tone + component descriptions + repacking diagram

Warm, honest, casual voice ('expect a long, tedious first game'); each component gets a short contextual description; even a labelled repacking guide.

+ 65 more praised and criticised rulebooks after you sign in

Questions

Does it cost anything?

No. Signing in is free and there is no paid tier. We ask you to sign in so we know who the material is reaching and which parts are useful.

What do you keep?

Your Google name, email and profile picture, your approximate country, and which pages and chapters you open. Nothing is sold or shared with advertisers.

Can I delete my account?

Yes — from the account menu, at any time. Your account and reading history are erased immediately.

Ready to read the whole thing?

Continue with Google