Amenity and clubhouse booking software
A shared calendar residents book against, rules that enforce themselves, and utilisation data that tells a committee which amenities are worth what they cost.
Amenity booking software lets residents reserve clubhouses, courts and halls in conflict-free slots, pay booking charges and deposits online, and works to per-flat quotas set by the committee. No-show penalties and utilisation reports come from the same booking record.
Fair access to the clubhouse, minus the register
Amenity booking runs on a diary in the office and a phone call to the manager in most societies. The diary is only accessible during office hours, only one person can see it at a time, and double bookings are discovered when two families arrive for the same hall on the same evening.
The deeper problem is fairness. Without a record, the residents who book most are the ones who know the manager, and the perception that the clubhouse belongs to a particular set of families is corrosive out of proportion to the amounts involved. Committees hear about it at every AGM.
A booking system with visible rules solves the fairness question more than the convenience one. When everybody can see the calendar, the quota and the rule that allocated a contested slot, the argument stops being about favouritism.
- Paper diaries are single-access. One person, office hours, and no way to check availability before asking.
- Double bookings surface late. Usually on the evening of the event, in front of guests.
- Opaque allocation reads as favouritism. And that perception costs a committee more goodwill than the amenity is worth.
Key capabilities
A calendar, money, rules, and the two mechanisms that stop a booking system being gamed.
Slot-based online booking
Each amenity is defined with its bookable slots — a badminton court in hourly slots, a party hall in half-day blocks, a guest room by the night — and residents book from the app against a live calendar.
Booking windows are configurable: how far ahead a slot opens, and how late it can be cancelled without penalty. Both settings do real work. A hall that opens twelve months ahead gets blocked speculatively by a handful of families; one that opens sixty days ahead does not.
Paid bookings and refundable deposits
Charges are collected at booking through the same gateway as maintenance, with the receipt issued immediately. Refundable damage deposits are held as a liability and released or adjusted after the post-event check.
Handling deposits properly is where paper systems fail most visibly. A deposit taken in cash and refunded months later, with no record of either, is a recurring source of both disputes and audit observations.
Usage rules and per-flat quotas
Quotas cap how much any one flat can book in a period — four court hours a week, one hall booking a quarter — which is the mechanism that actually distributes access. Rules can differ by amenity and by day, so peak weekend slots can carry a tighter quota than weekday mornings.
Rules are visible to residents in the app. A resident who can see the quota and see that it applies to everyone accepts a refused booking; one who is simply told no does not.
Conflict-free shared calendar
One calendar per amenity, visible to every resident, with committee bookings and maintenance closures on it as well. A court closed for resurfacing shows as closed rather than being discovered by a resident who has arrived with a racquet.
Because the calendar is the booking, double bookings are structurally impossible rather than merely unlikely.
No-show penalties
A booked slot that is not used is worse than an unbooked one, because it blocked somebody else. Bookings can require check-in, and repeated no-shows attract a penalty or a temporary restriction according to what the general body has resolved.
This matters most for high-demand slots. Without it, a weekend court hour gets block-booked by families who may or may not turn up, and the residents who would have used it stop trying.
Utilization reports
Bookings, hours used, revenue and no-show rates per amenity. This answers the question committees genuinely need answered: whether the amenity justifies its running cost, and which ones to invest in.
The results are frequently uncomfortable. A clubhouse that costs a substantial share of the maintenance budget and is booked eleven times a quarter is a conversation the general body should be having with numbers in front of it.
How it works
The rules do the refusing, which is the part committees would rather not do personally.
Who it helps
A small module that removes a disproportionate share of the interpersonal friction in a committee’s week.
Works with the rest of KeyMatrix
A booking is a small financial transaction attached to a flat, so it runs through the same billing and ledger path as everything else: charges collected at booking with a receipt in the same series, deposits carried as liabilities until released, penalties appearing on the next maintenance bill where the general body has resolved them.
The operational edges connect too. A hall booking notifies the gate so the guest list is expected rather than a surprise at eight in the evening. Damage found at the post-event check becomes a work order and, where warranted, a deduction from the deposit with the inspection evidence attached.
- Online payments. Booking charges and deposits use the same gateway and receipt series.
- Accounting. Deposits are held as liabilities and released or adjusted on the record.
- Visitor management. Event bookings pre-notify the gate about expected guests.
- Work orders. Post-event damage becomes a job, with evidence attached to any deduction.