Set the rules for your neighborhood's clubs

By default, every petition that reaches its signature goal waits for one of your organizers to approve it. That's the right setting when your club program is new or your community is large. If you'd rather not be a bottleneck, Club settings can formalize petitions automatically the moment they hit the goal. The signature threshold still applies either way — automatic skips the review step, not the proof that people want the club. A neighborhood that wants no friction at all sets the threshold to 1.

You're emailed when a petition starts, not only when it hits its goal — it's a public page headed with your neighborhood's name from day one, so Clubs → Petitions shows every open one with a badge. Open a petition and the "Manage this petition" card tells you what a reviewer needs: who's proposing, with their address and whether it sits inside your boundary (and "verified resident" if your address-verification program has them on record); which of your terms they accepted, with the version, time, and IP — or a plain warning that you have no terms configured, so approving commits nothing in writing; and a short list of exactly what forming the club does. If something needs settling first, send the proposer a note from the same card — it's emailed under your name and their reply comes back to you. The signature audit below the card marks each signer inside or outside the boundary and flags the proposer's own row.

Club policies are the documents your clubs are held to: terms for starting one, a liability waiver, a code of conduct, or a handbook they can refer back to. You write them yourself, in your own words. Each one carries a title, the text, and — the important part — when it's shown.

Three choices. "When starting a club" puts it on the petition form, so a neighbor agrees before proposing anything. "Before managing the club" holds a club's organizers at an agreement screen the first time they open the club's manage area — however that club got there, and including whoever takes it on next year. "Reference only" asks nothing; it just appears in the club's Handbook.

Their name, the date and time, their IP address, and a frozen copy of the wording exactly as it read at that moment. That last part is the one that matters: if you revise the policy later, the copy attached to their acceptance never changes, so what they agreed to stays provable. By default a revision asks everyone to accept again; turn that off per policy for typo fixes and formatting.

Whatever you put in the welcome message rides along with the email someone receives when their club is approved, or when an existing club's affiliation is accepted. House rules, who to ask, a link to your own handbook — links work. It's the first thing a brand-new organizer reads.

Your Clubs list flags any club where not one organizer has accepted your agreements yet. Those clubs are already held at the agreement screen — they can't manage anything until someone accepts — so the flag tells you who's stalled, not who's ignoring you. The per-person detail is on each club's own Handbook page.

If a club won't meet the terms, you can end its affiliation from the club's Neighborhood page — you'll see the control there because you're one of your neighborhood's organizers. A reason is required, and the club's organizers are emailed it. The club itself survives: same members, same events, same history, now independent. It loses your boundary, locations, facilities, and photo gallery, and starts carrying its own plan.