When to Redo Your Team's Headshots (Not on a Timer)

Somewhere in every company's headshot conversation, someone suggests redoing the set "every couple of years" and everyone nods, because it sounds reasonable and nobody has a better rule ready. It isn't a bad instinct. It's just not the actual trigger. A set redone right on schedule while it's still accurate is a wasted shoot. A set left alone past its schedule while three people carry new titles is quietly lying to anyone who looks at it.

The right time to redo team headshots isn't a fixed interval like "every two years." It's the moment an existing set stops telling the truth about who the company is now, or stops matching itself. Five triggers cause that: a role change, a visible appearance change, a brand refresh, a new-hire backlog, or a mismatched set shot by different photographers.

Forget the calendar — the real trigger isn't a date

The right time to redo team headshots isn't a fixed interval like "every two years." It's the moment an existing set stops telling the truth about who the company is now, or stops matching itself. Five triggers cause that: a role change, a visible appearance change, a brand refresh, a new-hire backlog, or a mismatched set shot by different photographers.

"Every two years" is a scheduling convenience, not a real answer. A set redone on schedule while still accurate is a wasted shoot. A set left alone past its schedule while three people carry new titles is actively misleading anyone who looks at it. The calendar doesn't know either of those things happened. What actually forces the question is specific and checkable: did a role change, did someone's appearance shift enough that the photo doesn't read as them, did the brand itself change, did new hires start piling up unphotographed, or does the set now look shot by three different people because it was. Each is a real trigger with a real cost, covered one at a time below.

A role change makes the old photo actively misleading

A role change is the clearest trigger there is: when someone's title, seniority, or public-facing responsibility shifts, the headshot tied to the old role becomes actively misleading rather than just dated. A junior hire promoted to director, a new department head, or anyone now facing clients or press needs a photo that matches what they actually do now.

An outdated headshot on a merely dated set is a mild inconsistency. One tied to a role change is a small factual error sitting on a website, deck, or press page. The photo taken when someone joined as an associate is still doing duty after they've become the partner clients actually deal with, paired with a title that didn't exist for them a year ago. That gap reads oddly to a journalist doing a background check, a client looking up who they're meeting, or a candidate researching the leadership page before an interview. It's not that the old photo looks bad — it's attached to information that's now wrong, and the mismatch is the kind of small thing that quietly erodes trust in everything else on the page. Promotions and role shuffles are the moments to check this, not a recurring date.

A visible appearance change beats any anniversary

A visible appearance change is a stronger signal than any anniversary, because the test isn't how much time passed — it's whether the photo still looks like the person walking into the room. New glasses, a different haircut, a beard grown or shaved, or a significant change in weight can all make a two-year-old photo stop functioning as identification.

This gets treated as vanity when it's actually practical. A headshot's basic job is letting someone recognize a person before they meet — at a conference badge table, in a client's inbox before a call, on a speaker page before they walk on stage. If the photo doesn't do that job, it isn't working, regardless of how recently it was taken. A photo from eight months ago can already be functionally wrong if the person changed their hair or grew a beard in that window, while a five-year-old photo of someone who looks essentially the same might still be fine. The person themselves is usually the last to notice, because the change feels gradual to them. It doesn't read as gradual to someone meeting them for the first time off a photo that no longer matches.

A brand refresh strands your old headshots visually

A brand refresh strands the old headshot set visually, even when nobody's face changed at all. New brand colors, a new visual identity, or a new backdrop standard makes a current, accurate photo look wrong next to the new logo, because the old set was lit and framed for a look the company no longer uses.

This trigger is easy to miss because it isn't about the people in the photos — it's about the photos next to everything else. A rebrand usually touches the website template, the color palette, sometimes the backdrop style used going forward. Headshots shot against a warm wood-paneled backdrop can look immediately out of place once the site around them shifts to a cooler, minimal palette, even though the portraits themselves are recent and fine on their own. The mismatch isn't in the faces, it's in the frame around them — the kind of thing a designer notices instantly and a founder might not notice until someone points it out. A rebrand that updates everything except the headshots leaves one visibly older layer sitting inside a newer one, undercutting the point of the rebrand itself.

A new-hire backlog is its own trigger

A new-hire backlog is a trigger on its own, separate from anyone's photo going out of date — it's the accumulated gap of people who joined since the last shoot and never got photographed at all. Once that group is large enough, the team page is showing a version of the company that's already missing people.

This is the quiet version of the problem, because nothing looks wrong at first — the existing photos are all current and well shot. The issue is who's missing. Every new hire after the last shoot either gets a phone photo standing in for a real one, or gets left off the page entirely until enough people are missing to justify booking another shoot. Both outcomes read worse than they seem from the inside: a visitor comparing a polished photo next to a phone selfie, or noticing a team page that hasn't kept pace with headcount, draws a conclusion about the company's size and momentum that may not be true. The backlog also compounds — six months of unphotographed hires becomes twelve, and the gap widens every month nobody addresses it.

Inconsistent sets from different photographers are a trigger now

A set built from different photographers on different days is a trigger the moment you notice it, because it means the team page or directory no longer reads as one company — it reads as a patchwork of whoever happened to be available each time someone needed a photo taken.

This tends to happen gradually and for reasonable reasons each time: someone joined between shoots and got a quick photo from a friend's camera, a second office opened and used a local photographer nobody coordinated with, or a founder updated their own photo without looping in the rest of the team. None of those individual decisions looks wrong in isolation. Stacked together, the result is a grid of headshots with different backdrops, lighting, crop ratios, and color casts sitting next to each other, and that inconsistency reads as disorganization even when the company itself is anything but. A visitor doesn't consciously catalog backdrop colors, but they register that something is off — the way a room of mismatched furniture reads as unfinished before anyone can say why.

What each trigger actually costs you if you ignore it

Ignoring these triggers has a specific cost, not a vague one: a role-change gap undermines credibility with clients and press, an appearance mismatch fails the basic job of recognition, a brand mismatch undercuts the rebrand it sits inside, a backlog understates the company's real size, and an inconsistent set reads as disorganized regardless of how the company actually runs.

None of these costs shows up as an obvious complaint — nobody emails to say the headshots look dated. They show up as a small, cumulative drag on how the company reads to anyone encountering it for the first time: a journalist skimming a leadership page before a story, a candidate deciding whether to accept an offer, a client checking who they're about to meet. Each person forms an impression fast, often from a page they spend under a minute on, and a mismatched or outdated set is exactly the kind of detail that shapes an impression without the viewer consciously noticing why. The company doing good work internally gets undersold by a visual layer that hasn't kept pace with it.

How to catch these triggers before they pile up

Catching these triggers early doesn't require a recurring shoot schedule — it requires a short, honest look at the team page a few times a year and a running list: who was promoted, who looks noticeably different, whether the brand changed, how many new hires are unphotographed, and whether the set still looks shot by one team.

The practical version of this is a quarterly five-minute pass, not a calendar reminder to book a photographer. Pull up the team page and look at it the way a stranger would: does every photo match the person's current title, does anyone look meaningfully different than their photo, does the style match what the brand looks like today, is anyone missing, and does the set look coherent or patched together. Most of the time the answer is "it's fine, check again later," which costs nothing. The times it isn't fine are the moments worth acting on, before the backlog grows or the mismatch sits on the site unnoticed for another year. Once a shoot is warranted, how the day itself runs and what the portrait standard looks like across offices is its own set of decisions, covered elsewhere.

Frequently Asked Questions

How often should a company redo its team headshots?

There's no single correct interval — the honest answer is "whenever one of the real triggers hits," not a fixed number of years. A fast-growing team with frequent promotions might need attention every six months; a stable team with no rebrand or hiring might genuinely go three or four years without a real trigger. Checking the team page against the five triggers a few times a year replaces guessing at a schedule.

Does one promoted employee justify reshooting the whole team?

No — a single role change usually justifies photographing just that person, not booking a full team shoot. The exception is when several individual triggers have quietly stacked up at once: a few promotions, a handful of unphotographed new hires, and a set that's started to look visibly inconsistent across the team. At that point, one coordinated reshoot is more efficient than several separate one-off sessions spread across months.

What if the team just doesn't like their current headshots?

Personal dislike of a photo is a real reason to reshoot, separate from the triggers covered here — it's just a different kind of trigger, based on how someone feels rather than how current or consistent the photo is. If someone genuinely dislikes their headshot, that's reason enough on its own, and it doesn't need to wait for a role change or a backlog to justify fixing.

How many unphotographed new hires is too many to ignore?

There's no fixed number, but the useful test is whether the gap is now visible to an outsider — a handful of people missing from a twenty-person directory reads very differently than the same handful missing from a two-hundred-person one. Once a visitor could reasonably notice the team page hasn't kept pace with who's actually there, the backlog has crossed from minor to worth addressing.

Is a slightly inconsistent set really worth fixing, or is that overthinking it?

It's worth fixing once it's noticeable, which is a lower bar than most people assume — mismatched backdrops, lighting, and crop ratios register as disorganization even to viewers who couldn't name what's wrong. It doesn't need fixing the moment one photo looks slightly different from another; it's worth acting on once the page as a whole, not just one photo, stops reading as one coherent team.