What Belongs in an Event Photography Contract

Micael

TIME&SPACE · Photographer's Edge

Most disputes between photographers and organisers are not about money. They are about something both sides assumed and neither wrote down.

What Belongs in an Event Photography Contract

In short: The argument is almost never about the fee. It is about how many photographs were promised, who may publish them, and what happens when the event runs three hours long. A contract is just those answers, written before anyone is annoyed.

Event photographers who work without a written agreement usually get away with it, right up until they do not. The failure is rarely dramatic. It is a client expecting six hundred images when you planned to deliver two hundred, or a brand using your frames in a paid campaign a year later, or an event that overruns and a fee that does not.

None of that requires a lawyer to prevent. It requires a document that says what both sides already think they agreed.

The scope, in numbers

Vague scope is where most of the trouble starts, because both sides read it optimistically and in opposite directions.

Hours of coverage, with a defined start and end. Not "the event". Events overrun.

What happens past those hours. An hourly overtime rate agreed in advance turns an awkward conversation at midnight into an invoice line. Without it you either work free or refuse in front of the client's guests.

Roughly how many edited images. A range is fine and more honest than a single number. What matters is that "a few hundred" does not meet a client who was imagining a thousand.

Delivery date. Say a real one and beat it. How many photos to deliver covers what a sensible number actually looks like.

Who else is shooting. If a second photographer is included, say so and say who pays them.

Rights, which is the clause that actually matters

This is the part most templates fumble, and the part with the longest tail.

Ownership of the photographs stays with you unless you explicitly sign it away. What the client buys is a licence, and the licence should say three things: what they may use the images for, for how long, and where.

The common shapes:

• Internal and social use. The client posts them, uses them in a recap, puts them on their own channels. This covers most events.
• Marketing use. The images appear in paid advertising, on a sales page, on a stand at a trade fair. This is worth more and should be priced accordingly.
• Full transfer. Rare, expensive, and should never happen by accident inside a standard package.

Say plainly whether the client may pass the files to sponsors, partners, or press, because they usually assume yes. If you want that to be a separate conversation, write it down. Getting event photos to press and media covers how that distribution should work when it is agreed.

Also reserve your own right to use the work in your portfolio. Corporate clients sometimes strike this out for confidentiality reasons, which is legitimate, but you want to know before the event rather than after you have built a case study around it. The copyright guide sets out where ownership sits by default.

Money mechanics

A deposit that is genuinely non refundable. It is the only thing that makes a held date mean something.

A payment schedule with dates. Deposit on booking, balance on delivery is the simplest version that works.

What a cancellation costs, on a sliding scale. A client cancelling three months out and one cancelling the day before are not the same event, and the contract should not treat them as one. Pricing for event photographers covers how to set the underlying numbers.

Expenses, named. Travel, parking, accommodation, second shooter. Anything not listed will be assumed included.

The clauses people skip and later want

Illness and substitution. If you cannot work, are you sending a replacement of equivalent standard, refunding, or both. Deciding this while ill is worse than deciding it now. The contingency plan guide covers the operational side.

Force majeure. Not theoretical any more.

Conditions you need to work. Access times, a place to store gear, permission to use flash, whether you can be in restricted areas. A contract that promises photographs of a ceremony you are not allowed to stand near is a contract you cannot fulfil.

Guest consent and who is responsible for it. Normally the organiser handles signage and notice, and it should say so. This matters more when face search is involved, because indexing faces is a separate processing activity from taking photographs. The GDPR guide for organisers sets out the shape of it.

How long you keep the archive. Say six months, or a year, or whatever you actually do, and then hold to it. Clients ask for re-delivery surprisingly late.

Insurance. Confirm whether the venue requires public liability cover, since many do and will ask for the certificate before letting you in. The insurance guide covers what is usually needed.

Keep it short enough to be read

A five page contract that nobody reads protects you less than two pages that both sides actually understood. Write it in plain language, keep the numbers in a table at the top, and have a lawyer look over your standard template once rather than every booking.

Then use the same template every time. The value is in it being routine, not in it being clever.

Micael

Founder, TIME&SPACE