Most studios handle initial approvals well, then lose clarity once term life gets messy. Injuries happen. Families travel. Pupils stop, then want to return three weeks later. This guide explains how to run those transitions in Classia without creating register confusion or billing disputes. It is written for real term pressure, not ideal conditions.
The first mistake to avoid
Do not treat every absence as the same thing.
A one-week school trip is not a deactivation. A six-week injury break is not always inactive. A learner who never returned after trial should not stay trial forever.
When status choices are vague, the cleanup lands at the busy times, usually just before payment due dates.
A practical transition playbook
Use this decision line:
- choose
trialfor short, defined assessment participation - choose
pausedfor temporary breaks with likely return - choose
inactivewhen the placement has ended - move back to
activeonly after return is confirmed
Keep the decision reason in your team notes, especially when parents are likely to ask for context later.
Handling trials without drift
Trials work best when they have a clear public form check before the first session starts.
Set three points up front:
- trial length (for example, two sessions)
- who confirms progression decision
- when parent receives outcome message
Concrete example: a ballet school sets two trial sessions for ages 4-6 on Saturdays. Decision is made after session two, with confirmation message sent by Monday 6pm.
Without this structure, trial records stay open and staff forget who needs follow-up.
Using pause safely and clearly
Pause is for temporary interruption, not quiet removal.
Good pause cases:
- short-term injury with expected return
- temporary transport issue
- exam-period break with return date discussed
Add a review date as soon as you pause. If no review date exists, paused records become hidden backlog.
Friction moment: paused records often look tidy in the list, but at month end they create awkward parent messages because nobody checked return plans.
When to deactivate
Deactivate when the placement has ended for now. This may follow a family decision, a completed trial that does not continue, or an explicit withdrawal.
Deactivation should be deliberate because it changes how the record is treated in live operations.
Use plain language with families:
- "We have marked this enrolment inactive from today."
- "If you want to return next term, we can review suitable class options."
This avoids the common confusion where families think they are "on hold" when the record is actually closed.
Reactivating with less rework
Reactivation is possible, but do not rush it.
Before moving back to active:
- confirm class capacity and fit still hold
- confirm responsible adult context for under-18s
- review payment schedule and due item expectations
Reactivation without these checks often creates attendance surprises in the next register and payment queries the same week.
Payment impact in UK terms
Status transitions influence billing operations, and families notice quickly if communication is unclear.
In class-level pause and deactivate actions, Classia stops future due line items linked to that enrolment from the reference date onward. That helps prevent charging for sessions a learner will not attend.
Still, staff should review payment schedules after transitions and communicate clearly:
- Direct Debit collections already submitted may still appear in bank timelines.
- Card charges already captured remain recorded and may need manual explanation if timing overlaps with a pause.
- Offline bank transfer entries should reflect actual receipt dates, not planned attendance.
Practical wording for parents: "We paused from 5 November. Future due items from that date were adjusted, but a Direct Debit submitted before that date may still clear."
Safeguarding on status-change days
When a child's status changes, teaching and supervision assumptions may also change.
For under-18 records, quickly verify:
- responsible adult linkage still matches family context
- contact pathway is current for attendance-related communication
- only authorised account staff are making status changes
This is especially important when cover admins are handling backlog during holidays.
Examples
Example: Dance school injury pause
A class of 15 had one pupil with a six-week ankle injury. Admin paused the enrolment with a review date three weeks later and a second review before return.
No accidental attendance marks and clear payment explanation to the parent.
Example: Martial arts trial decision
A club ran 12 trial places in September. Ten moved to active after two sessions, two moved to inactive. The admin processed all twelve outcomes in one Friday block.
No lingering trial records and clearer coach expectations.
Example: Music school reactivation backlog
A school had 9 paused learners after exam season. They reactivated only 5 after checking capacity and payment context; 4 stayed paused with planned follow-up dates.
Fewer timetable clashes and less billing confusion in the first week back.
Related guides
- Enrolments and status management
- Enrolment statuses in practice
- From request to enrolment records
- Mark and correct registers
Avoid these slips
1. Leaving trial status open indefinitely
Trial needs a clear decision date.
2. Using paused as a polite inactive state
If return is not realistically expected, inactive is clearer.
3. Reactivating without checking payment context
Families then receive conflicting messages about what is due.
4. Deactivating quick absences
Short temporary breaks usually need pause, not full closure.
5. Changing child statuses without adult linkage check
This can create safeguarding and communication risk.