When a Wedding Client Refuses to Pay (And How Your Contract Prevents It)
A photographer books a wedding. $3,000 package. The bride is lovely, groom seems chill, everything's great. A week before the wedding, the photographer has a family emergency. She reaches out to the couple, explains the situation, offers a full refund, and offers to help them find another photographer. Just about everything you can do in that situation.
But the bride is furious. Her mom is threatening legal action. They're demanding she pay for a replacement photographer AND issue a full refund simultaneously, which is not how any of this works. The photographer had a contract, but it was a two-pager. A lot had been communicated over DMs and Venmo. There was almost nothing in the contract about her cancellation policy, her refund policy, or what happens in an emergency.
The bride didn't actually sue. But she did blast the photographer publicly, and even when most people can see who's being reasonable and who isn't, that kind of thing is still stressful and damaging. The photographer issued a refund and spent weeks dealing with fallout that a better contract could have largely prevented.
This is not a rare story. Some version of it happens to wedding professionals constantly. The details change, sometimes it's the client canceling, sometimes it's a payment dispute, sometimes it's scope creep that spirals into a full breakdown, but the root cause is almost always the same. The contract didn't cover it.
Here's what a proper contract actually does for you. It sets expectations before anyone is upset, which means disputes are less likely to escalate into public blowups. It gives you legal ground to stand on when someone claims you didn't deliver what you promised. It protects your income when a client tries to cancel and demands a full refund after you've already turned down other bookings for their date. And it documents exactly what you agreed to so that "but I thought that was included" stops being a viable argument.
At minimum, your client contract needs to address scope of work so there's no ambiguity about what you're actually delivering, payment terms including how much is due, when it's due, and what happens if they don't pay on time, your cancellation and refund policy written clearly enough that a client can't claim they didn't understand it, a revision or change policy if that's relevant to your work, what happens if either party needs to terminate the agreement early, and a force majeure clause that covers genuine emergencies like the photographer story above.
That last one is worth talking about specifically because it trips people up. A force majeure clause covers circumstances beyond anyone's control that prevent you from performing. Without one, you're in a genuinely murky legal situation if something catastrophic happens. With one, the expectations are set in advance and both parties know what happens next. For photographers specifically, a substitution clause is worth adding as well. It allows you to send a qualified substitute in an emergency without it being considered a breach of contract. This is the kind of language most two-page contracts completely leave out.
The other place where contracts fail wedding pros is on payment enforcement. "Payment due upon receipt" is not a payment policy. You need specific due dates, what forms of payment you accept, what your late fee policy is, and what you will and won't do if a payment is missed. If you've ever had a client go quiet two weeks before a wedding while still owing you money, you already know why this matters.
If your current contract is a template you found online, something a friend sent you, or a document that hasn't been touched in a few years, it probably has gaps you don't know about yet. The Contract Club has attorney-drafted contracts built specifically for wedding professionals, planners, photographers, venues, florists, DJs, and more — with all of this language built in. You customize it for your business, you send it with confidence, and you stop finding out what your contract is missing only when something goes wrong.
