Music lesson studio

What's inside

• Students: instrument and level, teacher, weekly day and time, term package, and lessons left on the pass
• Lessons: each week's lesson and its status (New, Confirmed, Completed, Missed, Rescheduled, Cancelled); Completed and Missed use the pass
• Term packages: lessons, length, and price
• Recitals and Recital sign-ups: who plays which piece
• Families (parents who sign in) and Team (teachers and the office, with roles)
• Next week's lessons (automation, Sundays): adds every Active student's lesson on their weekly slot while their pass has lessons left, and emails the office one summary
• Booking confirmation (automation): emails the family when a first lesson or a moved lesson is confirmed
• New booking alert (automation): emails the office when a family books a first lesson
• School website (app): your school page; families see each child's term pass, book a first lesson and sign up for the recital; teachers and the office mark lessons, move them, sell terms and run the recital

Get started

1. Put in your teachers. With the instruments they teach.
2. Set your term packages. Lessons, length, and price.
3. Add your students. Weekly day, time, and a parent's email.

Playbook. The first thing in the project walks you through every step and ticks them off as you go. Delete it once you're done.

Sign-in. Parents sign in with a one-time code sent to their email in Families and see only their own children. Teachers and the office are on Team with a role (Teacher or Office); you and other project editors sign in with Teable and are Office. The school page is public.

Runs. About 25 automation runs a month: one on Sundays, plus one per first lesson or moved lesson. Weekly lessons send no email.

Comes with sample data for a made-up music school, Harbor Music: 96 students, 6 teachers, an autumn term and a winter recital. Every sample email is on example.com, so the automations send nothing to sample families.