A player aid should reduce a recurring interruption. It is not a miniature rulebook and does not need to answer every possible question. Start by noting what people repeatedly ask during play: when income arrives, what a symbol means, which action is optional, or how the final score is assembled. Design around the most useful answer.
Organize information by the moment of use
Put a turn sequence in the order players perform it. Use action verbs and distinguish mandatory steps from choices. If players select one action from several, show that relationship explicitly rather than presenting every action as a numbered instruction. A neat list can still teach the wrong procedure.
Separate the frequent from the exceptional. The front of an aid might contain the ordinary turn and the meaning of common icons. A reverse side can hold unusual timing cases or a scoring reminder. If a rare exception interrupts the main sequence visually, it may slow down every turn to help with a situation that happens only once.
Use the same terminology as the rules and components. Calling one resource “supplies” on a card and “materials” on the aid asks players to solve a vocabulary problem that the game does not need. Keep a small glossary in your design notes so revisions remain consistent across every surface.
Test at the actual reading distance
Print at the intended size. A layout that looks spacious on a monitor may become cramped beside a player board. Use readable type, generous line spacing, and clear contrast. Avoid long passages in capitals, decorative backgrounds behind rules, and tiny footnotes that contain essential instructions.
Keep meaning available without color. Pair resource colors with words or distinct icons, and test a grayscale print. Place the aid where the player can use it without moving a hand of cards. If a shared reference must be read upside down by half the table, consider individual copies instead.
Ask someone to complete a specific task using only the aid: “Show me what happens after you take an action.” Observe where their finger or gaze goes first. Do not explain the layout in advance. If they search the wrong area, revise the information hierarchy before adding more content.
Write scoring as a visible procedure
A score sheet is a small interface for a calculation. Label the unit being recorded, indicate whether a value is added or subtracted, and show when the entry should be made. Keep raw observations separate from calculated totals. A column called “sets” should not sometimes contain the number of sets and sometimes their point value.
For end-game categories, include a short worked example outside the writing spaces. Check the arithmetic independently with a known result, including zero values and ties if the game uses them. If penalties can produce negative totals, do not design a sheet that assumes every entry is positive.
The example below is deliberately generic: three additive rounds for up to four players. It is not an official score sheet for a published game. Its browser totals simply add the entered numbers; it does not enforce a game’s scoring rules, decide a winner, or apply a tie-break. Blank cells count as zero once any score in that row is entered.
Make a sheet that survives a pencil
Leave enough room for actual handwriting and corrections. Print a draft and ask someone else to record a whole round. If entries drift into adjacent boxes, increase writing space or reduce the number of categories on the page. Light rules can guide a pencil without turning the sheet into a dense cage.
Common paper formats differ: ISO 216 A4 is 210 × 297 mm, while US Letter is 8.5 × 11 inches. Leave generous margins and check the print preview for the paper you use. The print action on this page isolates the worksheet; your browser still controls paper size, scaling, headers, and PDF output.
Keep the reference synchronized
Give the aid a version label that matches the rules it supports. If a cost, timing window, or scoring category changes, search every reference surface for the old wording. A beautifully readable aid can cause more confusion than no aid when it confidently presents an outdated rule.
For a published game, identify the edition in your private notes and confirm the publisher’s rules before adapting a summary. BoardGameGeek can help you discover community discussions, but an uploaded aid is not automatically official or accurate. Check permissions before distributing publisher artwork or copied rule text.
After a few sessions, remove any aid element that nobody uses and investigate any question that still interrupts play. The goal is not to fill the available card. It is to make the next decision easier to understand.
Test note: when does an aid become clutter?
Cover everything except the turn sequence and run a short test. If players navigate better without the extra information, move that material to a reverse side or a separate reference. Keep exceptions available without making them compete with routine actions.