Class and trial booking
Families see classes with open spaces and book a trial or a term place in one visit.
A booking and intake website for dance schools lets families book trial classes, register for a term and complete the student record in one visit. It is built for the office manager who keeps class capacity in one head, emergency contacts in a binder and waitlists in a text thread.
The office manager wants proof that a class cannot be overfilled and that a student's registration is complete before the first lesson. Show a full class refusing one more sign-up and placing that family on the waitlist instead, with the waitlist moving up as soon as a place opens. A family should see a clear message the moment a class fills, not after filling in a whole form.
They also check the intake data. A demo family submits the registration with an emergency contact, a medical note and a photo consent choice. The record should appear on the instructor's roster for the right class, with the medical note marked as restricted.
Finally, they look at make-up and cancellation rules. Those rules cause most of the calls to the front desk, so the booking flow should show them before the family confirms.
The first release should cover class and trial bookings, the registration form and confirmations. Families see classes with open spaces, the teacher and the time, and they can book a trial or register for a term. The dance class sign up form collects the student's age, class level, emergency contact and any medical note the instructor needs.
Confirmations name the studio, the class, the first-day routine and what to wear. Payment at booking, class packages with credits and an automatic waitlist can wait for a later phase, once the registration flow runs well every day.
A registration system also needs a clear answer for families who change their minds after paying. Set the refund or credit rule in the confirmation, so the front desk applies it the same way every time.
Most dance studios already run dance registration software for rosters, billing and attendance, so the booking site should feed that system rather than compete with it. We check what you use during scoping so the connection matches your current data.
A common setup is studio management software for rosters and billing, a payment processor for card payments and a calendar for room bookings. Where a direct connection is not available, a scheduled export keeps the roster in step with the website, and a shared spreadsheet can hold the dance class waitlist until a system takes it over.
The studio's current software may already hold the rosters, so the first step is deciding which system is the source of truth. Every other tool should read from that record rather than keep its own copy.
Families see classes with open spaces and book a trial or a term place in one visit.
Captures student age, level, emergency contact and any medical note, with the medical field limited to instructors.
Classes show remaining places, and full classes move families to a waitlist automatically.
Each confirmation names the studio, class, first-day routine and what to wear.
The policy appears before the family confirms, and the reschedule option follows it.
Students are often minors, and the registration form holds emergency contacts and medical notes. Those details need restricted access, so only the instructors for that class see the medical field. A parent completes the form, which also fits COPPA rules where a child might otherwise enter data directly.
Waivers and photo consent are separate. The site should link to your current waiver, record acceptance against the student and keep the photo choice as its own tick box, since many studios share class clips online.
Set a retention period for registration records of students who leave, and keep payment card data with the processor. Accessibility matters too, so the form uses clear labels and works fully with a keyboard. Ask the instructors which details they check first on a new student, and make those fields visible on the registration form.
Registration surges arrive at predictable points: the start of the dance year, January for new adult and beginner classes, and the weeks before recital costume fittings are booked. A booking site that cannot handle those spikes sends families straight back to the phone.
The site should show open spaces as they change, so a family does not register for a full class by mistake. Limited classes can display a clear few places left note that updates when the roster changes.
During peak weeks, the office needs a short queue view that sorts registrations by class and date, so staff can work through them in order.
Start with one class type, such as the youth ballet program, and let the front desk run registrations through the site alongside the phone. Once the roster matches the website for a full term, move the other classes across.
Teachers need a short guide to the roster view and the waitlist, and parents need one clear link on the class pages and in the welcome email. Ask a few regular families to test the registration before public launch, and note any step that confused them.
Studio roster management works best when one person owns the rules, so name that person before launch. Peak weeks also need a named person who can approve a waitlist move, so no family waits on a decision nobody owns.
Yes. Each class has a set capacity, and the site stops taking places once the limit is reached. Additional families join a waitlist and are offered a place as soon as one opens.
Yes. A parent can register more than one student in a single visit, and each student gets their own intake record. Siblings can share an emergency contact, while medical notes stay with each child.
Private lessons use the same booking flow with a different calendar, so instructor and room availability both apply. The office sets private lesson terms in the same place as class fees.
They can cancel or reschedule from the confirmation email if your policy allows it, and the cutoff time appears before they confirm. Late cancellations can be flagged for the office to review.
Start a conversation about capacity rules, intake fields and the cancellation policy, and receive the plan on paper before design.