Running the pool, the clubhouse, and the parking lot without a feud

The bulletin-board calendar has one copy, no rules, and no record of who wrote on it. Every association has a story about two families who both booked the clubhouse for the same Saturday.

Amenity Reservations lets the board define each amenity and the rules that go with it: the booking window, how often one household may use it, and whether a reservation needs approval. Residents book from their phone and see what is already taken.

The per-household usage limit is the setting that prevents the complaint boards actually receive, which is not double-booking but monopolisation. One family books the pavilion every Saturday in June because they were quickest, and by July the board is being asked to write a rule. Set the limit before the season rather than in response to it, because a limit introduced afterwards reads as being aimed at someone, and it usually is.

Approval is worth thinking about separately per amenity. Requiring it for the clubhouse is reasonable, since a party has consequences. Requiring it for a tennis court turns a volunteer into a scheduling clerk for no gain. The rule of thumb: require approval only where the board would ever plausibly say no.

Nothing in an association is as emotionally loaded as a parking space, and nothing is as badly served by a paper list in a binder.

Vehicle & Parking Registry has residents register their own vehicles with make, model, colour, plate, and permit number. Leadership sees the registry with status filters and a grid of assigned, visitor, and unassigned spots, can flag a non-compliant vehicle, and can issue a matching violation in Violation Tracking that links back to the vehicle. Each vehicle keeps an activity log.

Self-registration is the part that makes this survivable. A registry maintained by the board is out of date within a season, because cars change and nobody tells anyone. A registry each resident maintains is as current as their interest in not being towed, which turns out to be quite current.

Guest Parking handles the scarce resource underneath it. The board sets how many guest passes exist each night, residents claim one when they have a visitor, release it when plans change, and each resident holds at most one pass per night. Capacity is enforced on the server, so two residents cannot take the last pass simultaneously even if they tap at the same moment.

That atomic-claim detail sounds like an implementation note and is actually the governance point. The most corrosive parking dispute is not about the rule. It is two people who each believe they claimed the last space, with no way to establish who did. A system where the claim either succeeded or did not, visibly, ends that argument before it starts.

Half of all amenity complaints are really complaints about not knowing. The rule was in the CC&Rs, adopted four boards ago, and the resident has never opened them.

1. Put the rule on the amenity, not only in the governing documents. The booking window and the usage limit should be visible at the moment someone books.
2. Announce a change before it takes effect, with a date. Announcements posts with admin approval, an expiry date, notifications to the audience you choose, and group targeting when something concerns one section rather than everyone.
3. Say what the rule is for. "Two passes per household so there is room for the Saturday market" is followed more often than a bare limit, because people comply with reasons and resent decrees.
4. Enforce the same way every time, starting with the first instance. Selective enforcement is how a parking rule becomes a lawsuit.
5. Review the limits once a year against actual usage rather than against complaints. The complaints tell you who is loud, and the usage data tells you what is scarce.

The pool light is out. The clubhouse door sticks. In most associations this is reported to whichever board member the resident runs into at the mailboxes, which means it is reported several times or not at all, and nobody can tell which.

Maintenance Requests takes the report from the member, lets leadership triage, assign, and resolve it, and shows the reporter the status through to resolution.

Visible status is doing more work here than it appears. The reason residents re-report an issue, or escalate it to a complaint, is almost never impatience with the repair. It is not knowing whether anyone heard. A request that visibly says acknowledged and assigned buys a board weeks of goodwill on exactly the same repair timeline.

Pair it with your vendor list so a request that needs a contractor starts from people the community has already used rather than from three names off a search.

Two smaller pieces complete the facilities picture, and both prevent a specific recurring annoyance.

Equipment Checkout is an inventory of what the organization owns, who has each item checked out, when it is due back, and the full lending history per item, recorded by leaders and viewable by everyone. Tables, the projector, the pop-up canopy, the pressure washer. The lending history is what answers the question that otherwise cannot be answered, which is who had it last and what state it came back in.

Shift Scheduler covers duties rather than things: recurring duties defined by leadership, assigned on a weekly grid or generated as a rotation, with each member seeing their own upcoming shifts. Pool monitors, gate duty, the front desk at a co-op. It is deliberately not a chore system with points, and for a volunteer roster that is the right shape.

Occasionally an association needs to take bookings from people who are not members and never will be. A contractor walk-through, a community sale, parent-teacher style slots at a school-adjacent club.

Booking Slots publishes a set of times, you share one link, and people book a slot with their name. No account, no app, nothing to install. That last property is the whole point, because any system that asks an outside visitor to register will simply not be used, and you will be back to a phone tree.

Within a season, the board stops adjudicating. The pavilion has a visible calendar with a limit that applies to everyone. Guest passes run out in a way both neighbours can see. The registry says which car belongs to whom without anyone knocking on a door. Maintenance reports get a status instead of a second email.

And the thing that matters for the volunteers: enforcement stops being a person. The difference between "the system shows no pass was claimed for Tuesday" and "I noticed your visitor's car" is the difference between a rule and a confrontation, and it is the reason board members resign.

• Amenity Reservations
• Guest Parking Passes
• Vehicle & Parking Registry
• Maintenance Requests
• Equipment Checkout
• Shift Scheduler
• Booking Slots
• Announcements

Every app in the library is included with the household plan. Install the ones this guide uses and skip the rest.

• Self-managed HOA software compared, by what each is for
• Running an HOA architectural review process homeowners trust
• Collecting HOA dues without chasing people every quarter