Skip to content
EventConsultant
EN
Privacy and information handling

Handle photo opt-out requests from delegates

The photographer has 600 frames, and a delegate has just emailed asking not to appear anywhere.

Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

A photo opt-out workflow lets a delegate say no early, shows that choice on the day in a way the photographer can see, and gives the secretariat a route for requests after the event. Each step needs a named owner.

Your data protection contact decides what the signage and form wording must say, and what the organiser may do with images. The workflow is the operating side of those decisions.

Five points in the delegate's journey

  1. Registration: ask the photo question separately and record the answer. See marketing permission separation for keeping questions apart.
  2. Confirmation message: repeat the choice and say how to change it.
  3. Check-in: confirm the choice and give the delegate the agreed marker.
  4. In the room: photographers and videographers work from a briefing that explains the marker and no-photo zones.
  5. After the event: a clear route for takedown or removal requests.

Choose a marker that works in a crowded room

A coloured lanyard, a badge sticker or a dot on the badge is easy for a photographer to see at a distance. Test it with the photographer before the event, in the venue lighting.

Avoid any marker that singles a delegate out in a way they might find uncomfortable. Ask your contact whether the marker itself raises any questions.

What the photographer needs in writing

  • The marker and what it means, with a photo example.
  • Areas where photography is not allowed, such as a closed roundtable.
  • What to do when a delegate says no on the spot: stop, move on and tell the desk.
  • How images are stored, labelled and sent to the organiser, to confirm with your contact.
  • Who approves images before they are published.
  • Who the photographer contacts if a delegate asks about an image.

Handle requests after the event

Name one person in the secretariat to receive requests and one decision-maker for borderline cases. Agree with your contact what the person may do on their own, for example removing an image from the website, and what must be escalated.

Log every request with its date, the image involved, the action taken and the date the delegate was told.

Things to settle with other parties

  • Sponsors and exhibitors taking their own photos: do they follow the same rules?
  • Delegates taking and posting photos: what does signage say?
  • Video, livestream and recordings: is the opt-out workflow the same?
  • Venue CCTV: is it the venue's own matter? Ask the venue.

Worked example · Fictional example

Photo workflow for a 600-delegate congress

Fictional organisation and figures, for illustration only.

A fictional professional body adds a registration question, issues a green lanyard to delegates who prefer not to be photographed, and briefs two photographers with a one-page sheet. The desk keeps a log of green lanyards issued each morning.

A delegate emails afterwards about an image from the opening plenary. The secretariat finds the image, removes it from the shared folder and the website, logs the request and tells the delegate the date. The data protection contact is told and decides whether any further steps are needed.

Use this yourself

Photo opt-out workflow log and briefing checklist

Use the checklist before the event and the log table during and after it.

  • Photo question added to registration, wording approved by data protection contact.
  • Choice recorded in its own column in the registration data.
  • Marker chosen, tested with the photographer in venue lighting.
  • One-page photographer briefing issued, with no-photo zones marked on the floor plan.
  • Signage wording approved and positioned at entrances and in the room.
  • Desk script for delegates who change their mind on the day.
  • Named person and decision-maker for post-event requests.
  • Request log set up: date, delegate, image, action, date told.
  • Rules for sponsors, delegates and video agreed and communicated.

Use the free tool: Event registration form field minimiser

Handle it in-house, or bring in help?

Your team can usually handle this when

  • A small event with a single photographer who knows your team.
  • Your organisation has an approved photo policy and signage.
  • No video, livestream or sponsor photography.

Outside planning help earns its fee when

  • Several photographers, video crews and sponsors capture images.
  • A previous event had a complaint and the workflow needs rebuilding.
  • The secretariat has no capacity to run the desk and the request log.

Want the photo workflow built into your event plan?

An Event Blueprint can include the photographer briefing, desk steps, signage list and request log, together with the question pack for your data protection contact. The contact decides the wording and the rules. The planner makes sure the workflow is in the plan and the supplier briefs. Share your brief on WhatsApp and we will reply with which level of support fits and what it would cover.

Ask for supportOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Event Blueprint →

Questions organisers ask

Do we need a photo question on the registration form?

Ask your data protection contact. Many organisers include one because it lets the choice be recorded and shown on the day, but the decision is theirs.

What if a delegate objects on the day?

Have a desk script: record the choice, give the marker and tell the photographers. Keep the process quick and polite.

How long do we keep the photos?

Set the period before the event with your data protection contact, name the owner and include the photographer's copies.

Related resources

Content record: Written by the EventConsultant team to our editorial rules. Sources are listed on pages that rely on them.