Some links in this article are affiliate links. If you buy through them, The Ludarium may earn a small commission at no extra cost to you. As an Amazon Associate, The Ludarium earns from qualifying purchases. How affiliate links work here.
If you want to know how to write a board game rulebook, start with one fact: almost nobody reads it the way you wrote it. One person at the table reads it under pressure while four others wait, then tries to teach from memory. A rulebook is a teaching script for a nervous volunteer. Write it for that person and it will work for everyone else.
This article covers the structure that works, the order to put things in, the mistakes that cause most table arguments, and how to test a rulebook before it costs you a game night.
Who is a rulebook really for?
There are three readers, and they want different things.
The teacher reads the whole thing once, often the night before, and needs to build a mental model of the game fast.
The referee opens it mid-game to answer one question and needs to find that answer in under thirty seconds.
The returning player has not played in six months and needs a two-minute refresher.
A rulebook that serves only the first reader is a textbook. One that serves only the second is a glossary. Good rulebooks serve all three, usually by being a clear linear teach with a strong index and a one-page summary at the back.
What order should a rulebook follow?
The order most publishers converge on is the order in which a new player needs information.
- Overview. Two or three sentences: what you are, what you are trying to do, how you win. Written before setup, because setup makes no sense until you know the goal.
- Components. A labeled photo or list. Players use this to check the box and to learn the names you will use later.
- Setup. A numbered list with a diagram. Every item in the components list should appear here.
- Turn structure. The core loop. What a turn is, what the phases are, who goes next.
- Actions in detail. One heading per action, each with an example.
- Special rules and exceptions. Only after the core is solid.
- Game end and scoring. Exactly when it ends and exactly how to count.
- Reference. Icon glossary, card clarifications, index, and a one-page summary.
Wingspan’s rulebook is a good model. It opens with the goal, walks through the four actions one at a time with a worked example for each, and puts card-specific clarifications in a separate appendix so they never interrupt the teach. Pandemic does the same with its roles and events.
How do you write a rule so it cannot be misread?
Most rules disputes come from three sources: an undefined term, an ambiguous pronoun, and an unstated default. Each has a fix.
Define terms once and use them exactly. If a card is “discarded” in one place and “removed” in another, players will assume the two words mean different things. Sometimes they do. If they do not, pick one. Keep a glossary as you write and check every term against it.
Kill the pronouns. “If a player attacks another player, they lose a card” is unreadable. Who is “they”? Write “the attacked player loses a card.” It is clumsier and clearer, and clarity wins.
State the default. Can you take the same action twice in a turn? Can you pass? Can a space hold two pieces? Players will guess, and different players will guess differently. Every “can I” question that comes up in testing is a missing sentence.
A simple test: read each rule and ask whether a hostile lawyer could find a second meaning. If so, rewrite.
If this is useful, the newsletter sends more like it.
How many examples do you need?
More than you think. A rule describes a category. An example shows a case, and most people learn from cases.
Every action that involves a choice or a calculation should have a worked example, ideally with a picture. “Anna plays a Fisherman. She takes two fish from the supply and places one on each of her two adjacent boats” tells the reader more than three sentences of abstract rules.
Use the same imaginary players throughout. Give them distinct names that start with different letters. Anna, Ben, and Carla are easy to follow. Player 1 and Player 2 are not.
Examples also catch your own errors. If you cannot write a clean example for a rule, the rule is probably not clean either.
What goes in the reference sheet?
A one-page summary is the most-used page in the box. It should contain:
- The turn sequence, in order, in one short list.
- Every action in one line each.
- Scoring, including end-of-game bonuses.
- The icon glossary.
Ganz Schön Clever fits its entire scoring summary onto the score sheet itself, which is why it is so easy to return to. Azul’s summary fits on the back of the rulebook. Both are models of how little space a reference needs when it is well made.
For games with many cards, a separate card-clarification appendix is worth the page count. Keep it alphabetical and keep it out of the main teach.
How do you handle the layout?
Layout is not decoration. It is how the referee finds things.
| Choice | Do | Avoid |
|---|---|---|
| Headings | One clear heading per concept, phrased as the question a player would ask | Clever titles that hide what the section covers |
| Paragraphs | Three sentences or fewer | Dense blocks of rules text |
| Emphasis | Bold for defined terms on first use and for the key word in a rule | Bold everywhere, which means bold nowhere |
| Diagrams | Setup and one example per complex action | Pictures that illustrate theme but teach nothing |
| Sidebars | Theme, designer notes, strategy tips | Rules that only appear in a sidebar |
| Index | Every defined term with a page number | Relying on the table of contents alone |
The last row matters more than it looks. A referee with a mid-game question thinks of a word, not a chapter. If “tiebreaker” is not in the index, the game stops while someone scans every page.
How do you test a rulebook?
The rulebook is a component. Test it like one. The method is called blind playtesting, and it is the single most valuable thing you can do before showing a game to a publisher or a Kickstarter audience. Our guide to playtesting a board game covers the broader process; here is the rulebook-specific version.
- Give the prototype and the rulebook to a group who has never seen the game. Leave the room, or sit silently in a corner and say nothing.
- Watch where they stop reading and start flipping. Those are the pages that fail.
- Note every question they ask each other. Each one is a missing or unclear rule.
- Ask them afterward to explain the game back to you. The gaps in their explanation are the gaps in your text.
- Rewrite, then repeat with a fresh group.
Three or four rounds of this will transform a rulebook. If you cannot find fresh groups, a lounge with a regular open-play crowd is the best source there is.
What mistakes do new designers make?
A short list of the ones that show up in nearly every first draft.
- Explaining setup before explaining the goal.
- Writing the rulebook in the order the designer thinks about the game rather than the order a player needs to learn it.
- Hiding a critical rule inside a long paragraph about something else.
- Putting a rule only on a card, or only in the rulebook, instead of both.
- Writing “simply” or “just” before a rule, which signals that the writer knows it is not simple.
- Skipping the end-game trigger, so nobody knows when to stop.
- Trying to be funny. A little warmth is fine. Jokes that obscure rules are not.
One more: writing the rulebook last. Write a draft early and update it with every change. It will show you where the design itself is unclear, which is more useful than any amount of clever wording later. A rulebook is also the first thing a publisher reads, so it is worth getting right before you pitch the game.
Why does a clear rulebook matter beyond the game?
A bad rulebook does not just slow a game down. It changes who gets to play. The friend who is comfortable reading dense text becomes the gatekeeper, and everyone else waits to be taught. A good rulebook hands the game to whoever picks it up, which means more people can host, teach, and bring new players in.
That is the real reason to care. A rulebook is the handshake between the designer and a table of strangers. The game is the reason. The people are the point.
FAQ
How long should a board game rulebook be?
As short as it can be while being complete. Many excellent games fit in four to eight pages; heavier games run twelve to twenty with a separate reference.
What is blind playtesting?
A test where players learn the game only from the rulebook, with the designer silent or absent. It reveals which rules are unclear in the text rather than in the designer’s head.
Should the rulebook include strategy tips?
A few, in a clearly separated sidebar. They help new players make sensible first moves, but they should never be mixed into the rules themselves.
Do I need a professional editor for my rulebook?
For a published game, yes. For a prototype, several rounds of blind testing with careful notes will get you most of the way there.
Test it on strangers
A table of people who have never seen your game will tell you more in an hour than a week of rewriting. The Ludarium plans open playtest nights for designers once its Indianapolis lounge opens. For more on design, hosting, and play, subscribe to the newsletter. New articles, sent to subscribers before it goes live.
Get the next one in your inbox.
Board game picks, strategy, and shelf advice from The Ludarium.