Record an agreed outcome for each class, then calculate the family’s bill and the teacher’s pay from that same record. Shared outcomes keep billing and payroll aligned because corrections reach both calculations, while each applies its own charge or pay rule.
What is a class outcome?
A class outcome says whether a scheduled class happened and, if the class did not happen, why. A useful record separates completion, student cancellation, student no-show and teacher no-show. The outcome also needs supporting details: who cancelled, when notice arrived, whether the teacher waited and whether an admin approved an emergency exception. A status label without that evidence cannot explain every financial decision.
Keep the scheduled class attached to the outcome. The student, teacher, start time and duration give the decision context. A cancellation message copied into a finance note loses meaning if nobody can tell which class the message concerns.
A shared record does not mean identical financial treatment. The family charge and teacher compensation answer different questions. Record what happened before deciding what money follows.
Why do separate attendance, billing and payroll records drift apart?
Separate records drift when a correction reaches one person but never reaches everyone who calculates money. The teacher marks a student absent, the admin later accepts an emergency explanation, and billing uses the revised decision. Payroll may still use the original note. Both people can follow their instructions carefully and still calculate from different evidence.
Avoid asking the finance team to interpret messages again at the end of the period. A private message may establish when notice arrived, but the agreed outcome belongs with the scheduled class. Billing and payroll should reference that decision rather than copy the message into separate working notes.
An emergency exception shows why shared evidence matters. In Halqora, the exception removes the family charge; teacher compensation for a student no-show still follows the waiting rule. Consistency means applying the correct rules to the same record, not making every adjustment produce matching financial changes.
Your teacher payroll rules based on class outcomes should explain that distinction before a dispute occurs.
Which outcomes create a family charge and teacher pay?
A useful outcome table shows the family charge, teacher compensation and supporting evidence together. The example below uses Halqora’s fixed outcome rules, as of 21 October 2026: rules such as the student notice window and teacher waiting requirement. Read the charge and pay columns separately: a family charge does not establish teacher earnings, and an emergency waiver does not erase the waiting requirement.
| Outcome | Family billed? | Teacher paid? | Evidence needed |
|---|---|---|---|
| Completed on time | Yes | Yes, in full | Completed outcome and lesson report |
| Completed, teacher 3 to 5 minutes late | Yes | Class pay minus a flat 5% | Completed outcome, report and admin-recorded late minutes |
| Student cancels at least 3 hours before | No | No | Who cancelled and actual cancellation timestamp |
| Student cancels under 3 hours before | Yes, in full | Set in your written pay policy | Actual cancellation timestamp and approved pay policy |
| Student no-show | Yes, unless emergency-excused | Full pay after waiting at least half the class; otherwise no pay | Student no-show outcome and admin-recorded wait minutes |
| Teacher cancels under 4 hours before | No | No; admin records teacher no-show | Notice timestamp and admin decision |
| Emergency-excused student no-show | No | Student no-show waiting rule still applies | Admin-recorded exception and wait minutes |
The late-cancellation pay entry is general operating guidance, not a statement of Halqora’s teacher compensation for that outcome. Halqora’s class and payroll rules are fixed; the table does not describe settings you can change.
Treat evidence gaps as unfinished decisions. A row that looks complete because someone selected a status can still lack the wait time needed for payroll. Resolve that gap before approving the payment calculation.
How should you handle lateness, waiting, emergencies and connection failures?
Edge cases need evidence that matches the rule being applied. A teacher’s late arrival needs late minutes; a student no-show needs wait minutes; a cancellation needs the actual notice time. An internet failure explains a problem but does not, by itself, decide the financial outcome. Assign the decision to an admin and record the reason with the class.
Halqora gives teachers up to 2 minutes of lateness without a deduction. From 3 to 5 minutes, the deduction is a flat 5% of that class’s pay. Beyond 5 minutes, the teacher loses a minute of pay for every minute late, counted from the scheduled start, with pay floored at 0.
Example: For a 60-minute class, half the duration is 60 divided by 2 = 30 minutes. A teacher who waits 29 minutes for a student no-show does not meet Halqora’s requirement; a teacher who waits 30 minutes earns full class pay. An admin records the waiting time.
For connection failures, keep the explanation alongside the attendance decision. Do not silently replace a no-show with “completed” to make a bill look right. If an admin grants an emergency exception, record the exception explicitly. Your no-show policy for online classes should explain who reviews these situations.
How do Preply, Tutorful, italki and TutorCruncher handle outcomes?
Published policies attach financial consequences to different kinds of evidence. Preply emphasizes notice, Tutorful specifies tutor attendance, and italki sets a waiting expectation. TutorCruncher separates cancellation from chargeability. The policies below were supplied as checked on 21 October 2026. Read each row within its stated scope: a student charge rule does not automatically describe teacher compensation.
| Provider | Situation | Published rule as of 21 October 2026 |
|---|---|---|
| Preply | Student cancellation, notice in hours | More than 12 hours: lesson returns to student balance and tutor is not paid. Less than 12 hours: no return and tutor is paid. |
| Tutorful | Online student no-show, attendance in minutes | Student charged in full when tutor attends at least 15 minutes from scheduled start; no charge if tutor did not attend for the first 15 minutes. |
| italki | Student arrives late | According to italki’s teacher terms, the teacher should wait until the scheduled lesson period ends. |
| Studio Arabiya | Student absence, waiting in minutes | According to Studio Arabiya’s terms, the teacher waits the first 15 minutes, then marks an unexcused absence with no refund or free makeup. |
Preply also says tutors need at least 12 hours’ notice to cancel, according to Preply’s tutor cancellation policy, as of 21 October 2026. Keep teacher-caused and student-caused cancellations distinct in your records.
According to TutorCruncher’s cancellation guidance, as of 21 October 2026, it distinguishes “Cancelled” from “Cancelled but Chargeable” and provides a late-cancellation notice setting in hours. TutorCruncher is a better fit if you need that setting rather than Halqora’s fixed notice window.
Preply’s published rule is a better match if you want a 12-hour student notice window instead of Halqora’s 3-hour window. Neither choice removes the need to keep cancellation evidence. A clear cutoff still needs a trustworthy timestamp.
How do timestamps, reports and approvals make outcomes trustworthy?
Trustworthy outcomes separate evidence from the final decision. Keep the actual cancellation time, require a report for a completed class and give an admin responsibility for exceptions. Review uncertain outcomes before calculating final amounts. A shared record reduces copying, but a shared mistake still reaches billing and payroll unless someone checks the evidence behind the status.
Use a review sequence that everyone understands:
- Identify the scheduled class and preserve the original cancellation notice or attendance explanation.
- Record when the person actually cancelled, rather than when the admin updated the schedule.
- Ask the teacher to record completion with a report, student no-show or student cancellation. Admins resolve other outcomes and enter late minutes, wait minutes and emergency exceptions.
- Review missing evidence before sending invoices or generating payroll. Keep an unresolved decision visible instead of treating an empty field as confirmation.
In Halqora, completed classes need an internal report with a 1 to 5 rating and written feedback. Families do not see those reports. Payroll for the teacher and period waits until reports are in; missing no-show wait time also requires admin review.
Classes already attached to a live invoice or teacher payment cannot simply be edited. Resolve outcomes before financial approval. For waiting decisions, explain the evidence requirement in your policy on paying teachers when a student doesn’t show.
How Halqora handles this
Halqora is management software for online academies. Halqora schedules, bills and calculates teacher pay for one-to-one classes using shared outcomes and fixed outcome rules. The teacher earnings screen uses the same compensation calculation as payroll.
Billing runs create draft invoices for an admin to review and send. Teachers record supported outcomes and internal lesson reports; admins resolve exceptions and record late or wait minutes. Halqora calculates payroll; the academy pays teachers separately.
See how Halqora connects teacher payroll to class outcomes.
Sources
- Preply’s student cancellation policy, checked 21 October 2026
- Preply’s tutor cancellation policy, checked 21 October 2026
- Tutorful’s terms, checked 21 October 2026
- italki’s teacher terms, checked 21 October 2026
- TutorCruncher’s cancellation guidance, checked 21 October 2026
- Studio Arabiya’s terms, checked 21 October 2026
