Every overbooking has the same story behind it. Availability was true in one place and stale in another: a whiteboard, a group chat, a spreadsheet nobody updated after the school called. The fix is not a better whiteboard. It is having exactly one answer to whether three o'clock on the fourteenth is open, and having the page that takes the money read that answer rather than a copy of it.
Pattern
The week you normally run
- Which days you open, and the times you start on each of them
- How long the thing takes, and the gap you need after it before the next one
- How far ahead people can book, and how close to the start you will still take one
- Whether places are a fixed group per start time, or a number of people who can be in at once
Exceptions
The weeks that are not that week
- A different capacity for a day of the week, a range of dates, or a stretch of hours
- Which rule wins where two of them overlap, decided by you rather than by luck
- More capacity through a season, less for the month a second instructor is away
- A minimum and maximum length of stay, including for one specific window of dates
Closures
The days that do not happen
- A closure across the whole place: a public holiday, a private buyout, a wedding
- Or one thing only, when the pool is closed and the restaurant is not
- One-off changes to a single start time: block it, cap it, or price it differently
- A bulk upload, for when next season already exists in a spreadsheet

Nine in the morning here is the middle of the night for whoever is booking it. Only one of those is the right answer.
Every time is the venue's time
A booking system that stores times without a place attached to them will eventually take a booking for a slot that does not exist. Days roll over at midnight somewhere, and if that somewhere is a server rather than your venue, the last slot of the evening lands on tomorrow and the day's report quietly splits in two.
Every place carries its own timezone, and each boundary is resolved in it: when a day starts, when tomorrow's cut-off falls, which day a slot counts towards in a report. Which also means a guest overseas browsing at their own midnight is looking at your Saturday rather than theirs.
When it is full
A full slot is the most valuable thing on the page, and what normally happens is that the visitor leaves. Instead they can join a waitlist for that date and time, and you get the list with party sizes attached, so when four people cancel you can see who is waiting for four, rather than posting it on a feed and hoping. Nobody is charged for waiting, and converting somebody off the list makes an ordinary booking, so they land in inventory and in the reporting like anyone else.
Common questions
Do I have to create every time slot by hand?
No. You describe the pattern once (the days you open, the start times, how long each takes, the gap between them) and slots follow from it for as far ahead as you let people book. Individual ones can still be overridden afterwards: block a single Tuesday, cap one morning at four, price one evening higher. If next season is already in a spreadsheet, it can be uploaded rather than typed.
Can capacity change through the year?
Yes, with rules rather than by editing every day. A rule can set capacity for a day of the week, a range of dates or a stretch of hours, and where two of them overlap you decide which wins instead of finding out. Twelve in high season and six for the month a second instructor is away is two rules, not a hundred edits.
How do I close for a holiday?
A closure on the date. It can cover the whole place or just one thing on it, so the pool can be shut for maintenance on a day the restaurant is still taking bookings. Bookings already taken for that date are not silently destroyed: what happens to them stays your decision.
What about two things that cannot both run at once?
Where the real constraint is how many people can be in one place at a time (a pool, a gallery, a gym floor) set it to count people rather than fixed groups, and the calendar limits occupancy instead of start times. Splitting one shared instructor or one shared room across separate bookable things is not something to lean on the calendar for today: keep it as one thing with real capacity, and talk to us about the ones that do not fit.
What happens when something sells out?
It shows as full rather than disappearing, and visitors can join a waitlist for that date and time with the size of their party. You get the list. When a cancellation comes back, converting somebody from it creates an ordinary booking. Nobody pays to be on a waitlist.
The rest of what we do

Guest management
One record per guest, built from the bookings rather than typed in afterwards.
Read more
On-site operations
The gate, the counter and the guest tab, on one code and one ledger.
Read more
Box office
Quicket POS at the counter: walk-up sales from the same inventory as your web store, with printed tickets.
Read moreTell us about the event
Describe your week: when you open, how many you can take, when you are closed. If it already exists in a spreadsheet, send that instead and we will load it.
Prefer email? support@quicket.me
