Attendance and registers

At 8:55pm, your final class has just finished, one child arrived late, another left early, and a parent asks why the register says absent. Use this guide for that exact moment. It explains how to run registers in Classia so attendance stays accurate when classes are busy and staff are tired. The aim is simple: one clear record of who attended, when they attended, and why changes were made. It also makes evening handover easier when different staff cover different days.

What attendance controls in real studio operations

Attendance is not just a teaching record. In most studios it affects:

1. parent conversations about missed sessions
2. coaching decisions on progression and class moves
3. payment and arrears follow-up when attendance is gated
4. trust when disagreements happen

When register discipline slips, every one of those areas becomes harder.

Attendance model in Classia

Classia attendance is session-based. You open a specific class session and mark the roster for that session.

Operationally important points:

• roster is built from active and trial enrolments
• valid statuses are present, absent, late, and excused
• unmarked clears an existing mark
• each enrolment can have one attendance record per session
• the app keeps who marked and when, so later checks are possible

That structure is why same-day corrections are worth doing properly.

A practical attendance rhythm for small teams

In a typical small UK dance school, this rhythm works well:

Before class

• open the session register
• check blocked rows before the door rush
• decide who is handling late arrivals updates

During class

• mark clear absences early
• use late only when arrival happens after start
• avoid guessing attendance for pupils not yet seen

After class (same day)

• resolve unmarked rows
• correct obvious mistakes while memory is fresh
• save and confirm last-updated details

Friction moment: if corrections wait until two days later, staff usually end up reconstructing from memory and messages.

Status meanings that keep decisions consistent

Present

Learner attended the session.

Absent

Learner did not attend and no attendance was observed.

Late

Learner attended but arrived after session start.

Excused

Learner did not attend, with accepted context by studio policy.

Unmarked

No final register decision recorded yet, or an existing mark has been cleared.

One sentence definitions like these stop staff from interpreting statuses differently.

Payment gating and attendance

Classia checks payment clearance at enrolment/session date level before allowing attendance to be recorded. If payment is not cleared, that row is blocked and cannot be marked until resolved.

This is deliberate. It prevents hidden drift where attendance looks complete but payment control says otherwise.

For bulk actions, "Mark all present" only succeeds when all roster entries pass payment checks.

Attendance workflow example (structured text asset hook)

Use this flow text as a printable process or visual later.

• Input: class session and roster (active + trial enrolments).
• Gate 1: confirm payment clearance state for each enrolment against session date.
• Gate 2: mark status per learner (present, absent, late, excused).
• Save step: write records with marker identity and timestamp.
• Correction step: switch to unmarked or a different valid status if a mistake is found.
• Review step: check counts and unresolved rows before ending admin block.
• Exception branch: if payment blocked, resolve payment path then return to register.
• Session branch: if class not delivered, cancel session with explicit reason instead of ignoring register.

Register correction standards

Corrections are normal. Quiet changes with no ownership are not.

Useful correction standard:

1. fix on the same day when possible
2. confirm whether change is factual (late vs present) or policy-based (excused)
3. check parent communication if previous status triggered a message
4. keep one owner for final register close each day

This avoids cross-team confusion where everyone assumes someone else fixed it.

Session cancellations and register truth

When a class cannot run, cancel the session with a clear reason. Do not leave it scheduled and hope staff remember later.

Common reason categories include:

• teacher unavailable
• venue unavailable
• weather
• holiday
• low attendance
• admin error
• other

Clear reason coding protects timeline accuracy and avoids disputes later.

Safeguarding in attendance work

Attendance handling for under-18s needs calm precision.

Key habits:

1. limit register access to authorised account roles
2. keep notes factual and minimal
3. avoid sharing child attendance details in broad chat groups
4. confirm identity before discussing attendance with adults

A tidy register is a safeguarding control, not only an admin convenience.

UK scenarios

Example: Dance school with 18 classes and 136 pupils

Registers were marked after classes ended, often in one late batch. Late arrivals were forgotten and absent counts were wrong. They switched to in-session marking plus a 15-minute same-day closeout.

Register corrections dropped by more than half in four weeks.

Example: Taekwondo club with strict payment gating

One Tuesday class had 3 blocked rows due to unpaid due items. Staff stopped overriding by memory and used a fixed payment-check script before re-opening marks.

Fewer parent disputes on both attendance and fees.

What this is not designed for

This attendance approach is not designed for delayed, memory-based reconstruction weeks later. It is also not designed for informal status labels outside defined register states. If your studio needs exceptional handling, document it clearly and keep owner accountability explicit.

Related guides

• Mark and correct registers
• Payment clearance before attendance
• Session cancellations and register accuracy
• Enrolments and status management
• Schedules, due items, arrears, and offline payments
• Access, roles, and visibility troubleshooting

Related feature

• Class attendance software

FAQ

Who can mark attendance?

Authorised account users with relevant class/session access can mark and correct registers.

What if we need to clear a wrong mark?

Set that learner to unmarked, then re-apply the correct status.

Does Mark all present skip blocked payment rows?

No. It requires all rostered entries to pass payment checks.

Should we mark excused for all known holidays?

Only where your studio policy uses excused for that case. Keep policy explicit.

Can cancelled sessions still appear in history?

Yes. They remain visible with cancelled status and reason, which protects accuracy.

How often should we review attendance quality?

At least weekly, plus same-day closeout for active teaching days.

Which page should we read next?

Read Mark and correct registers for step-by-step page handling during live sessions.