How to turn a handbook into a living rulebook
A handbook goes stale because nobody is asked whether a page is still true. A rulebook fixes that by giving every rule an owner and a date.
Most teams have a handbook, and most people on those teams ask a colleague instead of opening it. Often that is sensible: they cannot tell whether the page is current, who decided it or whether it was ever followed.
The steps below are an editorial method for turning the rules inside a handbook into a short list that stays accurate. They suggest a way of organizing the work; they do not promise that people will follow every rule, and long procedures still belong in the handbook.
- 1Pull out the rules
Which sentences tell someone what they must or may do, with a number or a limit in them?
- 2Name an owner
Who decides when the rule is unclear, and who is asked whether it still holds?
- 3Record why and when
What was decided, on what date, for what reason, replacing what?
- 4Check on a date
When will the owner confirm, replace or retire it?
Separate the rules from the explanation.
Google's team research lists structure and clarity among the dynamics it associated with effective teams, including understanding expectations. A rule is one of the most direct ways to state an expectation, but in a handbook it is usually buried inside a paragraph of background. [1]
Read through the handbook and copy out each sentence that says what someone must do, may do or may not do: an approval limit, a deadline, a refund threshold. Leave the explanations where they are. Start with the five questions people ask most often, rather than trying to convert the whole document at once.
Give each area one owner.
Atlassian's DACI definitions name a single Approver for a decision, and its responsibilities exercise is designed to expose work that has no owner or two. Apply the same idea to rules: group them by area, such as purchasing or safety, and name one person for each. [3][2]
The owner is the person who decides when the rule is unclear or missing, and who is asked later whether it still holds. If nobody can own an area, treat that as the finding. A rule with no owner will be reinterpreted by whoever happens to be asked.
Record when, why and what it replaced.
For each rule, write the date it took effect, the reason in a sentence and the earlier rule it replaced. When the rule changes, add the new one and mark the old one replaced, instead of editing it in place. The history is the part a handbook usually loses.
Keep the source too: the email, meeting or document where the decision was made. When two rules turn out to contradict each other, the dates and sources are what let you decide which one stands.
Put a check date on every rule.
Choose a date by which each owner should confirm the rule still holds. Use a shorter interval for rules about money or safety and a longer one for low-risk habits. On the date, the owner confirms, replaces or retires the rule.
Expect to retire some rules. A rulebook that only grows has the same problem as the handbook. Treat a rule that nobody can explain, or that people routinely work around, as a candidate for replacement rather than for more enforcement.
Put it into practice.
Pick one area where people ask the same question repeatedly. Write its three or four rules with an owner, a date and a reason, and agree a check date for each. Share the list with the people it affects, and revisit it when the date arrives or the work changes.
The boxes are a reading aid and are not saved. Download the worksheet to keep your notes.
Download the practical worksheetSources & reading
External sources support the factual background. The prompts and next steps are editorial recommendations, not promises of a particular result.
- 1Understand team effectiveness
Google re:Work. Google's internal team research and guidance on clarity, dependability and meeting agendas. Organizational context, not a universal causal estimate.
- 2Roles and Responsibilities
Atlassian Team Playbook. A facilitation method for finding overlaps and unassigned responsibilities, then agreeing ownership. No performance-uplift claim is used.
- 3DACI Decision-Making Framework
Atlassian Team Playbook. Defines Driver, Approver, Contributors and Informed. Used for role definitions only, not third-party performance statistics on the page.