Every lane, bay and room on one screen.
The whole floor reads the night at a glance. It updates live, so the person on the counter and the person on the headset see the same thing.
- Drag a booking to another lane, or another hour
- Start times worked out from your assets, hours and duration rules
- Day, week and stacked views, colour-coded by status
Assets across, time down.
Every lane, bay, room and court is a column. Every booking sits on the exact minute it starts, not rounded to the nearest slot. An 18 minute session that ends at 4:16 lets the next one start at 4:18.
The whole booking, without leaving the grid.
Reference, customer, mobile, what they bought, when to arrive, the party mix, and the money split three ways: total, paid, balance. Your staff answer the phone from the grid instead of opening the booking and losing their place.
It gets wider when the booking has notes on it. That is deliberate. The extra width is the signal that somebody wrote something you should read before the guest walks in.
Start times are calculated, never typed in.
One engine sits behind the website, the counter and the phone. It reads your asset pool, the bookings already on the grid, turnaround, opening hours and any date override, then hands back the start times that genuinely work.
- The day’s duration rule sets the spacing, per venue and per asset type. Saturdays can run 18 minute races while Tuesdays run 25, and a single date can override both.
- Capacity is a shared pool, not a lane each. A booking that needs three karts takes three out of the pool for its whole span, turnaround included.
- Blocked-out time and an asset in for repair both drop out of availability, because maintenance and the calendar read the same table.
Move a booking, and say why.
Drag a block to another lane or another hour. The original stays as a ghost, and a preview drops into the first run of columns wide enough to hold it. If nothing fits, it greys out.
Dropping asks for a reason before it commits. Six months later, when a customer swears they were moved without being told, the booking still knows what happened and who did it. Blocked time skips the question and just moves.
The shift, on one page.
One printable page for whoever is running the shift. How many bookings and where they came from, how many guests and how many are new, how full the day is, and what still has to be done before doors.
What changes on the floor.
- Activities with duration and capacity
- Packages and bundles
- Weeknight and off-peak pricing
- Resource-by-time grid
- Day, week and stacked views
- Duration rules and buffers
- Check-in and status colours
- Waiver status per participant
- Notes on the booking and the customer
Questions we get on the first call.
If yours is not here, ask it on the demo.
- Where does availability come from?
- One slot engine checks the asset pool, existing bookings, duration rules and any downtime before a start time is ever offered, online or at the counter.
- What about sessions that need more than one resource?
- Products can span several slots and resources, and the grid shows them as one block.
- Can we see where a booking came from?
- Every booking records its source, whether that was online, walk-in, phone, staff or social.
- Can we import our existing bookings?
- We migrate future bookings, customers and waivers for you before you go live.
See it running on your venue.
Thirty minutes. We put your venue, your activities and your real numbers on the screen, and you decide from there.
Book a 30-min demo