You decide how a room sells, not your software
A room can be a private buyout, where the slot sells once and party size changes the revenue rather than the availability. Or it can be sold per head and filled from several bookings until the session is full. Both are normal ways to run a room, and the platform models both rather than making you fake one with the other.
Private buyout or per head, chosen per experience
On a private buyout the unit is the slot. Six people and two people consume the same capacity, so party size moves the takings and leaves availability alone. On a per head session the unit is the position, remaining places stay saleable after the first booking, and a group of four leaves two seats that someone else can buy.
That choice sits on the experience, not on the account. An operator can run three private rooms and one shared session on the same site, on the same grid, in the same report, and change a room from one to the other without rebuilding the room.
The buffer is work, not a gap in the diary
Between sessions someone resets props, re-hides items, checks locks and clears the briefing room. That is labour with a duration, and it belongs in the model as part of the session rather than as empty space the booking engine is free to sell into.
Reset length differs by room and by how the last group left it, so buffers are set per experience and can be lengthened on the day without moving anything already sold.
Two rooms free and only one of them runnable
Rooms share the people who run them. If one host covers two rooms, the second slot is not available just because the room is empty, and a calendar that only knows about rooms will sell you into a session nobody can staff.
Staff are a constrained resource a session holds alongside the room, so availability answers the real question, which is whether this can actually run at four o’clock.
Waivers signed before anyone reaches the door
Waivers sent with the confirmation and chased before the session means the group arrives signed, and the front desk is checking a status rather than handing out tablets while the clock runs.
Outstanding waivers show against the booking on the run sheet, so the person on shift can see who still needs one without opening a second system.
Success rate, completion time and no-shows as native measures
Whether a group escaped, how long they took and how many clues they needed are the numbers that tell you if a room is working. They are recorded against the session as it closes, not typed into a spreadsheet someone maintains out of goodwill.
No-show rate sits beside them, per room and per time of day, because a room with a good success rate and a bad Sunday morning has a scheduling problem rather than a design problem.
Three things, and they compound
It assumes one selling model and forces you to fake the other. A per head tool has you buying out your own room with a dummy booking. A private-only tool has you creating a product per party size.
It treats the buffer as availability, so the reset either disappears from the schedule or is faked with a blocked slot that nobody can report on.
And it has no concept of a session outcome, so the thing you most want to know about a room is not in the system at all.
Tell us how your rooms sell and we will show you the model
Get early accessEarly access
Put one venue on it and keep your current system running beside it
We are onboarding a small number of venues before general availability.