It's easy to treat "I take a deposit" as the whole answer to protecting your business from last-minute cancellations. It's part of the answer, but a deposit and a cancellation policy are actually solving two different problems, and conflating them is how artists end up with a $100 deposit that doesn't come close to covering a lost wedding day.
What a deposit is actually for
A deposit does two things: it confirms the client is serious enough to put money down, and it compensates you if the date falls through. It is not automatically enough to cover the real cost of holding a date, unless it's sized correctly.
A common mistake is a flat, small deposit (say $50 or $100) regardless of the total booking size. On a $150 party booking that's meaningful. On a $600 bridal package where you turned away three other inquiries for that Saturday, it barely covers your time writing the contract.
A better approach: size the deposit as a percentage of the total (25–40% is typical), not a flat number. That way it scales with what you're actually risking.
What a cancellation policy is actually for
The cancellation policy is what determines what happens to the rest of the money if the client backs out, and how close to the date they can still do it without real consequence. This is the piece that protects the day itself, not just the deposit.
A workable structure uses tiers based on how much notice you get, since a cancellation eight months out costs you almost nothing (you can easily rebook the date), while a cancellation two weeks out likely costs you the whole day:
- 60+ days out: full refund of anything beyond the deposit
- 30–60 days out: 50% of the balance paid is refundable
- Under 30 days: non-refundable, since the date can no longer realistically be rebooked
The exact windows are yours to set based on how far in advance you typically book, but the principle holds: the closer to the date, the less refundable, because your actual ability to fill that slot with someone else drops the closer you get to it.
Rescheduling isn't the same as cancelling
Worth separating explicitly in your policy: a client moving their wedding date (which happens more than people expect) is different from a client cancelling entirely. A reasonable middle ground is allowing one reschedule at no charge if requested with enough notice, while treating a true cancellation under the standard policy. This avoids penalizing a client for something genuinely outside their control, while still protecting you from someone using "reschedule" as a way to dodge the cancellation terms.
Communicating this without sounding harsh
Clients aren't usually upset by a clear policy. They're upset by a policy they never actually saw or agreed to, then get surprised by later. The fix isn't softening the terms, it's making sure they're presented clearly and signed before the deposit is even paid, not buried in a paragraph of a longer document. A short, plainly worded summary alongside the contract (not instead of it) goes a long way:
Example summary line
"Your deposit of $200 secures your date and is non-refundable. The remaining balance is fully refundable if cancelled 30+ days before your event, 50% refundable 15–29 days out, and non-refundable within 14 days."
Said plainly, up front, this reads as professional, not aggressive. It's the vague or after-the-fact version of this conversation that actually damages a client relationship.
The real goal: never chase this by hand
The other reason this whole system quietly falls apart for a lot of artists isn't bad policy. It's that tracking who paid what, and when a balance is actually due, becomes its own part-time job once you're juggling more than a few bookings a month. That's usually where "I have a deposit policy" and "I actually enforce it consistently" start to drift apart.
Deposits tracked automatically, balance reminders sent for you
HireMUA tracks deposit and balance status on every booking, and sends payment reminders before you have to ask.
Start Free Trial