The recital lineup mistake almost every studio makes
April 17, 2026 · 5 min read · by James, half-owner of a dance studio
Every spring, somewhere around 9pm the night before recital, I used to get the same call from my wife.
"Maya's mom just texted. We have her in Hip-Hop Advanced as number 14 and Lyrical Intermediate as number 15. There's no way she's making that change."
Every single year. Different student, different two classes, same panic. And every single year we'd spend two hours rearranging the lineup, calling other parents, double-checking other students for the same problem we'd just found. Sometimes we'd catch a second one. Sometimes a third.
After three or four recitals running this fire drill, I started paying attention to why it kept happening. Because it's not random. It's a predictable mistake that comes from how studio owners build the lineup in the first place.
The mistake
Most studios build the recital lineup the same way: open a spreadsheet, type in the class names in the order you want them to perform, print it, give it to the stage manager. Done.
That works fine for the dance order. It catches none of the costume-change problems.
The costume-change problem only shows up when you ask a different question: not "what order should the classes go?" but "what does any individual student's day look like?" A student who's in Hip-Hop Advanced and Lyrical Intermediate doesn't think about lineup positions. They think:
- I'm done dancing at the end of Hip-Hop, around 7:38pm.
- Lyrical Intermediate starts at 7:39pm.
- I have one minute. I need to take off my Hip-Hop sneakers, my snapback hat, change tops, find my Lyrical wrap skirt, get my hair down, and run.
One minute is not enough. Two minutes is barely enough. The dressing room mom will tell you anything under five minutes for a young dancer is dicey, and for a costume that involves shoes and hair, ten minutes is what you want.
When you build the lineup in a spreadsheet, you literally cannot see this problem. Each row is a class, not a student. The conflict is invisible until the night before, when somebody actually walks through the program from a single student's perspective.
Why it keeps catching us
A few reasons:
The rosters change late. Students drop classes in March. They add new ones in April. Even if you sat down in February and did the full back-to-back check by hand, it's out of date by April.
Most studios have hundreds of dual enrollments. If you have 200 students and a quarter of them are in two or more performing classes, that's 50+ students you have to mentally cross-reference against every lineup change. No one actually does this.
The problem is silent until showtime. A schedule with a back-to-back conflict looks identical to a schedule without one until you ask the specific question "is anyone in both of these adjacent classes?" Nothing on the page screams at you.
The practice habit that fixes it
The fix is simple in principle and tedious to do by hand:
For every pair of adjacent numbers in your lineup, list the students in both. If any student appears in both lists, you have a conflict.
That's it. That's the whole exercise. For a 30-number recital, that's 29 pair-comparisons. For each pair, you pull the roster of two classes and check for overlap.
Done by hand, this takes about three hours for a typical studio. If your rosters are clean and you have them in spreadsheets, it's a series of VLOOKUPs. If they're not clean, it's three hours of cross-referencing class lists.
Every studio I know that has stopped getting the 9pm phone call has institutionalized some version of this check. Usually it falls to whoever has the patience for it: an admin, a teaching assistant, the owner's spouse on a Sunday afternoon.
What "good enough" looks like
You don't have to eliminate all back-to-back appearances. You just have to make sure the gap is survivable.
- Same costume, same shoes: back-to-back is fine. The student walks off and walks on.
- Costume change with no shoe change: you need at least one number between them, ideally with no hair adjustments.
- Full costume + shoe change for a young dancer: you want two numbers between them, or three if hair has to come down.
- Hair change (e.g. bun to half-down for ballet → lyrical): three numbers between them, minimum.
These aren't industry standards — they're rules of thumb. Every studio's costumes are different. The point is: you set your own threshold, then you check every pair against it.
The reason we built our software
You probably saw this coming, but the thing my wife and I were doing on the dining-room table the Sunday before each recital is exactly the thing we built into Presently. When you drag a class into a recital lineup, the system automatically lists every student that appears in any adjacent class and flags conflicts with a red or yellow badge. The exercise that used to take three hours takes zero, and the data is always current.
I'm not bringing it up to sell anything in this post — we already have a comparison page if you want that. I'm bringing it up because even if you don't use Presently, the principle applies: the question your lineup spreadsheet can't answer is "what does this student's afternoon look like?" Whatever tool you're using, you need a way to ask that question.
The one-question pre-mortem
Here's the test I recommend running on your current lineup before the next recital, regardless of what software you use:
Pick three students at random. Three students who are in two or more performing classes. Walk through the program from each of their perspectives. Write down their day: what number they're in, what they're wearing, what they need to change into next, and how many minutes they have.
If even one of them has under three minutes between numbers with a costume change, you have a problem somewhere. Find it now, not at 9pm the night before.
James runs a dance studio with his wife and built Presently because nothing else fit the way studios actually work. If you want studio software with a real recital lineup tool, we made a few comparison pages. Otherwise, just borrow the spreadsheet check.