Amenity booking software versus a shared Google Calendar is a real choice, and the calendar wins more often than vendors admit. It breaks at predictable points: rules, money, waivers, and proof. URBI is built for the building that has reached them.
Most vendor pages here treat the reader as careless. A building running its party room on a shared calendar gets called chaotic. That is a sales tactic, not an argument. Plenty of buildings run bookings that way on purpose and it works.
What does a shared calendar actually get right?
More than software companies like to admit. It is free, already on every phone in the building, and needs no training for the resident and no onboarding for the manager. That is a strong starting position.
- Nobody has to learn anything. A resident who can read a week view can read the party room schedule.
- It is visible. One link shows the whole month. No login wall, no download, no password reset at nine at night.
- Permissions are simple. Google documents five sharing levels, from free and busy only up to "Make changes and manage sharing", which gives full control of events. Read only for residents and edit access for the manager covers a small building.
- It has more rules in it than critics admit. Google appointment schedules add a self serve page with a minimum lead time, buffer time, and a cap on maximum bookings per day. Eligible plans send up to five reminders and take payment through Stripe. Anyone telling you the calendar has no controls has not looked.
- It costs nothing to abandon. No contract, no data migration, no procurement conversation with a board.
Scale matters here. The Foundation for Community Association Research counted about 373,000 community associations housing 78.1 million residents in 2025, roughly 35.2 percent of United States housing. Divide one figure by the other and the average association is small. A building with one bookable room and four bookings a month has no booking problem.
If that is you, stop reading and keep the calendar. I would rather you did that than buy something you do not need.
Where does a shared calendar start to cost you?
At the moment a booking stops being a note and becomes a promise the building has to keep. The gap is not scheduling. It is that a calendar has no idea who lives here, what your rules say, whether money moved, or who signed what.
Why does every booking still have to go through a person?
Because the shared calendar itself is not self serve and cannot safely be made one. Give residents edit rights and any of them can overwrite any booking. Give them read only and every booking becomes a message to the front desk, a look at the calendar, and a manual entry. Appointment schedules are Google's fix, but Google states you cannot add appointments to a resource calendar, so the room and the booking page stay separate.
Staff time is the hidden cost. National Apartment Association staffing guidance notes that on a 300 unit property open seven days a week, the traditional one office and one maintenance employee per 100 units standard would only allow a fully staffed office three days per week. That is 2020 guidance. Onsite hours are the scarcest thing a building owns.
In URBI the resident books from the app and it is done when they tap confirm. They can also book through Arthur, the resident facing AI, by voice, text message, email, or in app chat. If the amenity has the confirmation required toggle on, the request goes to the manager instead.
What happens when the rules live only in someone's head?
They get applied unevenly, and residents notice. A calendar can hold the simpler rules. What it cannot do is tie a rule to a person or to a room. It cannot cap how many active bookings one unit holds, because it does not know what a unit is. It cannot run a four hour maximum on the party room and a one hour maximum on the coworking room in one shared view.
Residents do care whether rules mean anything. In the Foundation for Community Association Research's 2024 Homeowner Satisfaction Survey of 3,006 respondents, 63 percent said the rules in their community protect and enhance property values. A rule that only holds when the front desk is paying attention does not do that.
URBI turns each of those into a field on the amenity itself. Max continuous booking length, booking limit, max total active bookings per resident, max colliding bookings for capacity, and booking notice hours sit on the amenity record and apply to everyone automatically. Schedules can be fixed slots or free form. More on the fairness side in our guide to booking rules residents accept.
Can a calendar know that a tenant may use the gym but not the guest suite?
No. A calendar has one access level per person and no concept of who someone is in the building. Owners, tenants, dependents, and the property manager of a rented unit all look identical to it. If your rules say tenants may not book the guest suite, the only enforcement is a staff member who knows each unit by memory.
Getting this wrong is not only annoying. Federal fair housing law reaches amenity access directly. It is unlawful to discriminate in the terms, conditions, or privileges of rental of a dwelling, "or in the provision of services or facilities in connection therewith". Rules applied from memory are applied inconsistently, and inconsistency is what a complaint is built on.
URBI holds a per occupant type restriction on every amenity. For each of the five occupant types, Owner, Resident, Tenant, Dependent, and Property Manager, the rule says whether that type may book it and whether a surcharge applies, charged automatically at booking.
Where does the deposit go, and how do you prove it came back?
Into a separate channel from the booking, which is the whole problem. The calendar entry says the room is taken. The deposit is a paper check in a drawer, a transfer confirmed by text message, or a line in a spreadsheet. Reconciling the two is manual, and nothing surfaces a mismatch until an owner asks.
They do get asked about. California's association records statute lets members inspect check registers, invoices, receipts, and bank statements as part of the defined association records. Florida requires accurate, itemized, and detailed records of all receipts and expenditures. A deposit trail across three places answers neither.
URBI keeps the money and the booking in the same object. Each building is its own Stripe Connect connected account, so deposits sit in that account as escrow and the board or manager refunds or keeps them. URBI never holds the money. Every booking carries a transaction log with payment logs, deposit status, and payment links. Damage billed back to a unit after a party is a Charge Back, a named object in the platform, rendered as Activity Fee in a school. On a calendar it is a sentence in an email. Longer piece on running deposits without making residents feel policed.
Who is allowed to see the money attached to a booking?
On a calendar, everyone who can open the booking, or nobody at all. That is the entire range. A shared calendar has one dimension of access. It cannot separate the person who administers a booking from the person allowed to see what it cost, what deposit is held, and whether it came back. So the concierge who needs Saturday's schedule either gets the payment spreadsheet too, or gets locked out of the booking record.
URBI splits those two things. User permissions can restrict who sees the accounting side of a booking, so a board member or a concierge manages bookings without seeing the financials. Per person overrides handle edge cases without changing anyone's base role, so a treasurer can be granted reserve fund detail and a probationary staff member locked out of financial dashboards. No calendar configuration expresses this.
Who signed the waiver, and which version did they sign?
Nobody knows, because a calendar has no place to put a waiver. Buildings that require one for the gym or the pool collect it once at move in, file the paper, and never look again. Then the board updates the text, and half the building is signed to a version that no longer exists with no way to tell which half.
URBI attaches versioned waiver templates to the amenity, the resident type, or an event, and records the signature at the point of booking. Check in then gates on it, returning GRANTED, DENIED_NO_WAIVER, DENIED_EXPIRED, DENIED_REVOKED, DENIED_GROUP_RESTRICTION, or DENIED_UNKNOWN_USER, so a denial says why. An emergency override records who overrode it, the reason, and when. More in our post on amenity waivers.
Who moved that booking, and is there a record?
Someone with edit access, and the honest answer depends on your plan. The usual version of this claim is overstated, so here it is straight. On managed Google Workspace an administrator can search Calendar log events and track changes to calendars and events, including who acted, the old event title, and deletions. That is real. It is also an administrator security tool, not a booking ledger a manager can hand a board, and it does not exist for a building running this on a personal Google account.
Double bookings come from the same gap. Two people editing the same week can both put an entry in one slot, and the calendar shows both. It has no concept of capacity.
URBI writes a permanent log for every action on the platform, bookings included. Max colliding bookings caps capacity per amenity, so the system refuses the second entry rather than displaying it. The same logic drives elevator and loading dock booking.
What do you show the board when a resident disputes a booking?
A calendar entry anyone could have edited, which is weak evidence and everyone in the room knows it. The harder version is a board asking whether the rules were applied evenly all year. A calendar holds no record of who was refused, why, or whether the same rule was waived for someone else in March.
Records requests put a clock on this. Florida requires an association's official records to be made available to a unit owner within 10 working days after receipt of a written request, presumes willful failure past that window, and attaches a daily penalty capped after ten days. Rebuilding a booking history from a calendar and a text thread does not fit in ten working days.
It is a trust question as much as a compliance one. In the same 2024 survey, 82 percent said their elected board strives, absolutely or for the most part, to serve the best interests of the community as a whole. That number holds when a board can show its work.
What happens to existing bookings when the room closes for repair?
Nothing, until a resident arrives to find the door locked. Taking a space out of service on a calendar means adding a long block titled CLOSED. The bookings underneath it do not move, do not alert anyone, and do not refund. Somebody scrolls the affected weeks by eye.
URBI treats a closure as an event with consequences. Amenity status can be set to MAINTENANCE, and closing an amenity for repair auto detects the bookings that now conflict inside the closure window. The manager resolves or refunds them in one flow. The same detection runs from a maintenance ticket.
Who reminds the resident, and who records the no show?
The reminder is the easy half and the calendar already does it. Google appointment schedules send up to five reminders. What no calendar does is record what happened afterwards. A booked slot that went unused looks exactly like one that was used. A room sitting empty while three residents were told it was full is a real cost, and on a calendar an invisible one.
The evidence on reminders is adjacent, and I would rather label it than dress it up. A randomized trial in The American Journal of Medicine compared reminder methods across 9,835 analyzed patients and found no show rates of 23.1 percent with no reminder and 17.3 percent with an automated one. That is healthcare, not housing. I could not find a published study measuring reminder effects on amenity bookings in residential buildings, and I would not trust a vendor who claimed one without showing it.
What URBI does here is record arrival. The check in flag on the amenity captures it, and a QR code at the door handles check in where it matters. Bookings also sync to the resident's own phone calendar, so the entry lands where they already look.
That is narrower than the category usually implies, so put two questions to every vendor, including us, and make them answer in writing.
- Does the resident get a reminder before the booking, who sends it, and on which channel?
- When a resident does not turn up, is that a number you can report on, or only a check in that never happened?
A vendor who answers both precisely is telling you the truth. A vendor who answers with the word automated is not.
Side by side: what actually changes?
What changes is who does the remembering. Same list of jobs, and which tool handles each without a person in the middle.
| What the building needs | Shared calendar | URBI |
|---|---|---|
| Resident books without asking staff | Not on a room calendar. Appointments cannot attach to a resource | Self serve in the app, or via Arthur by voice, text, or email |
| Booking limits and maximum length | A daily cap at best, never per room or per unit | Fields on the amenity, applied automatically |
| Notice period before a booking | Minimum lead time on an appointment page | Booking notice hours on the amenity |
| Cap on active bookings per unit | Not possible. A calendar has no units | Max total active bookings per resident |
| Room capacity and double booking | Shows both entries without objecting | Max colliding bookings refuses the conflict |
| Who may book what | One access level for everyone | Per occupant type rules across all five resident types |
| Surcharge for a category of resident | Handled off system | Applied automatically at booking |
| Deposits | Separate channel, reconciled by hand | Escrow in the building's own Stripe account |
| Cost billed back to a unit | Nowhere to put it | Charge Back, a named object in the platform |
| Who may see booking financials | One access level covers the schedule and the money | Permissions hide the accounting side from staff who manage bookings |
| Waiver at the point of booking | No place to put one | Versioned waivers with check in gating |
| Edit history | Workspace admin log only, not a record a board can be handed | Permanent log plus a booking transaction log |
| Maintenance closure | A block laid over existing bookings | MAINTENANCE status auto detects conflicting bookings |
| Reminders and no shows | Up to five reminders. Nothing records the no show | Check in recording plus phone calendar sync |
So when should a building actually switch?
When two or more of the following are true. Fewer than two and I would keep the calendar. The test is not door count. It is how many things one booking sets off besides holding a time slot.
- Three or more bookable spaces. One room on a calendar is manageable. Three rooms, a rooftop, a guest suite, and a service elevator is a scheduling job, and the interactions are where mistakes live.
- Money changes hands. A deposit, a cleaning fee, or a surcharge means the booking and the payment must reconcile. Once they live in different places, someone reconciles by hand and nobody checks the work.
- Written rules someone wants enforced. Not aspirational ones. Rules a board voted on and expects to hold. If the calendar cannot enforce it, the rule is currently optional.
- One dispute you could not settle from records. One is the threshold, not five. That argument is the building telling you the records are not adequate.
- A changing amenity mix. The 2024 NMHC and Grace Hill Renter Preferences Survey of 172,703 renters found interest in a shared workspace grew from 35 percent to 48 percent. A coworking room booked in one hour blocks is a different problem from a party room booked twice a month.
If your building is small and self managed, the math is different, and we wrote that up in our guide for small condo buildings. If you are already comparing products, start with the amenity booking software comparison.
What do you give up by leaving the calendar?
Less than you expect, because the part residents liked comes with them. URBI bookings sync to the resident's own phone calendar, so a confirmed party room reservation sits next to their dentist appointment. That was the real benefit of the shared calendar.
One more thing, said plainly. A standalone booking tool usually means a sixth login on top of five you already have. Amenities in URBI sit next to service tickets, packages, documents, news, and board decisions in one system with one audit log. Here is what URBI is, and how it fits a building.
Frequently asked questions
Can we keep Google Calendar for staff scheduling and use software only for amenities?
Yes, and many buildings do. Staff shift scheduling and resident amenity booking are different problems. A shared calendar handles internal scheduling well because everyone on it is a colleague with a reason to behave. The failure modes here come from opening a calendar to residents. Keep the calendar for the team.
Does a resident need to download an app to book?
The app is the main path, a free download on iOS and Android. Residents who will not install it can book through Arthur by phone call, text message, or email, and Arthur applies the same rules. A manager or concierge can also enter a booking on a resident's behalf.
Who holds an amenity deposit?
The building does. Each building on URBI is its own Stripe Connect connected account, and deposits sit there as escrow until the board or manager releases or keeps them. URBI never holds the money. Permissions control which staff can see the financial side of a booking at all.
What happens to our existing booking history when we move?
Most buildings keep the old calendar as an archive and start clean, because the forward looking record is the one a board will ask for. Migrating historical entries is a case by case conversation rather than a button. From day one, every booking, edit, payment, waiver signature, and check in writes a permanent row.
If the calendar is costing you front desk hours, unenforced rules, or an argument you cannot settle from records, that is the signal. If it is not, keep it with my blessing. When you want to talk it through, including the case for staying put, email us at hello@myurbi.co and we will tell you straight whether your building is ready.
