How to Choose Dance School Software: 12 Things to Check

Choosing software for a dance school is harder than it looks. Most systems are built for gyms or salons, and a dance school is neither: you have terms, age groups, parents, recitals, costumes and a timetable that changes every September. This guide explains how to choose dance school software with a 12-point checklist you can use in any demo or free trial. It names no providers, because the right choice depends on how your school works.
Use it as a list of questions. If a system can't answer one of them clearly, write that down.
1. Start with your term structure, not the feature list
Before you look at any software, write down how your school actually runs. Two schools with the same number of students can need very different tools.
Answer these questions first:
- Do you teach in terms (for example three terms a year), monthly, or both?
- Do students enrol for a whole term, buy class passes, or drop in?
- How many age groups and levels do you run?
- Do you have one studio or several rooms?
- Do you put on recitals, shows or exams?
Checklist point 1: Can the software model your year, with terms, breaks and enrolment periods, without workarounds?
Checklist point 2: Can it handle the mix of enrolment types you use, side by side?
2. Class timetable, drop-ins and term enrolment
Your timetable is the heart of the system. Look for:
- A weekly timetable with classes, teachers and rooms.
- Capacity per class, so a class can't be overbooked.
- Term enrolment, where a student is booked into every class of a course in one step.
- Drop-ins for adult classes, if you offer them, kept separate from term courses.
- Holiday handling, so classes skip half-term and bank holidays without manual deletion.
Checklist point 3: When a student enrols in a 12-week course, are they automatically booked into every future class, and freed from them if they drop out?
Checklist point 4: Can you skip holiday dates in bulk?
3. Parents, children and family accounts
In a children's dance school, the paying customer is usually a parent, and one parent may have two or three children enrolled. This is where many systems fall short, so test it carefully.
Ask:
- Can you link siblings to one family or primary account?
- Who receives confirmations and reminders: the student, the parent, or both?
- Can a parent log in and see their children's classes and invoices?
- Can a parent book or enrol on behalf of a child online?
Be precise in a demo. "Family accounts" can mean anything from a simple link between records to a full parent login. Ask the provider to show you each step live, and ask which parts are available today and which are planned.
Checklist point 5: Does the family setup match how your parents actually book and pay?
4. Payments: term fees, monthly plans and passes
Payment is where admin time disappears. Write down how you charge today and check the software supports it:
- Term fees paid up front.
- Monthly plans that renew automatically.
- Class passes (for example 10 classes) with an expiry date.
- Sibling and early-bird discounts.
- Part payments for expensive courses or intensives.
- Costume, exam and material charges on top of tuition.
Also ask:
- Does money go directly to your own payment account, or through the provider's?
- Which payment methods can parents use? If you rely on bank debits, ask specifically whether they are supported in your country and how they are set up. Don't assume.
- What happens when a recurring payment fails? Is there an automatic follow-up?
We go deeper into this in our guide to dance school billing.
Checklist point 6: Can the system handle every way you charge, including discounts and extra charges?
Checklist point 7: Is there a clear process for failed or late payments?
5. Waitlists, cancellations and make-up classes
Popular classes fill up, students get ill, and parents ask for make-ups. Your software should make these fair and simple:
- A waitlist for full classes, with a clear order.
- Whether places are offered automatically when someone drops out, or staff handle it.
- A cancellation policy with a cut-off time.
- Make-up credits for missed classes, with an expiry date, so students can join another class.
Checklist point 8: Can you grant a make-up credit in a few clicks, and does it expire automatically?
6. Recitals, events and costume orders
The end-of-year show is the highlight for families and a big admin project for you. Check whether the software can:
- Create events with ticket types (adult, child, family).
- Sell tickets to family and friends.
- Track rehearsal schedules separately from regular classes.
- Record costume charges per student, and see who has paid.
Some schools manage recitals in a separate tool, which is fine, but then check that the two don't create double data entry.
Checklist point 9: Can you run your recital without a separate spreadsheet for tickets and costume payments?
7. Data, GDPR and moving your records
You hold data about children, sometimes with medical notes such as allergies or asthma. Treat data protection as a selection criterion, not an afterthought.
- Where is the data hosted? For a European school, EU hosting is a sensible requirement.
- Who can see what? Teachers may need class lists and emergency contacts, but not payment details.
- Can you export your data at any time, for example to CSV?
- Can you import your existing student list, so you don't retype everything?
- Is there a data processing agreement you can sign?
The EU's General Data Protection Regulation applies to most European schools. You stay responsible for how you use the data, so ask your provider how they support you.
Checklist point 10: Can you import your current list and export everything if you ever leave?
Checklist point 11: Are roles and permissions fine enough for teachers, front desk and owner?
8. How to choose dance school software: a printable checklist
Checklist point 12 is the one most people forget: test it like a parent. Book a trial class from your phone, enrol a "child", pay, cancel and rebook. If it feels clumsy to you, it will feel clumsy to parents.
Here is the full list to print or copy into your notes:
- The software models your terms, breaks and enrolment periods.
- It handles term enrolment, passes and drop-ins side by side.
- Term enrolment books students into all future classes automatically.
- Holiday dates can be skipped in bulk.
- Family and sibling setup matches how parents book and pay.
- Every way you charge is supported, including discounts and extra charges.
- Failed and late payments have a clear follow-up process.
- Make-up credits are easy to grant and expire automatically.
- Recitals and ticket sales work without an extra spreadsheet.
- You can import your data and export everything.
- Roles and permissions fit your team.
- The booking flow feels easy on a phone, from a parent's point of view.
How to run a fair comparison
Feature lists all look similar. A fair test looks at real tasks. Pick three or four scenarios from your own school and run each one in every system you're considering:
- "New family": a parent signs up two children for a term of ballet and pays online.
- "Missed class": a student is ill; you grant a make-up credit and book it into another class.
- "Full class": a popular hip hop class is full; a new student joins the waitlist and gets a place when someone drops out.
- "End of term": you look at who has paid, who hasn't, and export the figures for your accountant.
Time each scenario and note where you got stuck. Ask the provider to explain anything that wasn't obvious. Also ask about support: how do you get help on a Saturday morning before class, and in which language?
Don't forget the people who aren't in the demo. Your teachers will mark attendance, perhaps on a phone in the studio. Ask one of them to try it. If it takes more than a few taps, it won't get done consistently.
Finally, think about the next three years. Will the system still fit if you add a second studio, an adult programme or a summer school?
For a broader view beyond dance, see our guide on how to choose a business management platform.
FAQ
What is the most important feature in dance school software?
How it handles your term structure and enrolments. Everything else, payments, attendance and reminders, depends on it.
Do I need separate software for recitals?
Not necessarily. If the system supports events and ticket types, you can sell show tickets in the same place as you manage classes.
How long should a free trial be?
Long enough to run real tasks: enrol students, take a payment, mark attendance and handle a cancellation. A few weeks is usually enough if you test with real scenarios.
Should I ask about the provider's roadmap?
Yes. Ask which features are live today and which are planned, and base your decision on what is live.
How BizBrew helps
BizBrew is dance school software built on the same platform as our dance, coaching and education setup. You build a weekly timetable with classes, teachers and capacities, run courses where active students are booked into every future class, take drop-ins and class packs, and grant make-up credits with an expiry date (scheduling and bookings). Classes have waitlists, and staff can offer a freed place to the next student waiting.
Payments run through your own Stripe account, on Growth and Pro you can add tuition memberships for monthly billing, and on any plan you can record part payments on a course (payments and billing). A parent or guardian can be linked to each child's profile and gets a copy of the child's booking e-mails and reminders (client management). Data is hosted in the EU, and you can import and export via CSV. Plans start from €15/month; start your 2 free months.