Measure tutor performance by separating teaching quality from reliability: track teacher-caused cancellation, late-cancellation, no-show and lateness rates per period. Use recorded outcomes, compare the previous period, and withhold a reliability rating below 3 recorded classes.
Which teacher reliability metrics matter?
Teacher reliability needs separate measures for cancellations, late cancellations, no-shows and late starts. Keep report timeliness beside those rates because an attended class can still have unfinished administration. Reliability measures whether the teacher met the class commitment. Reliability does not establish whether the teacher explained a lesson well or helped the student progress.
Keep the underlying class list available beside every rate. A percentage should lead you to the affected classes, their notice times and their recorded outcomes. A combined status can help you find a problem, but the status should not replace that review.
For teaching quality, read lesson feedback and review student progress separately. In Halqora, lesson reports are internal: teachers submit a rating and written feedback for admins, and families do not see those reports.
Keep reliability alongside your other KPIs for online academies. Do not turn an attendance dashboard into a complete judgment of a teacher.
How do you calculate each rate?
Calculate a reliability rate by dividing the relevant teacher-caused outcomes by the eligible classes in the same period, then express the result as a percentage. Keep the denominator explicit. Cancellations and no-shows use the period’s recorded class outcomes; lateness uses completed classes. Report timeliness also uses completed classes, because a cancelled class does not need a completion report.
A simple scheduled-class denominator can mislead when the schedule still contains unresolved classes. Halqora counts recorded outcomes: completed, cancelled, missed by teacher, missed by student and rescheduled. Open scheduled or pending entries and unrecorded recurring events do not count.
Use a consistent calculation process:
- Select the reporting period and resolve unfinished class outcomes.
- Separate teacher-caused events from student-caused events.
- Count the eligible classes for each metric.
- Calculate the rates and retain the underlying counts.
- Compare the result with the previous period using the same definitions.
Do not add overlapping rates together. A late cancellation may explain a no-show classification; the notice detail is useful without treating the event as another missed class.
Which example thresholds should you use?
Halqora’s status thresholds provide an example for reviewing reliability, rather than an industry benchmark. The cancellation thresholds are 3%, 8% and 15%; the no-show thresholds are 0%, 2% and 5%; the lateness thresholds are 5%, 15% and 25%. These are fixed defaults, not configurable targets. Read the separate rates before deciding what action is appropriate.
| Metric | Formula | Example thresholds (Halqora defaults, %) | What to check before acting |
|---|---|---|---|
| Teacher cancellation rate | Teacher-cancelled classes / recorded class outcomes | 3% / 8% / 15% | Responsibility, notice and correct final status |
| Teacher no-show rate | Teacher no-shows, including cancellations under 4 hours’ notice / recorded class outcomes | 0% / 2% / 5% | Admin resolution; converted late cancellations count once |
| Lateness rate | Completed classes more than 2 minutes late / completed classes | 5% / 15% / 25% | Admin-entered late minutes and the grace period |
| Late-cancellation rate | Teacher cancellations inside the notice window / recorded class outcomes | No separate teacher status thresholds supplied | Notice detail; under 4 hours becomes a no-show after admin resolution |
| Lesson reports on time | Reports filed within 24 hours of class end / completed classes | No percentage threshold supplied | Missing reports, submission time and completed status |
Fewer than 3 recorded classes means Not enough data. Passing that minimum permits a score; it does not justify a major decision without reading the class history.
The table keeps late-cancellation detail visible without implying Halqora has a separate teacher late-cancellation status band. Report timeliness is also a separate administrative measure, rather than another attendance penalty.
How do you attribute responsibility fairly?
Fair teacher attendance tracking assigns responsibility to the person who caused the disruption. A student no-show belongs in the student’s record, not the teacher’s no-show numerator. A teacher cancellation belongs in the teacher’s record. Confirm the final outcome and notice time before using the event in a coaching conversation or a reliability score.
Separate the outcome from the source of the information. In Halqora, teachers can record completed classes with reports, student no-shows and student cancellations. Admins resolve other outcomes and record teacher late minutes, student no-show wait minutes and the emergency exception.
A cancellation under 4 hours’ notice becomes a teacher no-show when an admin records or approves that outcome. Halqora does not convert the class automatically. Review unresolved entries before relying on the period’s score.
Keep student-caused disruptions visible through student attendance tracking. A teacher may need help managing an unreliable timetable even when the teacher’s own record is sound. Discuss the schedule problem without assigning the student’s missed classes to the teacher.
How do you compare periods and find weekday or hour patterns?
Previous-period comparisons show whether a teacher’s reliability is improving or worsening under the same definitions. Read the change beside the class counts and the individual rates. Then inspect weekly, weekday, hour and notice patterns. A concentrated scheduling problem calls for a different response from unrelated absences spread across the teacher’s timetable.
Compare periods of equal length and check whether the teaching load changed. A rate can move because the numerator changed, the denominator changed, or both. A smaller workload does not remove the need to investigate a missed class, but the workload affects how you interpret the percentage.
Use the pattern view to ask concrete questions. Does lateness cluster around a particular teaching slot? Do cancellations arrive close to the notice deadline? Did the pattern begin after a timetable change?
Agree which time zone you are discussing before changing a recurring slot. Keep scheduling rules in each IANA time zone. Treat a pattern as a question to investigate, rather than proof of its cause.
How do marketplaces score tutor reliability?
Marketplace reliability policies are platform rules, not benchmarks for your academy. As of 21 October 2026, Preply requires tutors to give at least 12 hours’ cancellation notice and tracks tutor cancellations over 90 days. According to Preply’s tutor cancellation policy, repeated cancellations and absences can reduce search visibility. Your coaching process need not copy that marketplace consequence.
As of 21 October 2026, italki’s instructor terms say teachers generally cannot cancel or reschedule within 24 hours of the lesson except in true emergencies. These policies demonstrate different notice rules, rather than evidence that a particular cancellation percentage is acceptable everywhere.
Attendance reporting is also available outside marketplaces. As of 21 October 2026, Pencil Spaces’ classroom page advertises organization-wide engagement and attendance reports. Pencil Spaces may suit an academy whose priority is reviewing attendance alongside engagement across the organization.
As of the same date, Wise (wise.live)‘s scheduling page advertises Quality Control metrics for student attendance patterns and session completion rates. Wise (wise.live) is worth considering when those measures match your reporting needs. Neither vendor claim establishes an industry cancellation benchmark.
How do you turn reliability numbers into coaching?
A coaching conversation should connect a verified pattern to a practical change. Show the teacher the affected classes, explain the calculation, and invite the teacher’s account before agreeing on an action. Keep the discussion about attendance commitments and classroom administration. Do not use a reliability percentage as a substitute for reviewing teaching quality or understanding an emergency.
Use a short review sequence:
- Confirm the outcomes, responsibility and notice times together.
- Compare the current period with the previous period.
- Discuss recurring weekday or hour problems and possible schedule changes.
- Agree on an action and review the result in the next reporting period.
Keep coaching separate from explaining established pay rules. Your teacher lateness policy should make the distinction clear. Halqora’s fixed rules allow up to 2 minutes late without a deduction; 3 to 5 minutes costs 5% of that class’s pay. Beyond 5 minutes, each minute late removes a minute of pay, with a floor of 0.
How Halqora handles this
Halqora is management software for online academies. Its teacher reliability analytics show per-teacher rates, previous-period changes, fixed status thresholds, and weekly, weekday, hour and notice patterns. Below 3 recorded classes, Halqora shows Not enough data.
Admins resolve disputed outcomes and enter late minutes. Classroom join and leave events are logged, but those logs do not calculate lateness or provide an attendance report screen. Lesson reports are due within 24 hours of class end, and payroll for the period waits until completed-class reports are in. Use these records to support coaching and explain decisions.
Sources
- Preply’s tutor cancellation policy, checked 21 October 2026
- italki’s instructor terms, checked 21 October 2026
- Pencil Spaces’ virtual classroom features, checked 21 October 2026
- Wise (wise.live)‘s tutor scheduling features, checked 21 October 2026
