The Email That Saves Your Headshot Day

The single cheapest fix for a bad headshot day is a better email. Not better lighting, not a longer session, not a bigger budget. The message that lands in everyone's inbox a week out decides how many people show up, what they wear, and whether they arrive already braced for something unpleasant.

A headshot-day email should answer four things: when the person's slot is, what to wear, where the photo will be used, and how long it takes. Vague announcements produce no-shows and stiff expressions because people fill the gaps with worry. Specifics remove the guesswork that makes a five-minute portrait feel like a performance review.

What the Announcement Email Is Actually Doing

A headshot-day email is not a calendar notice. Its real job is to lower the stakes before anyone walks into the room, because most of the tension in a corporate portrait was generated hours earlier by someone reading a vague announcement and quietly deciding this was going to be embarrassing.

People are not nervous about cameras in the abstract. They are nervous about being caught unprepared, about the photo living somewhere they cannot control, and about looking wrong next to colleagues who apparently got a memo they missed. Every one of those worries is an information problem, and every one of them is fixable in a paragraph.

This is why we treat the email as part of the production, not admin overhead. A well-briefed room shoots faster, needs fewer retakes, and produces expressions that look like the person rather than like someone waiting for the shutter to be over. The photographer can only work with whoever walks in. The email decides who that is.

Give People a Slot, Not a Window

The most useful thing an email can contain is a specific time and a specific length: your slot is 10:40, it takes about five minutes, you can go straight back to your desk. A four-hour window with an open invitation to drop by produces two problems at once — a queue at lunch and nobody at 9:15.

Open windows also make the day feel optional in a way that quietly raises the no-show rate. When a slot has someone's name on it, skipping it becomes a decision rather than a default, and people who would have wandered off do the thing. If a signup sheet is doing the scheduling, the email still needs to say how long a slot actually takes, because most people budget half an hour in their head and then avoid the whole thing.

It also helps to name the practical shape of the day: where the setup is, whether there is somewhere to leave a bag, whether there is a mirror. These sound trivial written down. They are the difference between someone arriving composed and someone arriving flustered, and the camera reads that difference immediately.

It is also worth naming who is running the day. A schedule with a person's name attached — the coordinator, not the photographer — gives people somewhere to send a conflict, and it turns the whole thing from a corporate event into a normal appointment with a colleague.

Wardrobe Guidance That Isn't a Dress Code

Wardrobe advice works best as a short set of practical notes rather than a policy: solid colors photograph more cleanly than tight patterns, mid-tones sit better against most backgrounds than pure white, and layers give the photographer options. That is enough. A long dress code turns a portrait into a compliance exercise.

The instinct to over-specify usually comes from a good place — someone wants the set to look consistent. But consistency comes from the lighting, background, crop, and retouching standard, which are all the photographer's job. It does not need to come from making forty people dress like each other, and attempts to enforce that tend to produce a set that looks like a uniform rather than a team.

One line worth including: people can bring a second option. A jacket in a bag costs nothing and solves the case where someone's shirt turns out to fight the background. It also gives anyone who is anxious about the day a small amount of control, which does more for their expression than any amount of reassurance in the email body.

Say Where the Photo Will Actually Be Used

Naming the destination — website bio, LinkedIn, internal directory, a conference program — changes how people feel about the session more than any other line in the email. An unexplained photo feels like surveillance. A photo with a stated job feels like work, and people are generally fine with work.

It also produces better decisions on the day. Someone who knows the image is going on a client-facing bio page dresses for that. Someone who knows it is replacing a fuzzy avatar in an internal directory relaxes accordingly. Without that context, everyone defaults to the highest-stakes interpretation they can imagine, which is exactly the mindset that produces a tight jaw in every frame.

If there is a retention or replacement policy — photos get refreshed when someone changes roles, or the old one comes down when a person leaves — say so plainly. That single sentence resolves a surprising amount of quiet resistance, particularly from people who have been burned by a stale photo following them around a company intranet for six years.

The People Who Would Rather Skip It

In every group there are a few people who genuinely do not want to be photographed, and pretending otherwise makes the day worse. The email should acknowledge that directly and offer a smaller ask: come see the setup, we will take a couple of frames, you decide afterward whether you use one.

That framing works because the objection is usually not the photo — it is the loss of control over the result. Handing back the decision about whether the image gets used removes most of the reason to avoid the room, and in practice a lot of reluctant people end up with something they are happy with once the shutter is no longer the point of no return.

It also matters who sends this. An email from a manager reads as an instruction; the same words from whoever is coordinating the day read as logistics. When there is a specific person to reply to with a question — a scheduling conflict, a private concern about how the photos will be used — that path needs to exist in the email itself, not in a thread nobody can find.

Two Emails Beat One

The pattern that works is a longer email about a week out and a short one the day before. The first carries the context — what the photos are for, wardrobe notes, how long it takes. The second carries only what someone needs in the next twenty-four hours: your slot, the room, bring a second top if you want options.

One email tries to do both jobs and does neither. Sent early, the details are forgotten by the time they matter. Sent the night before, the wardrobe guidance arrives after everyone has already decided what to wear, which is the most common version of this failure and the one that shows up in the final set as a wall of unfortunate patterns.

The day-before note is also the last cheap chance to catch schedule collisions. People who were traveling, out sick, or double-booked surface at that point, and a coordinator can still move a slot. Finding out during the shoot means either a gap in the schedule or a gap in the team gallery, and the second one tends to get noticed later by whoever is building the website page.

What to Leave Out

Leave out the pep talk. Lines about having fun, bringing your best self, or smiling naturally have the opposite of their intended effect, because they signal that a performance is expected. The most relaxed rooms we work in got that way from clear logistics, not from encouragement.

Also leave out anything that sounds like a threat. Attendance is mandatory, photos will be used regardless, this is the only chance until next year — even when parts of that are operationally true, leading with it guarantees a set of portraits where everyone looks like they were summoned. If a deadline genuinely exists, state it as a fact about the schedule rather than as leverage.

And skip the retouching promises. Telling people not to worry because everything gets fixed afterward tends to increase self-consciousness rather than reduce it, and it sets an expectation about the finished look that a natural-retouching standard will not meet. If people ask, the honest answer is that the edit removes temporary distractions and leaves the person recognizable — which is a better sentence in a reply than in a mass email.

Frequently Asked Questions

How far in advance should you email employees about a headshot day?

About a week out for the full email, then a short reminder the day before. A week gives people time to think about wardrobe and flag scheduling conflicts without the details going stale. The day-before note only needs the slot time, the room, and one wardrobe reminder. Sending a single email either too early or too late is the most common reason people arrive unprepared or do not arrive at all.

What should you tell employees to wear for corporate headshots?

Keep it to a few practical notes rather than a dress code: solid colors over tight patterns, mid-tones rather than pure white, and a second option in a bag if they want one. Consistency across the set comes from the lighting, background, and crop, not from everyone dressing alike. Long wardrobe rules tend to make people anxious, and anxious reads clearly in a portrait.

How do you handle employees who do not want their photo taken?

Acknowledge it in the email and lower the ask. Invite them to see the setup, take a couple of frames, and decide afterward whether any of them get used. The resistance is usually about losing control of the result rather than the camera itself, so handing that decision back removes most of the objection. Also name a person they can raise a private concern with.

How long does one person's headshot slot actually take?

For a standard team session, roughly five minutes per person once the setup is running, which is why slot-based scheduling works better than an open window. People tend to assume it will take much longer and avoid the day accordingly. Stating the real length in the email removes that assumption and keeps the schedule tight enough that nobody spends their morning in a queue.

Should the email say where the headshots will be used?

Yes, and it is one of the highest-impact lines in the whole message. Naming the destination — website bio, LinkedIn, internal directory, event program — turns an unexplained photo into a task with a purpose. Without it, people default to the highest-stakes interpretation they can imagine, which produces visible tension. If there is a policy for replacing or removing old photos, say that too.