The target
A parent gets their shift rota on a Sunday night. They open your site on a phone, see the October half term programme, book Monday, Tuesday and Thursday for one child and the whole week for the other, pay, and get a confirmation with the drop-off time and the address in it. You open the register on Monday morning and both children are on it with their consent already attached.
That is the whole job. Everything below is the configuration that makes it happen.
1. Decide what a bookable unit actually is
Clubs sell time in a way most booking software does not assume. Before you touch a platform, write down your real units:
- Breakfast club, per morning, with a drop-off window rather than a start time.
- After-school club, per afternoon, with a standard finish and a late finish.
- Holiday club, per full day, per half day, and per week at a week rate.
- Extended hours as an add-on at either end, priced separately.
- Inset day cover, which is a single day sold on its own.
Then decide what is bookable as a block and what is bookable ad hoc. Most clubs need both: a termly Tuesday and Thursday block for the regulars, and single days for the parent whose childcare fell through this week.
2. Model age groups as the constraint they are
A club is not one room. Ratios, activities and often staff differ between the under-eights and the older group, and the capacity you can sell is per group, not per site.
Set each age group up as its own bookable session with its own capacity, so the platform stops selling five-year-old places when the junior group is full and the senior group is half empty. ClassForKids, Sawyer, iPAL and Bookeo all handle capped sessions; what varies is how neatly they express an age range, so check that before you commit a whole holiday's programme to one of them.
3. Build the calendar as the parent reads it
Parents think in weeks and days, not in courses. The booking screen that works looks like a grid: days across, sessions down, prices visible, a tick in each box they want.
If your platform only offers a list of individual sessions, do the grid on your own page and link each cell into the platform. A week that takes eleven separate add-to-basket taps is where holiday bookings die.
4. Let one parent book two children in one basket
Multi-child households are most of your market. Test this properly: add two children, give them different day patterns, apply the sibling discount if you offer one, and pay once.
If the platform forces a separate checkout per child, say so on the page before they start, and make the sibling discount automatic rather than a code they have to find.
5. Set the cut-offs and the waiting list
Two settings save you the most phone calls. The booking cut-off, which is the last moment a session can be booked, and what happens when a session is full.
Publish the cut-off in words next to the calendar, something like bookings close at six the evening before, and let the platform enforce it. Then turn the waiting list on for full sessions rather than showing a dead button, and make sure a cancellation releases the place and notifies the list automatically.
6. Take payment the way parents pay
Card at checkout is the default, but a club that only takes cards loses the parents who pay through a childcare account or a voucher scheme. Configure your platform to allow an alternative payment route on the booking, so the place is held while the transfer arrives, and state the reference the parent has to quote.
Set out what happens if payment does not arrive by the cut-off. The fees and funding page carries the detail; the booking flow only needs to confirm which routes you accept and how long a place is held.
7. Wire the buttons on the website
One booking page, and every programme page links to it with the week already chosen where the platform allows a deep link. A Book button in the header of every page, and on phones a fixed bar at the bottom with Book and a tappable phone number.
Hosted booking pages tend to behave better on small phones than embedded widgets. If you embed, reserve the height so the page does not jump, and check the calendar is not trapped in an internal scroll on a small handset.
8. Make the confirmation do work
The confirmation email is the most read thing you will ever send. Put the dates booked, the arrival window, the exact entrance, what to bring, whether lunch is included, and the cancellation terms in it. A confirmation that only says thank you generates a phone call the next morning.
9. Test it as a parent, then as a stranger
Book a test child end to end on mobile data, including from the link in your Instagram bio, because a lot of holiday club traffic arrives there and in-app browsers are where payment sheets fail quietly. Then cancel it and confirm the place went back into stock.
Repeat before every holiday programme goes live, not just at launch.
10. Watch which page fills the week
Record booking clicks by page. If the Easter programme page gets read and the February one converts, the difference is usually a missing price or an unclear finish time, and it is a ten minute fix.
Where this sits
Day, week and session booking wired around ClassForKids, Sawyer, iPAL or Bookeo is the core of an after-school and holiday club website, and the same booking discipline runs through the other childcare websites we build. Packages are on pricing. The platform holds the register. The site's job is to get a working parent from a rota to a booked week in one sitting.