AI Workflow Notes · Event Production MOFU
Event Photographer Prep: 5 Things to Send
A working photographer's list of the five documents that decide whether your event coverage lands clean or scrambles all day.
Last October I shot a product launch in Neihu. The organizer sent the run of show at 11pm the night before — the client had kept editing the speaker order until midnight. I showed up at 7am, scanned the PDF for two minutes, and spotted a problem: the CEO’s opening remarks were slotted before press check-in ended. Half-empty room for the money shot. I texted her, she moved the first fifteen minutes around, and the launch photo landed on three tech outlets the next day.
That save cost me nothing. It could have cost her the shot. Most event photographers I know have a version of this story. We can rescue a lot on the day, but only if we’ve had time to actually read the plan.
The gap between a good event shoot and a mediocre one is rarely about camera gear. It’s about how much runway the organizer gave the photographer to prepare. Five documents, one week ahead. Here’s what and why.
1. Run of Show With Honest Timing
Three columns: time, activity, location. No decorative styling.
The timing has to be honest. Not the version you sent the client to make the day look tight. The real version, with buffer. If registration runs 9:00-9:30 on paper but always spills to 9:45, write 9:45. If the keynote is billed at 20 minutes but the speaker always runs 30, write 30.
I plan lens changes, battery swaps, and position moves around the schedule. If transitions are off by ten minutes, I’m in the wrong spot with the wrong lens twice a day. Off by twenty, I miss handshakes and applause moments. Honest timing lets me sync with the actual event, not the fantasy.
Prep time: 45 minutes if you already have a working run of show. Duplicate, strip the client polish, add the honesty pass.
Also flag the moments the client will ask about later. Awards, group photo, ribbon cutting, gift exchange. If you don’t tell me, I guess from industry context, and my guess is about 80% right.
2. Priority Shot List (Not a Wish List)
Every organizer has a shot list. The problem is “want” usually means 60 shots when the day budgets for 25 well-executed ones. No priorities means a wish list, and wish lists lead to compromise across the board.
Tier it. Tier 1 is must-have — 8-12 shots that if missing would trigger a client complaint. CEO on stage, keynote wide, sponsor logo, awards moment, main group photo. Tier 2 is nice-to-have, 15-20 items for depth if time allows: networking candids, detail shots, atmosphere frames. Tier 3 is opportunistic bonus.
For each Tier 1 shot, include the name spelled correctly, the moment I should be in position for, and any special context. “James Wu, CFO, will present the 5-year growth chart at approximately 10:45. Capture him gesturing at the screen, not standing at the podium.” That level of detail changes what I do with the fifteen minutes leading up to 10:45.
Without a priority list, I shoot broadly and hope. That produces 800 mediocre frames instead of 400 great ones.
Prep time: 90 minutes for a new event type, 30 if you can adapt an old list. Send it as a Google Doc so I can add questions in comments.
3. Access Map With Real Constraints
The access map is the venue floor plan annotated. Where I can and cannot stand, where the best sightlines are, where the invisible constraints live.
Red for restricted zones: backstage, sponsor lounge, VIP prep, anywhere I need permission first. Yellow for AV and lighting positions so I know not to block them. Green for the two or three angles you already know will produce the strongest shots. Weird lighting quirks (LED wall that flickers on camera, low ceiling that kills flash) go directly on the map.
Also show me power outlets and a place to leave my bag. Sounds small. Isn’t. On a 10-hour event, a designated corner to swap batteries, dump SD cards, and drink water is the difference between staying sharp all day and making mistakes by hour six.
I’ve had events where I discovered restricted-zone rules by getting yelled at by venue security in front of guests. Ten minutes of your prep saves an hour of on-the-day friction.
Prep time: 30 minutes with the venue floor plan open. If you’ve never been to the venue, do a site visit first. This map is way better if you’ve physically walked the space.
4. Contact Grid for Mid-Event Decisions
During the event I’ll need to make 5-10 real-time calls that require input. Follow the CEO into the sponsor room? Is this cocktail hour a shoot moment or a break? Did the client actually want the last-minute VIP captured?
I can’t figure out who to text on the fly. Give me a small grid: role, name, phone, best channel (LINE, WhatsApp, SMS), what to escalate.
- Overall event decisions → You. LINE. Anything schedule-related or client-facing.
- VIP and speaker questions → Sarah, client-side liaison. WhatsApp. Anything about the invited guests specifically.
- Venue and access issues → Mike, venue coordinator. SMS. Locked doors, missing equipment, security friction.
- AV and tech questions → Jason, AV lead. LINE. Lighting changes, mic issues affecting shots.
Four contacts is usually enough. More than six and I won’t remember who does what under pressure.
Without a grid I default to texting you for everything, which floods your phone during the exact hours you’re busiest. With one, questions route correctly and get answered in under two minutes.
Prep time: 20 minutes. The hardest part is convincing the four people they’ll get a few texts from an unknown Taiwan number and shouldn’t ignore them. Warn them a day ahead.
5. Delivery Expectations, Written Down
The most-avoided conversation between organizer and photographer. Everyone assumes it’s obvious and everyone means something slightly different. Write it down before the event so there’s no post-shoot negotiation.
Four questions to answer:
- How many selects? Give me a number. “200-300 hero shots” beats “the good ones.”
- What formats? Full-res JPG for archive, web-optimized for social, or both? Any raw files? If the client wants raw, that changes my in-camera settings.
- When? 24-hour turnaround for 10-20 social selects, 5-day for full delivery is a common pattern. Confirm it upfront.
- Delivered to whom, and how? Google Drive to you, or direct to the client? Named folder structure? Watermarking?
Post-shoot delivery is where most photographer-organizer relationships get frayed. You told the client “photos this week” and the photographer told you “5 business days” and those two things collided on a Tuesday morning with an angry email. Written expectations, agreed one week ahead, prevent this.
Prep time: 15 minutes and one clarifying message. If you’re not sure what to ask for, default to my four questions and I’ll fill in reasonable numbers.
The Real Return on Prep
I’ve shot around 400 events across ten years of running a studio in Taipei. The correlation between how well an organizer prepared and how well the coverage landed is close to 1:1. Events with strong pre-briefs almost never produce complaints. Events without them produce complaints roughly a third of the time, even when the photography itself was solid.
The five items above take a working organizer about three hours to prepare. Three hours of your time buys 8-12 hours of a photographer’s undivided attention, focused on the shots that matter to your client. That trade is worth making every time.
If you’re budgeting a new event and thinking about coverage scope, event video pricing in Taiwan has current numbers for how coverage cost scales with event length and scope. If you want the underlying system I run all this prep through, Solo Stack Method shows the four layers I use to keep a solo studio delivering enterprise-scale work.
FAQ
Do I really need all five if it’s a small event? For anything under 3 hours with fewer than 30 guests, you can compress items 3 and 4 into a single WhatsApp message. But 1, 2, and 5 always apply. Event scale doesn’t change how photographers prepare, it changes how much prep you can skip without consequences. For a two-hour brand meetup, missing the run of show still means I show up unprepared.
What if the client keeps changing things last minute? Send me the current version one week ahead, then send updates as they happen. I’d rather plan against a stale version and get three revisions than have nothing until midnight. Version-control it if you can. “Run of show v3, final” tells me at a glance where we are.
How much of this is different for a videographer vs a photographer? Videographers need the same five documents, but the run of show matters even more because they’re often locking down camera positions that can’t move. Hiring both? One shared package works. See event photo vs video coverage for how the two roles differ on the day.
Is a professional photographer expected to figure all this out on their own? No. A working photographer will ask you these questions if you don’t send them. But asking the day before means you’re doing prep on the wrong timeline. The point of sending everything a week ahead is that both sides have time to spot problems while there’s still room to fix them.