How long should a rule book be?

As long as it needs to be to settle disputes, and no longer. Most competition rule books run between 20 and 80 pages. If a section is never referred to in a protest or a question, consider moving it to guidance.

Should rules be numbered?

Yes. Numbers let officials, players and appeal panels point to exactly one rule. Use a consistent hierarchy such as 1, 1.1 and 1.1.1 and never reuse a number within the same version.

Who should review a rule book?

The people who apply it. Judges, referees, team captains and the disciplinary committee will find ambiguities that the authors miss.

How to write a rule book people can actually use

A practical structure for sports and club rule books, from the first section to the appendix, with the numbering, wording and review habits that stop disputes before they start.

A rule book has one job: when two people disagree, it tells them who is right. Everything about how you write it should serve that moment, which usually comes on a cold Saturday, with a protest form in someone's hand and a time limit running.

Start with the questions, not the chapters

Before you write anything, list the disputes your competition actually has. Ask your officials and your disciplinary committee what came up last season. Typical answers:

Who is eligible to play, and by when must they be registered?
What happens when a match can't be finished?
How are ties broken?
How, and how quickly, can a result be protested?

Each question needs a rule that answers it plainly. The chapters then organise themselves around them.

A structure that works for most competitions

General: who the rules apply to, and what wins when documents conflict.
Eligibility and entry: membership, registration and deadlines.
Format: rounds, draws, progression and scheduling.
Playing rules: the sport itself, or a reference to the international laws you adopt.
Officials and judging: who decides what, and which decisions are final.
Conduct and discipline: the standard expected, and the sanctions available.
Protests and appeals: who may protest, how, and within what time.
Appendices: fines tables, forms and diagrams.

Write each rule so it can only be read one way

One obligation per rule. If a rule contains "and" twice, it is probably two rules.
Use "must" and "may", never "should". "Should" invites an argument about whether something is required.
Name the decision-maker. "The Head Judge decides" settles more arguments than "it will be decided".
Put numbers in figures, with units. "Within 30 minutes of the result being announced", not "shortly after the match".
Define a term once, then use it exactly. If you define "Match Controller", don't later write "the official in charge".

Number it, and keep the numbers honest

Numbers are how people point at rules: in protests, in emails, in appeal decisions. Pick a scheme (1, 1.1, 1.1.1 is the most widely understood), and make sure every cross-reference updates when rules move. Broken references ("see 4.7", where 4.7 is now about something else) are among the most common sources of appeals.

This is where word processors let you down. Inserting a rule means renumbering everything after it by hand, and every "see rule" link in the document becomes a small trap. A structured rule book editor keeps numbers and references in step automatically.

Review it with the people who use it

Send the draft to officials and captains and ask them to comment on specific rules, not in a single long email. A comment attached to rule 5.1.02 is easy to act on. "A few thoughts on protests" is not.

Publish one version, and say what changed

Publish the rule book at a single address that always shows the current version, and keep earlier versions available for appeals about past events. With each new version, publish a list of the rules that were added, removed or reworded. Your players will read the change list even if they never read the whole book again.