Platform

Schedules that handle recurrence, timezones, and Tuesdays off.

Fixed dates, publish-now-schedule-later, and fully bookable time slots, with weekly recurrence, exceptions, lead times, and per-session timezones that survive daylight saving.

Sound familiar?

Slot math by hand

Weekly windows, slot sizes, lead times, and horizons computed in a spreadsheet produce collisions by week two. Recurrence is a typed rule here, not a copy-paste.

Recurrence hacks

Duplicating an event 52 times means 52 things to fix when the room changes. One recurring schedule, date exceptions for the holidays.

The daylight-saving bug

A slot that drifts an hour twice a year is a support queue. Per-session, timezone-correct scheduling keeps local time honest.

Three schedule modes, one model

01Fixed, TBD, or bookableAnnounce with a date, publish now and confirm later, or open recurring slots buyers reserve, per session.
02Weekly recurrence windowsOpen hours per weekday, slot sizing, lead time, and booking horizon, previewed before a single slot exists.
03Date exceptionsClose for a holiday or add a one-off window without touching the base rule.
04Resources & servicesStaff or equipment with their own working hours, matched to the services they perform.
05Venue conflict visibilityScheduling a date shows what else is booked on that venue. Double-booking is stopped by the database, not by diligence.
06A timeline of everythingA Gantt-style view lays every event's schedule side by side, with a drawer for the details.

A bookable schedule in four steps

  1. 01Set the windowsWeekly open hours, slot size, lead time, and how far ahead buyers can book.
  2. 02Add exceptionsHolidays and one-offs layer on without editing the rule.
  3. 03Preview the slotsSee the generated calendar before buyers do, timezone-correct, DST-safe.
  4. 04Take bookingsReschedule and manage bookings from the calendar grid as they come in.

Open your first bookable schedule

Recurrence, exceptions, and slot previews, live in the demo.