A 24-hour cancellation policy sounds airtight until a client no-shows a 6am session, since the notice window that works fine for a 2pm appointment gives almost no real runway for the first slot of the day. By the time 24 hours’ notice would even be possible, the trainer’s morning is already unfillable.
PocketSuite powers 7,000+ service businesses, including 1,000+ pet service businesses, whose clients have collectively processed nearly $1 billion in income and scheduled over 9.2 million appointments.
A policy is only as good as a trainer’s ability to actually enforce it without an awkward, one-off conversation every time it gets tested, and that’s where PocketSuite does the actual work: card-on-file deposits, an enforced cancellation window, and a package-credit deduction that happens automatically instead of a trainer having to ask for the fee by hand.
This post covers why a flat 24-hour window doesn’t fit every time slot, charging a fee vs. deducting a session from a package, and three scripts for enforcing the policy without torching the client relationship over it.
Why One Flat Window Doesn’t Fit Every Slot
A 24-hour cancellation policy assumes a client has 24 hours of runway before their session to give proper notice. For a 6am slot, that assumption breaks: 24 hours before 6am is 6am the day before, an hour most clients aren’t awake to text a cancellation, and definitely not one that leaves a trainer any real chance of filling the spot.
A tiered window fits reality better: a longer notice requirement for the first slot or two of the day, when there’s genuinely less runway to fill a cancellation, and the standard 24-hour window for everything later. The goal isn’t a stricter policy overall, it’s a policy that actually gives a trainer the notice they need for the slot in question, rather than one number applied uniformly regardless of what time that number actually falls at.
The same logic extends to a trainer’s slowest booking windows generally, not just the literal first slot of the day. A mid-afternoon slot that’s historically hard to refill on short notice deserves the same longer-window treatment as an early morning one, since the actual question a policy should answer is “how much notice does this specific slot need to have a real chance of being filled,” not “what time does the clock read.”
Charging a Fee vs. Deducting a Session
With a card on file, a late cancellation or no-show fee through Invoicing charges automatically per the policy a trainer sets, without a trainer having to run a card manually or send a follow-up invoice after the fact and hope it gets paid.
For a client on a session package, the cleaner enforcement is often deducting a session from the package instead of charging a separate fee, since Packages tracks that deduction automatically against the client’s remaining balance. That framing, “a no-show uses one of your sessions,” tends to land better with a client than a separate charge showing up on their card, even though the practical cost is the same.
Which approach fits depends on how a business already sells: a business running mostly single-session bookings enforces with a card-on-file fee, and a business selling mostly packages enforces with a session deduction. Many trainers run both side by side, since a single-session client and a package client are being charged in the way that already matches how they pay for training.
We make adjustments to our retention efforts and upsells of existing clients. Easier to keep people than to find new ones.
Dominic Anastasio, owner, Forza Fitness
Setting the Policy Up Front, Not After the First No-Show
A cancellation policy that’s already attached to a client’s intake paperwork, through Contracts & Forms, gets agreed to before the relationship starts, not introduced defensively the first time it’s actually needed. A client who e-signed the policy at booking already knows the window and the consequence, so enforcing it later is applying a rule they agreed to, not springing a new one on them.
Retention is the real reason this is worth getting right rather than skipping it out of conflict-avoidance. A trainer who never enforces a no-show policy is quietly training clients that a missed session has no cost, and that pattern compounds: the client who no-shows without consequence today is more likely to no-show again, and a business that’s inconsistent about it with one client but strict with another has a fairness problem waiting to surface.
It’s worth separating a genuine emergency from a pattern of late cancellations, too. A policy that’s enforced identically regardless of circumstance, a client’s car breaking down once versus a client who’s canceled inside the window four times this month, misses an obvious difference most clients would agree is fair to treat differently. The policy still applies either way; how warmly a trainer follows up around it is where that judgment actually lives, and that distinction is exactly what keeps a consistently-applied policy from also feeling rigid or uncaring.
Three Scripts for Enforcing It Without the Awkwardness
“Hey [name], I saw the app flagged this morning’s session as a late cancellation, so a session came off your package per our policy. Let’s find a time this week to make it up if you’d like.” This script leads with the system doing the enforcement, not the trainer personally deciding to penalize the client.
“No worries about this morning, life happens. I did want to flag that this one falls inside our 24-hour window, so it counts as used per the policy you signed at booking. Want me to help find a good replacement slot?” This one acknowledges the situation warmly while still applying the policy consistently.
“Since we’re coming up on your first session together, just a heads up on the cancellation policy you’ll see in your intake form, anything inside 24 hours (12 for early-morning slots) counts as used. Just wanted that clear before we start so it’s never a surprise later.” This last script sets the expectation with a brand-new client before the policy is ever tested, which is consistently the easiest of the three conversations to have well.
A PocketSuite fitness training software setup that already has the policy on file and the deduction happening automatically is what makes all three of these conversations easier, the trainer is explaining a system’s rule, not defending a personal decision to charge a friend or a regular client.
What a Fair, Consistent Policy Actually Looks Like Over Time
Consistency is what makes a no-show policy hold up under scrutiny over the long run, not just in the week it’s introduced. A trainer who waives the fee for one client because they’re a favorite, and charges another who’s newer or less established, isn’t running a policy anymore, they’re making case-by-case exceptions that a client will eventually notice and resent if they find out a friend got a pass they didn’t.
That doesn’t mean zero flexibility ever. A trainer can build in a stated, limited grace policy, one free pass per client per quarter, say, applied the same way to everyone, rather than an unstated, ad hoc leniency that varies by client and by mood. A documented exception is still a policy; an undocumented one is favoritism with extra steps.
Reviewing actual enforcement data periodically, how often the policy actually gets triggered, and for which clients, through the same Invoicing and Packages records used to enforce it in the first place, is also worth doing every few months. A policy that’s rarely triggered may not need to change; one that’s suddenly triggering far more than usual is worth investigating before assuming clients have simply gotten less reliable, since a sudden spike is sometimes a signal about a specific time slot or a specific season rather than about clients generally.
A flat 24-hour window works for most slots, but an early-morning session often needs a longer notice requirement, since 24 hours before a 6am slot falls at an hour clients rarely have any chance of giving notice.
Both work, and which fits depends on how the client pays: a single-session client is charged a fee via a card on file, and a package client has a session deducted from their remaining balance, which tends to feel like a more natural consequence than a separate charge.
At intake, before the first session, attached to the client’s booking paperwork. A policy a client agreed to in writing before training started is far easier to enforce later than one introduced for the first time after a no-show already happened.
Frame the consequence as the system applying a policy the client already agreed to, not as a personal decision to penalize them, and keep the tone warm while staying consistent. Enforcing it the same way for every client is what keeps it feeling fair rather than personal.
