Start here when you are preparing a full term, not just adding classes one by one. It explains how to plan term structure, class records, and launch sequencing so the first month stays manageable. You will learn what to decide before you start entering data, and what to hold back until checks are complete. The examples are written for UK studios where class delivery, parent communication, and payment timing are all live pressures at the same time.
Start with the term map, not the class list
A common mistake is opening the classes page and building timetable rows immediately. It feels productive, but it usually creates correction work later.
Start with a term map first:
- Term name and date boundaries.
- Planned closure weeks and holiday impact.
- Which classes are launch wave one.
- Which classes stay draft until staffing is confirmed.
Concrete example: one dance school built 18 classes before finalising half-term closure dates. They spent the next evening checking generated sessions manually.
Decisions to lock before data entry
1. Term pattern for the year
Choose clear term naming and date logic across Autumn, Spring, and Summer. Keep it stable so staff can filter quickly and parents see familiar language.
2. Room and venue limits
Capacity should come from real room and staffing limits. Do not set capacity by demand alone.
Concrete example: a hall can hold 22 children physically, but safe movement and supervision may cap practical delivery at 16.
3. Age bands and progression expectations
Define age ranges based on delivery reality, not marketing copy. This helps approvals and reduces parent confusion.
4. Teacher availability and backup plan
If one teacher covers six classes, plan contingencies before launch week. Build draft classes for uncertain slots and publish in stages.
5. Payment approach by class type
Decide which classes use term-based collection and which allow single-class payment routes. This decision belongs in planning, not after public links are shared.
Build one reference class before scaling
Use one class as your model. Set every field carefully:
- day and time
- studio
- teacher
- capacity
- age range
- class copy
- status
Then check generated sessions and linked records. Once that class is clean, replicate its structure.
This step prevents pattern errors. Pattern errors are expensive because they spread quickly across the timetable.
Practical sequence for a full-term build
Step 1: Create term and validate dates
Confirm start and end dates and ensure they match your internal and public calendar plan.
Step 2: Add studio and teacher records needed for launch wave one
Do not wait for every future class to be staffed. Set up the records you need for classes you plan to publish first.
Step 3: Build launch classes in draft
Create classes with realistic limits and clear descriptions. Keep them in draft while checks are running.
Step 4: Review generated sessions
Scan sessions for day, time, and closure exceptions. Record cancellations with explicit reasons where needed.
Step 5: Assign payment profiles for launch classes
Confirm method rules and communication wording before classes go public.
Step 6: Publish in controlled waves
Publish only classes that pass checks and have clear ownership for request handling.
Real UK planning scenarios
Example: Dance school planning 24 classes across three venues
The school launches 10 classes first, then 8, then 6. The first wave includes classes with confirmed staff and room availability. The last wave stays draft while waiting on two teacher contracts.
Enrolment starts smoothly without a chaotic first-week queue.
Example: Martial arts provider with 12 children’s classes and 4 adult classes
They separate class setup by age band and assign distinct approval owners. Children’s classes are checked for guardian assumptions before publication. Adult classes with self-enrolment pathways are reviewed separately.
Approval decisions stay consistent across mixed cohorts.
Safeguarding checks during planning
Term planning can feel operational, but safeguarding decisions are embedded in it.
Check these before publishing child classes:
- age ranges match teaching and supervision reality
- request approvers understand guardian requirements
- class descriptions avoid ambiguous eligibility language
If there is uncertainty, keep class status in draft until it is resolved.
Payment readiness during planning
Payment setup is part of term planning because families ask payment questions as soon as enrolment opens.
Use plain UK wording internally and externally:
- Direct Debit collection day and expected clearing window.
- When card checkout is available.
- How offline bank transfer is recorded.
- How arrears are handled and communicated.
Concrete example: “Direct Debit requests are submitted on Monday. Most banks show collection by Wednesday or Thursday.”
One-hour term review meeting that keeps plans usable
Before publishing your first wave, run a short meeting with whoever makes launch decisions. Keep it to one hour and a clear agenda.
Agenda that works:
- Review launch classes only, not the whole year.
- Confirm unresolved staffing or venue risks.
- Confirm payment language for each launch class type.
- Confirm queue owner schedule for the first five working days.
- Confirm what remains in draft and why.
This meeting is not about perfecting every detail. It is about preventing preventable confusion in week one.
Concrete example: a studio with 19 classes used this meeting to hold four classes in draft because one venue contract was still pending. They launched 15 classes cleanly and avoided retraction messages to parents.
Signals your term plan is slipping
Watch for these warning signs before launch:
- class names are still changing daily
- capacity numbers move without clear reasons
- staff give different answers on who reviews requests
- payment timing wording is still being rewritten
If two or more signals are present, delay publication and stabilise first. Publishing unstable records creates larger queues, and those queues are much harder to tidy once families are already waiting.
Practical handover between planning and live delivery
The handover from setup to daily operations often gets skipped. Use a short handover note with these five lines:
- Which classes are live now.
- Which classes remain draft.
- Who reviews requests tomorrow.
- One payment timing note for staff.
- One safeguarding watchpoint.
When this note exists, teams make fewer contradictory decisions. Without it, you get the Monday morning issue where one staff member assumes a class is live and another treats it as draft.
Related guides
- Build terms, dates, and holidays
- Create classes, capacity, and levels
- Studios, teachers, and session generation
- Getting started
- Set up your first term
- Enrolments and status management
Related feature
FAQ
How many classes should we publish in wave one?
Publish only classes with confirmed staffing, venue, payment readiness, and queue ownership.
Should we set all future terms now?
You can set future terms, but focus quality checks on the current launch term first.
What if a teacher is not confirmed yet?
Keep those classes in draft and publish later.
How do we handle classes with high demand but low safe capacity?
Use clear capacity limits and consistent waitlist decisions.
Is this process still valid for very small studios?
Yes. Small teams benefit most from clear sequence and fewer corrective loops.
What page should we read next?
Read Build terms, dates, and holidays if you are finalising calendar structure.