Decide what the policy is trying to protect
A cancellation policy is not primarily a punishment system. It protects time that cannot easily be resold, gives students predictable expectations and reduces case-by-case negotiation. If every late cancellation becomes a personal conversation, the tutor spends emotional and administrative energy on a rule that should already be clear.
Start by identifying the operational problem. Do you lose income because students cancel an hour before class? Do no-shows block prime-time slots? Do you travel and need reliable scheduling? The policy should solve the pattern you actually experience rather than copy someone else's wording.
This is operational guidance, not legal advice. If you sell lessons independently, local consumer law, payment rules or contract requirements may affect what you can enforce. If you teach through a marketplace, its platform policy takes precedence over your personal preference.
Choose a notice window you can apply consistently
The exact notice period can vary. Some tutors use 12 hours, others 24 hours or a platform-defined rule. The important operational question is whether you can apply the rule consistently without inventing a new exception every week.
A notice window should be easy to state: cancellations before the deadline can be rescheduled; cancellations after the deadline may be charged or treated according to the platform's rules. Avoid vague phrases such as “please give enough notice” because students cannot know what counts as enough.
If you make a first-lesson exception or one emergency exception, define that as a deliberate courtesy rather than silently creating a second policy.
Separate cancellations, reschedules and no-shows
These events create different operational costs. A student who moves a lesson three days in advance gives you a chance to refill the slot. A student who cancels ten minutes before class usually does not. A no-show also consumes the teaching window because you were present and ready.
Write the policy so the categories are distinguishable. For example: advance reschedule, late cancellation and no-show. If your platform automatically handles one or more of these, match your wording to the platform rather than contradicting it.
Students are more likely to accept a boundary when they understand it before the first conflict.
Define exceptions before emotions are involved
Emergencies happen. Decide in advance how much discretion you want. You might allow one courtesy exception, treat documented emergencies differently, or simply use the platform policy in every case. Any of those can work if the rule is predictable.
Avoid creating an exception so broad that the policy becomes meaningless. “I understand if something comes up” can turn every late cancellation into a negotiation. A better approach is to state that genuine emergencies can be reviewed individually while routine schedule changes follow the normal rule.
Keep records simple: date, event and whether an exception was used. You do not need a complex disciplinary system.
Use plain language students can understand
A useful policy can fit in a short paragraph. Example framework: “Lessons can be rescheduled without charge until [notice window] before the start time. Later changes and no-shows follow [platform or tutor rule]. If there is a genuine emergency, message me and I’ll review it case by case.” Adapt the wording to the service you actually use.
Do not hide the policy in a long welcome document if it matters financially. Mention it during onboarding or place it where students can find it easily.
The best policy reduces conversation, not increases it. When a late change happens, refer calmly to the existing rule and move on.