← Selected work

Fitness booking operations

A booking platform designed around the whole timetable

A production-oriented booking system connecting customer accounts, timetables, waitlists, credits, forms, instructors and operational reporting.

End-to-end booking journeyCapacity and waitlist rulesLaunch-gated controls
OPERATING ARCHITECTURESYSTEM / CONTROL / EVIDENCE

A rules-led booking service connecting member eligibility, capacity, attendance and instructor operations.

EXTERNAL BOUNDARYCustomer notification serviceApproved payment or credit source
  1. 01
    CustomerDiscover and manage activity
    • Account
    • Credits
    • Required forms
  2. 02
    Booking engineApply service rules
    • Timetable
    • Capacity rules
    • Waitlist
  3. 03
    DeliveryOperate each session
    • Instructor view
    • Attendance
    • Cancellation state
  4. 04
    Communication and insightKeep people and leaders informed
    • Notifications
    • Exception queue
    • Operational reporting
ASSURANCE BOUNDARYEligibility checkCapacity holdCancellation ruleAttendance close
KEY CONNECTIONS
  1. 01Account to eligibility
  2. 02Eligibility to booking
  3. 03Booking to capacity
  4. 04Attendance to reporting
Illustrative architecture — anonymised reconstruction.
ACCOUNTABLE PROCESS FLOWINPUT / OWNER / OUTPUT / EXCEPTION
  1. 01
    CustomerDiscover
    Input
    Timetable need
    Output
    Selected session

    ExceptionNo suitable session

  2. 02
    Booking engineCheck eligibility
    Input
    Account and session
    Output
    Eligible request

    ExceptionCredit or form missing

  3. 03
    Booking engineReserve
    Input
    Eligible request
    Output
    Capacity hold

    ExceptionCapacity changed

  4. 04
    Booking engineConfirm / waitlist
    Input
    Capacity state
    Output
    Confirmed place or queue position

    ExceptionNotification failed

  5. 05
    Customer and instructorAttend / cancel
    Input
    Active booking
    Output
    Attendance state

    ExceptionLate cancellation or no-show

  6. 06
    OperationsReport
    Input
    Bookings and attendance
    Output
    Capacity and service view

    ExceptionUnclosed session

Illustrative process flow — anonymised reconstruction.

A fictional interface reconstruction showing the principal operating controls described in this case study.

Illustrative interface — anonymised reconstruction.

Situation

The operating context

Booking capacity, customer eligibility, credits and instructor administration needed one reliable operational record.

Mandate

The work to be done

Translate the service rules into clear customer journeys, accountable administration and a launch-ready operating design.

Delivered

What the work connected

  • Customer accounts and timetable discovery
  • Booking, cancellation and waitlist rules
  • Credits and eligibility controls
  • Customer forms and instructor administration
  • Operational reporting and security boundaries

A useful first conversation

If your system is fragmented, start with the whole view.