Conflicting bookings can't reach the database. The check happens at the SQL level, not just the UI, so a fast finger or a janky network can't slip a duplicate through.
Every court has a unique constraint on (court_id, time_range). When the database sees two bookings whose ranges overlap on the same court, the second insert is rejected. The UI then translates that error into a friendly message — "That slot was taken about a second ago" — and refreshes the grid so the member sees the actual state of the world.
On their booking page, the slot greys out with a small "just booked" tag. They can pick another slot. If they were halfway through Stripe checkout when the conflict happened, the payment intent is voided automatically — no double charge, no manual refund.
The successful booking lands in the audit log as booking.create. The failed attempt is logged at debug level (visible in the dashboard's diagnostics tab but not in the public audit log). If you suspect abuse — a member spamming bookings to deny others — both the success and failure are visible to staff.
If anything's missing or wrong, email us — we update articles when readers point things out.
How to refund cleanly, and what happens when a member doesn't turn up.
Pro and Enterprise plans can map a custom domain. Add a CNAME, we provision SSL automatically — usually live within an hour.
From the new-tournament screen to a confirmed winner. Eight to 32 players, single elimination or round robin, Stripe entry fees, owner-confirmed scoring.