Substitution queue
Instructor requests appear alongside the qualified substitutes who are free at that time, so cover is confirmed in one tap.
A dance studio manager app gives the general manager one queue for instructor substitutions, failed payments, room conflicts and staff assignments, along with reports that show which classes fill and which ones lose money. The studio stops running on group texts and memory, and the manager sees what needs a decision today.
A dance studio runs on a timetable that changes every week. An instructor calls in sick on a Tuesday, a sound system fails before the evening session, and a teen class is double booked into the same studio room. Each problem is small, yet together they fill the manager's day, usually through texts and phone calls that nobody else can see.
The owner or general manager often carries the schedule in their head. That works until the studio grows to several instructors and two rooms, at which point one missed substitution means an empty floor and a refund request. An oversight app puts open issues in one place, so the manager can see what is waiting, who owns it and whether it was closed.
Revenue also depends on how full each class runs. A studio can see a sold-out Saturday morning and a nearly empty Wednesday lunchtime and still not know why, because attendance lives in the booking platform while staffing lives in a spreadsheet. The app brings those two records together for the manager.
The first release should cover the decisions a general manager makes every day. Those are instructor substitutions, failed membership payments, room and sound conflicts, and a daily view of which classes are under-filled. Reporting on staff hours can wait until the queue is trusted.
Each queue item should show its age, its owner and the next action. A substitution request that has sat unanswered for two hours should rise to the top automatically, so nothing depends on someone remembering to check the messages.
At 7:30 in the morning the general manager opens the app on a phone. The queue shows three items: an instructor asking for a substitute for the 6:00 evening class, two failed class pack payments, and a conflict where a children's workshop and an adult class both claim the main room.
The manager taps the substitution item and sees which instructors are free and qualified for that dance style. One is assigned, and the app sends the substitute a confirmation with the room, the music location and the class roster. The original instructor is marked as covered, and the item closes without a phone call.
Next, the children's workshop moves to the smaller studio, which the app shows as open at that hour. The conflict clears, both groups get a notice, and the front desk sees the change at check-in. By lunchtime the queue is empty, and the day's report shows the evening class has a full roster.
Instructor requests appear alongside the qualified substitutes who are free at that time, so cover is confirmed in one tap.
Failed membership and class pack payments sit in one list with the member's record and the next step beside them.
Double bookings in shared rooms and missing sound equipment are flagged before the class starts, not after members arrive.
Attendance by class, instructor and time slot shows which sessions to promote, move or retire.
The most common mistake is building a dashboard that looks impressive but does not change anyone's morning. Charts of lifetime member value are interesting in a board meeting and useless when a substitute must be found at 5:15. We would start with the queue and add reporting only where a manager acts on it.
A second mistake is letting instructors keep requests in group chats while the app becomes a record that is always behind. Requests must enter the app, even if a voice note is the first step. A third is designing too many user roles before the studio has agreed who approves what.
A manager oversight app only works if instructors and the front desk actually use it. Start with the one task that already causes pain, such as substitution requests, so the team feels the benefit from the first day of use rather than reading a training document.
Agree on rules that the whole studio follows. For example, a substitution is not confirmed until it appears in the app, and a payment problem is logged the same day. Those rules are easy to enforce when the queue is the only place the decision is recorded.
Measure the numbers the studio already tracks, so results are easy to compare before and after launch. Useful examples are the share of classes that run with a confirmed instructor, the average time from a substitution request to a confirmed cover, and the number of failed payments recovered within a set window.
Also track late room changes and the number of classes cancelled at short notice. A manager who clears the queue faster should see fewer last-minute cancellations, and the fill rate report shows whether weak classes are being moved or fixed. We agree the baseline during scoping and review it with the general manager after launch.
No. The booking platform stays the system of record for members, classes and payments. The manager app reads from it and writes back the decisions that matter, such as a confirmed substitution, so the two records do not drift apart.
They should not. Instructors see their own classes, confirm or decline a substitution request and mark a class as covered. The management screens stay with the general manager and the owner.
Each role sees only what it needs. Instructors see their own assignments, while the general manager sees the full studio. Access is set during scoping and can be changed later if the studio's roles change.
The queue can be shared with a named deputy, and escalation rules can pass an unanswered item to the owner after a set period. The studio decides these rules during scoping, so no request is left waiting without an owner.
We will review how your schedule and payments work today and confirm scope and price in writing.