Three Routines, One Dancer, One Sunday: Scheduling a Dance Studio's Recital Season

Why does the ordinary class week break first?

Because the ordinary week was never built around the studio. It was built around school hours and parents' working hours, and what survives is a narrow strip of late afternoon and early evening. Recital season wants the same strip, and there is no slack underneath.

The harder problem is that the extra blocks are not more of the same thing. A recital season is a sequence of unlike sessions. There is the counting rehearsal, run without music, which exists so dancers own the steps. There is the rehearsal with the accompaniment, a different session with a different requirement, because now the musicians or the track have to be there. There is the run where costume, stage, lighting and sound are tried for the first time. And there is the gladi bersih.

Stack those as if they were interchangeable and the season looks solved on a wall planner. One needs a lighting rig. One needs an accompanist who is not on your payroll. One needs nothing but floor and a mirror.

One dancer, three routines, and a collision the studio built

The dancer in three routines is not an unlucky family. She is the predictable output of how studios cast.

Casting load is uneven by design. A studio curriculum gives some dancers one piece over a term, some two, some more, sorted by what each can hold. That is good teaching, and it also means the strongest dancers accumulate pieces, each bringing its own rehearsal block. So when her Saturday has two rehearsals in it, nobody put her there. Casting did, weeks earlier, on a document with routines down one side and no times on it at all.

The fix is an order-of-operations fix and it costs nothing. Cast against the rehearsal grid rather than the programme order, and before a cast list is confirmed read it a second way: dancer by dancer, not routine by routine, counting how many blocks each name owes and on which days. Caught in the casting meeting it is an edit. Caught after publication it is an apology to a parent who has already rearranged a weekend.

What does the recital calendar actually have to hold?

More than the show. The separate rehearsal track tends to open around a month out and steps up sharply about a fortnight before the day, not because the dancers are behind but because that is when the live accompaniment joins, and putting dancers and musicians in one space is a scheduling event, not an intensity setting.

The gladi bersih is one session, not a phase. It is the last rehearsal before the show, a trial run of the show itself. Studios that treat it as a category run three of them and none properly.

The recital is also not the only thing wanting those weeks. A working studio gets asked to fill outside events in the same window: the arts festival, the national day programme, a wedding, a reception for visiting guests. Those carry real rehearsal costs and arrive by phone rather than on a plan. So the calendar has to hold the ordinary week, the recital track, the accompaniment sessions, the one gladi bersih, the show, and whatever the city asks for. If those live in different places they are not being scheduled. They are being remembered.

The Sunday problem is a staffing problem, not a calendar problem

Most studio weeks run every day from late afternoon until they are finished, except Sunday. Sunday is not a quiet day on the timetable. It is a day the timetable does not describe at all, which is why Sunday blocks cost more than they look. There is no staffing pattern to inherit, and nobody rostered to open the building or to be the adult at the front when a parent arrives early.

Evening blocks break a different rule. The timetable ends where it ends because it was set not to collide with school or with parents' working hours. An extra evening block pushes past the boundary the timetable exists to protect, and it lands hardest on the families who travel furthest.

Both are worth doing, but not one week at a time. Decide the Sunday and late-evening blocks for the whole season in one sitting, and you spend the goodwill once rather than every Wednesday. Scheduling and enrollment is where that plan belongs, alongside the ordinary week rather than in a document beside it.

Which space, not just which hour?

Space is a separate variable, and it is the one that gets dropped. An hour being free does not mean a space is free. A single session can occupy two spaces at once when a group is large enough to be split, half indoors and half on the terrace. Sessions also move between spaces by nature: the main floor, the hall, an open stage, the yard. And which space a block sits in changes what the block can be, since you cannot try lighting on a terrace.

This is where the honest limit sits, and it is better said now than discovered in week six. Happy Kamper holds the timetable. It records that a block exists, when it runs, who is in it and which site it belongs to, across music and dance studios running more than one location. It does not look at two blocks and tell you that you have put two groups in the same space at the same hour. Nothing in the stack is watching for that.

So the control has to be human, and small enough to actually happen. Write a named space on every block, never just a time. Then have one person read the whole season by space rather than by day, once, before anything is published. Reading by day hides the clash. Reading by space is where it surfaces.

How do schedule changes actually reach parents?

Usually through a single phone number, captured on a paper form when the child enrolled. One contact per family is not the same as reaching the parent who does the driving. A studio Instagram account is not a substitute: it is an outward channel, built for people who are not yet customers.

To work, a change has to be readable as the current version. A thread of corrections is not a schedule. If the fifth message contradicts the second, some parent will bring a child on the wrong day, and that costs a rehearsal you cannot repeat. Keep one place authoritative; let every message point at it rather than restate it. Parent communications only helps if the change lands there first and the noticeboard never disagrees.

The same argument covers who turned up. When attendance lives on a card the dancer carries and the teacher signs, whoever rebuilds next week's blocks cannot see it. Digital attendance earns its place in recital season for one reason: it tells you which routine is short of bodies before the gladi bersih does.

One calendar, and the thing it will not do for you

The version that works is unglamorous. One timetable carries the ordinary week and the recital blocks together, cast lists are read by dancer before confirmation, every block names a space, and the Sunday and evening decisions are made once for the season.

Be just as clear about the edge. The season plan and the running order for the day itself are two separate documents. The plan orders the weeks. The running order lists, minute by minute, who is on and what equipment they need, and it belongs to whoever is standing in the wings. Software holds the first. It does not hold the second and should not be sold to you as though it does: no module for the running order, the ticketing or the front of house, and nothing watching your spaces for a clash.

What you get is one place where the extra blocks and the regular week are the same calendar, and a way to tell every family when it moved. Smaller than the season feels like it needs, and still the part that keeps failing.