Remote headshots for distributed teams: the playbook

Why consistency is the whole game

An individual headshot is easy. A hundred of them that belong together is the hard part, and it is the only part that matters for a team. The value of a company directory, a leadership page, or a set of email signatures comes from the grid reading as one deliberate thing — same crop, same light, same distance from the wall. The moment one portrait is warmer than the rest, or one head is framed tighter, the eye catches it and the whole page looks improvised.

Variance is also invisible until it is too late. Each employee, left to their own phone, produces something that looks fine on its own. The mismatch only appears when the frames are assembled side by side — by which point re-shooting a scattered workforce is exactly the problem you were trying to avoid. So the job is not to collect a hundred good photos. It is to shoot one photo a hundred times.

That reframing is what makes a remote program tractable. You are not asking employees to be photogenic or to know anything about cameras. You are defining a single standard and then applying it with the same hand to every session. On CLOS, that hand is one operator directing each phone remotely, which is why a distributed remote corporate headshots program can hold a consistent look that a hundred self-timers never could. The rest of this playbook is how to build and run that standard.

Set the standard once

Before you book a single session, write the spec. It has three parts, and every one of them is something the operator can hold constant across every employee.

Background. Pick one type of wall and describe it plainly: a single flat, matte surface in a neutral tone, free of art, shelves, doorways, and busy texture. Ask people to stand a little away from the wall rather than pressed against it — a gap keeps a hard shadow from stacking up behind the head. If your team can’t all find the same wall, choose a family that reads consistently (a light neutral, say) rather than letting some go dark and some go bright.

Framing. Decide the crop and the eye-line once. A head-and-shoulders portrait with a little headroom is the safe default; write down where the top of the frame sits and where the crop lands on the chest so the operator repeats it exactly. Fix the orientation to match where the photos will run, and set the lens at the subject’s eye level — a phone propped low points up the nose and instantly breaks the set. The operator controls focus and framing live, so this is a standard they enforce, not a hope you place on the employee.

Light. Daylight from a window is the cheapest good key light there is. Put the window in front of the person, slightly to one side, never behind them — backlight turns a face into a silhouette. Kill overhead office lights that drop raccoon shadows under the eyes, and keep one dominant color temperature so a warm bulb and cool daylight don’t fight. Where you need even light across every session regardless of the room, Pro plans let the operator hold white balance, ISO, and shutter speed steady from person to person.

Then do the one thing most programs skip: shoot a reference frame. Photograph a single willing colleague to the exact spec and treat that image as the gold master. Every later session gets matched to it, not to a written description someone interprets differently. Piloting the look on the Free plan first is a low-cost way to lock the master before you scale — see pricing for when RAW and the manual controls justify Pro.

Batching sessions across time zones

One operator can only run one camera at a time, so treating the program as one long open calendar wastes their day and scatters the results — and a distributed team rarely shares working hours anyway. Batch instead.

Group employees by region and give each region a block that lands inside its own business hours — nobody should take a headshot at 6 a.m. their time. Within a block, run short back-to-back slots. Fifteen minutes per person is a comfortable default: enough to seat the phone, run a framing check against the gold master, direct a handful of frames, and confirm a keeper before the next person joins. Put a small buffer between slots so one slow setup doesn’t cascade into the whole block running late.

Let people self-book into the slots rather than assigning times; a booking link per region fills the block without a scheduling thread and lets employees pick a window when their room has good daylight. Keep a couple of catch-up slots at the end of each block for the inevitable no-shows and connection hiccups, so a missed session is a five-minute reschedule instead of a second event weeks later. Because the operator moves from one phone to the next with no room to reset and no travel, a department fits into a single block, and a whole company is a handful of blocks across a week. The event-team variant of this — capturing a roster against a hard marketing deadline — is covered in headshots for events and speakers.

What HR should send employees

The single biggest cause of a slot running long is an employee who reads the instructions for the first time when the session starts. Head that off by sending one short, literal checklist with the calendar invite. Copy this, adjust the slot length to match your block, and paste it into the invite:

Before your 15-minute headshot slot, please have ready:

• A spot by a window with daylight — face the window, don’t sit with your back to it.
• A plain wall behind you: no art, shelves, or open doorways. Stand a step away from it.
• Your phone on a stand (or propped on a stack of books) at eye level, rear camera facing you.
• The CLOS app installed and the join link from this invite open and ready.
• Turn off overhead lights, silence notifications, and wear what you’d wear to meet a client.

That’s it — you don’t need to know anything about the camera. The photographer controls focus, framing, and the shutter for you. Just show up and follow direction.

Keep it to that. A longer note gets skimmed; a five-line list gets read. The point of the checklist is that the room and the light — the two things the operator can’t fix remotely — are already right when the session opens, so the whole slot goes to directing rather than troubleshooting.

Onboarding: headshots as a repeatable step

Headshot programs decay the moment they are treated as a one-time project. You run a company-wide push, the grid looks great for a quarter, and then every new hire arrives without one — so within a year the directory is half-matched again. The fix is to stop running a project and start running a step.

Wire the headshot into onboarding the same way you wire in a laptop or a payroll form. When a new hire is scheduled, a booking link goes out with the first-week materials; the session is a standing 15-minute slot the operator runs on a recurring cadence, not a special event. Because the gold master and the written spec already exist, the new person is shot to the identical recipe as everyone hired before them, and their portrait drops into the directory matching the set from day one — no re-shoot, no placeholder avatar lingering for a quarter. Assign one clear owner for that recurring slot (usually People Ops) so it never falls between roles; the forthcoming CLOS for HR and People Ops guidance goes deeper on owning it. Handled this way, consistency stops being something you re-establish every year and becomes something the onboarding flow maintains on its own.

Delivery and rollout

Everything captured lands in one shared CLOS Cloud album in real time, and that single destination is what keeps a distributed rollout from turning into an inbox of attachments. As each session runs, the frames appear in the album, so whoever owns the program reviews and picks a select while the person is still on the call — a weak frame gets re-shot on the spot instead of discovered a week later.

From the one album you pick one keeper per employee and push it where it needs to go: the HR system and internal directory, team and leadership pages, email signatures, and the profile photos people carry to LinkedIn and slide decks. Because the whole company flows into the same place regardless of which time-zone block captured them, you approve the entire set from a single view rather than reconciling files from a dozen sessions. Download a single portrait, a curated selection, or the whole set as a ZIP for whatever pipeline consumes it next, and on Pro the album doesn’t expire — so when a brand refresh calls for a new template, the last set is still on hand and you simply re-shoot everyone to the new gold master on the same platform. One standard, one operator, one album: that is the entire playbook, and it is why a remote program scales to a workforce a studio day never could.