Double-booking a meeting room is one of the fastest ways to erode trust in your workspace. A member shows up for a client call to find someone already in the room. Now you have a conflict, an awkward conversation, and a member who's questioning whether they should renew.
It happens constantly at spaces that manage bookings through a shared calendar, a WhatsApp group, or a front-desk process. Not because the operators aren't careful — but because the tools aren't built for it.
WitSpace treats booking management as a first-class problem.
Every Facility Has a Type
Before a booking can happen, you model your space. WitSpace classifies every facility into one of four types:
- Bookable — resources that members reserve for a specific time slot (meeting rooms, focus pods, event space)
- Assignable — resources that are assigned to a member for ongoing use (dedicated desks, private offices)
- Consumable — resources consumed in amounts rather than time (printing credits, locker access)
- Amenity — shared services with no direct booking required (parking, kitchen, shower)
This classification determines how conflict detection works. A Bookable facility checks for time-slot overlaps. An Assignable facility checks for existing long-term assignments. You configure both at the facility level.
Real-Time Conflict Detection
When a member submits a booking request in the Member App, WitSpace performs several checks simultaneously:
Availability check — Is the requested time slot free? If another member has an active or pending booking that overlaps with the requested window, the slot is unavailable. This check is atomic — concurrent requests for the same slot can't both succeed.
Entitlement check — Does the member's active membership cover this facility type? If the entitlement is credit-based, does the member have enough balance for the requested duration?
Rule validation — Does the request comply with the facility's booking rules? You can configure minimum advance notice (e.g. bookings must be made at least 2 hours ahead), maximum booking duration, and blackout periods.
All three checks run before a booking is confirmed. Members see clear, specific feedback if a request fails any of them — not a generic error.
Booking States
Bookings in WitSpace move through a defined lifecycle:
- Requested — the member has submitted the booking; it's pending confirmation
- Confirmed — the booking is active and the time slot is held
- Checked In — the member has arrived (for spaces using check-in workflows)
- Completed — the booking period has ended
- Cancelled — cancelled by the member or an admin
Admins can see all bookings across all facilities in the Admin App, filter by status, facility, or member, and take action on any booking. Members see their own bookings with full status visibility.
Cancellations and Credit Refunds
When a member cancels a booking, WitSpace handles the downstream effects automatically. If the booking was charged against a credit balance, the credits are returned to the member's entitlement balance. If the booking was paid, refund handling follows the rules you configure for that facility.
The facility's time slot is immediately released and becomes available for other members to book.
What Admins See
The Admin App gives operators a complete picture of all bookings across all branches. You can view a timeline of upcoming bookings per facility, identify quiet periods, and spot patterns across your space. When something goes wrong — a member needs an emergency cancellation, a facility becomes unavailable — admins have everything they need to act without hunting through multiple tools.
Booking operations are live and running in production workspaces today. See a demo to see how WitSpace could work for your space.