A final brief becomes authoritative when it carries a version label and date, is approved by the named decision maker, and is acknowledged by the photographer. After that point, changes go through the same route. Older versions are marked as superseded. The shared document builder helps you write the brief; this guide covers how it becomes the one that counts.
Plans change as an event approaches, and the number of copies grows. A schedule in an email, a list in a chat, a PDF from last week. When the day arrives, the crew needs to know which of them to follow.
This guide belongs to our booking and scope guide. To write the brief itself, use the event photography brief builder.
What makes a brief final
A brief is final because of what has been done to it, not because of what it says. Three steps make it so.
- Labelled. It carries a version number and a date.
- Approved. The named decision maker has accepted it.
- Acknowledged. The photographer has confirmed receipt and understanding.
Until all three have happened, treat it as a draft. Once they have, treat it as the reference.
What the brief should hold
The shared document builder suggests the content. At minimum, check that the brief shows:
- The event, date, start and finish times, and setup time.
- The venue, entrance, parking and day contact.
- The moments, people and groups to be photographed.
- Restrictions on access, flash or positioning, as confirmed by the venue.
- The deliverables and when they are needed.
- The approver for extra work and for images, if any.
Confirm venue rules with the venue for your date. Do not copy them from another event. Our venue photography checklist helps.
Version control that people follow
A simple pattern works. Name the file with the event and version, such as "Annual dinner brief v3 final". Put the date and the approver on the first page. Move older versions into a folder marked superseded. When a new version is issued, send it with one line saying what changed.
| Version state | How to label it |
|---|---|
| Working draft | Draft v1, v2 |
| Approved | Final v3, approved by name on a date |
| Changed after approval | Amendment A, or Final v4 with a change note |
| Replaced | Moved to the superseded folder |
The photography brief handover tracker, our brief handover tracker, records who received which version and when.
Acknowledgement
Ask the photographer to reply that they have the final brief and have read it. A one-line reply is enough. It gives you a dated record, and it gives the photographer the chance to raise anything unclear. We reply with our understanding of the key points, so that any gap shows up early.
After the final
Changes still happen. Do not edit the final in place. Treat each change as an amendment, approved in the same way. For changes on the day, see approving extra photography work during an event. Keep a scope change log to show the order of events.
If a change was agreed verbally, send a summary the same day. See what to record when a photographer agrees to a verbal change.
A hypothetical example
Imagine a charity gala with three people contributing to the plan. The organiser compiles the brief, marks it "Final v2, approved by the chair, 12 March" and sends it to the photographer and the two day contacts. The photographer replies with a summary.
Two days later the chair adds a presentation. The organiser issues "Final v3", with a note on what changed, and asks for another acknowledgement. On the day, everyone holds the same version. Nobody has to wonder which message was right.
Who is responsible
Name one person to maintain the brief. Others send them changes, not the photographer. Our responsibility planner helps. If an agency is involved, decide whether the agency or the client approves. See handling conflicting instructions from the client and event agency.
What we do
We read the final brief, reply with our understanding and confirm in writing that it matches the date, venue, crew, deliverables and quotation we hold. If it differs from the quotation, we say so and ask which should prevail.
A short pre-event call
If the event is large, a ten-minute call a few days before can confirm that everyone has the same version. Ask each contact to name the start time, the first three moments and the person who approves changes. If their answers differ, the brief needs another look.
Checklist
- Use one document as the brief.
- Label it with a version and date.
- Name who approved it.
- Mark older versions as superseded.
- Send it to the photographer and the day contacts.
- Ask for written acknowledgement.
- Route later changes through the same approval.
When your plan is nearly final, send it to us and we will confirm in writing that it matches what we have prepared for the day.
Send our final brief to confirmCommon questions
When should the final brief be sent?
Early enough to fix errors but late enough that the plan is stable. Many teams aim for about a week before. Ask us what we need for your event and by when, and we will confirm.
How do we show which version is final?
Put a version number and date at the top, such as Final v3, and name the approver. Mark earlier ones as superseded. Send the final to everyone who needs it, and ask for acknowledgement.
What if changes arrive after the final?
Treat them as amendments. Issue a new version or a dated addendum, and have it approved in the same way. Do not rely on a verbal change.
Who needs a copy?
The photographer, the day contact, the backup contact and anyone who gives instructions. Keep a list so that nobody works from an old copy.
Send our final brief to confirm
When your plan is nearly final, send it to us and we will confirm in writing that it matches what we have prepared for the day.
What happens next: You send your event details on WhatsApp. Our team reads the brief, asks what is missing, then confirms in writing whether the date, venue and coverage can be booked, with a quotation. Opening WhatsApp does not send anything, and a message is not a booking until both sides confirm.
Last reviewed: