Skip to main content
GullySystem
Education

Appointment Scheduling for Swimming academies

Reserve time with named staff or resources and track changes.

Bookings and Appointments

Does this function belong in your operation?

Use when work is delivered through scheduled time slots with people or resources.

A customer or team member requests a scheduled session.

Assessment swims, private lessons and make-up classes are booked into open lane slots with a named coach. Reminders reduce no-shows. Reception moves a slot when a coach calls in sick.

Bring the records the workflow depends on.

  • Staff or resource availability
  • Session types and durations
  • Booking and cancellation rules

Outputs to check

  • Confirmed appointment calendar
  • Attendance and cancellation history
  • Available-slot and waiting-request view

Follow the appointment scheduling workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Capture the request

    Identify the session type, participant and required duration.

  2. 2. Check availability

    Match the required person or resource with an allowed slot.

  3. 3. Confirm the appointment

    Record the booking decision and agreed details.

  4. 4. Manage attendance or changes

    Track arrival, cancellation, lateness or rescheduling.

  5. 5. Release and reconcile time

    Return cancelled capacity and record the completed or missed-session outcome.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Booking coordinator

Checks the requested session, availability and booking rules, then records changes and attendance.

Service professional

Reviews the assigned sessions and informs the coordinator when availability or duration changes.

Operations manager

Reviews cancelled, missed and completed sessions before adjusting capacity or booking rules.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Two requests for one slot

Confirm only the booking allowed by the capacity rule and offer the other an alternative.

Service professional unavailable

Reschedule affected appointments and record communication status.

Customer arrives late

Apply the agreed queue or rescheduling rule without silently extending later bookings.

Can this work independently?

Scheduling can run with locally maintained people and resource calendars. Online booking, billing and notifications are optional connections. A requested slot is not confirmed until the booking rule is satisfied, and appointment attendance does not establish completion or payment for the service.

Systems and records it connects with

  • Online booking portal: Customer booking requests and confirmation references.
  • Customer records: Permitted customer identifiers and service-contact details.
  • Billing: Issued invoice references, line amounts and outstanding balances.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • Map session types, opening hours, breaks and the people or rooms each booking needs. Decide whether a submitted request reserves capacity immediately or waits for confirmation.
  • Import a checked sample of future bookings. Test different durations, unavailable staff, rescheduling, cancellation and simultaneous requests for the last available slot.
  • Have the booking team and service staff complete a trial day. Reconcile the calendar with the existing record, resolve differences and agree who owns later changes before live use.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Bookings respect configured availability.
  • Conflicting appointments are identified.
  • Cancellations release the correct slot.
Swimming academies

How the business operates.

A swimming academy sells lessons, but what it really runs is a timetable of lanes. Each class has a level, an instructor, a lane and a start time, and every one of those must agree with the pool hours before a single swimmer is booked. Parents ask. They want to know where their child stands. Instructors want to know who is ready to move up. Both need a record.

Enquiries and assessment swims

Log each enquiry, book an assessment swim, record the level the instructor assigns and offer a class and lane that suit the child’s age and the family’s school-run hours. The family’s answer is kept with the enquiry. Some say yes. Some wait.

Classes, levels and lane plans

Define levels from water confidence to squad. Set class sizes by lane. Keep each lane plan by hour. Instructors and lanes are never double booked, and the head instructor can see at a glance which lanes sit empty at ten in the morning and which are full after school.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and assessment swims. Log every enquiry with the swimmer’s age and goal, book the assessment swim, and keep the instructor’s level and notes so the placement is not repeated.
  • Swimmer files and consents. Hold date of birth, medical notes, guardian contacts, photo permission and signed consent forms for each swimmer, with renewal dates for forms that expire.
  • Levels, classes and lane plans. Define levels from water confidence to squad, set class size for each lane and hour, and prevent a lane or an instructor from being double booked.
  • Registers and attendance. Mark attendance at the poolside on a phone, with late arrivals and cancellations noted, and see attendance by class, level and swimmer.

Operational bottlenecks to check

Lane plans are drawn on a whiteboard

A lane holds one class, a lap lane for adults, or a squad set. The whiteboard shows the plan until someone rubs it out. Two instructors then arrive for the same lane. A class of six-year-olds waits on the deck, shivering in towels, while the desk looks for another free lane at that hour.

Levels are decided from memory

A child may pass the back float but not the breathing drill. Instructors remember who is close to the next level, yet no sheet lists the skills passed. A parent asks why a friend moved up first. The answer is a guess, and the guess is rarely written anywhere the head instructor could check it later in the term.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and assessment

    A parent asks for lessons. It arrives by phone, form or message. The enquiry is noted with the swimmer’s age, an assessment swim is booked, and then the instructor enters the starting level.

  2. 2. Class and lane

    The swimmer is placed in a class at that level, on a lane and at an hour with a free place. Consent, medical details and the pass are recorded before the first lesson.

  3. 3. Lessons

    Instructors mark the register at the poolside and tick the skills practised. An absent swimmer joins the make-up list for the same level.

  4. 4. Progress

    When the skills checklist is complete, the instructor passes the swimmer to the next level. A badge is issued. A report card goes to the family.

  5. 5. Pass renewal

    Lessons used are counted against the term pass. The desk lists passes ending soon. It messages the family and posts the receipt on renewal.

  6. 6. Pool checks

    Water readings are logged at set times. Checks are quick. Anything out of range is flagged to the manager, and the entry is kept against the pool and the date.

Industry reports to connect with

  • Swimmers by level, class and lane
  • Lane use by hour, with empty places
  • Attendance by class and swimmer, with make-ups owed
  • Skills passed and badges issued by level

Questions before implementation.

When should swimming academies consider appointment scheduling?

Use when work is delivered through scheduled time slots with people or resources. A customer or team member requests a scheduled session.

What should we bring to the requirements discussion?

Bring anonymised examples of Staff or resource availability; Session types and durations; Booking and cancellation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Reserve time with named staff or resources and track changes. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Professional suitability and service outcomes remain the responsibility of the service provider. Reminders and payments are separate scope items.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Bookings respect configured availability. Use this check when reviewing the first working version.

Talk to us

Discuss appointment scheduling for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements