Headshot planning · Time
How Long Should Corporate Headshots Take Per Person?
There is no single “five minutes per person” answer. Two clean directory portraits and a magazine-style environmental leadership image are different jobs and should be scheduled differently.
What actually matters
The practical variables behind the answer.
This guide comes from the kind of operating decisions we keep running into on real corporate assignments, not from a generic photography checklist.
Simple employee headshot
A repeatable plain-background setup can move efficiently once lighting and crop are locked.
More image variety
Four genuinely different images need more than simply pressing the shutter four times.
Executive environment
A portrait in an office, library, factory or architectural space often needs scouting, clearing and lighting.
Always add buffer
People arrive late, glasses reflect, hair changes and meeting schedules shift. Cut-to-cut planning usually fails.
A workable sequence
How we would think through it on an actual assignment.
Define final count
Decide how many genuinely different images each person needs.
Choose setup type
Plain background and environmental portraits require different time models.
Add transition buffer
Leave 2–5 minutes around each slot for real-world friction.
Protect setup time
Do not pretend lighting build and pack-down are portrait minutes.
Optimise, do not rush
If the total is too long, reduce image variety or split the day rather than destroy consistency.
From the field
A useful rule from actual office portrait days
This is the part that tends to become obvious only after doing the work repeatedly.
We would rather optimise the brief than schedule 15 hours of portraits into a day and hope everyone moves like a machine. Sometimes taking fewer variations per person or separating leadership portraits from employee headshots gives the client a better result and the team a more realistic day.
Decision table
A faster way to make the call.
| Portrait type | Useful planning range | Typical reason |
|---|---|---|
| 2 simple images, one setup | About 10 minutes/person | Fast repeatable team-directory or LinkedIn use. |
| Up to 4 image options | About 15 minutes/person | Allows expression and subtle framing variation. |
| Environmental leadership portrait | 45–60 minutes/setup | Location, light, styling and room preparation add time. |
| Very large employee day | Use blocks + buffers | Scheduling and queue management become part of the shoot. |
Related planning
Continue with the part of the brief you are solving next.
People also ask
Direct answers to the questions that usually follow.
01Can corporate headshots be done in five minutes per person?
Sometimes for a very controlled single-image requirement, but five-minute slots leave little room for expression, grooming, glasses issues or review. We usually prefer a little more breathing room.
02Why do executive portraits take longer?
The location is part of the image. Lighting an office or environmental scene, moving furniture, testing composition and creating a more editorial result takes additional time.
03Should setup time be included in the headshot schedule?
Yes for production planning, even if the commercial quote treats it separately. The team still needs enough time to build, test and pack the setup safely.
04How much buffer should be kept between employees?
A few minutes is useful, especially for larger teams. An office coordinator who keeps the next people ready can dramatically improve throughput.
05Is eight hours too long for a headshot day?
Eight hours of repeated portrait work is already demanding. Plan breaks and avoid treating the entire day as uninterrupted shooting time.
06Can Tell-a-Tale Studios estimate timing before the shoot?
Yes. Share the employee count, number of final images, background style, location and usage, and we can build a realistic schedule.
Planning something similar?
Share the date, location, timings, people involved, intended usage and delivery expectations. We will suggest a realistic setup instead of forcing the brief into a generic package.