School case study
Tahoe Kids Academy: The Small-School Workflows Behind My Academy HQ
A parent-led enrichment program needs more than a student list. Flexible enrollment, family contributions, and shared schedules have to work together.
My Academy HQ was originally built for Tahoe Kids Academy, an enrichment program in South Lake Tahoe. This is a case study of the program that shaped the product, written by the team behind it. It describes published operating requirements and product workflows, rather than claiming independently measured time savings.
Our founding story describes the original problem: enrollment in a spreadsheet, tuition reminders sent individually, and no single place for families to find schedules, sign forms, and pay. Connecting those tasks became the starting point for the platform.
The program: small classes and flexible enrollment
Tahoe Kids Academy’s published 2026–2027 program serves ages 5–10 and offers flexible enrollment tiers. It forms groups based on enrollment and ages, includes monthly field trips, and adjusts its class structure as the program evolves.
For software, that means enrollment needs to connect a student, family, program, schedule, and tuition arrangement. A single list of names is not enough to tell an administrator which agreement applies or what a family should see in the portal.
The parent-hours requirement is part of enrollment
The public program describes monthly contribution requirements of six hours for full-time families and three for part-time families. It lists classroom help, field trip driving, fundraising, and maintenance among the ways families contribute, and says families receive monthly hour reports.
That requirement explains why contribution tracking belongs beside enrollment. In My Academy HQ, schools can configure requirements by enrollment tier, publish volunteer opportunities, and track family balances. The important connection is between the commitment a family makes and the work recorded against it.
A useful monthly review checks the requirement, completed hours, corrections, and remaining balance together. A claimed slot and a completed activity are different facts, so the school still needs clear attendance and correction rules.
One family workflow, from agreement to ongoing communication
The platform’s enrollment workflow connects agreements and signatures with student enrollment and portal access. Its billing tools connect tuition invoices and payment status. The parent portal then gives families a place to return for communication and the school activities enabled by their program.
The operational benefit of that design is continuity: an administrator can move from the family’s enrollment to the related school work without reconstructing the relationship from separate lists. It does not remove the need to check data, set permissions, or maintain accurate policies.
What another small school can take from this example
Start with one process that crosses several tools. Write down what starts it, who approves it, what the parent receives, and what record closes it. For contribution hours, that might be a tier requirement, a volunteer signup, a completion check, and a monthly family statement.
Try the entire process with a fictional family before importing everyone. Check one full-time and one part-time enrollment, a corrected contribution entry, and a parent account. Use your own requirements; Tahoe Kids Academy’s policies are examples, not defaults that every school should adopt.
Start with the school work you already do.
Bring a real workflow to the trial or demo. We can walk through enrollment, tuition, parent communication, and contribution tracking together so you can assess the fit for your program.