Writing a club constitution nobody actually has to read to follow

A club founded in 2019 has a Google Doc titled 'Club Constitution,' last edited three years ago. It lists a dues amount nobody currently charges, names two approved run leaders who moved away in 2022, and describes a cancellation policy that the current organizers have never once followed, because they didn't know it existed.

A constitution nobody re-reads isn't governance, it's an artifact

This is the normal state of a club document, not a failure of any particular club. Bylaws get written once, during the founding burst of energy when everything feels like it needs formalizing, and then nobody opens the document again until something goes wrong — a dues dispute, an injury on a group run, a founder stepping back — at which point it turns out the written policy and the lived practice diverged years ago and nobody updated either one.

The useful version is settings, not sentences

Making the document longer or more thorough doesn't fix this — it just makes the drift more expensive to find later. The actual fix is moving the policies that matter out of prose and into the system members interact with every week, so the policy and the practice are the same thing by construction. Dues aren't a paragraph, they're an amount that actually charges. Run leaders aren't a name list from 2022, they're a role assigned in the system to whoever is currently doing the job.

• Dues amount and who's exempt — as an actual billing setting, not a sentence describing what dues "should" be.
• Who's an approved run leader right now — a role assigned in the system, not a name list nobody's updated since the person moved away.
• The weather cancellation threshold and who's authorized to call it — so it's a real notification trigger, not a judgment call reinvented every storm.
• What happens to a member's access if dues lapse — an automatic, consistent rule instead of an awkward one-off conversation.

Succession is a settings problem too

The scenario a written constitution is supposedly there for — the founder stepping back — is exactly where a document fails hardest, because whoever takes over has to first figure out what's still true. Admin roles that live in the system transfer cleanly: the new organizer can see, immediately, who's a run leader, what dues are set at, and what the actual cancellation policy is, because those are live settings rather than someone's memory of a Google Doc.

The best club constitution is the one members never have to open, because the system already enforces it.

That's a five-step setup, not a rewrite project — the settings that matter get defined once, at onboarding, and then they're just how the club runs.