The same three units win the party room because your booking system rewards speed, not need. Amenity booking fairness comes from rules: caps per resident, sane notice windows, a lottery for the scarce dates, and enforcement that applies to everyone. URBI holds each of those as a setting.
Why do the same three units get the party room every weekend?
Because a plain first come first served calendar is a race, and the same people keep winning it.
Nothing there breaks the rules. The resident who books at one minute past midnight is following the policy exactly. The policy is what is broken. It measures who was awake and calls that need.
Owners have a real claim here. Florida's condominium statute says common elements and recreational facilities "shall be available to unit owners ... for the use intended", and in the next sentence allows the association to adopt reasonable rules about that use, per section 718.123 of the Florida Statutes. Access belongs to every owner. Rules exist to make it real instead of theoretical.
Reasonable is the load bearing word, and courts have put content in it. The Virginia Supreme Court held in 1982, in Unit Owners Association v. Gillman, that condominium rules are measured by a standard of reasonableness, and that an association may not impose "arbitrary and capricious rules ... bearing no relation to the purposes of the condominium", per the reported opinion. So write down the scarcity problem a rule solves before adopting it.
Forty units and twelve good Saturdays is a rationing problem, and rationing problems need a rule. If the building will not choose one, the calendar chooses for it, and the calendar picks the fastest fingers.
Which rationing mechanism should you actually use?
Pick by what the amenity is short of: time, capacity, or specific peak dates.
Most buildings reach for caps because caps are easy to explain. Often right. But a gym is short of capacity, not calendar time, and a rooftop on the Fourth of July is short of exactly one date.
| Mechanism | Good at | Fails at | Best suited to |
|---|---|---|---|
| Cap on active bookings per resident | Stopping one household holding six future dates at once | Anything about which dates they hold | Party rooms, guest suites, BBQ areas |
| Cap on bookings per period | Spreading access across the roster over a month or quarter | Households with legitimate high frequency needs, such as a caregiver | Party rooms, theaters, work pods |
| Maximum continuous booking length | Breaking up all day blocks that lock others out | Genuine all day uses, a wedding party or a move | Courts, pools, sauna, work pods, elevators |
| Booking notice window | Preventing a wall of bookings a year out and giving staff lead time | Fairness, on its own. A window is still a race | Every amenity that needs staff setup |
| Lottery or rotation for peak dates | The handful of dates everyone wants at once | Ordinary weeks. Heavy for low demand slots | Long weekends, holidays, hot Saturdays at the pool |
| Blackouts and maintenance closures | Protecting building events, deep cleans, and repairs | Resident to resident fairness. It rations nobody | Every amenity, on a maintenance calendar |
| Peak surcharge | Reducing casual demand and funding wear on the space | Fairness across incomes. It sells the scarce date | Rarely. Only alongside a lottery or cap |
| Capacity and occupancy caps | Sharing one space among many people at once | Exclusive use spaces only one group can occupy | Gyms, pools, coworking, lounges, saunas |
| Manager confirmation | Catching the bad request before it becomes a dispute | Speed and staff time. Every request becomes a task | Party rooms, guest suites, moves, elevators |
Most buildings need two or three of these, not all nine. Stacking every mechanism on every amenity produces a policy nobody reads and staff quietly stop applying.
Do booking caps work, and where are they blunt?
Caps work, and they are the first thing to try, because they change the behavior residents are actually angry about.
Three caps do most of the work:
- Maximum active bookings per resident. How many future bookings one person may hold at once. This stops a household claiming the next six months of Saturdays in one sitting.
- Booking limit per period. How many times a resident may book in a month or a quarter. Residents expect this one and rarely find it.
- Maximum continuous booking length. A four hour ceiling on the party room turns one Saturday into two available slots.
In URBI those are three separate amenity fields. Set them per amenity, because the right cap for the guest suite is not the right cap for a squash court.
Caps are blunt at the edges, and you should say so when you adopt them. A resident whose disabled parent visits monthly hits the guest suite cap through no fault of their own. Write an exception path into the policy, and record who granted each one and why.
Does a window that opens at midnight measure need, or just who was awake?
It measures who was awake. A window opening is a starting gun, and a starting gun at midnight selects for night owls and people with the app already open.
The window is still worth having. Without one, a single resident books every long weekend for two years and staff get no lead time. URBI carries a booking notice hours setting per amenity, plus opening hours and a 24 hour flag for spaces that never close. Put the AGM, the holiday party, and the annual deep clean on the amenity calendar before the window opens, because a closure applied after residents book costs you apologies.
What you can fix is the race at the moment the window opens:
- Open the window during the day. Nine in the morning is still a race, but it is a race a normal person can enter.
- Shorten the horizon. Four weeks out instead of twelve months puts far fewer dates in play, so a fast booker captures less of the year.
- Take the peak dates out of the race. That is what a lottery is for, and it is the only option that stops rewarding speed.
Federal recreation agencies solved this one in public. Yosemite National Park releases sixty percent of wilderness permit reservations by lottery twenty four weeks ahead, and the remaining forty percent first come first served seven days ahead, according to the National Park Service. The lottery application period runs a full week, so entering at midnight buys you nothing. That is the design lesson worth stealing.
When is a lottery worth the administrative weight?
When demand for a specific date is several times the supply and the date matters to people, which in most buildings is a short list.
Three requests for New Year's Eve and one for a Tuesday in March means one contested date, not a broken system. A lottery for that date takes five minutes. A lottery for all fifty two weekends is a staff burden that gets abandoned within a year. If the real dispute is noise and damage rather than access, the answer is how you handle party room deposits, not a draw.
Signs a lottery is earning its keep:
- The same dates are contested every year and residents can name them.
- More than a handful of units want the same slot, so a cap alone cannot separate them.
Being straight about the product: URBI does not run the draw, and there is no lottery engine. What it does is make the draw enforceable afterwards. You draw the winners and enter the bookings, and each carries a permanent record of who booked what and when. The board keeps the rota. The platform keeps the proof.
Is this bureaucracy for a problem most buildings do not have?
For a lot of buildings, yes, and the honest move is to measure before you ration.
Rationing costs something. Every cap is a rule someone explains, a setting someone maintains, and a refusal someone delivers at the front desk. A quiet gym gives nothing back for that. The strongest case against this whole post is that a building with a real monopolization problem has a neighbor problem, and no setting fixes a neighbor.
Two concessions, both real:
- Nobody can tell you what normal looks like. We went looking for a benchmark and came up empty. No public national data on amenity utilization, booking complaint rates, or no show rates in US buildings turned up. The large datasets measure what residents say they want, not what they book. A board adopting caps because the building down the road did is guessing.
- A conversation beats a rule when the numbers are small. If one household books the room monthly and nobody else asks for it, that is not monopolization. That is the only household using the amenity.
So run the count first. Per amenity, over one quarter: how many separate households booked it, what share of booked hours the busiest tenth held, how many requests failed because the slot was taken, and how many ended in a no show. If the busiest tenth holds a modest share and nothing gets refused, close the file.
Where the numbers do show a problem, the proportionate move is a rule with an end date. California's rule change statute is a good model even outside California. A board there notifies members at least 28 days before an ordinary operating rule change, tells them within 15 days once it is adopted, and may run an emergency rule for 120 days, under section 4360 of the California Civil Code. Borrow the shape. Adopt the cap for one season, publish the numbers, and make the board vote again on the evidence.
Is a peak surcharge fair rationing, or selling access to the highest earner?
It is both, and any building considering one should say the second part out loud before it votes.
The case for it is real. A busy Saturday costs the building more than a quiet Tuesday: more cleaning, more wear, more staff attention. A surcharge tied to a cost the amenity genuinely incurs is defensible, and it is the version most likely to survive the reasonableness test.
Now the part boards skip. A surcharge does not ration by need. It rations by ability to pay. Where owners, tenants, and dependents share one amenity, a peak price hands the good dates to the wealthier households and everyone else gets Tuesday. That is a legitimate choice. It is also a choice about who the amenity is for, and it should be argued in those terms.
A workable middle path: allocate the contested dates by lottery or cap, and price only to recover cleaning and setup costs. URBI supports per occupant type rules on each amenity deciding whether Owner, Resident, Tenant, Dependent, or Property Manager may book it and whether a surcharge applies, applied automatically. That makes the policy consistent. It does not make it wise.
How do capacity caps ration differently from time caps?
Capacity caps share a space among many people at once. Time caps hand the space to one group and lock everyone else out.
That decides which setting you need. A gym with fifteen machines does not need a booking limit per resident. It needs a ceiling on how many people are in the room at once. A party room needs the opposite.
URBI splits these into different fields. Max occupancy is how many people the space holds. Max colliding bookings is how many bookings may overlap in the same window, which is the real capacity control for shared spaces. Booking types cover the rest: DROP_IN, RESERVE, or BOTH, where some capacity is reservable and some stays open.
A check in flag and a QR code close the loop on no shows. A resident who books the court weekly and shows up twice a month consumes the same scarce slots as a monopolist. Check in data lets you say so with evidence instead of suspicion.
Which amenities deserve manager confirmation, and which should book themselves?
Confirmation belongs on amenities where a bad booking is expensive to unwind. Everything else should confirm itself instantly.
Confirmation costs real time, and it is where discretion creeps back in. Each request becomes a task, a slow queue trains residents to book by text, and every judgment call is one more decision a resident can dispute.
- Confirmation on: party rooms, guest suites, moving elevators, roof terraces, anything with a deposit, a waiver, or a contractor.
- Confirmation off: gyms, courts, work pods, laundry, saunas, bike rooms, and most equipment loans.
URBI carries a confirmation required toggle per amenity, plus a slot versus free schedule toggle. Fixed slots are the better default for anything contested, because free scheduling lets one booking straddle two slots and waste half of each. Moves are covered in elevator booking for condos, and waiver gated bookings in how amenity waivers work.
Demand moves, so revisit which amenities need which treatment. The 2024 NMHC and Grace Hill Renter Preferences Survey, drawing on 172,703 renters across 4,220 communities, found interest in shared workspaces rising from 35 percent in the prior survey to 48 percent, per NMHC. The amenity your rules were written for may not be the one that is scarce now.
Why do most amenity rules die at enforcement?
Because a rule nobody enforces teaches residents that none of the rules are real.
This is the failure mode. The board adopts a two bookings per month cap. Three months later a resident has four. Staff decide it is not worth the argument. The next resident told no has a fair question, and the board has no good answer.
The professional guidance is blunt. The Community Associations Institute's public policy on rules development and enforcement asks that violations be "enforced in a consistent, uniform manner using common sense", per the CAI public policy.
The legal exposure is worse than the political exposure. Selective enforcement is a recognized defense for an owner facing a rule the association ignored for everyone else. Carol Lang of the community association firm Marcus, Errico, Emmer and Brooks walks through White Egret Condominium v. Frank in a firm newsletter, where a Florida court found the association estopped from enforcing a restriction it had applied unevenly.
That defense is narrower than boards fear, and the narrowness cuts against booking caps. Jeffrey Rembaum, a Florida attorney board certified in condominium and planned development law, writes that it applies only where "the violation or circumstances are comparable", in his association roundup. Letting a bike room infraction slide does not cost you the party room cap. Letting one household hold six dates while telling the next household two is the limit is exactly the comparable case. A booking cap is the worst rule to enforce unevenly, because every breach looks like every other one.
The fix is not sterner emails. It is automatic application. A cap the booking system refuses to exceed never needs enforcing, because the violation cannot happen. That is the argument for putting caps in software rather than a policy binder, and most of what separates a real system from a shared calendar.
Can your board prove the rules were applied evenly?
Only if every booking left a record, which is the question almost no amenity policy anticipates.
Here is the accusation that ends careers on volunteer boards. A resident stands up at the AGM and says the board member in 1802 has the party room every month. Sometimes it is true. More often it is one coincidence and a lot of assumption. Without the record the board loses the room either way.
What the record has to show:
- Who booked which amenity, on which date, and when the booking was made.
- Every cancellation and every change, with who made it.
- Every exception granted, who granted it, and the stated reason.
- Every closure and every refund tied to it.
In URBI every booking writes to a permanent log, and the booking edit drawer holds the transaction history, payment logs, and deposit status. Closing an amenity for maintenance auto detects the bookings inside the closure window, so the manager resolves or refunds each one in a single flow and the refund lands in the record. A board can produce the twelve month history for one amenity and let the numbers answer the accusation.
Fairness also needs the rules and the money to be separable. Whoever allocates a scarce date has no business knowing the payment history of the households competing for it. URBI permissions can restrict who sees the accounting side of a booking, so a concierge or a board member administers bookings, closures, and exceptions without seeing the financials. The allocation record stays open to anyone checking whether the rule was applied evenly.
Two habits make the record useful. Publish a plain summary of amenity usage to owners once a year. And apply the cap to board members with no exceptions, because a board member who books the room monthly is the fastest way for a building to lose it. For the wider picture, start with what URBI is and how it works in residential buildings.
Frequently asked questions
What is a reasonable cap on party room bookings per unit?
Most buildings land on one active booking at a time plus one or two per month, then adjust after a season of real data. Start looser than you think you need. Tightening a cap after residents see the usage numbers is easier than loosening one after you have told people no.
Can a condo board charge more for peak amenity slots?
Usually yes, subject to your governing documents and state law, but ask whether you should. A peak price rations by ability to pay, so the scarce dates go to the households with the most money. If fairness is the goal, allocate by cap or lottery and price only to recover real cleaning and setup costs.
How do you stop no shows from wasting scarce slots?
Require check in and measure it. A resident who books the court weekly and appears twice a month consumes the same slots as anyone else. URBI supports a check in flag and a QR code per amenity, so attendance is recorded. Then enforce a no show rule, or attach a deposit, covered in amenity booking deposits and tenant experience.
Do these rules need to be in the bylaws?
Usually not. In most states a board can adopt reasonable rules about the use of common elements without a bylaw amendment, but the process comes from your state's condominium act and your governing documents. California, for one, sets a notice period before an operating rule change and a deadline to tell members after. Ask your association counsel, then publish the rule before it takes effect.
Amenity fairness is not a software problem with a software answer. It is a policy the board chooses and then actually applies. The software's job is to apply it the same way every time and keep the receipts. For a straight answer about what amenity booking software can and cannot fix, email hello@myurbi.co with your current rules in front of you.
