The cancellation policy that actually works (vs. the one you put on the booking page)
The written policy clients see is one thing. The way it actually gets enforced is another. Here's both, in language you can copy.
Last post made the case that most stylists who handle cancellations well have a strict-looking policy and a lenient-in-practice enforcement habit. This post is the actual language for both — the official document clients see, and the unofficial decision tree that determines whether the policy ever gets invoked.
The official policy (what clients see)
This is the version that goes in the booking confirmation email, on your booking page, and in the new-client welcome message. Strict enough to deter, vague enough to leave room for judgment.
Cancellation policy
24-hour notice, please. Less than that, and there's a 50% charge to the card on file. No-shows are billed in full.
We get that life happens — if something comes up, let us know as soon as you can and we'll figure it out.
Three things this language does:
1. The number is specific. "50%" and "in full" are concrete. You're not asking clients to interpret what "appropriate fee" means; you've named it.
2. The threshold is clear. 24 hours. Not "reasonable notice." A clear number is easier to enforce later because the client knew where the line was.
3. The last sentence is the escape valve. "We get that life happens" is your room to be lenient when you want to be. It doesn't commit you to anything; it just signals that you're a person and not an algorithm.
I'd suggest writing your own version of those three sentences in your own voice. Read it out loud to make sure it sounds like you. Then put it everywhere — booking page, confirmation email, the new-client welcome text.
The unofficial policy (how you actually enforce)
This is the decision tree. It doesn't appear anywhere a client sees. It's how you actually decide whether to charge.
The five-question test
When a cancellation triggers the policy, run these questions in order:
- Is this a first-time offense for this client? → If yes, wave.
- Is the reason real (illness, family emergency, weather)? → If yes, wave.
- Have they been a regular for more than 6 months? → If yes, wave.
- Did they ghost (no text, no call, no-show)? → If no, ask before charging.
- Are you actively trying to fire this client? → If no, wave.
If you've answered "no" to every question and you'd still rather not charge — that's your gut telling you something. Wave it.
My opinion on who should actually get charged, after running the five-question test: repeat offenders (third no-show or third same-day cancel within a few months), brand-new clients who book a $200+ service and ghost, and clients you've already privately decided you don't want back. For everyone else, the fee exists as deterrent, not revenue. Push back if your situation calls for a different threshold.
The language for the wave
When you decide not to charge — which will be most of the time — the text matters. The wave should be light, friendly, and small. You're not making a big deal out of being generous. You're handling it like a normal human.
Hey Sarah — totally fine, things happen. I'll get you on the books for next week. No charge.
That's it. No "policy this time only, but next time…" No "I'll let it slide." Just "totally fine" and the rebook. The client doesn't remember the policy because the policy never got invoked.
The language for the charge
When you do decide to charge, the text is different. Short, factual, non-judgmental. You're not lecturing; you're processing.
Hi Tara — went ahead and ran the cancellation fee on your card per the policy ($60). Let me know if anything's off — happy to chat if there's context I'm missing.
The phrase that does the work: "if there's context I'm missing." You're explicitly leaving an opening for the client to tell you a real reason. If she does, you reverse the charge. If she doesn't reply, you've made the charge stick without burning the bridge.
The Yelp-review hedge
If you're going to charge — especially a first-time charge — you want to communicate it in a way that doesn't escalate. Two specific habits help:
Tell them before you charge. Wherever possible, give them the chance to explain. The text above does this implicitly ("if there's context I'm missing") but a separate "before-I-run-the-card" text is better for new clients you don't know well.
Document the decision quietly. Write down why you charged in your client notes. If they Yelp-bomb you later, you have a fact-based response: "Charged per our written policy after the third same-day cancellation in 90 days. We'd communicated about the previous two." Calm. Factual. Hard to argue with.
What this whole thing buys you
A strict-looking policy on paper. A lenient enforcement habit in practice. The combination keeps your best clients comfortable (because they never see the policy invoked) and your worst clients controllable (because the policy is real when you decide to use it).
The honest cancellation strategy isn't really about the policy. It's about the recovery — filling the slot beats charging the fee, every time. The policy is the backup.
Related reading
- Should you charge a cancellation fee? — the longer argument for the strict-policy + lenient-enforcement approach.
- How to fill a same-day cancellation — the recovery playbook that makes the fee policy a backup, not the front line.
Next up: how to use color processing time for admin (until you have software to fill it).