Academy › Build › Bookings and orders

When you waive the charge (and when you don't, no matter how much they push)

With a two-question filter, you decide before the phone even rings what you'll let slide: a genuine emergency, always, and other surprises once a year per client, not based on how likable the person asking happens to be.

By Yodai · Published September 6, 2026 · Updated October 13, 2026

Writing a cancellation policy is the easy part. The hard part comes the day someone asks you, rightfully, not to enforce it. The phone rings on a Tuesday at nine at night. "I can't make it tomorrow, my mom's in the hospital, please don't charge the deposit." You let it go, of course. Thursday it rings again: "I got a flat tire, I'm running late for everything, don't charge me." You let that go too, because saying no in the moment feels tacky.

And there's a third kind of call, the one that really tests your patience: the client who cancels with a different excuse almost every month, each one with a grain of truth, no two alike. With that client you can't tell if you're being understanding or getting played, and you end up deciding on the spot again, with the same old doubt.

A month later you realize you almost never charge the penalty you wrote yourself. Not because the rule is wrong, but because you decide each case in the heat of the moment, with the person waiting on the other end. And in the heat of the moment, sympathy wins over judgment almost every time. Each pass you give that night quietly becomes next month's habit.

The problem isn't having a heart. It's not having decided, before the phone rings, which cases you actually forgive.

Two questions, not a list of excuses

The temptation is to make a list of valid reasons: hospital, yes; flat tire, no; a family wedding, yes; slept through the alarm, no. The list never ends. There's always a new reason that isn't on it, a computer breakdown, a postponed exam, a mix-up with the babysitter, and you're back to deciding on the spot, phone in hand.

A two-question filter works better, the same one no matter what reason someone gives you. First: could they have avoided it? A hospital stay isn't avoidable; running late because you didn't leave with enough time is. A move you'd had on the calendar for weeks counts too: that's something you plan for. Spain's Civil Code starts from the same idea: unless the law or the agreement says otherwise, nobody is liable for events "that could not have been foreseen, or that, even if foreseen, were unavoidable" (Article 1105). Second: did they tell you as soon as they knew, or did they wait to see if it would slide? Someone who finds out at three in the afternoon that they can't make it and texts you at 3:05 passes the filter. Someone who knew since that morning and texts ten minutes before the appointment doesn't, even if the reason is the same.

Both answers have to be yes. If only one is, you charge the same as for any other no-show. Your cancellation policy fits in a short paragraph: the deadline, what's forfeited, and, if you want, the exception clause. You don't need a list of approved reasons. What you keep is the filter, not a catalog of excuses, so it works just as well a year from now as it does today.

Decide it ahead of time, not with the client waiting

You already know that canceling, rescheduling, and no-showing each carry their own consequence, and that starting with the second miss, the client pays upfront. This piece is about what happens before you get to that second time: who gets the benefit of the doubt the first time, and what standard decides it, not what mood you're in that night.

The filter doesn't remove judgment. It moves it earlier. You work through it once, calmly, in front of this text, not every Tuesday at nine at night with someone waiting for an answer on the other end of the phone.

Before you decide what to charge, it's worth seeing how the law treats this elsewhere. Spain's General Law for the Protection of Consumers and Users considers it abusive to impose "a disproportionately high penalty" on someone who doesn't follow through (Article 85.6). If you keep the deposit when a client cancels, a policy like that has to spell out the same thing in reverse: it's abusive to keep it "without providing for an equivalent payment if the business cancels instead" (Article 87.2). The condition has to be written clearly, and the client has to be able to see it before booking (Article 80). An abusive clause under that law is void and treated as if it were never written (Article 83): it's as if you'd never put it there.

In Yodai your clients request a time on your site and you confirm it from your dashboard. See how online booking for your business works.