What to Include in a Photography Contract: The Clauses That Prevent Real Disputes

Contract disputes almost never come from bad photos. They come from a canceled session and a retainer nobody defined, or a gallery that landed in week ten when the client was quietly expecting week two. In every case like that, two people held different assumptions about the same event, and no sentence anywhere settled it. Writing that sentence down ahead of time is the whole job of a contract. It doesn't need to sound like a law firm wrote it. It needs to be readable, signed, and specific about the handful of situations that actually go wrong.

If you're still standing up the rest of the business, the contract is one piece of a larger legal setup, and the full sequence is in our guide to starting a photography business. But this piece can't wait for the LLC. A contract costs nothing to put in place and starts protecting you on the very next booking.

• Parties and scope of work. Legal names on both sides, the date, start and end times, locations, how many photographers are showing up, and exactly what's included: hours of coverage, a second shooter, an engagement session. Scope creep dies in this paragraph. If coverage ends at 9pm and the sparkler exit is at 10:30, the contract already answered the question before anyone asked it at the reception.
• Total price and payment schedule. The full fee in dollars, when each payment lands, what forms of payment you accept, and what happens if the final balance doesn't arrive. For weddings and events, spell it out: unpaid balance by the due date means no coverage. And make sure the figure underneath the schedule is worth defending; if you haven't done the cost math yet, work through how to price your photography before you lock a number into a signed document.
• A retainer, called a retainer. The word matters. In some states a "deposit" is presumed refundable, which is exactly the fight you're trying to avoid. Name a retainer, state the amount (25 to 50 percent of the total is typical), say it's non-refundable, and say what it buys: your date, held against every other inquiry you'll now turn away.
• Rescheduling. How much notice a client owes you, whether the retainer transfers to a new date and how many times, how far out the new date can be, and what happens with weather on an outdoor shoot. A one-time transfer to a date within six months is a common, fair default.
• Cancellation, in both directions. If the client cancels, the retainer stays with you, and many photographers add a sliding scale as the date gets close, since a slot canceled two weeks out rarely rebooks. If you cancel or can't perform, say what you'll do: a substitute photographer you arrange, or a full refund of everything paid.
• Deliverables and timeline. A range of edited images, never an exact count. The delivery format, which for most working photographers now means an online gallery. A delivery window in weeks, with a longer one for weddings than portraits. How long the gallery stays up, and whether the client can download and print. Vague deliverables generate more angry emails than any other gap in a contract.
• Copyright and usage rights. Under US law you own the copyright the moment you press the shutter; the contract's job is to say so and then license the client what they actually need, which is personal use: printing, sharing, posting. Commercial use, meaning anything that sells or promotes something, requires a separate license at a separate price.
• Model release. This is the mirror of usage rights: the client's permission for you to show their images in your portfolio, on your website, and in your marketing. Include it by default and give clients a genuine way to opt out, because some jobs and some families have real reasons to stay off your Instagram.
• No raw files, and creative license. You deliver edited images only, and editing decisions are yours. Clients hired your published style, and the contract should say the style they saw is the style they'll get. This clause feels petty until the first "can you just send everything unedited" email arrives.
• Limitation of liability and force majeure. If a card fails, gear breaks, or something outside anyone's control cancels the event, your maximum liability is what the client paid you. Without this cap, a corrupted card at a $40,000 wedding is an argument about $40,000 instead of an argument about your fee.

A contract is a list of answers to arguments you haven't had yet.

These two clauses cause the most confusion in the whole document, so it's worth slowing down. Usage rights govern what the client can do with the photos. A model release governs what you can do with the client's likeness. They're separate permissions moving in opposite directions, and a contract that blurs them invites both classic disputes at once: the client's portrait session showing up on their company's ad campaign, and your best frame of them showing up in your marketing when they never agreed to be public.

The clean structure: you keep copyright, the client gets a written personal-use license broad enough that they never feel policed for printing a canvas or posting an album, and commercial use is explicitly carved out as a separate negotiation. Then the model release grants you portfolio and marketing use, with an opt-out. Most clients happily agree. The ones who don't will tell you at signing, which is precisely when you want to know, not after the images are live.

One more boundary worth writing down for weddings: an exclusivity line saying you're the only hired photographer, and that guest photography can't interfere with your coverage. You can't ban phones, and shouldn't try, but you can establish that the aisle shot blocked by a guest's tablet isn't a reshoot you owe anyone.

A contract that exists but isn't signed protects nobody, and the most common failure isn't a bad template, it's sequencing. The photographer holds the date on a friendly email, the retainer arrives by payment app, the contract goes out "to make it official" and never comes back. Now there's money exchanged, a date reserved, and no signed terms: the exact ambiguity the document was supposed to remove. The fix is mechanical. Signing happens at booking, before the date is held, with the retainer collected in the same step. No signature, no reservation, no exceptions, including for family.

Digital signatures make this painless: they've been legally binding in the US since the ESIGN Act in 2000, so there's no reason to print anything, just keep the signed copy and its timestamp. The smoothest version is a single flow where the client picks a time, signs, and pays the retainer in one sitting. That's the shape PicurPhoto is built around: clients book from your real availability, your contract and questionnaires ride along in the same workflow, and the retainer is charged through your own Stripe account, so the money, payment plans, and any refunds stay under your control rather than sitting in a platform's balance. The free plan covers a working setup at $0 (up to 10 galleries, 1 GB of storage, one user), and no plan ever takes a percentage of what you charge. What it won't do is write the legal language for you. Draft from a solid template, then pay a local attorney for one review, because the rules on retainers and cancellations genuinely vary by state, and one billable hour is cheaper than one dispute.

Once the signature and retainer are locked, the paperwork isn't finished, it just changes subject. The contract settles the legal side of the shoot; a photography client questionnaire, sent right after booking, settles the creative side. Send it after signing, never instead of it.