Most disputes between creatives and clients don't come from bad work. They come from two people who never actually agreed on what "the job" was. A proper contract isn't paperwork for paperwork's sake. It's the single document you can point back to when a client asks for something that was never part of the deal, or when a shoot gets rained out and nobody's sure who eats the cost. Here are the twelve clauses worth having in every contract you send, regardless of how small the job is.
1. Scope of services
Exactly what you're being hired to do: the type of shoot, the number of hours or days, and how many final images or minutes of footage the client can expect. Vague scope is the single biggest cause of scope creep: a client who assumes "wedding photography" includes a second shooter, drone footage, and same-day editing has a very different mental model of the job than you do, unless the contract says otherwise.
2. Deliverables and delivery timeline
What the client actually receives (raw files? a curated gallery? a specific number of edited images?) and by when. "A few weeks" means something different to everyone. Give a real number of business days, and say what happens if delivery slips because of something on the client's end: late selects, late payment, or a delayed brief.
3. Payment terms and deposit
Deposit amount, when the balance is due, accepted payment methods, and what happens if an invoice goes unpaid. A deposit isn't just cash flow. It's what actually locks the date in and filters out clients who aren't serious.
4. Usage rights and licensing
This is the clause most new photographers get wrong. Delivering a file is not the same as handing over unlimited rights to it. Spell out exactly what the client can do with the images (personal use, social media, print, commercial advertising) and for how long. If a client wants broader usage than what's included, that's a separate, paid negotiation, not something implied by the fact they paid for the shoot at all.
5. Copyright ownership
In most jurisdictions, the photographer owns the copyright by default unless it's explicitly signed away, but "most jurisdictions" and "by default" are exactly the kind of thing you don't want to be arguing about after the fact. State it plainly.
6. Cancellation and rescheduling policy
What happens if the client cancels a week out versus the day before. What happens if you have to cancel. Whether the deposit is refundable, and under what circumstances. Weather-dependent shoots need their own explicit rescheduling terms. Don't leave "what if it rains" as an assumption.
7. Model releases (separate from the main contract)
If you intend to use any images from the shoot in your own portfolio, marketing, or competition entries, that needs its own release, signed by every identifiable person in frame, not buried as a single line in the client contract. Client permission to use their photos and a subject's permission to be photographed are two different consents.
8. Liability and equipment failure
Cameras fail. Cards corrupt. Backup drives die at the worst possible moment. A liability clause that caps your exposure to a refund (rather than open-ended damages) protects you from a single lost memory card turning into a business-ending claim, while still giving the client a real remedy if something genuinely goes wrong on your end.
9. AI usage restrictions
A newer one, but increasingly non-negotiable for a lot of clients and photographers alike: whether AI tools can be used to edit or enhance the delivered images, and whether the client can feed your work into AI tools of their own (for training data, generative editing, and so on) without your separate consent.
10. Force majeure
The standard "neither party is liable for delays caused by things genuinely outside anyone's control" clause: natural disasters, venue closures, illness. Not an excuse clause, a genuine allocation of risk for events nobody could have planned around.
11. Confidentiality
Relevant more often than people expect: corporate shoots, product launches, unreleased campaigns, even a couple keeping an engagement private a little longer. If you'll have access to anything sensitive before it's public, say explicitly that you'll keep it that way.
12. Governing law and dispute resolution
Which jurisdiction's laws apply, and how a disagreement gets resolved if it ever comes to that. Doesn't need to be aggressive (most contracts are never actually tested), but it should exist, because "we'll figure it out if it happens" is not a plan.
Writing all twelve of these from scratch for every job isn't realistic, which is exactly why a reusable clause library is worth building once and reusing. SetBook's contract builder ships with all of the above as ready-to-use clauses you can mix into any contract in minutes, not hours.