Decide what a participant is reserving before choosing class-booking software. A whole-course booking commits them to a defined sequence of dates; a drop-in booking reserves a particular session; a pass can provide credits that still need to be exchanged for dated places. The website and the booking account must make the same promise.
For an adult workshop organiser in Formby or Freshfield, the practical question is whether the right person will have a place in the room on every date they expect. Start with that requirement, then compare the software features needed to deliver it.
Use a whole-course place for a sequence people attend together
A course is a useful arrangement when participants build skills over several sessions and the same group is expected throughout. Show every included date before booking, explain any entry requirements and make clear whether joining after the start is possible.
Ask the supplier to demonstrate how a purchase reserves capacity across the course. What happens if one date has a different room limit? Can the organiser close late entry? How are affected attendees identified if a session must move? These are more meaningful checks than the presence of a button called “Course”.
As a specific example, Bookwhen’s course documentation describes a ticket covering all dates on an entry, rather than a customer-selected subset. Its setup also needs explicit attention to late joining. Treat this as one provider’s model, not a definition that every booking service implements in the same way.
Separate the capacity rule from your participant policy. What happens when someone misses a week, requests a transfer or asks to bring a substitute still needs an agreed answer. Have the relevant terms reviewed as needed; software settings alone do not settle those decisions.
Use dated drop-ins when each visit stands on its own
A drop-in should identify the session it reserves. It can be suitable for an independent activity or repeat practice where attendance at earlier dates is not necessary. If preparation or experience is required, explain that before someone selects a date.
Confirm that capacity is attached to the actual session. If website bookings, phone reservations and places allocated by a tutor all draw from the same room, they must reach the same attendance record through an agreed process. A separate handwritten list can leave the public booking page offering places that are already committed.
Use precise button wording. “Reserve Thursday’s practice session” is clearer than “Join now” when there are several dates and formats. The confirmation should identify the date, time, venue and what the participant has reserved.
Distinguish a class pass from a seat reservation
A pass can be useful for someone who attends regularly but needs flexibility. It might provide a number of credits that can be used against eligible sessions. That purchase and the act of choosing a date are separate steps unless the provider explicitly combines them.
Bookwhen’s pass guidance, for example, states that buying a pass does not automatically book particular dates. This distinction belongs beside the purchase action and in the confirmation, so the participant knows whether another step is needed.
- Eligible sessions: identify which classes accept the pass.
- Validity: explain when credits can be used and which date determines expiry.
- Reservation: show how the holder selects a session and recognises a confirmed place.
- Changes: establish what happens to a credit when a booking is cancelled or moved.
- Availability: explain whether a pass guarantees access to any particular session.
Ask the supplier to demonstrate a pass purchase followed by a dated booking, then a permitted cancellation. Check what the participant sees and what remains in the organiser’s attendance and credit records. Do this using the provider’s supported testing method, without making live customer bookings.
Test mixed course and drop-in sales against the same room limit
Mixing formats creates a capacity problem that a simple sales total can hide. Consider a fictional six-date craft course with eight physical places at each session. Six people book the full course. Two others then reserve only the third date. That session is full, so a seventh whole-course participant cannot safely be added even though most dates still have spare seats.
The supplier needs to show how the account handles that case. Does it prevent an impossible whole-course sale? What does the customer see when a date is full? Can a cancellation release the correct place without changing the other sessions?
Bookwhen documents this interaction in its course FAQ: a full date can prevent a whole-course checkout. Its availability display has qualifications, so test the actual customer journey rather than assuming an unavailable course will disappear. Other systems may handle the same requirement differently.
Keep the physical limit separate from the ticket limit. Bookwhen’s ticket setup guidance distinguishes event capacity from limits on particular ticket types. Closing one type of ticket is not a substitute for correctly controlling the total number of people who can attend.
Give suppliers a booking example they can demonstrate
Write a short acceptance brief using your real programme. Include the session dates, room limits, ticket types and how existing bookings are recorded. List the customer messages you need and who will administer changes.
Ask each shortlisted supplier to demonstrate the same ordinary journey and the same awkward case. Useful cases include a course with one full date, an expired pass, a moved session and a phone booking entered by the organiser. Check the resulting attendance lists as well as the public page.
Confirm the account tier and current terms for the features demonstrated, including messaging, payments, exports and administrator access. Do not infer that a feature in a sales demonstration is included in every plan.
Our booking-system selection guide covers the wider appointment decision. Its meeting and service shortlist is a starting point for those tasks; a class programme needs the group-place and entitlement checks above.
Make the website explain the chosen arrangement
Once the booking model is agreed, reflect it in the class description, date selector, button and confirmation. Avoid a page promising a six-week course while its button sells one visit. If a pass holder must reserve a date, provide a clearly labelled route back to eligible sessions.
The website timetable guide helps keep dates, exceptions and joining actions connected. If you are replacing an existing booking service, plan the changeover of existing commitments before removing old links or accounts.
For a wider local website project, start with our Formby class and workshop website brief. To discuss the build, contact Formby Web Design with one example of what you sell, the system you use and the booking behaviour you need.
