How to run a
high-volume headshot event

How many photographers do you actually need?

Start with three numbers: how many people need photographing, how long the event runs, and roughly how long each session takes. A fast, efficient headshot session — get someone in position, a few frames, done — typically runs 2–4 minutes per person. A session with outfit changes, more posing direction, or a more involved setup can run 6–10 minutes or longer.

From there, the math is straightforward: total available shooting minutes per photographer is roughly event duration × 60, minus a buffer for breaks and overhead — 15% is a reasonable starting assumption for a typical event. Divide your target headcount by however many people one photographer can realistically shoot in that time, and round up.

How should you organize registration?

This depends entirely on whether you know who's coming in advance.

• Known list (corporate, internal event): import the roster ahead of time — HR's employee list, a membership database, a spreadsheet export. Everyone is already in the queue before the event starts, and a booking page can let people pick their own time slot rather than waiting in a line.
• Unknown, walk-up traffic (conference, trade show, public event): QR code self-registration is the better fit. A printed code at the booth, a name and email typed on a phone, and someone's in the queue in under fifteen seconds — no advance list needed at all.
• A mix of both: most real events end up here — some people pre-booked, others walking up on the day. Both should feed the exact same queue rather than being managed as two separate lists that need reconciling afterward.

What equipment do you actually need?

Beyond the obvious camera and lighting setup, three things matter specifically for running a queue-based session smoothly:

• A tethering workflow that supports clipboard-based file naming — Capture One's own Next Capture Naming token is the most common, direct route; a Lightroom-based workflow works too via Smart Shooter. This is what lets a file get named to the right person automatically as you shoot, rather than sorted afterward.
• A second device running the queue — a laptop or tablet separate from your shooting setup, positioned where you (or an assistant checking people in) can see who's next without stepping away from the camera.
• Printed or displayed QR codes for any walk-up registration, placed somewhere obvious before someone reaches the front of the line — not at the camera itself, where it just adds a step to an already-moving queue.

How do you prepare participants before they arrive?

A surprising amount of on-the-day friction comes from people simply not knowing what to expect — what to wear, where to go, what the session actually involves. A short, branded pre-event page covering location, timing, a wardrobe suggestion, and a couple of posing tips measurably reduces the number of people who show up unprepared, which is exactly the kind of thing that quietly adds minutes to every single session in the queue.

How do you run the queue without creating bottlenecks?

The single biggest source of dead time in a live queue is the gap between one person finishing and the next person actually being ready. A few things keep that gap short:

• Keep the next 2–3 people visibly aware they're coming up, so nobody's caught off guard when it's their turn
• Activate the next person in the queue the moment the current session wraps, not after you've finished reviewing the shot
• If sessions are running longer than planned, it's usually worth knowing early rather than discovering it an hour before the event ends with fifty people still waiting

How do you name and match files as you shoot, not afterward?

The single most time-consuming manual task in an unmanaged headshot event is matching finished photos back to the right person — worse at 300 people than at 10, and worst of all if it's left until after everyone's gone home. The fix is doing it live: a tethered file-naming workflow where activating someone in the queue copies their unique name prefix to your clipboard, ready to paste into Capture One's Next Capture Naming field once, at the start of their turn. Every frame from that point carries their name automatically. There's no matching step afterward because there's nothing left to match — it already happened during the shoot.

How do you manage multiple photographers at one event?

Beyond a single photographer and a single queue, the same principles need to extend across stations rather than being managed as separate, disconnected setups. Each camera station should have its own independent queue view, so one photographer being backed up doesn't create confusion at another station's screen — while all of it still feeds into one shared registration list and one final set of galleries, not several that need merging by hand afterward.

How do you handle walk-ins and no-shows alongside a schedule?

A pre-booked appointment system inevitably meets two realities: people who don't show up for their slot, and people who show up without one. The practical approach is letting both flow into the same queue rather than treating a missed slot as a problem to solve separately — a no-show's gap gets filled by the next walk-in, and the queue itself doesn't need to know or care which category someone came from.

What happens if the venue's WiFi goes down?

Worth planning for specifically rather than discovering the hard way — convention centers, hotel ballrooms, and shared office WiFi are all notorious for this exact failure. If the tool running your queue depends on a live connection with no fallback, an outage doesn't just slow things down, it can stop the event's logistics entirely mid-session.

How do you match photos to people once the event is over?

If file naming happened live during the shoot (see above), this question mostly shouldn't need answering after the fact at all — every frame is already named to the right person by the time the event ends. The events where this becomes a real, painful task afterward are almost always the ones where naming was left as a manual step for later, which is exactly the habit worth breaking first.

How do you deliver hundreds of galleries efficiently?

Manually emailing individual gallery links doesn't scale past a handful of people before it becomes a genuine, multi-hour task on its own — worth putting a real number on with the workflow cost calculator. The alternative is delivery that happens automatically the moment each person's photos are ready — an email with their own private gallery link, sent without anyone needing to sort or send anything by hand, whether that's the 10th person of the day or the 500th.

How do you manage retouching selections at scale?

Asking 300 people individually which photo they'd like retouched, by email, is its own significant administrative task if handled manually. Built into each person's own private gallery, selection becomes something they do themselves, directly — a shortlist that arrives already organized per person rather than a scattered set of email replies that need matching back to names.

What's worth checking once everything's delivered?

A short list worth confirming before considering an event fully closed out: everyone registered was actually photographed (not just everyone who was scheduled), every gallery was actually delivered rather than stuck in a queue somewhere, and any retouching or print requests are tracked somewhere a client or HR contact can be given a clear answer about status — rather than that answer requiring you to go check.