If you need one page to keep nightly register admin under control, use this one. It explains how to mark attendance quickly, how to correct mistakes safely, and how to avoid accidental data drift when classes are busy. The steps are based on how the attendance page actually behaves in Classia. Follow this process and you will spend less time arguing with yesterday's register.
Start with a practical checklist
Before you mark anything, run this quick check:
- are you in the correct class session date?
- do all roster names match expected attendees?
- who is responsible for final corrections tonight?
- are blocked payment rows already identified?
This takes less than two minutes and prevents most wrong-session edits.
Marking the register in-session
Open the session attendance page from session actions and work row by row.
For each learner:
presentwhen attendance is confirmedabsentwhen not seen in the sessionlatewhen arrival is after startexcusedwhen your studio policy supports that absence reason
If a saved status is wrong, switch it immediately. Do not keep mental notes for later.
When to use Mark all present
Mark all present is useful in stable classes where everyone is known to be attending. It is not a substitute for checking blocked rows.
Use it when:
- class has started and attendance is near-complete
- you have no unresolved payment-gated rows
- one owner will still review late arrivals before final save
Avoid it when:
- several learners are still arriving
- you already know absences are likely
- payment checks are unresolved
Correcting a mistake without creating another
Most corrections are simple if done quickly.
Correction method:
- locate learner row in same session
- choose new status, or set unmarked to clear
- save attendance
- re-check totals for present/absent/late/excused/unmarked
If you are unsure whether a learner was present or late, confirm with coach notes first. Guessing creates repeated parent messages.
What unmarked means in practice
Unmarked is not a fifth attendance outcome. It means "no final mark recorded" for that session row.
Use it when:
- a previous mark was entered by mistake
- attendance should be re-confirmed before final status
- you need to clear a stale value during cleanup
Leaving too many rows unmarked overnight is a warning sign that process ownership is unclear.
Keep accountability visible
Attendance quality improves when staff know records are traceable. Classia surfaces latest update timing and marker identity so teams can resolve conflicts quickly.
Practical habit: if a correction is sensitive, note briefly in your daily handover why it changed. One sentence is enough.
Mobile reality after class
Many small studios close registers on phones after classes end. Keep mobile edits disciplined:
- finish one session fully before moving to next
- avoid switching between multiple class tabs
- save after meaningful status blocks, not just at the end
This cuts accidental overwrites on poor venue Wi-Fi.
Examples
Example: Dance school with 42 pupils on a Monday evening
Two teachers marked from memory after classes. Late arrivals were often logged absent. They switched to immediate row updates and one final owner per class.
Parent correction messages dropped the next week.
Example: Karate club with mixed-age classes
A coach used Mark all present in a session where three learners arrived late. Admin then corrected all three rows to late before closeout.
Accurate progression records and fewer grading disputes.
Example: Tuition centre with one admin and two sites
The admin reviewed each site's final register at 9:30pm and used unmarked to clear uncertain rows pending teacher confirmation.
Cleaner next-day attendance exports and less rework.
Related feature
Avoid these slips
1. Marking from memory after leaving the venue
Small recall gaps create many avoidable corrections.
2. Using Mark all present as default
It is fast, but often wrong when arrivals are staggered.
3. Leaving uncertain rows unmarked overnight
Unmarked rows accumulate and reduce register trust.
4. Correcting status without re-checking totals
Counts then stop matching real class behaviour.
5. Multiple staff editing same session without ownership
You lose clarity on final register truth.
Related guides
- Attendance and registers
- Payment clearance before attendance
- Session cancellations and register accuracy
Avoid these slips
1. Marking from memory after leaving the venue
Small recall gaps create many avoidable corrections.
2. Using Mark all present as default
It is fast, but often wrong when arrivals are staggered.
3. Leaving uncertain rows unmarked overnight
Unmarked rows accumulate and reduce register trust.
4. Correcting status without re-checking totals
Counts then stop matching real class behaviour.
5. Multiple staff editing same session without ownership
You lose clarity on final register truth.