Booking photography across several related events under one agreement

A series of events looks simple on a planning sheet: a launch dinner, a conference, a site visit, a closing lunch. When photography is booked as one package, the details are not simple. Each event has its own date, place, people and risks.

This guide is part of our overview of booking event photography and agreeing the scope.

When does a single agreement make sense?

A single agreement works well when the events share the same client, the same brief and the same delivery arrangement. Examples include a multi-day conference programme, a roadshow, a set of related ceremonies or a company's regional events within one campaign.

It works less well when the events have different clients, different approvers or very different needs. In those cases, separate quotations linked by a common reference are often clearer. Our multi-event photography commission organiser helps you decide how to structure it.

How should each event be recorded?

Treat each event as a short section of its own. Record:

1. Name, date, start and end time.
2. Venue and access details.
3. Coverage hours and crew.
4. Deliverables and delivery timing.
5. The person who approves changes.
6. Any special conditions.

Put the common terms, such as payment arrangement and image use, in one place. This keeps the document readable and avoids repeating the same text. A one-page summary table at the top lets anyone see all events at a glance.

What happens if one event changes?

This is the question to settle before signing. If one event moves date, changes venue or is cancelled, does the rest of the agreement stay the same? Does payment change? Does the crew assignment shift?

Ask how each type of change is handled. Rescheduling is covered in our guide on rescheduling an event-photography booking, and cancellation in the one on cancellations and refund questions. For a series, the key is to state that a change to one event affects only that event, unless the written terms say otherwise.

Can events share crew and deliverables?

Sometimes. A photographer may be able to attend several events, but dates can clash, and travel between locations takes time. Do not assume the same crew can attend every event. Ask us for confirmation of the crew for each date.

For deliverables, decide early whether each event has its own gallery and delivery date. Separate deliveries make approval and invoicing simpler. A combined delivery suits a single report, but it may delay the first images. Our guide on travel and outstation planning is useful if events are in different towns.

How are payments linked?

Payments can be tied to the whole agreement or to each event. The latter is easier to follow if one event changes. Ask how deposits and later payments will be arranged, and state it in writing. Our guide on deposits and payment milestones explains what to ask.

An example scenario

For example, imagine an organisation books photography for three events in one month: a Monday kickoff dinner, a Wednesday seminar and a Friday awards lunch. They are managed by one team but approved by different directors.

The agreement has a summary page and three sections. If the seminar moves to the next week, only its section changes, and the others stay as written. The awards lunch has its own approver, so that director's decisions apply only there. The team uses the common terms for image use.

How do you keep the record clear over time?

Use version dates and keep a change log. When something changes, issue an updated section and mark the old one as replaced. Our guide on amending scope after the deposit is paid describes the practice, and the scope change log is a simple tool for it.

If the series continues for months or years, see our guide on recurring photography retainer agreements.

What we confirm

We confirm each event's date, venue, crew, deliverables and quotation in writing, together with how a change to one event affects the others. Ask us whether the same crew can attend all your dates, and we answer for each date.