Read this first when you are building class records that are ready for real enrolment traffic. It focuses on capacity, age range, level, and status decisions that often create pressure in week one. You will see how to avoid “looks finished” classes that still need correction work. The examples reflect UK studios where room limits, mixed age groups, and parent expectations are all active constraints.
The expensive mistake to avoid first
The most expensive setup mistake is setting capacity and age ranges for marketing demand, then trying to enforce safe delivery later.
Concrete example: a class is listed with capacity 24 to attract interest, but the room and teacher ratio only support 16 safely. The queue then becomes a negotiation problem instead of an enrolment process.
If you correct one thing early, correct this.
Build class details in this order
1. Core class identity
Set class name, term, day, and time first. Keep names parent-readable.
2. Delivery limits
Set capacity and age range based on real supervision and room constraints.
3. Teaching level
Use level labels that match your teaching programme. Keep labels clear for families and staff.
4. Status and visibility
Start in draft. Publish only when checks are complete.
5. Public-facing copy
Write concise, specific class descriptions. Avoid vague terms such as “all welcome” if age or experience limits apply.
Capacity choices under pressure
Demand pressure is real, especially in September and January. You still need to set limits that are safe and sustainable.
Use practical checks:
- What is the usable floor or room space?
- How many participants can one teacher supervise safely?
- Do assistants change safe capacity?
- Will late arrivals or parent handover create congestion?
If your answer changes by venue, capacity should change by class.
Age bands and safeguarding
Age range is not a decorative field. It shapes approvals, safeguarding expectations, and class experience.
Concrete examples:
- Ages 4-6 often need slower transitions and parent handover clarity.
- Ages 7-10 may tolerate larger groups with clear structure.
- Mixed 11-15 classes may need stricter behavioural boundaries and staffing awareness.
If you are unsure between two ranges, choose the safer and clearer option, then review after launch data.
Level structure that avoids confusion
Use level labels consistently across classes. If “Beginner” means first-term participants in one class, it should not mean “any level welcome” in another.
Inconsistent level meaning causes two problems:
- poor fit requests
- increased waitlist friction
Keep level names practical and map them to expected experience in descriptions.
Examples
Example: Dance school, 20 classes, split by age and level
The school sets beginner ballet (ages 5-7) at capacity 14 and junior ballet (ages 8-10) at 18. Advanced teen classes are capped lower due to choreography space needs.
Example: Martial arts club with strong demand in one age band
A club sees high demand for ages 9-12. They avoid overfilling by opening a second class slot instead of increasing one class from 18 to 28.
Example: Yoga and movement provider with mixed-term entry
They run one full-term progression class and one drop-in style class. Payment profile assignment reflects this, with term collection on one class and card checkout on the other.
UK payment note at class setup stage
If classes have different collection approaches, decide this before publication:
- full-term plans with Direct Debit
- single-class pathways with card
- whether offline bank transfer is accepted
Staff should know how to explain the difference in one sentence. If they cannot, refine class/payment setup before launch.
Related guides
- Term planning and class setup
- Build terms, dates, and holidays
- Studios, teachers, and session generation
- Payments and billing (UK)
Avoid these slips
1. Setting capacity for demand, not safe delivery
This creates avoidable queue conflict and parent dissatisfaction.
2. Leaving age range broad to avoid difficult decisions
Broad ranges often shift complexity into approvals and class experience.
3. Publishing classes with inconsistent level meaning
Families choose classes that are not a fit, then need manual reassignment.
4. Assuming one payment approach fits every class
Mixed delivery models often need different class-level setup.