Booking App for Tutors: Recurring Lessons, Prepaid Hours & No-Show Control
Most private tutors and small centers run their whole business out of text threads, a shared Google Calendar, and a spreadsheet that tracks who has how many prepaid hours left. It works until a parent disputes the hour count, a student no-shows the slot you turned down other work for, or two families both land on Tuesday at 4:00. A booking app for tutors — hosted on ybuild and served on your own domain — turns that scramble into one system where recurring lessons, prepaid packages, and reminders run themselves.
The problem
- Recurring lessons live in text threads and a shared calendar, so a moved Tuesday 4:00 slot or a swapped week quietly turns into a double-booking or a missed session.
- Prepaid hours are counted by hand in a spreadsheet — and every few weeks a parent disputes how many sessions are actually left.
- A no-show or a same-day cancellation costs you an hour you turned down other work for, but there is no enforceable policy attached to the booking.
- The person who pays (the guardian) is not the person who shows up (often a minor), so billing, reminders, and consent all have to reach the right inbox.
What you’d build
A booking calendar built around weekly slots — set Every Tuesday 4:00 PM with Maya once and the series generates itself. Reschedule or skip a single week without touching the rest, mark each session completed, no-show, or cancelled, and see the whole week at a glance.
Sell packages of hours — a 10-hour block, a monthly 4-lesson plan — and let the system do the counting. Every completed session decrements the balance, a valid cancellation restores it, and low-balance students get flagged before they run out, so the count is never a spreadsheet argument.
Automated reminders go out 24 hours before each lesson to both the guardian and the student, with the meeting link or address attached. Late cancellations and no-shows are stamped on the booking so your cancellation policy applies itself instead of living in a forgotten email.
The data model
A day in the system
- A parent books a trial through your booking page (on your own domain), and the system creates a guardian record with billing details and consent, then links the student to it.
- You lock in a recurring slot — Every Wednesday 5:00 PM — and the session series generates for the term, each occurrence its own row you can move or cancel individually.
- The guardian buys a 10-hour package; an invoice is issued to their email, and once it is paid the ten hours are credited to that student's balance.
- 24 hours before each lesson, an automated reminder reaches both the guardian and the student with the video link for online sessions or the address for in-person ones.
- You run the lesson and mark it completed — one hour is drawn down from the package and the remaining balance updates instantly.
- A student cancels the morning of a lesson; you mark it a late cancellation, your policy charges the hour, and the balance reflects it — no awkward follow-up text.
- When a student drops to two hours remaining, the dashboard flags a low balance and prompts you to send a renewal invoice before the next lesson.
- At week's end you review completed sessions, income, and next week's schedule on one dashboard — the whole business, hosted on ybuild and served from your domain.
Where AI trips up
- Recurring slots are not a single calendar event. A naive build creates one booking instead of a series with per-occurrence exceptions, so skipping a holiday week or moving one lesson either breaks the whole series or silently double-books it.
- The payer and the learner are two different people. Modeling everyone as one user collapses guardian and student together, then sends the child the invoice and the parent the homework reminder. Billing, consent, and reminders each have to route to the right party.
- Hour math has to decrement on completion, not on booking — and restore on a valid cancellation. Deduct too early and a rescheduled lesson double-charges; forget to restore and parents lose paid hours. Half-hour and 90-minute lessons must count as fractions, not whole sessions.
- Cancellation windows must use the lesson's local timezone, not the server's. For an online student two zones away, 24 hours before is a classic off-by-one that wrongly charges a fee or wrongly waives one.
- Students are frequently minors, so collecting their information can trigger children's-privacy rules — in the US, COPPA requires verifiable parental consent before gathering data from under-13s. Route sign-up and consent through the guardian rather than letting children self-register.
- A recurring lesson calendar with per-session status (scheduled, completed, no-show, cancelled) and single-occurrence reschedule.
- A prepaid hours ledger that decrements on completed lessons and restores on valid cancellations.
- Automated 24-hour reminders to guardian and student, plus a cancellation-policy flag on each booking.
- Built-in video calling — paste a Zoom or Google Meet link on the session instead.
- A public tutor marketplace with discovery, ratings, and reviews.
- Multi-tutor payroll and commission splits — add tutor accounts later once the core booking flow is solid.
FAQ
Can it handle recurring weekly lessons and let me move or skip a single week?
Yes. You set the weekly slot once and the series generates for the term. Each lesson is its own record, so you can reschedule or cancel one Wednesday without disturbing the rest of the series.
How does it track prepaid packages so I don't over-deliver hours?
Each student has an hours balance tied to their package. Completed lessons draw it down, valid cancellations put hours back, and the dashboard flags a low balance before a student runs out — so the count is never a guess or a spreadsheet argument.
The parent pays but the child attends — can the app separate them?
Yes. Guardians and students are separate records linked together. Invoices and billing go to the guardian, lesson reminders can reach both, and consent stays attached to the guardian — which also keeps you on the right side of children's-privacy rules.
Can I enforce a 24-hour cancellation and no-show policy?
You mark a booking as a late cancellation or a no-show and your policy applies automatically — charging the hour or the fee you set — using the lesson's local timezone so the window is always calculated correctly.
Does it work for online tutoring across timezones, and can I add other tutors later?
Each student and lesson carries its own timezone, so reminders and cancellation windows stay correct wherever a student is. You can start solo and add tutor accounts later as you grow into a small center — everything stays hosted on ybuild and served from your own domain.
Sources
- US Private Tutoring Market to Grow by USD 28.85 Billion (2025-2029) — Technavio — Market-size and 11.1% CAGR figures showing how fast demand for tutoring — and the admin behind it — is growing.
- How to deal with lesson cancellations: a tutor's guide — PMT Education — Practical norms for notice periods and for charging 50% or 100% on late cancellations and no-shows.
- Children's Online Privacy Protection Rule (COPPA) — Federal Trade Commission — The US rule governing data collected from under-13s and the verifiable-parental-consent requirement.
- COPPA: A Six-Step Compliance Plan for Your Business — Federal Trade Commission — FTC walkthrough of how a small operator that collects kids' data can actually comply.
Describe it, go live on your own domain in one pass — hosted, full-stack, no server. Free to start.