Photography Contract Essentials: What Every Contract Needs
Most photographers' first contract is someone else's contract — a template found online, copied from a friend, or inherited from a course. That's a fine starting point. The problem is most of those templates were written for a different market, a different kind of shoot, or a different set of risks than the ones you'll actually run into.
A contract isn't there for the bookings that go well. It's there for the one wedding where the venue floods, the one client who wants a refund after the shoot because they "didn't like the vibe," or the one guest who claims you didn't have permission to photograph them. Here's what actually needs to be in it.
The clauses that matter most
Payment schedule, in specific numbers. Not "a deposit is required" — an actual amount or percentage, an actual due date for the balance, and what happens if it's late. Vague payment terms are the single most common source of awkward conversations after a shoot, not before.
Cancellation and rescheduling terms — for both sides. What happens if the client cancels a week out versus a day out? What happens if you have to cancel — illness, equipment failure, family emergency? A contract that only protects you looks exactly like what it is, and clients notice.
Copyright and usage rights. This is the clause most templates get vague on, and it's the one that causes real disputes. You own the copyright to the images by default in most jurisdictions — but what you're granting the client (personal use, print rights, social media use, commercial use) should be spelled out explicitly, not assumed.
Your right to use the images too. Portfolio use, marketing, social media — put it in writing, and give clients a real way to opt out if they want one. "I'll assume it's fine" is not a policy.
A delivery timeline. A specific number of weeks, not "soon." This is the single most common client complaint in photography, and it's entirely preventable with one sentence in the contract.
Model releases, if there are identifiable people who aren't the paying client. Weddings especially — guests, bridal party, kids. If images might be used beyond the private gallery, this needs its own signature, not an assumption buried in the main contract.
A liability limit. Equipment fails. Memory cards corrupt. If the absolute worst happens and images are lost, what's your liability? Most photographers cap it at a refund of fees paid — but that needs to be a term you both agreed to, not something decided after the fact.
Overtime and additional charges. If the reception runs two hours past the contracted time, what happens? Say it in the contract, not in the moment.
A signature — from both parties, actually collected. Not implied by a deposit landing in your account. A contract nobody signed is a lot harder to enforce than one that was.
The mistake that causes the most disputes
It's not missing a clause. It's having a contract that exists as a PDF nobody actually reads and signs before the booking is confirmed. If a client can pay a deposit and start planning before they've signed anything, the contract isn't really protecting either of you — it's a formality that shows up after the relationship has already started.
The fix isn't a longer contract. It's making signing part of the booking flow itself, so there's no version of "we're locked in" that happens before "we both agreed to the terms."
Where LensFlow fits
Contracts in LensFlow are built to close that gap specifically — sent as part of the booking flow, signed electronically before a client is confirmed, and stored against that client's record permanently, not as a separate PDF you have to go dig up later if a dispute ever comes up. See how it works, or start free if you're ready to stop sending contracts as an afterthought.
This isn't legal advice — contract law varies by jurisdiction, and a real dispute is worth a real lawyer. Treat this as a checklist for what to make sure your contract covers, not a substitute for having one reviewed.