Dance school management software: what a studio needs beyond the timetable

The Royal Academy of Dance graded ballet syllabus runs from Pre-Primary in Dance through Grade 8, with five vocational graded levels above that. A studio entering pupils across even half of those levels is running a progression system, not a timetable, and almost no dance software is built for the progression half.

What does a dance school actually have to manage each week?

A mid-sized independent studio looks, on a timetable, like a grid of rooms and hours. Underneath it is something closer to a school.

Take a representative example. Ridgeway School of Dance in Harrogate, run by a principal we will call Frances Ogilvie, has 214 pupils spread across 19 weekly classes in ballet, tap, and modern, taught by four teachers over a 34-week dance year in three terms. Most pupils take one or two classes a week. About 60 of them are working towards a graded exam in any given year, some through the RAD syllabus and some through the Imperial Society of Teachers of Dancing, whose faculties cover tap, modern theatre, and classical ballet separately.

So in a single week Frances needs to know who turned up, who is drifting, who is ready to be entered for an exam with a hard external deadline, who is available for the extra Sunday rehearsal, and which parents still have not read the costume note.

None of that is a timetable problem.

Why is class booking software the wrong place to start?

Most principals shopping for "dance school management software" start with booking and billing, because that is the part of a studio that looks like a business system. We would argue that is the wrong end, and the reasoning is specific rather than ideological.

Enrolment and fees are annoying, but they are stable. A studio that invoices by term with standing orders has a process that works even when it is ugly. What is not stable is the pupil who misses three Saturdays in February, tells nobody, and does not re-enrol in September. Booking software will show you an empty seat only after the money stops.

Exam entries are the second unstable thing, and they carry an external deadline. Once an entry closes, the decision is made for the whole term. A studio that discovers in week eight that a Grade 4 candidate is not ready has lost the chance to do anything about it, which is a teaching failure that started as an information failure.

Fix the register and the readiness note first. Bolt billing on afterwards if it is still hurting. Studios that do it in that order rarely regret it; studios that buy a bookings product first usually still have a paper register a year later.

How do you track exam readiness without publishing a list?

This is the design decision that breaks the most studio setups, exactly as it does in independent music schools working through graded exams.

The tempting version is a class-wide readiness board: names down the side, syllabus elements across the top, ticks in the grid. It is easy to build and it does real damage. The pupils sitting at the bottom of that grid are, reliably, the pupils closest to giving up, and teenage drop-out in dance is already the sharpest problem the sector has. One Dance UK, the sector's national support body, spends a considerable part of its healthy-dancer work on exactly this territory: the pressure, comparison, and body-image load that sits on adolescent dancers.

The version that holds up is one private readiness note per pupil, held against the level they are actually working towards, updated two or three times a term, and visible only to that pupil's family and the teaching staff. The note should name the blocker in plain language: "spot is late on the right turn", "port de bras arrives ahead of the music in the adage", "set exercise four is solid, three is not".

A parent who reads "spot is late on the right turn" can help. A parent who reads "working hard, doing well" cannot, and a parent who reads a grid can only compare.

Principals we speak to describe the change in almost identical terms: "I stopped being asked how she's getting on, because they already knew, and started being asked what to practise at home."

How should a studio handle show casting and rehearsal attendance?

The summer show is where an otherwise calm studio generates six weeks of chaos, and it is worth treating as its own operational problem.

Three things arrive at once: extra rehearsals outside the normal timetable, costume logistics with money and sizes attached, and casting decisions that carry real feeling for both pupils and parents. Handled in a class WhatsApp group, all three interleave into a thread nobody can search on the morning of a fitting.

The pattern that works is boring and effective. Availability first: one poll per rehearsal weekend, posted at least ten days out with a firm cut-off, so casting is built on facts rather than on who happens to reply on the night. A single pinned running order per show, edited in place rather than reposted, so there is exactly one version anyone can find. Costume and payment notes as their own announcement, kept out of the rehearsal thread.

Casting itself should go to families individually, not as a posted list. The list format converts a private disappointment into a public one, and the studio gains nothing by it.

In Bitir this is one private group per class, with polls carrying deadlines, pinned announcements, and per-pupil messages that never touch the group. The same attendance record used for ordinary classes covers rehearsals, so a pupil who has missed two rehearsals in a row surfaces before the dress run rather than during it.

What does a paperless dance school run on day to day?

Studios that settle into a stable setup tend to converge on the same shape after a year or two.

One private group per class rather than per pupil or per studio. Per pupil is unmanageable at 214 pupils and isolates the class from itself; a single studio-wide group means a Pre-Primary parent reads Advanced 1 exam logistics every week and stops reading anything. Per class is the unit that matches how the teaching actually happens.

Attendance marked at the start of every class in a few taps, with a standing rule that a second consecutive absence triggers a message to that family the same day. A private readiness note per exam candidate, reviewed at half term when there is still time to act on it. Availability polls with cut-offs for anything outside the normal timetable. Announcements for kit, fees, and closures kept in their own lane. Individual messages for anything sensitive, including casting.

The part principals underestimate is the view across classes. Nineteen class groups in one dashboard means Frances can sit down on a Sunday evening and see which registers were not marked, which families have not answered the rehearsal poll, and which exam candidates have a readiness note more than a month old. Studios accredited through the Council for Dance, Drama and Musical Theatre will already keep registers and safeguarding records to a defined standard, and a per-class digital register satisfies that more cleanly than a folder of paper does. The software organises the studio; the safeguarding duty, the DBS checks, and the teaching stay exactly where they were.

Related reading: how a Newcastle dance school made exam prep visible to parents for the first time, and how a London piano school made grade progress visible across 40 pupils.