Keep every subject tied to the right gallery
Use a consistent studio-side record for the subject, proof set, selection state, and client communication instead of relying on filenames alone.
Corporate headshot operations
Keep many subjects, selections, retouching instructions, file variants, and final handoffs moving through a process the studio can verify.
Where volume breaks the process
Corporate headshot work multiplies small operational questions: who has chosen, which frame is approved, what needs retouching, which file sizes were promised, and whether the final package reached the right person. A repeatable workflow makes those states visible.
Operating stages
Use a consistent studio-side record for the subject, proof set, selection state, and client communication instead of relying on filenames alone.
Separate favorites from final submissions and keep image-specific notes attached to the selected proof so production begins from an explicit brief.
Prepare predictable file variants, archive naming, delivery instructions, and a clear finals-ready state before the handoff goes out.
Keep the sent message and client download moment connected to the gallery so the studio can see what was delivered and what still needs follow-up.
Final package
• Full-size retouched finals
• Web- or profile-ready versions when the job requires them
• Predictable filenames that identify the subject
• A simple manifest or usage note for multi-file packages
• A branded delivery message with the exact download action
• A studio-side delivery and download record
Selection control
The Studio Ops guide explains how to curate proof sets, separate favorites from submitted choices, and keep retouching notes connected to the right image.
Read the high-volume headshot proofing guide Use the free corporate job tracker Use the file-naming checklistFAQ
Treat each subject as a tracked workflow: proof set, submitted selection, retouching notes, finals-ready package, delivery message, and confirmed download. Consistent states matter more as subject count grows.
They can belong to the same job, but they should remain distinct stages. Proofs support a choice; final delivery presents the completed files without leaving the earlier selection record ambiguous.
The exact contents depend on the client agreement, but a clear package commonly identifies full-size finals, any web-ready variants, predictable filenames, and simple usage or download guidance.