After School Club Booking System: Bookings and AI Reminders

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for After School Club Booking System: Bookings and AI Reminders.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for After School Club Booking System: Bookings and AI Reminders.

Choose a booking system that handles sessions with capacity limits, waitlists, upfront payment, attendance registers and parent messages, and that exports your data. Free tools such as a form plus a spreadsheet work for small clubs; paid tools pay off once waitlists, part-week bookings and refunds appear. AI helps with reminder wording, not with children's records.

Most club owners do not choose software; they drift into it. A form in September, a spreadsheet by October, a payment link someone shared, and by January a parent is texting the organiser's personal phone at 7am asking whether Tuesday is full. The better route is to decide deliberately, then use AI for the one job where it saves hours without touching sensitive records: writing the reminders.

Follow me on Instagram@sagnikteaches

The club used for every example

All names and figures are illustrative. Imagine an after school club running Monday to Thursday from 3:15pm to 5:45pm in a school hall, with 45 registered children aged 5 to 11 and a maximum of 30 per day. Three staff and a part-time organiser run it. Families book by term, by the day or, occasionally, for a single session. About a third pay by block, the rest per session. The waitlist for Tuesday and Wednesday has 11 names. The organiser spends around eight hours a week on booking, payment chasing and messages.

Connect on LinkedInSagnik Bhattacharya

What the system must do: the seven jobs

JobWhat to checkWhy it bites small clubs
Session booking with capacitySeparate capacity per day and per age groupOverbooking leaves a staff ratio broken
WaitlistOrdered list, automatic offer when a place opens, time limit to acceptManual waitlists get lost in text threads
PaymentCard payment at booking, instalments for terms, refunds and creditsChasing unpaid sessions is the biggest time sink
Attendance registerPrintable or tablet register, with collection details and medical alerts for staff onlySafeguarding needs a reliable register
Parent messagesGroup and individual, with a record of what was sentPersonal phones and unrecorded chats
Siblings and part-week bookingsDiscounts, one account for several childrenSibling and discount rules break basic tools
Data exportFull export of children, bookings and paymentsSwitching later needs your own copy

Rank the seven for your club before looking at any product. For the example club, the order is waitlist, payment, attendance, parent messages, siblings, capacity, export. Another club, one that takes drop-ins only, might put payment first and waitlist last.

Subscribe on YouTube@sagnikteaches

Free versus paid: three realistic set-ups

The choice is rarely "free or paid" but "how much stitching can I tolerate". Three set-ups cover most small clubs.

Set-up 1: a form, a spreadsheet and a payment link

A booking form (Google Forms is free; Jotform's Starter plan is free with 5 forms and 100 submissions a month) feeds a spreadsheet. Payment is a link from your payment provider. Registers are printed from the sheet. This costs nothing beyond card fees and works for a single weekly session with a stable group. Be aware of the limits: Google Forms can branch only on multiple-choice and dropdown questions, so a form that asks "which days?" and then "which child?" gets clumsy, and Jotform's free 100 submissions a month can be used up by one term's booking rush. There is no automatic waitlist, and no link between a payment and a booking unless you match them by hand.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Set-up 2: a general scheduling tool

Tools built for appointments, such as Calendly or Square Appointments, can take bookings with limits and payment. As of November 2026, Calendly's Standard plan lists from $10 a seat a month and Square Appointments has a free plan for solo professionals, with Plus at $49 and Premium at $149 a month per location. These suit a club that sells one-off sessions or taster days. They are less natural for term bookings, siblings and registers, and rarely hold collection and medical details in a way staff can print. Use them for tasters and parent meetings, not as the register.

Set-up 3: a dedicated club booking platform

Software built for clubs and children's activity providers bundles some or all of term bookings, waitlists, payments, registers and parent messaging, and charges a monthly fee, a percentage of bookings, a fee per child or a mix. Some publish prices. Pembee, for example, lists Standard at $45 a month and Premium at $105 a month, each with a 0.59% application fee on Stripe payments on top of Stripe's own processing fees; booking reminders and attendance rosters come with Standard, but waitlists for full sessions only with Premium. That split shows the question to put to any vendor: which tier holds the feature you ranked first? Others quote on request, so ask for a figure based on 45 children and 120 bookings a week, and for the total including payment processing. The cost is higher than set-up 1, but it removes the matching and chasing that dominate the organiser's week.

Set-upTypical monthly costBest forBreaks down when
Form, sheet, payment linkAbout $0 plus card feesUnder 30 children, one or two sessionsWaitlists, refunds, siblings
General scheduling tool$0 to about $50Tasters, one-off sessions, parent meetingsTerm bookings and registers
Dedicated club platformAbout $45 to $105 where published; others quote on request30 or more children, several days, paymentsYou want a tool for only one thing

A worked choice for the 45-child club

The organiser's eight hours break down as: payment chasing 2.5, waitlist and cancellations 2, messages and reminders 2, registers and collection lists 1, other 0.5. A dedicated platform would plausibly remove most of the waitlist and payment chasing, and some of the registers, perhaps 4 to 5 hours a week. At an assumed $18 an hour, five hours a week over 36 term weeks is about $3,240 a year of time. On a published plan with waitlists, such as Pembee's $105-a-month Premium, the year costs $1,260 plus the 0.59% application fee: on, say, 120 bookings a week at $15 each over 36 weeks ($64,800), that fee adds about $380, for roughly $1,640 a year before the card processing the club pays anyway. The time saving exceeds the cost. If the quote were $300 a month, the sums look weaker, and a cheaper set-up plus a better process might win. The hours and booking values are invented; replace them with your own, and remember a block of time saved only matters if you spend it on something useful.

Where AI earns its keep: reminders and messages

Booking tools send reminders, but the wording is generic and parents learn to ignore it. AI is good at drafting short, clear messages in your voice. The rule for a club is strict: AI writes the template and never sees a child's details. You write with placeholders and your system merges the names.

Write a reminder message for parents of children at an after school club.
Placeholders to keep exactly: [parent first name], [child first name],
[session day], [start time], [collection time]. Tone: warm, plain, under 50
words. Include: bring a water bottle, and that changes must be made 24 hours
ahead using the booking link. No emojis.

A realistic output reads: "Hi [parent first name], a reminder that [child first name] is booked in on [session day]. Doors open at [start time] and collection is at [collection time]. Please send a water bottle. To change a booking, use your booking link at least 24 hours before." What you fix: the draft may drop one placeholder, turn "doors open" into "drop-off", or sound too bubbly. Check every placeholder is present before you save it, because a missing one produces a message to a parent with a blank where a name should be.

The five messages worth templating

  1. Booking confirmation. What was booked, how much was paid, the cancellation rule.
  2. Day-before reminder. Time, what to bring, collection rule.
  3. Waitlist offer. "A place has opened on [day]. It is held for you until [time]. Accept here: [link]."
  4. Payment nudge. Polite, factual, with the amount and the link; escalate once and stop.
  5. Change of plan. Staff illness, school closure, weather. Short and early.

Write them once with AI help, read each one aloud, and store them in the booking system or a shared document. Re-draft them at the start of each term, when the details change.

Before and after: a payment nudge

The organiser's old message: "Hi, you haven't paid yet for this term, please sort it asap." After a pass with an assistant and some edits: "Hi [parent first name], a quick note that the payment for [child first name]'s term booking is still showing as due ([amount]). You can pay using this link: [link]. If something has gone wrong or you would like to talk about instalments, just reply and we will sort it out." The second message tells the parent what to do, shows no blame and offers a route. It also contains no child details beyond a first name in the merge field.

What stays out of any AI tool

Children's records are sensitive. A good rule for staff: nothing about a particular child goes into a general AI tool, ever. That includes allergies, medical conditions, special educational needs, behaviour incidents, who may collect a child and family circumstances. For a short note to a parent about an incident, use your incident process and a human-written message. If your booking platform offers its own AI features, ask the same questions you would of any vendor: what the feature sees, where the text goes, whether it is kept, and whether you can switch it off. Building the registration form and consents covers what you collect in the first place, and the less you collect, the less there is to protect.

Waitlist rules to settle before you need them

With 11 names on Tuesday and Wednesday, a waitlist will cause arguments unless the rules are written down. A simple version for the example club: places are offered in order of waitlist date; an offered place is held for 24 hours; a family that declines twice moves to the bottom; siblings of children already attending move up one place; staff may override for safeguarding reasons and note why. Check that your system can enforce at least the first two automatically. If it cannot, a spreadsheet with a column for date joined and a column for offer time is enough, and the organiser sends the offer message from the template.

Illustrative case: a place opens on Tuesday at 4pm when a family cancels. The system offers it to the first family on the list at 4:05pm, with 24 hours to accept. They do not respond, so at 4:05pm the next day it moves to the second family, who accept within the hour. The organiser spent no time on it. In a manual version, the same place would sit empty for two or three days while messages went back and forth, which across a term and several cancellations is money.

Attendance, collection and the register

Whatever the system, the register is a safeguarding document. It must show who is in the building, who is authorised to collect each child and any medical alert, and it must be available when the internet is not. Print the register each day, or confirm that the tablet version works offline. Staff should be able to mark late arrivals and early collections with times. Test it with an awkward case: a child booked but absent, a child present but not booked, a collection by someone not on the list. The right answer to the last is a phone call to the parent, not a system setting.

Reminders that actually reduce no-shows

Track two numbers for a term before and after changing your reminders: no-shows per week and late cancellations (under 24 hours). In the example club, suppose no-shows average five a week out of 120 bookings. A day-before reminder with a one-tap cancel link might halve that over a term, but treat any such figure as something to measure rather than expect. If it does not move, the reminder is not the problem; the cancellation rule, or the way families book, is.

Channel matters too. Email reaches everyone but is read late; text messages are read quickly; messaging apps are convenient but mix a club's messages with personal ones. WhatsApp's free Business app is separate from its Business Platform, which from 1 October 2026 resumed charging for service messages beyond 1,000 a month per number and for utility messages sent inside an open customer-service window, so a club using a platform provider should ask what messaging costs. Pick one channel for reminders and one for urgent changes, and tell parents which is which at booking.

Three more worked examples from the club's term

Example: the term-booking launch week

The organiser opens autumn bookings on a Sunday evening. In a form-and-spreadsheet set-up, 38 submissions arrive in the first hour, six of them duplicates, four asking for Tuesday after it is full, and two with the wrong child's year group. The organiser spends Monday matching payments to rows. In a dedicated platform, Tuesday closes at 30, the extra requests land on the waitlist automatically, and duplicates are blocked by the family account. Either way the launch message matters: a three-line email with the opening time, the link and the cancellation rule, drafted with an assistant and checked by a colleague, cuts the "where do I book?" replies by a noticeable margin.

Example: a school closure at 7am

Snow closes the school. The organiser needs to tell 30 families that afternoon's session is cancelled, what happens to the fee and when the next session is. A template stored in advance reads: "Hi [parent first name], the school is closed today so [club name] will not run this afternoon. Your [session day] fee will be credited to your next booking automatically. We will confirm [next session day] by [time]." It takes two minutes to send, instead of fifteen minutes of writing under pressure. The check: the credit promise must match the policy you actually have, so write the template when you are calm and have the policy open.

Example: a parent who books the wrong day

A parent books Thursday instead of Wednesday and finds Wednesday full. The easy reply is "sorry, we are full". The better reply, drafted from a template, offers a swap to Thursday at no charge if they cancel by the deadline, puts them on the Wednesday waitlist and says where they are in the queue. An assistant can produce three tones of the same message (brisk, warm, formal) in seconds; you choose, check the facts and send. Over a term, a handful of these replies, each handled in a minute, is the real saving.

Checking the set-up after one term

At the end of the first term, review five things. Hours spent on admin per week against the eight-hour baseline. Unpaid sessions at term end. Empty places that went unfilled when a cancellation could have been offered to the waitlist. The number of messages parents sent asking something the booking confirmation should have answered. And staff comments on the register: was it correct, readable and available on the day? If two or more of these have not improved, the software is not the whole problem, and the process (opening the booking, closing the waitlist, the cancellation rule) needs another look. If they have, you have a tested set-up and a library of tested messages, and next term's launch takes an hour instead of a weekend.

Questions to ask any vendor before paying

  • Show me a Tuesday session that is full, with a waitlist, and what happens when a family cancels.
  • What are all the fees: monthly, per child, on payments, for text messages?
  • Can I export every child, booking and payment as CSV if I leave, and how soon?
  • What can staff see on a printed register, and who can see medical information?
  • Where is children's data stored, and who at your company can see it?
  • Do you use AI in the product, and can I switch it off?

For a wider view of admin jobs around a club, seven admin jobs and their risks is the companion, and late-pickup fees and fair wording applies directly to collection times. If you want a second pair of eyes on your set-up, my AI implementation consultation covers it, but the decision table above gets most clubs to a sensible choice on their own.

Questions club owners ask about booking tools

Can a small club get by with free tools?

Often, for up to roughly 30 children with one or two sessions a week. A form, a spreadsheet and a payment link cover bookings. Trouble starts with waitlists, part-week bookings, refunds and siblings, which is where a dedicated system earns its fee.

What should a booking system do about a full session?

Close the session, offer a waitlist and, when a place opens, notify the first family automatically with a time limit to accept. Check that the order is recorded, and that you can override it for a safeguarding or sibling reason.

Is it safe to put children's names into ChatGPT to write reminders?

No. Write reminders from templates with placeholders such as [first name] and [session date], and let your booking system merge in the details. The AI only needs the wording, never the child's name, allergies or pick-up arrangements.

How many reminders should parents get?

Usually one booking confirmation, one reminder the day before a session or term, and a short message only when something changes. More than that and parents mute you; fewer and no-shows rise.

Should we take payment upfront or after the session?

Upfront for blocks or terms reduces chasing and no-shows. Pay-per-session suits drop-in clubs, but expect more admin. Whichever you choose, state the cancellation and refund rules at booking, and make sure the system records them.

Further reads

Sources: Google Docs Editors Help on section logic, Jotform, Calendly, Square Appointments and Pembee pricing pages, and Meta's WhatsApp Business Platform pricing page (all checked 4 November 2026).

Want your booking and reminder set-up mapped?

On a 1:1 call we can look at how families book, pay and get reminded today, and decide which step is worth fixing or automating first.

Book a 1:1 call with me