Use this when…
Use this guide when a lesson has finished and you need to record what happened. Attendance is one of the most important operational fields in TuitionFlow because it affects reporting, billing, parent communication, and tutor payments.
Before you start…
Open the relevant session from Scheduling, a tutor portal workflow, or a lesson-related shortcut. Confirm the date, student, tutor, and subject before changing the outcome. If you are not sure what happened, check with the tutor before saving a final outcome.
Choose the right outcome
Use Attended when the lesson happened. Use No-show when the student did not attend and your policy treats it as a missed lesson. Use Late cancel when the family cancelled inside the chargeable window. Use Excused or early cancellation outcomes where your organisation policy says the family should not be charged. Use tutor-cancelled outcomes when the tutor could not deliver the lesson.
Why attendance matters
Attendance is not just a diary note. It is the signal many downstream workflows use to decide whether a lesson should appear in reports, invoice candidates, analytics, parent history, and tutor payment calculations. Leaving old lessons as Scheduled makes the business look less complete than it is.
Record attendance promptly
Admins should encourage tutors and coordinators to mark outcomes soon after lessons. The longer attendance remains unresolved, the harder it is to remember what happened and the more likely billing or reporting will be delayed.
Add useful notes
If the outcome needs explanation, add a clear operational note. For example, “Parent cancelled at 09:30 for illness” is more useful than “cancelled”. Keep sensitive welfare detail out of ordinary attendance notes unless it is appropriate and necessary.
Check billing before invoicing
Before issuing invoices, review any sessions still marked Scheduled in the invoice period. If your billing policy depends on attendance, confirm outcomes are saved and visible after refresh. Do not claim an attendance-to-billing flow is validated unless you have checked the current saved outcome and the invoice candidate or invoice result.
Common mistakes
Leaving completed lessons as Scheduled.
Using No-show when the family gave notice that should be treated as a cancellation.
Changing historic attendance without checking existing invoices or payouts.
Putting safeguarding detail into an attendance note instead of the safeguarding workflow.
Troubleshooting
If an outcome does not save, refresh the session and try again. If it still reverts, treat that as a defect before relying on billing. If an invoice does not include a lesson, check the attendance, date range, student, family, package, and billing policy. If a tutor cannot mark attendance, check their portal access and session assignment.
Expected outcome
Every past session should show a clear outcome, any necessary operational note, and a downstream billing/reporting status that matches your organisation policy.
