New Hire Headshots: How to Make a Photo Part of Week One

Treat the headshot like a laptop or an email account: a week-one onboarding task with a named owner and a hard deadline. Pick one delivery method — self-serve AI, a quarterly batch day, or a per-hire local shoot — store one canonical file, and push it to every system from there. Drift stops.

Why the photo only ever happens in week one

Every company photo program dies the same way: it launches with a big shoot, looks sharp for six months, then decays one hire at a time. By month twelve the team page is a mix of studio portraits, cropped wedding photos, and four people with no picture at all.

The math is unforgiving. A company growing headcount 20% a year with 15% attrition replaces or adds roughly a third of its faces annually. If the only way to get photographed is "wait for the next all-hands shoot," then at any given moment a meaningful slice of your directory is wrong — and it's always the newest people, who are the ones most likely to be introduced to customers, candidates and partners.

Distribution makes it worse. Gallup's tracking of remote-capable US employees has been stable for a while now: roughly 52% work hybrid and about a quarter are exclusively remote, with only about a fifth fully on-site. A single-office shoot day simply cannot reach a workforce that is spread across three time zones and rarely in the same room.

Week one is the moment of maximum compliance. A new hire is filling out tax forms, signing a handbook, setting up 2FA and joining eleven Slack channels. Adding "submit a headshot" to that list costs you almost nothing in goodwill. Asking the same person in month seven, mid-quarter, mid-deadline, gets ignored — politely, but ignored. Nothing about the request has changed; the surrounding context has.

Here's where the gap actually shows up, usually at the worst time:

• Sales proposals and pitch decks with a bio slide that has a grey silhouette on it
• The public About or Team page, where half the grid is inconsistent and the newest hires are missing
• Slack and Teams, where default initials make a new colleague harder to recognize in their first month
• The careers page and recruiting materials, which quietly signal how organized you are
• Conference and webinar speaker cards, requested with 48 hours' notice
• Badges, intranet org charts and email signatures — small things that make onboarding feel finished or unfinished

Three delivery models, and when each one wins

There are only three practical ways to get a photo of a person who joined on Monday: they shoot themselves and run it through AI, they wait for a scheduled batch day, or you send them to a local photographer. Most companies should run one as the default and keep a second as the fallback.

Model A — self-serve: selfies plus an AI generator

The new hire takes a handful of phone selfies, runs them through an AI headshot tool, picks a result that matches your spec, and sends the file back. It is the only model that works identically for someone in Denver, Lisbon and Manila, and it is the fastest — minutes, not weeks.

• Best for: distributed teams, high-volume hiring, contractors, anyone who joins between batch days
• Cost per hire: low, and predictable — no travel, no studio, no coordination time
• Turnaround: same day, which is the whole point in a week-one process
• Watch-outs: results depend heavily on the input photos. Bad lighting, hats, sunglasses, heavy filters and group crops produce mediocre or uncanny output. Send hires a short input guide, not just a link — our guide to input selfies that actually work covers what to capture and what to avoid.

Be honest with yourself about the limits. AI output is a portrait of a person against a generated backdrop; it is not a photo of that person in your office, holding your product, or standing with their actual team. If your brand relies on documentary-style environmental photography, AI headshots will look like a different visual language sitting next to it. Fine detail can also misbehave — glasses, jewelry, unusual hair — which means someone has to actually look at each file before it goes live. And in a few conservative contexts, such as senior legal, private banking or executive bios in regulated industries, some people will prefer a photographer's work, and that preference is reasonable.

Model B — the quarterly batch day

You book a photographer for one day per quarter, in one hub office, and every hire who joined since the last session gets photographed. New hires who joined between sessions use a temporary photo, then get replaced on batch day. This is the classic answer, and it is genuinely good when your people are co-located.

• Best for: single-hub companies, teams with a strong in-person culture, brands with a distinctive photographic look worth protecting
• Cost: published 2026 pricing guides put half-day corporate sessions at roughly $1,500–$3,500 and full days at roughly $3,000–$6,000, with individual photographers quoting inside that band — one NYC/NJ studio lists $2,500 for a half day and $4,500 for a full day
• Per-person economics: rates fall as headcount rises. One Bay Area studio publishes about $200–$300 per person for a group of 5–10, dropping to roughly $100–$150 per person above 50 people
• Watch-outs: the quoted number is rarely the real one. Extra retouched images are commonly billed at $25–$75 each, on-site setup fees run $150–$500, and the same NYC/NJ guide puts the effective per-person cost at volume closer to $300–$450 once retouching and coordination are counted. Add the people who don't show up to their slot, and someone hired the day after a session waits up to three months.

Model C — per-hire local shoot

You give each new hire a budget and a spec and let them book a local photographer near them, then reimburse it. It scales geographically without your team coordinating anything, and the photos are real photographs of real people, taken by someone who can direct them.

• Best for: small senior teams, exec hires, client-facing roles where the photo works hard
• Cost: highest per person, and it varies wildly by city — individual corporate sessions are commonly quoted from around $150 for a short mini-session up to $1,500 or more for executive work; see our honest benchmark on what professional headshots cost
• Watch-outs: consistency. Fifty photographers produce fifty backgrounds, fifty crops and fifty retouching styles. Without a tight written spec this model is the fastest way to get an incoherent team page, and the admin load lands on whoever approves expenses.

The pragmatic setup for most growing companies is a hybrid: self-serve AI as the default so nobody ever waits, plus a batch day once or twice a year for the people whose photos do heavy commercial lifting. That keeps coverage at 100% while spending real photography budget only where it earns its keep.

What week one actually looks like

A process people follow is short, has one owner, and states the deadline up front. Here is the sequence that survives contact with a busy People team, mapped to days. Adjust the days, keep the structure: request before day one, submit by day three, published by day five.

1. 1Pre-boarding (before day one): the photo request goes out with the rest of the paperwork, alongside laptop shipping and account setup. Include the spec, an example image, the deadline and the name of the person to ask.
2. 2Day one: the onboarding checklist in your HRIS shows "Submit headshot" as an assigned task with a due date. If it isn't a task with a due date, it isn't a process.
3. 3Days two to three: the hire submits. Self-serve hires generate and choose; batch-day hires book their slot; local-shoot hires book and file the expense.
4. 4Day three: the owner reviews the file against the spec — crop, background, lighting, resolution. One round of feedback maximum. Nobody's second week should be spent re-shooting.
5. 5Day four: upload the approved master file to the HRIS as the canonical record and note the capture date in a custom field. That date is what makes future refresh cycles possible.
6. 6Day five: publish everywhere — Slack, Microsoft 365 or Google Workspace, the intranet directory, the public team page if the hire consented, email signature, badge.
7. 7Day five: mark the task complete. The manager's week-one wrap-up should confirm the photo is live, the same way it confirms hardware and access.

One design choice does most of the work: make the request opt-out, not opt-in. "Here is your slot, or your link — tell us if you'd rather not" produces near-complete coverage, because doing nothing is not an option. "Let us know if you'd like a headshot" produces a trickle and a spreadsheet of follow-ups, because doing nothing is the path of least resistance. Same task, opposite default.

Where the photo should live — and which copy is canonical

Most directory drift is not a photography problem, it's a file-management problem. Ten systems each hold a differently cropped, differently compressed copy, nobody knows which is current, and when someone changes their photo in Slack the team page keeps the four-year-old one forever.

Pick one canonical source

Store the master in your HRIS record — Workday, BambooHR, Rippling, HiBob, whatever you run — and keep the original high-resolution file in a single shared drive folder with a strict naming convention, for example lastname-firstname-2026-07.jpg. Everything else is a derivative generated from that master:

• Master: square, roughly 2000×2000 pixels, minimal compression, untouched original retained
• Web derivative: 800×800, compressed for the team page and intranet
• Avatar derivative: 512×512 or 1024×1024 for chat and collaboration tools
• Optional wide crop: for speaker cards, press kits and blog author bylines

Platform specs worth knowing before you upload

Every system has its own ceiling, and hitting the wrong one is why photos look soft or refuse to upload. These are the current published requirements for the tools most People teams touch. Our full LinkedIn size and spec reference goes deeper on the profile side.

• LinkedIn: minimum 400×400, up to 7680×4320, file under 8MB, JPG, GIF or PNG. Around 800×800 is the practical sweet spot, and the frame is cropped to a circle.
• Slack: Slack's help center asks for a minimum of 512×512 and no larger than 1024×1024.
• Microsoft 365 (Teams, Outlook, SharePoint): Microsoft's admin documentation states the maximum supported photo size is 4MB, in PNG, JPG or GIF. Microsoft Graph serves HD sizes up to 648×648, so treat that as the useful ceiling. Note two quirks: profile picture changes can take up to 24 hours to appear everywhere, and while admins can set a photo from the Microsoft 365 admin center, removing one requires Microsoft Graph PowerShell.
• Google Workspace: JPEG or PNG only, maximum file size 5MB, maximum 20 million pixels. Admins can add, replace or remove a user's photo from the Admin console, or script it with the Admin SDK Directory API.
• BambooHR: the web uploader takes PNG, GIF, JPG or BMP up to 10MB and recommends a square image, because the display box is square. If you push photos through the API instead, the file must be square within one pixel and at least 150×150 — the endpoint does not crop for you.
• Your website: whatever your CMS wants, generated from the master — never re-uploaded from someone's Slack avatar.

If your HRIS has an API and your identity provider supports scripted photo updates, one script that reads the canonical folder and pushes to Google or Microsoft removes the most annoying manual step in the whole flow. That's an afternoon of work that pays for itself within a year of hiring.

The new-hire photo request, ready to copy

Most photo requests fail because they ask for a favor instead of assigning a task. This template does five things: names the deadline, names the method, states the spec, says exactly where the photo will appear, and offers a clean opt-out. Swap the bracketed parts and send it with pre-boarding paperwork.

<strong>Subject: Your headshot — one small week-one task</strong><br><br>Hi [Name], welcome aboard. One quick item for your first week: we need a photo for your Slack profile, your email and HRIS profile, and our team page.<br><br><strong>Deadline:</strong> end of day Friday, [date].<br><strong>How:</strong> [Option A: take 6–10 phone selfies following the short guide linked here and run them through [tool], then send us your favorite. / Option B: book a 15-minute slot with [photographer] at [link]. / Option C: send an existing photo that meets the spec below.]<br><strong>Spec:</strong> square crop, head and shoulders, eyes to camera, plain light-grey or neutral background, business-casual top in a solid color, even natural light, no hats or sunglasses, at least 800×800 pixels, JPG or PNG.<br><strong>Where it appears:</strong> [HRIS], Slack, [Google Workspace / Microsoft 365], your email signature, your badge, and the public team page at [URL].<br><strong>If you'd rather not appear publicly:</strong> reply and say so. We'll use your photo internally only — that's a normal request and it changes nothing else.<br><strong>Questions:</strong> reply here or ping [owner] in [#people].<br><br>Thanks — [Owner], People Ops

The failure modes this template is designed to remove, in rough order of how often they bite:

• No deadline, so it lands in the "someday" pile
• No example image, so five people interpret "professional" five different ways
• No named owner, so questions go nowhere and the task stalls
• No statement of where the photo will be used, which is both a trust problem and, in the EU, a transparency obligation
• No opt-out, which forces awkward conversations for people with genuine safety, religious or personal reasons
• Sent in week three instead of week zero, at which point you're chasing

Write the spec once so photos stop drifting

Consistency comes from a written standard, not from a shared vendor. Two photographers with the same one-page spec produce a more coherent grid than one photographer working from vibes across two years. Write the spec once, publish it where hires can find it, and reference it in every request.

Six variables do almost all the work:

• Background: one approved option, stated as a color, not a mood — "light grey, seamless" beats "clean and modern"
• Crop: head and shoulders, square aspect ratio, and a stated headroom figure so nobody guesses — for example, top of the head roughly 8–10% down from the frame edge
• Wardrobe: solid colors, collar or clean neckline, no busy patterns or logos
• Expression: pick a house style — warm closed-mouth smile, or open smile — and show an example of each
• Light: soft, frontal, no hard shadow across the face, no mixed color temperature
• Delivery: file format, minimum pixels, naming convention, and where to send it

If you'd rather not draft it from scratch, our copy-paste company headshot guidelines template is written to be pasted straight into a Notion page or handbook, and team headshots for remote teams covers the harder problem of getting one consistent look across cities and methods.

Consent, privacy, and what happens at offboarding

This is the part most onboarding checklists skip, and it's the part that creates real exposure. An employee photo is personal data, a public team page is a publication, and a US-only mental model will not survive your first European hire. None of what follows is legal advice — run your version past counsel.

Three things to get right:

1. 1Separate internal use from public use. Under GDPR, employers commonly rely on legitimate interests for operational uses like an internal directory, backed by a documented balancing assessment, while clearly discretionary publication — the marketing site, campaigns, social posts — is usually handled with specific, freely-given consent. UK ICO guidance treats consent in the employment relationship as a last resort precisely because of the power imbalance, and the European Data Protection Board has said consent is unlikely to be a valid basis at work. That is exactly why the public-website ask should be separate, documented and genuinely refusable.
2. 2Know what your AI vendor does with the face. Illinois' BIPA excludes photographs from its definition of a biometric identifier, but a scan of face geometry derived from a photograph has been treated as covered — and BIPA carries liquidated damages of $1,000 per negligent and $5,000 per intentional or reckless violation, plus fees, with a private right of action. A 2024 amendment softened the arithmetic by counting repeated collections of the same data from the same person as a single violation, and courts remain split on whether a scan must actually be capable of identifying someone. The practical takeaway is unchanged: read the vendor's retention and deletion terms, keep the request voluntary, and never make participation a condition of employment.
3. 3Write down retention and deletion. State how long you keep original files, who can access the folder, and what happens on exit. "Forever, in a drive folder nobody owns" is the default state at most companies and it is not a policy.

Then build the mirror-image offboarding step. Removing a former employee's photo from the public team page, the intranet, proposal templates and the shared drive should be a checklist item with the same weight as revoking SSO access. Directory hygiene is bidirectional — the team page that still shows three people who left last year damages credibility just as much as the one missing your newest hires.

What this costs at three company sizes

Budget conversations get easier when you compare total annual cost of coverage, not price per photo. The relevant number is what it costs to have a compliant, current photo for every active employee, including the hires who arrive in the awkward gaps between shoots.

• 15-person startup, 8 hires a year, fully distributed: a batch day makes no geographic sense — you'd fly people in to stand against a grey wall. Self-serve AI as the default, with a small per-hire reimbursement for the two or three client-facing roles that want a real photographer. Annual cost: low hundreds, plus a couple of hours of coordination.
• 80-person scaleup, one hub office, 30 hires a year: two photographer days a year covers the hub. At published full-day rates that's roughly $6,000–$12,000 before extra retouching and setup fees, and it still leaves anyone hired in the intervening months without a photo — so self-serve becomes the interim standard, not an afterthought.
• 400-person company, multiple offices, continuous hiring: per-hire photographer bookings across dozens of cities are an administrative tax with no upside. Standardize on a written spec plus a self-serve default, book photographers only for leadership, brand and recruiting assets, and enforce it through HRIS tasks rather than reminders.

One cost most plans miss: coordination time. Chasing photos is somebody's unbudgeted afternoon, every month, forever. Any model that removes the chase is worth more than its sticker price suggests.

Making it stick: one owner, one trigger, one quarterly audit

Programs don't fail from bad intentions, they fail from missing ownership. Three mechanisms keep an onboarding photo step alive past the first enthusiastic quarter: someone accountable, an automatic trigger, and a scheduled audit that surfaces gaps before a customer does.

1. 1Name an owner. One person in People Ops owns coverage. Not "HR," not "marketing" — a name.
2. 2Automate the trigger. Most HRIS platforms can fire a task or an email on start date. The request should go out because someone's start date arrived, not because a human remembered.
3. 3Report one metric. Percentage of active employees with a spec-compliant photo in the canonical location. Show it monthly. It will be lower than anyone guesses the first time you measure it.
4. 4Run a quarterly sweep. Compare the HRIS roster against the team page and the chat directory. Fix additions and removals in one sitting.
5. 5Set a refresh cadence. Every two to three years, or after a significant appearance change. The capture date you stored in the HRIS makes this a filter, not a memory exercise.
6. 6Keep one escape hatch. A hire who missed the window, hated their photo, or joined the day after batch day needs a route that doesn't require waiting a quarter.

The individual benefit is worth mentioning in your internal comms, because it drives voluntary participation better than any policy: LinkedIn's own guidance to sellers says a profile photo can bring up to 21 times more profile views and 9 times more connection requests. Most new hires want a decent photo. They just don't want to organize one — so organize it for them, in week one, and let the calendar do the rest.

You can start with a spec document, an HRIS task, and one AI headshot generator link in your pre-boarding email. That combination gets you to full coverage faster than any shoot day, and it's the version that's still running in eighteen months.