Skip to main content
GullySystem
Education

Resource and Room Booking for Swimming academies

Reserve shared rooms, equipment or facilities for defined periods.

Bookings and Appointments

Does this function belong in your operation?

Use when several people compete for shared rooms, facilities or equipment.

A person or team needs exclusive use of a shared resource.

Lanes, the teaching pool and the diving end are booked by session, with lane ropes assigned to each class. A club hire or a school block takes its lanes away from the grid. Coaches see the free lanes.

Bring the records the workflow depends on.

  • Resource list
  • Availability calendars
  • Eligibility and booking rules

Outputs to check

  • Resource reservation calendar
  • Approval and access handoff
  • Utilisation and cancellation record

Follow the resource and room booking workflow.

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

  1. 1. Identify the resource

    Choose the room, facility or equipment and required period.

  2. 2. Check eligibility

    Apply user rights, maintenance blocks and booking conditions.

  3. 3. Reserve the time

    Confirm capacity and retain the responsible user.

  4. 4. Prepare the handoff

    Notify the custodian or approved access process where needed.

  5. 5. Close or release

    Record actual use, cancellation or an authorised extension and resolve overlaps.

Who uses the module, and who approves?

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

Front desk or community manager

Books for members who ring. Settles clashes. Keeps the day straight.

Member or staff

Requests permitted resources, checks confirmation and cancels reservations that are no longer needed.

Accounts assistant

Reviews approved chargeable usage and passes it into billing under the agreed booking terms.

Owner

Sees what is used and what is decoration. Numbers decide.

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.

Resource under maintenance

Block availability and review existing reservations.

Booking overruns

Record the change and resolve the conflict with the next user.

Restricted resource requested

Hold for the required approval rather than treating an available slot as permission.

Can this work independently?

Resource booking can run independently with its own calendars and eligible users. Billing, door access and notifications are optional handoffs. Reserving a room or device does not prove that it is prepared, safe or accessible; operational readiness remains with the resource custodian.

Systems and records it connects with

  • Online booking portal: Customer booking requests and confirmation references.
  • Member records: Eligible users and the booking rights attached to their accounts.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Notifications: Approved event messages and delivery or failure status.

Configure, test and introduce the workflow.

  • We note rooms and equipment with their rules. You provide plans and rates, and receive a booking policy for review.
  • Each plan’s hours and limits are entered. Sample members are used to test them. The board and reminders are set up. Front desk staff try booking, moving and cancelling.
  • Extra-hour pricing is connected to invoices. A test bill is checked by accounts. Groups of members receive logins. Usage numbers begin to collect from the first week.

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.

  • Overlapping reservations follow the agreed rule.
  • Restricted resources remain limited to eligible users.
  • Cancelled bookings release their allocation.
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 resource and room booking?

Use when several people compete for shared rooms, facilities or equipment. A person or team needs exclusive use of a shared resource.

What should we bring to the requirements discussion?

Bring anonymised examples of Resource list; Availability calendars; Eligibility and booking 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 shared rooms, equipment or facilities for defined periods. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Reservations do not establish equipment readiness, safety or suitability for a particular use.

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. Overlapping reservations follow the agreed rule. Use this check when reviewing the first working version.

Talk to us

Discuss resource and room booking 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