Education & SaaS

A holiday camp operator running 3 venues (Brisbane, Gold Coast, Sunshine Coast) with 50–200 kids per week (250–800 total per 2-week season) across 4–6 different activity themes (Code Camp, Robotics Challenge, Sports Mix, Arts Festival, STEM Hackathon, Multi-Activity), teaching coding (Scratch, Python, block coding), STEM (LEGO, Arduino, Micro:bit), sports (ball games, fitness, team activities), arts (painting, drama, video making), and mixed themes. Each venue runs 5-day camps (Mon–Fri, 8am–3pm with lunch break) during school holidays (2–3 weeks Dec–Jan summer, 2 weeks Apr autumn, 2 weeks Jul winter, 2 weeks Sep–Oct spring). Revenue model: week-based enrolment ($150–300/kid per week depending on theme intensity, 50–200 kids per week = $7.5k–60k per week × 4 holiday seasons = $150k–240k/yr). Current system chaos: week booking is email-based (parent emails "2 kids Code Camp Week 1 Jan," admin replies "yes, $150 each, bank transfer please," no confirmation email, no invoice), group rotation is paper-based (60 kids split into 3 groups, printed schedule on wall, groups move when instructor rings bell, if a kid is absent Day 2, admin scrambles to reassign, if group finishes activity early, no backup schedule), activity planning is siloed (camp director plans activities in Trello but plan isn't connected to booking system, so when 10 kids cancel Week 1, director still plans for 60, over-orders LEGO kits, wastes $2k budget), emergency contacts are paper forms (parent writes on sign-in sheet at 8:30am Monday, if child gets sick at 2pm Wednesday, admin hunts through papers for mum's phone, finds it after 3 mins, mum is stressed). Billing is manual (admin checks bank transfers Friday night, tries to match "$150" transactions to families, 3–5 families haven't paid, admin emails them, process is chaotic, no audit trail). WWCC compliance is ad-hoc (admin has 8 instructor names in an email, 1 WWCC expired 2 weeks ago, instructor still teaches, venue is liable if regulator audits). Total operational bleed: ~$75k/yr manual labour + compliance risk + parent frustration + activity budget waste.

Why Mindbody, Acuity, Square Scheduling Fall Short for Holiday Camps

Mindbody (gym + fitness class booking, $99–299/month + per-booking fees) is built for recurring weekly classes (yoga Mon 6pm, spin Tue 7pm), not week-based holiday camps. No group rotation engine (system can't rotate 3 groups through 3 daily activities—it treats each activity as a separate "class slot," not a rotating carousel). No activity theme planning (no drag-drop daily schedule builder tied to enrolment numbers). No emergency contact storage (parent data is minimal—phone only, no medical info, no alternate contacts). Acuity Scheduling (appointment booking, $15–50/month) is 1-on-1 tutor scheduling, not group camps. Square Scheduling (point-of-sale + basic scheduling, free–$300/month) is retail + appointments, not camps. None handle: (1) week-based enrolment (camps open booking Monday morning for Week 1 Jan, close Friday of Week 1, enrolment is per-week not per-class), (2) group rotation (kids are split into cohorts, rotated daily through activities, system needs to track which group is where each day + handle absences), (3) activity planning (admin plans daily themes + assigns activities + forecasts supplies based on enrolment number, e.g., "Day 2 has 60 kids + 2 cancellations = 58 kids across 3 groups, need 3× LEGO kits, not 4"), (4) emergency contacts + medical (e.g., "Kai has dairy allergy, contact mum Sophie 0412-XXXXX if reaction, emergency contact is Nonna at 0411-YYYYY"), (5) recurring week-to-week billing (each week is a new cohort, billing resets Monday, auto-reminders for unpaid families), (6) WWCC pool per camp (8 instructors per camp, track WWCC per instructor, alert 90 days before expiry per state). Generic SaaS treats holiday camps as "book a weekly class," missing the rotating-group + theme-planning + emergency-contact complexity. Result: camps stay manual, lose $75k/yr to ops labour, risk WWCC breaches, waste activity budgets, and have high parent frustration (no confirmation email, delayed updates on group assignment, week-to-week cancellation chaos). Custom platform handles all 6 steps automatically.

What Custom Replaces: Six Features Holiday Camps Need

1. Week-Based Booking with Auto-Invoice & Payment Confirmation

Dec 10, 2025. School holidays start Dec 20. Camp director logs into custom system: "Code Camp Week 1 (Dec 20–24, Ages 8–12, Coding + Game Dev, $180/kid, max 60 kids). [PUBLISH BOOKING PAGE]." System generates page: "Code Camp Week 1 Dec 20–24 [ENROL NOW]." System emails past families: "Code Camp starts Dec 20! Week 1: Coding + Game Dev, $180/kid. [ENROL] [CURRICULUM] [FAQ]." Parent Kai's mum clicks [ENROL], selects "Code Camp Week 1 + sibling Tech Mix Week 1," system shows: "Kai Code Camp $180. Sibling Tech Mix $150. Total: $330. [CHECKOUT]." Mum enters card (Stripe), pays $330 in 30 secs. System auto-generates invoice: "Holiday Camp Week 1 Booking. Kai + Sibling. $330 paid. Dec 20–24. [ADD TO CALENDAR] [PAYMENT RECEIPT]." Email to parent + admin. Admin dashboard: "Week 1 Enrolment: 45 kids, $8.1k collected, 15 spots remaining." Zero admin touch. Manual system (Mindbody): parent emails "2 kids please." Admin replies "yes, $330, bank transfer." Parent transfers. Admin receives 2 days later, has to match to families, admin emails "which kids?" Parent replies 1 day later. Admin manually enrolls 2 kids in Mindbody. Process takes 5 days. Labour: 20 min × 50 families = 16.7 hrs/week × 8 weeks per year = 133 hrs = $4k. Custom system: 45 kids enrolled in 2 days, zero admin labour, instant revenue confirmation.

2. Group Rotation Engine with Absence Management

Dec 20, Week 1 Day 1. Camp has 60 kids enrolled, split into 3 groups: A (20 kids, 8am–1pm Coding), B (20 kids, 8am–1pm Robotics), C (20 kids, 8am–1pm Arts). At 1pm, groups rotate: A → Robotics, B → Arts, C → Coding (3-group carousel, each group experiences all 3 themes across 5 days). System shows camp director digital schedule: "9am: Group A Coding (Room 1), Group B Robotics (Lab), Group C Arts (Studio). 10am: Group A Robotics (Lab), Group B Arts (Studio), Group C Coding (Room 1). [etc—5 rows, all 15 slots filled]." Each instructor sees roster: "Coding 9am: Group A (20 kids). Maya, Kai, Emma, …[roster names]. [START CLASS]." Instructor taps [START CLASS], system marks attendance. If Kai is absent (mum calls 8:15am "Kai is sick"), system auto-reassigns: "Kai absent. Remove from Group A 9am Coding. Rotation remains: 20 kids in A still." At 1pm rotation, system re-fills: "Group A 1pm Robotics: 20 kids (Kai absent, slot remains open or fills from wait-list if any)." By end of day, Kai is absence-marked (flagged: "1 absent day"). By Week 5 (if winter camp 2 weeks), system shows: "Kai: attendance 8/10 days = 80% (good). If >2 absences mid-week, system alerts: "Kai absent 3 days. Parent check-in: is everything ok? Email: [SEND CHECK-IN]." Director can follow up, ensure kid's family is ok. Manual system (paper schedule): 60 kids, 3 groups, printed schedule on wall. Groups move when bell rings. If Kai is absent Day 1 morning, admin doesn't know until Day 2 morning (parent calls, says "Kai is sick today"). Admin has no system to re-assign. Instructors might count: "Group A should have 20, I count 19," no way to know which kid is missing. If 3 kids are absent without notice, chaos (group has 17 kids instead of 20, activities planned for 20, supplies allocated for 20, instructor has to improvise with 17). By Day 3, if Kai is still absent, admin doesn't track (is it a 1-day absence or 3-day absence?). Custom system: absence is logged instantly, groups auto-rebalance, no day-of chaos, automated parent check-in if multiple absences. Labour saved: $8k/yr (manual group re-assign + absence tracking + parent follow-up).

3. Activity Theme Planning with Supply Forecasting

Dec 15, 5 days before Week 1 starts. Camp director Sarah plans Week 1 activities in system: "Mon: All kids Coding (Python loops, 60 kids, 3 instructors). Tue: All kids Robotics (LEGO EV3, 60 kids, need 15 kits for 4-kid teams). Wed: Rotation (Group A Game Dev, Group B Robotics, Group C Coding). Thu: All kids Mixed Team Challenge (groups compete, LEGO kit + laptops). Fri: Showcase (projects displayed, parents visit 2–4pm)." System calculates supply demand: "Mon: 3× laptops, 60× Python IDEs. Tue: 15× EV3 kits. Wed: 5× EV3 kits (Group B only), 20× laptops (Groups A+C). Thu: 15× EV3 kits, 60× laptops. Fri: display setup (no new supplies)." System cross-references inventory: "Current stock: 18× EV3 kits (enough for Thu, short 2 for Tue + Wed combo). Alert: [ORDER 5 MORE EV3 KITS BY DEC 18]." Sarah clicks [ORDER], system sends purchase order to supplier (integrates with camp's vendor account). Sarah also plans: "If >10 kids drop out before Week 1, revise Tue supplies (from 15 EV3 kits to 10 kits, save $400 hire cost)." By Dec 18, 5 families cancel (55 kids enrolled instead of 60). System recalculates: "Tue supply demand: 13 kids across 3 groups = 3 EV3 kits (not 4). Cancel 2-kit hire reservation, save $200. Supply revised." System auto-sends to instructors: "Week 1 final plan. Tue Robotics: 13 kids, 3 EV3 kits. All instructors updated. [CONFIRM]." Zero last-minute supply surprises. Manual system: Sarah plans on Trello "Mon Coding all kids," but Trello isn't connected to booking system. Sarah thinks 60 kids are enrolled, but 5 cancel mid-week (admin emails parents individually, cancellations aren't in Trello). Sarah orders 15 EV3 kits for $3k. Week 1 Tue arrives: only 55 kids show up. Sarah runs Robotics with 13 kids per day = only need 3–4 kits, not 15. 11 unused kits sit in storage, $2.2k wasted (kits hired for week, can't return). Over season (8 weeks), this waste repeats: ~$5k wasted supplies due to booking mis-match. Custom system: activity plan is fed real-time enrolment, supplies scale with bookings. Waste eliminated. Labour saved: $3k/yr admin re-planning + $5k supply waste prevented = $8k/yr.

4. Emergency Contact Storage & Incident Logging

Week 1, Day 2, 2:15pm. Kai is playing in Arts class, says he feels dizzy. Instructor calls admin immediately: "Kai dizzy, need to contact parent." Admin opens system: "Kai search." System shows: "Kai [Student ID: 4521]. Parent: Sophie (0412-4821-XX). Alternate: Nonna (0411-1234-YY). Medical: dairy allergy (not anaphylaxis risk, just stomach upset), asthma mild (inhaler in office). Recent form (Dec 20): emergency contact is Sophie first, Nonna if unreachable." Admin calls Sophie immediately (phone from system). Sophie arrives in 8 mins, Kai feels better by then. Incident logged: "Kai dizziness 2:15pm, parent contacted 2:16pm, parent arrived 2:24pm, kid recovered by 2:25pm. Medical: dairy allergy, no food involved. All clear." Report is auto-filed (accessible to camp director for review, or regulator if incident audit). By Week 2, if Kai feels dizzy again, system shows history: "Kai: 1 prior incident Week 1 Day 2. Pattern: afternoon, might be fatigue or heat. Recommend water check + rest." Director can proactively support. Manual system: parent writes emergency contact on paper sign-in sheet at 8:30am Monday (Sarah, 0412-XXXX, calls mum). If kid gets sick Wed 2pm, admin hunts through papers (papers are in office, takes 2–3 mins to find), calls mum, mum takes 10+ mins to arrive (kid is uncomfortable). No record of incident (if it repeats, director doesn't know there was a prior event). By season end, no incident log (if regulator asks "how many medical incidents?" camp has no record). Custom system: emergency data is centralized, accessible in 10 secs, incident history guides future decisions, regulatory compliance is auto-documented. Labour saved: $4k/yr (manual emergency contact hunting + incident logging) + risk prevented (faster parent response = better care).

5. Recurring Weekly Billing & Payment Tracking

Week 1, Friday 4pm. Camp closes for the day. System auto-calculates: "Week 1 Enrolment: 55 kids enrolled, 53 attended (2 absences from prior cancellations). Total revenue due: 55 × $180 (Code Camp avg) = $9.9k. Status: 48 families paid ($8.64k collected). 7 families unpaid ($1.26k outstanding)." System auto-sends email to 7 families: "Week 1 Code Camp (Dec 20–24) [INVOICE] Complete. Amount due: $180 per kid. If you haven't paid yet, [PAY NOW] [CONTACT US]." 5 families click [PAY NOW], pay instantly. 2 families don't respond. System waits 24 hrs, sends 2nd reminder: "Final reminder: Week 1 invoice due today. [PAY NOW] or call admin." 1 family pays. 1 family goes dark (admin calls on Sunday, finds out parent lost job, offers extended payment plan "split into 2 weeks," reschedules $180 payment for next payday). By Monday (Week 2 starts), System recalculates: "Week 1 closed. $9.9k due, $9.7k collected (98%), $200 deferred. Week 2 Enrolment opens (Dec 27–31): new cohort, new billing. [NEW BOOKINGS OPEN]." Week 2, Friday: $9.1k collected from 51 new families. By end of season (4 weeks of holidays), admin has zero manual billing work, zero follow-ups, 95%+ payment rate, complete audit trail (every transaction tied to family). Manual system: admin checks bank statement Friday night. 55 transactions of varying amounts (some families pay $180 for 1 kid, others $360 for 2 kids, some partial). Admin tries to match transactions to enrolment list, gets confused. Sends email blast to all 55 families "please confirm your payment" even though 48 already paid. Chaos. 3 families say "we paid you," and admin has to dig through transactions to verify (cost 30 mins per dispute). By season end (8 weeks × 50 kids/week), admin spends ~30 hrs on billing chaos. Labour lost: $1k/week × 8 weeks = $8k administrative bleed. Custom system: zero manual billing work, instant payment reconciliation, zero disputes (payment is auto-matched to family). Labour saved: $8k/yr.

6. WWCC Compliance Database & Expiry Alerts

Dec 1, before holiday season. Admin sets up camp instructor records: 8 instructors for holidays. System: "[+ADD INSTRUCTOR]" Admin adds: Sarah (QLD, WWCC #654321, expiry Mar 2027), Tom (QLD, WWCC #789012, expiry Dec 2026), Jake (NSW, WWCC #345678, expiry Feb 2026). System auto-alerts: "Jake's WWCC expires Feb 2026 (in 2 months). [SEND REMINDER TO JAKE]." Admin clicks. System auto-emails Jake: "Your WWCC expires Feb 15. Renew now. [LINK TO NSW WWCC RENEWAL]." Jake renews on Jan 15, updates system: "Jake WWCC renewed, new expiry Feb 2029." Dec 15 arrives (Tom's expiry): system alerts "Tom's WWCC expires Dec 26 (in 11 days). [SEND REMINDER]." Admin reminds Tom. Tom renews Dec 20. System confirms "Tom clear (new expiry Dec 2029)." Dec 26 arrives (Week 1 starts): Tom's old WWCC would have expired, but Tom renewed, so Tom is cleared to teach. System shows: "All 8 instructors cleared for Week 1. ✓ Sarah (valid Mar 2027), ✓ Tom (valid Dec 2029), ✓ Jake (valid Feb 2029), [+5 more]." Zero expired staff working. Manual system: admin has 8 names in an email. Doesn't check expiry dates. Tom's WWCC expires Dec 26. Admin doesn't notice. Tom teaches Week 1 Dec 20–24 (4 days before expiry). Tom's WWCC expires Dec 26. Admin still doesn't notice. Tom teaches Week 2 Dec 27–31 (1 day expired, 4 days teaching with expired WWCC). Parent notices Tom's name on notice board, googles "Tom WWCC," finds it expired. Parent complains to venue manager. Venue is now liable (staff with expired WWCC worked with children, breach of Working with Children Act). Fine: $5k. Reputation damage: school stops recommending camp. By season, admin discovers 1 other instructor also expired mid-holiday. Total liability: ~$10k fines + reputational damage. Custom system: 90-day alerts prevent expired staff from working. Zero liability. Labour saved: $2k/yr (WWCC admin) + risk prevented ($5–10k fines + reputation damage). Mandatory in Australia (it's the law).

Australian Holiday Camp Regulatory & Operational Context

Holiday camps in Australia must comply with: working-with-children background checks (WWCC, mandatory if staff work with <18-year-olds, issued per state: NSW, QLD, VIC, WA, SA, TAS, ACT, NT, each with own validity period 3–5 years). Duty of care (venue responsible for student safety, supervision ratios: typically 1 instructor per 15–20 kids). Consumer law (Australian Consumer Law: programs must have clear terms, refund policy, no false claims like "guaranteed to make your kid a coding expert"). National Quality Standards if registered as OSHC (Out-of-School-Hours Care, applies to care-focused camps; coding camps often don't register, but mixed-activity camps might). School holidays calendar (Dec–Jan summer, Apr autumn, Jul winter, Sep–Oct spring). Venue safety (if rented, comply with venue's insurance + safety rules). Supervision records (if incident occurs, audit trail needed). Custom system should track: WWCC per state (NSW vs QLD, different expiry periods), attendance + incident log (for care duty records), refund policy (e.g., "cancel by day 1 = full refund, day 2+ = no refund, emergency = full refund"), supervision ratios (system can flag "Group A Coding has 25 kids, 1 instructor, ratio is 1:25—need 2 instructors per NQS"). System enables compliance + audit trail without replacing policies.

Six FAQs

Can we run camps across 3 venues with 1 admin team?

Yes. System is multi-venue. Admin sets up: Brisbane, Gold Coast, Sunshine Coast. Each venue has own booking page (kids see "Code Camp—Brisbane Dec 20–24" vs "Code Camp—Gold Coast Dec 27–31"). Instructors assigned per venue (Sarah teaches at Brisbane + Gold Coast). Equipment tracked per venue (Brisbane has 15 EV3 kits, Gold Coast has 10). Reporting is global (admin sees "60 kids Brisbane Week 1, 45 Gold Coast Week 1, 50 Sunshine Coast Week 1 = 155 total, $27.9k revenue across 3 venues"). No per-venue licensing creep. Manual system (Mindbody): per-location fees = $100/month per venue × 3 venues × 2 months (each holiday season) = $600 per season × 4 seasons = $2.4k/yr in fees alone. Custom system = flat $2k/yr hosting (scales 1–50 venues).

What if kids join mid-week or do drop-in days?

Week-based model expects 5-day commitment (Mon–Fri). But flexibility: mid-week join = kid joins Wed (after Mon–Tue), pays pro-rata ($180 × 3/5 = $108 Wed–Fri). System shows in billing: "Kai joined Wed, rate pro-rata $108." Drop-in days: kid is enrolled Tue–Fri but can only attend 3/5 days (e.g., "want to attend Mon–Tue + Thu only, skip Wed + Fri"). System tracks: "Kai 3/5 days = 60% attendance, pro-rata $108. Group rotation adjusted Wed + Fri (Kai not in rotation)." Flexible enrolment is supported.

Can we refund mid-week if a kid wants to drop out?

Refund policy: "Day 1 (Mon) full refund. Day 2–3 (Tue–Wed) 75% refund. Day 4+ (Thu–Fri) 50% refund. Medical/venue closure = full refund anytime." System auto-calculates: if Kai paid $180 for 5 days (= $36/day), attends Mon–Wed, drops Thu, system refunds: $180 - (3 days × $36) - (50% of $72 remaining) = $180 - $108 - $36 = $36 refund. Stripe refund instant, parent gets receipt. Typical drop-out is <5% (kids love camps, hard to leave mid-week once they're in). Refund processing = zero admin labour.

How do we assign kids to groups if everyone doesn't show up?

Group assignment is dynamic. If 60 kids enrol but 55 attend: system recalculates group sizes (55 kids ÷ 3 groups = 18–19 kids per group instead of 20). Rotation schedule auto-adjusts (same activities, but group sizes change). If mid-week 5 more kids cancel, system re-calculates again (50 kids = 16–17 per group). Instructors are alerted: "Group A revised: 19 kids (was 20, due to cancellation)." Lesson plans adjust automatically (fewer kids = same lesson, less time, can add enrichment activity). Group assignment is never manual—system does it based on real-time enrolment.

What if an instructor calls in sick mid-week?

Breakdown scenario: Sarah teaches Coding 9am Monday. Tue 8am, Sarah calls: "Sick, can't teach this week." System alerts admin immediately: "Coding instructor (Sarah) unavailable. [REASSIGN] or [CANCEL CLASS]." Admin options: (1) Reassign to backup instructor (Tom, if trained in Coding). System updates: "Coding 10am Tue: Tom teaching (was Sarah). [NOTIFY PARENTS]." Parents get email "Instructor change: Tom will teach Tue's Coding." (2) Cancel Coding classes Tue–Fri (rotate other activities instead). System shows: "Coding classes cancelled Tue–Fri. Refund to families: $36 per kid = $1980 total. Approve? [YES]." Refunds auto-process Stripe. 95% of camps have backup instructors, so reassign is fast.

How do we handle kids with medical conditions (allergies, asthma, etc)?

Parent enters medical info at enrolment: "Kai: dairy allergy (stomach upset, not anaphylaxis), uses Ventolin for asthma if needed, emergency inhaler in office." System stores encrypted (secure, only staff access). System alerts instructors: "Kai: dairy allergy, asthma inhalers available. [VIEW MEDICAL PROFILE]." Each class, instructor sees roster + medical flags. Lunch time: if pizza is served, instructor avoids giving Kai pizza (or admin provides dairy-free alternative). If Kai wheezes during sports, instructor has inhaler on hand. System logs: "Kai used Ventolin 2pm Day 2, feeling ok after 5 mins. Parent notified." Notification: "Kai used asthma inhaler today (minor, recovered quickly). [VIEW INCIDENT LOG]." Parent is aware, feels confident kid's safety is managed. Manual system: medical info is on paper form. Gets lost. Or staff forget to check. Kai eats pizza (mum warned about allergy), gets stomach upset, mum is angry (kid had preventable reaction). Custom system: zero missed allergies, proactive safety, parent confidence high.

The Bottom Line

Holiday camps and school vacation programs (50–200 kids per week, 3+ venues) need week-based booking + invoice, group rotation engine (kids rotated daily through themed activities), activity planning tied to enrolment (supply forecasting, budget optimization), emergency contact storage + incident logging, recurring weekly billing, and WWCC database. Mindbody (fitness booking), Acuity (appointments), Square Scheduling (point-of-sale) all lack group rotation, activity planning, emergency contacts, and compliance tracking. Manual systems bleed ~$75k/yr to ops labour (week-booking, group-scheduling, activity-planning, emergency-contact management, billing, WWCC admin) + compliance risk (WWCC expiry unnoticed, staff work illegally, venue faces fines) + supply waste (10–15% overspending due to booking mis-matches). Custom platform automates all 6: week booking auto-generates invoice + payment link (parent pays 1 click), group rotation is auto-scheduled (60 kids split into 3 groups, rotated daily, absence updates rotation in real-time), activity planning is drag-drop + supply-tied (adjust activities based on enrolment, forecasted supplies scale with bookings), emergency contacts are centralized (10-sec lookup, incident history logged), billing is auto-recurring weekly (payment reminders sent, 95%+ collection, zero manual reconciliation), WWCC database alerts 90 days before expiry per state (zero expired-staff risk). Build cost: $80–120k. Year one: $100k investment. Year two: $2k/yr hosting. Break-even: month 18. Year 2+: $40k enrolment labour + $12k activity planning + $8k emergency-contact + $6k WWCC admin + $4k billing + $5k supply waste = $75k/yr labour + waste saved + zero compliance fines (~$5–10k liability prevented). Scale from 1 venue (50 kids/week, $2.5k/week revenue) to 3 venues (150+ kids/week, $25k/week revenue) without per-venue licensing creep. Own your camps. Own your scheduling. Own your themes. Own your compliance. Build custom. Ship faster. Scale to multi-venue without manual ops bleed.

Ready to build a custom holiday-camp platform for your network? Check Aidxn's custom software packages, or book a call to discuss your current weekly volume (50–200 kids per week?), venue count (1–3?), activity themes (Code Camp, Robotics, Sports, Arts, Mixed?), instructor team size, current pain points (group scheduling chaos? billing delays? WWCC tracking?), and growth goals (scale to 5+ venues and 500+ kids per season by 2028).