Assigning a backup contact when the main organiser becomes unavailable

On the day of an event, the organiser is the busiest person present. They greet guests, handle suppliers, solve problems and keep the programme on time. When the photographer has a question, the organiser may not be able to answer. That is why a backup contact matters.

This guide belongs to our overview of booking event photography and agreeing the scope.

What does a backup contact do?

A backup contact is the person the photographer asks when the main organiser cannot be reached. They give quick answers about access, timing, who is who and what to prioritise. They also relay questions that need a bigger decision.

The backup is not a replacement for the organiser's authority. They have the authority you give them, no more. Writing down that authority is the main purpose of this page.

Who makes a good backup?

A good backup is someone who:

• knows the programme and the brief
• will be at the event or reachable by phone throughout
• can make small decisions without delay
• has the standing to speak for the organiser on those points
• is calm under pressure

It may be a co-organiser, a venue coordinator, an assistant or a senior volunteer. Avoid choosing someone who is already overloaded, such as the person running the stage cues.

What may the backup decide?

Set the limits clearly. A simple split works well:

Decision	Backup alone	Needs main organiser or approver
Small timing shift within the booked hours	Yes	No
Access to a room or area	Yes	No
Which of two simultaneous moments to cover	Yes	No
Extra coverage beyond booked hours	No	Yes
Change to deliverables or cost	No	Yes
New use of the images	No	Yes

Adjust the table to your event. Share it with the backup, the main organiser and us. Our photography responsibility planner helps list who does what.

How is the backup recorded?

Put the backup's name, role and number in the booking record, and note the limits. Update it if anyone changes. If the booking is made through an assistant or agency, record both the backup and the way approvals reach the client. Our guide on bookings made through a personal assistant covers that arrangement.

The brief handover tracker keeps these contacts with the brief, and the guide on recording the final photography brief before event day shows what the final brief includes.

An example scenario

For example, imagine a charity dinner in a hotel ballroom. The main organiser will be on stage for much of the evening. She names a co-organiser as backup, with a phone number, and tells us the backup may decide on timing shifts of up to thirty minutes and on which table to photograph first.

At 8pm, the speeches run late and the photographer asks whether to move the group photograph. The backup says yes and tells the organiser afterwards. Later, a guest asks for extra coverage of an unplanned presentation. The backup checks with the main organiser by message before agreeing.

How should the backup be briefed?

A backup who has never seen the brief cannot answer well. Send them the final programme, the list of priority moments and the contact list a few days before the event. Ask them to read it and note any questions. If possible, introduce the backup to the photographer by message beforehand, so the first contact is not a rushed call on the day. A two-minute exchange at the start of coverage, confirming where each person will be, saves time later.

What if the plan changes sharply?

Some changes are bigger than a backup can handle: a venue problem, a delayed programme or an emergency. Our guide on programme changes and overrunning hours explains how coverage is handled when the plan shifts. The backup's role is to keep communication clear and pass decisions up quickly.

If two parties give different instructions, see our guide on conflicting instructions from the client and event agency.

What we confirm

We confirm the backup contact's name, role and number in writing, with the limits of their authority as you have told us. Our crew will use that contact when the main organiser cannot be reached.