The most common cause of poor event photo delivery is not the AI system, not the photographer's skill and not the guest list size. It is a brief that did not include upload instructions. Photographers are hired for their creative output and they are genuinely excellent at that, but unless someone explicitly tells them when and how to upload during the event, they will default to delivering everything at the end, or after editing, or sometime next week.

This guide is a complete brief template you can adapt and send to any event photographer. It covers everything needed for AI-ready photo delivery: gear requirements, shot list priorities, connectivity planning, upload schedule, file naming and post-event handoff. Use it as a document you fill in before sending, not a general set of suggestions.

Why most briefs fail

A typical photographer brief covers: start time, end time, key moments to capture (first dance, cake cut, keynote speaker), dress code and contact details. This is the minimum viable brief for getting usable photos. It is completely inadequate for AI photo distribution.

The gap is operational rather than creative. AI delivery depends on photos being available in the system while the event is still running, which means the photographer needs to upload in batches throughout the day, not deliver a card at the end. That requires a laptop or upload device, a connectivity plan, an agreed batch schedule and a naming convention that integrates cleanly with the platform.

Photographers who have not been briefed on these requirements will not simply figure them out on the day. They will shoot, they will deliver beautiful images and every guest notification will go out three days after the event when nobody cares anymore. Brief them properly and the same photographer produces the same creative output. But it lands while the emotional memory is still live.

Shot list for AI-ready delivery

AI photo distribution matches guests to photos based on their face appearing clearly in the frame. This creates specific shot-list priorities that differ from a standard event brief:

Brief Section 1

Shot list priorities

Registration desk / arrival: This is the highest-value location for AI matching. Guests are stationary, facing forward and well-lit (or can be). A photographer spending 30–45 minutes at the registration area during peak arrival, capturing clear frontal portraits of guests as they check in, generates the seed photos used to anchor each guest's cluster. Prioritise this above almost everything else.

Group shots with identifiable faces: Wide group shots where faces are small and turned away are low-value for AI matching. Where group shots are requested, ask the photographer to also shoot a tighter version, closer, more frontal, that gives the system clean face data to work with.

Candid coverage: Standard event candids work well. The system handles varying poses, lighting and angles. No special instructions needed for candid coverage beyond ensuring the photographer moves through all areas of the venue, not just the stage.

Speaker and stage coverage: Every speaker should be photographed at the podium within the first two minutes of their slot. Flag these photos in the upload with the speaker's name if possible, priority processing can be configured for named individuals.

Award presentations and key moments: Capture from two angles where possible. The moment of handshake or trophy receipt is the photo guests will actually share.

Gear requirements

AI face recognition accuracy is directly related to image resolution and sharpness. The following are minimum requirements, not aspirational targets:

Brief Section 2

Gear minimum specification

  • Minimum resolution: 24 megapixels. Below this threshold, face crops from wide shots may not contain sufficient detail for reliable matching.
  • Lens: A fast prime (f/1.8 or faster) or a zoom with f/2.8 maximum aperture is strongly recommended for indoor and low-light work. Soft, noisy images from slow lenses under poor lighting significantly reduce matching accuracy.
  • ISO capability: The photographer should be confident shooting at ISO 3200–6400 without excessive noise. Modern full-frame sensors handle this well. Crop sensors vary significantly.
  • Upload device: A laptop or dedicated upload device with a card reader. The photographer should confirm this is available before the event. Mobile uploads from a phone are not recommended for events above 500 guests.
  • Spare cards: At least 3× the expected card capacity for the shoot duration. Card swaps should not be a bottleneck in the upload schedule.

Connectivity plan

Upload batches require a stable internet connection. This sounds obvious until you are at a venue where the public WiFi throttles uploads to 2 Mbps and 1,000 RAW files are waiting to transfer. Connectivity planning must happen before the event, not on the day.

Brief Section 3

Connectivity options (choose one)

Option A - Venue dedicated WiFi circuit: Contact the venue AV team at least one week before the event and request a dedicated upload circuit with guaranteed bandwidth. Specify 50 Mbps minimum upload speed. This is standard at most hotel and conference venues and typically incurs a small fee. This is the most reliable option.

Option B - 4G/5G mobile hotspot: The photographer uses their own mobile data or a dedicated event hotspot for uploads. Test the signal at the venue in advance, basement ballrooms and thick-walled historic buildings frequently have poor mobile coverage. Confirm the data plan is unlimited or has sufficient allowance for the expected upload volume (estimate 5–8 MB per JPEG at full resolution).

Option C - Pre-arranged ethernet drop: For venues where WiFi is unreliable, arrange an ethernet connection at the photographer's base station (often the registration area or a side room). Confirm with the venue AV team that a port is available and active.

Document the agreed connectivity option in this brief and confirm it is operational at the start of the event before photography begins.

Critical: Do not assume venue WiFi will be adequate without testing. Upload a 50 MB test file at the venue during your pre-event site visit and record the speed. If it is below 20 Mbps upload, arrange a backup option before the event date.

Upload schedule

The upload schedule is the single most important operational instruction in this brief. State it explicitly, with times, not as a general principle.

Brief Section 4

Upload schedule template

Please upload photos in batches according to the following schedule. You do not need to edit or cull before uploading, upload JPEGs straight from card at full resolution. Edited versions can follow later.

Batch 1: [Time, e.g., 7:30 PM], Arrival and registration coverage. Target: 200–400 photos. This batch is the highest priority for guest matching. Please upload as soon as the arrival period is complete.

Batch 2: [Time, e.g., 9:00 PM], First half of event programme coverage.

Batch 3: [Time, e.g., 10:30 PM], Second half of event programme coverage.

Final batch: [Time, e.g., 11:30 PM or on departure], Remaining coverage from the event close.

Upload each batch directly to [platform upload link or use the Eventiere photographer app]. Each batch should be uploaded within 15 minutes of shooting completing for that session. If you encounter connectivity issues, contact [organiser name] on [phone number] immediately.

File naming convention

The platform processes photos regardless of filename, but a consistent naming convention makes troubleshooting faster and keeps the event library organised if manual review is needed. Use the following format:

Brief Section 5

Naming convention

Export JPEGs with the following naming format: [EventCode]_[YYYYMMDD]_[Sequence]

Example: GALA2025_20251114_0001.jpg

The event code will be provided by [organiser name]. Sequence numbers should be continuous across the full event, not reset between batches. Set your camera's sequential numbering to continue rather than reset at the start of each card.

Post-event handoff

After the event, the full edited delivery follows the standard timeline agreed in your contract. For AI delivery purposes, the unedited JPEG exports uploaded during the event are sufficient. After editing is complete:

What to do if things go wrong

Connectivity fails, cards fill up and laptops crash. The brief should include a clear escalation path so the photographer knows exactly what to do rather than making decisions independently under pressure.

Brief Section 6

Contingency instructions

If connectivity fails mid-batch: Continue shooting. Do not stop. Save all photos to card and attempt upload from a different location or network as soon as possible. Contact [organiser name] on [phone number] to alert them.

If upload speed is too slow to complete a batch on schedule: Upload the registration/arrival batch first (these are the highest priority for guest matching). Defer subsequent batches if necessary. The system will continue processing as uploads arrive, even if they are late.

If the upload platform is unavailable: Continue shooting and save to card. Contact [organiser support contact] immediately. Do not attempt to use alternative upload methods (Dropbox, WeTransfer, etc.) without confirming with the organiser first.

Emergency contact: [Organiser name], [phone number], available from [time] to [time] on the event day.

Send this brief to your photographer at least two weeks before the event. Review the connectivity plan together, confirm the upload device is available and do a test upload at the venue if possible during your pre-event site visit. A brief that is agreed, reviewed and tested is orders of magnitude more valuable than one that is sent and never discussed.

Ready to set up your event for same-night delivery?

Eventiere includes a photographer briefing pack template and a dedicated uploader app with every event subscription. Book a demo to see it in action.

Book a free demo