One grid for every court at every site. Recurring series, weather alerts, partner invites and refunds in one place. Conflict-free at the database level — your front desk gets their evening back.
Tennis, padel, pickleball, squash, badminton — all rendered on the same grid with sport-coloured booking blocks. Members book it, staff manage it, the database keeps it honest.
Block league nights, coaching slots and ladder rounds in one flow. Members can opt out of a single date without breaking the whole series. Cancellations are visible in the audit log so committee meetings have a paper trail.
When the forecast turns, members with a booking on an affected outdoor court get an email with a one-click reschedule link. The forecast feed is Tomorrow.io and only fires if a club opts in to weather alerts.
A unique database constraint rejects any overlapping booking on the same court before the row is written. The UI translates the rejection into a friendly "that slot was taken just now" message and refreshes the grid.
Members self check-in via a QR. Anyone who hasn't checked in 10 minutes after the slot starts gets flipped to no-show by the end-of-day sweep. Auto-suspension policy kicks in if someone hits the threshold.
Full or partial refunds happen from the booking detail. Stripe handles the reverse; the booking lands in the audit log as booking.refund with the amount and the reason field.
Create, update, refund, cancel, no-show — all land in the audit log with a before/after diff. Owners filter by actor, action or entity. Soft-delete on every booking, so an accidental cancellation is recoverable.
A booking app that looks like your club, on your subdomain, with your colours. Members manage profiles, partners, payments and notifications themselves.
Pick a court, slot, partner. Pay if your tier requires it.
Email confirmation lands in seconds, with a one-tap calendar add.
QR on arrival, or staff mark them in from the day roster.
No. The conflict check is a database-level unique constraint on (court, time range), not just a UI check. If two browser tabs race to book the same slot, exactly one wins; the other sees a friendly "just booked" message and a refreshed grid. More detail in the double-bookings article.
Yes. Slot length, minimum and maximum booking length, advance window, and buffer between bookings — all set per court. Per-tier pricing and peak/off-peak are on the roadmap.
Configurable per court. Stripe handles the charge if pay-on-booking is set; otherwise it's free for members in good standing.
14-day trial, no demo call, your subdomain goes live the moment you sign up.