Absences are hard to explain
If attendance is recorded later, it is unclear whether the student was absent, excused, transferred, or simply forgotten.
Attendance
Turn every lesson into a reliable attendance record
Record who attended, who missed, and how each lesson affects billing, so attendance stays connected to invoices, balances, and reports.
No card required. No migration needed to test the attendance flow.
Attendance breaks billing when lesson context is missing
The mark itself is not enough. Schools need to know which lesson it belongs to, why it changed, and how it should affect the rest of the workflow.
Billing needs reconstruction
Administrators have to rebuild what happened from notes, chats, calendars, and teacher messages.
Reports show problems too late
Missed lessons and attendance trends become visible only after billing or reporting is already behind.
Attendance should be recorded where the lesson happened.
Open the lesson, mark each student, keep absence reasons and billing treatment visible, and let the rest of the workflow use the same record.
One attendance record, used across the whole workflow
Attendance is recorded once in the lesson context, then reused for billing, balances, and reports.
1
Lesson context
Record attendance inside the lesson, with group, teacher, students, and schedule already known.
2
Student status
Mark present, absent, excused, or transferred before billing starts.
3
Billing and reports
Use the same attendance record for invoices, balances, and operational reports.
Review attendance across lessons
See which lessons already have attendance, where marks are missing, and which records may need attention before billing.
Mark attendance inside the lesson context
Administrators do not need to recreate the lesson manually. Students, lesson time, and billing treatment are already attached to the record.
- Mark all present when the lesson is normal
- Keep notes next to the student
- Save attendance once the lesson is checked
Typical admin question
Should this missed lesson be charged, excused, or transferred?
Choose the attendance result while the lesson context is still clear, so billing does not need to be reconstructed later.
Every attendance decision can affect billing
When a student is absent, excused, or transferred, the invoice can reflect that decision automatically instead of being corrected later.
Mark attendance during daily operations
Administrators can mark attendance during the day, while the lesson is still fresh and before billing depends on it.
Attendance connects the operational chain
Schedule creates the lesson, attendance confirms what happened, and billing, reports, and payouts can use the result.
Schedule creates the lesson
Teacher, group, time, and students are already known before attendance is marked.
Billing uses lesson facts
Invoices and balances can reflect what actually happened, not a reconstructed month-end spreadsheet.
Reports use the same records
Attendance risks, activity, revenue, and operational summaries can start from the same lesson history.
Workflow guides
Learn how attendance affects the next steps
Use these guides to connect attendance decisions with scheduling, invoices, and teacher payout calculations.
Record attendanceSee what to mark, when to mark it, and how billing treatment affects the result.Build the schedule firstUnderstand why attendance should start from approved lesson records.Explain student invoicesFollow how attendance decisions become charged, free, discounted, or adjusted invoice rows.
Check how attendance affects billing before you move everything
Start with demo data or mark a few real lessons to see whether attendance statuses, absences, and billing treatment match your school process.