Corporate Headshot Day: Approving 60 Employees' Photos

The scheduling math nobody checks before booking the day

Photography studios that run headshot days routinely quote 5–10 minute booking slots per person, but once you count the walk-in, the seat adjustment, the couple of expressions, and the walk-out, the realistic per-person budget lands closer to 12–15 minutes. That gap is where headshot days quietly run three hours long.

The buffer figures above add roughly 10 minutes per hour of shooting — a standard scheduling practice for headshot days, to absorb late arrivals and no-shows without the whole line sliding. Do the arithmetic before you book the room: 600 minutes ÷ 60 minutes = 10 hours of pure shooting, and no single-day booking window comfortably holds an 11.7-hour session plus setup and teardown. That's the argument for shoot-and-go, not a preference — it's the only version of the math that fits in a working day.

The same math scales the wrong direction fast. At the 10-minute on-site pace, a 120-person company doesn't need a longer day — it needs a second photographer, a second day, or both, because 120 × 10 minutes is 20 hours, well past what a single booth can absorb even across a long shift. At the 6-minute shoot-and-go pace, that same 120 people fits into a 12-hour day with one photographer, or a comfortable 6-hour day split across two stations shooting in parallel. Run the number for your own headcount before you commit to a room booking: minutes-per-person × headcount, divided by 60, is the hours of shooting you're actually scheduling — before setup, breakdown, or a single review happens.

Two stations running in parallel doesn't double throughput as cleanly as it sounds, either. Each station still needs its own background, its own lighting setup, and ideally its own retoucher applying the same editing preset afterward — otherwise the two halves of the directory end up looking like they were shot by two different studios, which is its own consistency problem the approval stage then has to catch.

Why on-site review costs more time than it saves

On-site review feels efficient — the employee picks their favorite right there, done. In practice it adds a queue: one workstation, one person reviewing at a time, while the line behind them waits on the same clock as the shooting. A 4-minute review per person against a 6-minute shoot doesn't run in parallel on one line; it adds straight to the total.

Sending a private review link after the session removes the queue entirely. The photographer keeps shooting at a fixed cadence; each employee reviews on their own time, from their phone, without holding up anyone else.

There's a second, quieter cost to on-site review: the employee is deciding under the worst possible conditions. They've just sat under studio lighting, they're aware of the line behind them, and they're looking at unedited frames on a monitor they didn't calibrate. That's a rushed decision on a photo that's going to represent them on LinkedIn and in the company directory for the next two or three years. A review link sent that evening lets them look at retouched, color-corrected frames on their own phone, with no one waiting — which produces a faster approval on average, not a slower one, because there's nothing to second-guess later.

The workstation itself is also a cost most schedules don't count: it's a second piece of equipment, a second person to staff it or a self-serve kiosk to configure, and floor space next to the shooting area. None of that shows up in the per-slot time estimate, but all of it has to be booked, powered, and struck at the end of the day along with the lighting rig.

One link per employee, not one shared folder for sixty

A shared drive folder with 60 subfolders looks organized until an employee has to find their own name, open the right one, and guess which of four similar frames is "final." That friction is what turns a same-week turnaround into a three-week one, because half the delay in a bulk shoot isn't editing — it's employees not knowing a decision is waiting on them.

The status view is the part that actually saves the admin hours. If HR has to individually message stragglers, that's roughly 5 minutes of drafting and follow-up per non-responder. At a typical 15–20% non-response rate on a 60-person shoot, that's 9–12 people × 5 minutes — 45 to 60 minutes of pure chase work that a status dashboard and an automated reminder replace for free.

Permissions matter here too, and a generic shared folder handles them badly. Employee A shouldn't be able to open employee B's unretouched frames — not because any one photo is sensitive, but because a shared folder with 60 people's unedited faces in various expressions is exactly the kind of thing someone screenshots and forwards before the retouched versions ever ship. A per-employee link scoped to that employee's own frames removes the problem structurally instead of relying on everyone behaving.

It also solves a smaller but real annoyance: naming collisions. Two people named "Sarah Chen" or a folder sorted by first name instead of last name turns a two-second lookup into a search. A unique link per person sidesteps naming entirely — there's nothing to search, because there's nothing to find among.

Who actually approves the photo — and why it can't be the employee alone

Employee choice and brand approval are two different decisions, and conflating them is where corporate headshot sets go sideways. An employee picks the frame where they look most like themselves. Brand or HR checks it against the standard: consistent background, consistent crop, consistent retouching level across the whole directory.

Name one person — usually someone in Brand, Marketing, or HR — as the final approver before the shoot, not after the first inconsistent frame shows up in the directory. Their job is narrow: confirm the crop, background, and retouching match the standard the other 59 photos are held to. Everything else is the employee's call.

Skipping this second layer is how a directory ends up with one person's headshot noticeably brighter than everyone else's, or a background that's slightly warmer in one crop because a different preset got applied by mistake. Individually, none of those photos looks wrong. Side by side in a company directory or an all-hands slide deck, the inconsistency is the first thing anyone notices — and by then it's 60 photos to re-review instead of one.

Write the standard down before the shoot, not during review. A one-paragraph brief — background color, crop ratio, retouching level (skin smoothing yes or no, teeth whitening yes or no, blemish removal only) — gives the approver something concrete to check against instead of a subjective "does this look right" pass on 60 photos in a row. It also gives the photographer and retoucher the same brief, so fewer photos fail the check in the first place.

Handling the retake list without a second full day

On any 60-person shoot, a handful of people won't have a usable frame: eyes closed on every shot, a shirt collar that didn't sit right, someone who was out sick on the scheduled day. Budget for this instead of being surprised by it — a single review link per person makes the retake list self-reporting: anyone who doesn't approve a frame within the review window is, by definition, on it.

Keep a standing half-day slot two to three weeks out for retakes and new hires, rather than trying to catch every straggler on the original day. Chasing the last three people in person costs more scheduling overhead than one short follow-up session that reuses the same background and lighting setup.

New hires make this a recurring problem rather than a one-off. A company that onboards four or five people a month accumulates a retake-and-new-hire backlog of roughly the same size as the original shoot within a year, one or two people at a time. Treat the retake day as a standing quarterly slot on the calendar rather than something someone has to remember to schedule, and the backlog never grows large enough to need its own full production day.

Set the review window explicitly — five to seven business days is typical — and say so on the link itself. An open-ended "review whenever" window is how a 60-person shoot still has four unapproved photos two months later, not because anyone refused, but because nothing ever forced the decision.

Delivering files people can actually use

The directory needs one crop; LinkedIn wants a different one; some employees want a print-ready file for a conference badge. Deciding this per request multiplies the same admin problem the review stage just solved.

Generate all three at export time and attach them to the same per-employee link the approval happened on, rather than fielding individual format requests after the fact. This mirrors the same logic that applies to fast-turnaround delivery in other verticals: the bottleneck is almost never the edit itself, it's the number of separate touches a file needs before it reaches the person who wants it.