Branch events work best when head office sets the outputs it needs and each branch confirms its own schedule, venue and contact. Gather verified details from every local organiser, resolve contradictions centrally before the crew is briefed, and name one head-office contact who settles questions. The photographer should never be left to choose between two instructions.
A company with branches in several towns may hold a similar event at each: an anniversary dinner, a customer day, a community event. Head office wants a consistent record. Each branch has a local organiser who knows the venue, the guests and the timing. The photographer, who arrives on the day, needs a single clear set of instructions.
This page is part of our overview of agency and recurring event-photography commissions.
Where contradictions come from
Contradictions come from two sources. The first is a mismatch between central requirements and local reality. Head office may ask for a group photograph of all staff at 7pm, while the branch dinner serves at 7pm. The second is local organisers giving different information, such as different start times quoted in different emails.
Neither is anyone's fault. They arise because information passes through several hands. The aim is to catch them before the crew sees them.
Start with the central outputs
Write down what head office needs from every branch event, whatever the local programme. Typical items are:
- A small number of required photograph types, such as the opening, a group of staff and the main speaker.
- A delivery format and file naming.
- An approval route and a deadline.
- Any restrictions on publishing images of staff or customers.
Keep it short. The shorter it is, the more likely each branch is to follow it. Our guide on agreeing photography priorities with several decision-makers explains how to settle priorities when more than one party has a view.
Then collect local details, verified
For each branch, ask the local organiser for the date, the venue, the programme with times, the guest numbers, the contact on the day, and any venue rules for photography. Ask for these in one form, not in a chain of emails.
Verify what you can. If the venue has a website or a booking confirmation, check the date and the room against it. Our photography brief handover tracker is useful for recording who supplied which detail and when, and the guide on confirming the exact event venue before requesting a quote helps where venues are uncertain.
Merge into one brief per event
The agency or head office merges the central outputs and the local details into one brief for each branch event. This is the document the photographer receives. It should not require the photographer to refer back to the central requirements or to the organiser's emails.
If something conflicts, resolve it before the brief is sent. For example, if the local dinner conflicts with the central group photograph time, agree a new time with both sides. Our shared page on turning a changing draft programme into a usable photography run sheet explains how to deal with drafts.
A hypothetical example
For example, a retail company holds customer appreciation evenings at six branches in different states over a month. Head office needs a group shot of staff, a customer moment and a short selection of images within an agreed time of each event.
The agency collects local details through one form. It finds that two branches give different start times for the same event, because one quoted the doors-open time and the other the programme start. It asks both to confirm, builds a one-page brief per branch, and names a head-office contact. The photographers receive consistent briefs and a single person to ask.
Crew for branches in different places
Branches in different towns may need a local crew, a travelling crew or a mix. We do not state in advance which we can supply for a given place. Our guide to local photographer or travelling photography crew explains the choices, and we confirm travel and assigned crew in writing for each location.
Approval and consistency
Decide who approves images. If head office wants uniform results, it may need to approve each branch's selection. If branches are to use their own images, they may need their own approvers. Our guide on image approval across marketing, agencies and leadership shows how to avoid a loop of conflicting comments.
What to send us
Send the list of branches, the central requirements and each local contact. Tell us which details are verified and which are still to be confirmed. We reply in writing with what we need for each event and what we can confirm.
Checklist
- List every branch event with date, venue and local contact.
- State the central outputs required from every branch.
- Collect each local schedule and check it against the central plan.
- Resolve contradictions centrally before briefing the crew.
- Name one head-office contact for questions.
- Decide who approves images: branch, head office or both in turn.
Send us the list of branch events, the central requirements and each local contact, and we will tell you in writing what we need confirmed before we plan coverage.
Plan photography for our branch eventsCommon questions
Should head office or the branch brief the photographer?
Head office should set the required outputs and approvals, and the branch should supply its local details. Combine them into one brief per event before it reaches the photographer. If the photographer has to merge two sets of instructions, contradictions are likely.
What if a branch organiser changes the programme?
The branch tells the named head-office contact, who passes on the change. Agree this route in advance. The photographer should not take programme changes from a local organiser unless that organiser is the agreed contact for the event.
How do we make branch outputs consistent?
State the central requirements clearly: required shot types, the delivery format and the approval route. Let branches add local priorities within that frame. Review the first delivered set against the requirements and adjust the brief for the next branch.
Can branches approve their own images?
That is your decision. If branches approve their own, name the approver at each branch. If head office approves everything, say so. Having both approve the same set slows delivery and tends to produce conflicting comments.
Plan photography for our branch events
Send us the list of branch events, the central requirements and each local contact, and we will tell you in writing what we need confirmed before we plan coverage.
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: