Calendar Booking

Online scheduling that fits how a business really runs.

A configurable booking platform for organisations that need customers to book online while staff retain control of spaces, timings, and approval.

WEEK · ROOM AMONTUEWEDTHUFRI9:0011:0013:0015:0017:0019:0021:00PENDINGCONFIRMEDPENDINGRECURRINGBUFFER

The operational problem

A calendar alone does not run the operation.

When several rooms, event types, recurring activity, and exceptions share the same schedule, publishing a simple booking link can create more work rather than less.

  • Customers need a clear way to request a time without calling or emailing back and forth.
  • Staff need to see the wider day before committing a room or assigning responsibility.
  • Availability must reflect closures, recurring use, buffers, and the real capacity of the organisation.

How it works

A guided request for visitors. A working calendar for staff.

  1. 01

    Choose the booking

    Visitors select a configured event type—such as a rehearsal, celebration, or another bookable activity—then choose a date and an available time.

  2. 02

    Request the slot

    The public form collects the details needed for the booking. The request is received without creating a public account.

  3. 03

    Review with context

    Staff see pending requests alongside rooms, recurring activity, and upcoming bookings before they accept, reject, edit, or assign them.

  4. 04

    Keep everyone informed

    Confirmation, decisions, comments, and cancellations are communicated by email, while visitors can request details of their next booking.

Public booking flowScreenshot placeholder: a visitor selects a configured booking type, date, and available time before providing their contact details. Use anonymized demonstration data.
Request receipt and follow-upScreenshot placeholder: the confirmation state shows that a request was received and remains subject to staff review. Use anonymized demonstration data.

Scheduling with operational context

Availability is calculated around the space, not just the appointment.

The platform accounts for room occupancy, overlapping recurring activity, configured buffers, working hours, days off, and public holidays before it presents an available time. A declined request releases the slot; an accepted request becomes part of the active calendar.

  • Pending review and room selection
  • Week, two-week, and month calendar views
  • Recurring room use and one-off closures
  • ICS and CSV calendar exports
Operations calendar and review queueScreenshot placeholder: staff review pending requests alongside upcoming activity, then accept, reject, edit, comment on, or cancel bookings. Use anonymized demonstration data.
Room-aware recurring schedulingScreenshot placeholder: recurring classes or room blocks are assigned to specific spaces, so parallel activity can be represented without making unavailable rooms bookable. Use anonymized demonstration data.
Availability exceptionsScreenshot placeholder: days off, special closures, public holidays, working hours, and buffers define when online booking is available. Use anonymized demonstration data.
Organisation configurationScreenshot placeholder: administrators configure event types, rooms, formats, translated content, permissions, and tenant-specific presentation without changing application code. Use anonymized demonstration data.

Built to be configured

Adapt the scheduling rules without rebuilding the system.

Administrators can shape the public experience and the rules behind it to reflect the way their organisation operates.

  • Event types and durations
  • Rooms and recurring use
  • Time zone, date format, hours, and buffers
  • Days off and public-holiday imports
  • Roles, translations, and tenant-specific branding

Start a conversation

Tell us what you would like to make simpler.

Start a conversation