October 18, 2026

Multi-Location Headshot Rollout: A Plan That Holds

Elise Webb

Multi-Location Headshot Rollout: A Plan That Holds

Elise Webb

A multi-location headshot rollout is one coordinated photo program across every office, run to a single visual standard, with one set of consent rules and one delivery schedule. It works best when one team owns the standard, a production partner brings the studio to each site, and consent is settled before anyone steps in front of a camera. This guide covers how to plan it, what it costs, and where rollouts usually go wrong.

It is written for marketing, HR and operations leads who have to make 40 people in Austin, 25 in Boston and a newly acquired team in Miami look like the same company.

studio2U
Align Headshots Across Every Office
Studio2U brings portable studios to multiple locations, helping organizations maintain consistent executive and team photography across offices.
Explore on-location photography

TL;DR

  • Decide the standard first (background, crop, lighting, retouching limits), then book photographers. Rollouts fail when each office improvises.
  • Bring a portable studio to each site instead of sending people to a rented one. It keeps disruption low and the setup identical.
  • Get written, use-specific consent before the shoot. State rules differ, so have counsel review a nationwide release.
  • Sequence by business priority: leadership and the public website first, then sales and recruiting teams, then everyone else.
  • Plan for the second wave. New hires and remote staff need a repeatable path, or the set drifts within a year.

Table of Contents

Why a rollout is different from a single office shoot

One office shoot is a logistics problem. A rollout across several cities is a consistency problem, and consistency is what viewers notice. Mismatched backgrounds, different crops and uneven skin tones on a team page read as a company that does not talk to itself.

Three things change when you add locations:

  1. Variables multiply. Different rooms, different light, different photographers, different retouching taste.
  2. Legal footing varies. Employees in different states fall under different likeness and publicity rules.
  3. Timing matters. Photos are often needed for a specific event: a funding announcement, an acquisition close, a rebrand or a conference.

That last point is the most common trigger. A company that has just closed a round, merged with another or launched a new site usually needs the whole team photographed in weeks, not quarters.

Start with the trigger and the audience

Before you pick dates, write down why the rollout is happening and who will see the photos. The answer sets priority and scope.

Trigger Who sees the photos first Prioritize
Funding round closed Investors, prospects, candidates Founders, executives, board, then sales and engineering leads
Acquisition or merger Employees of both companies, customers, the market Combined leadership, then every team page at once
Rebrand or new website Customers and press Leadership and customer-facing staff
Expansion into new offices Local recruits and clients The new office, matched to existing sets
Conference or event season Attendees and speakers Speakers and booth staff

If you are merging brands, treat headshots as one part of a larger effort. MIT Sloan Management Review notes that branding decisions in a merger send signals to employees, customers and the investment community, and that in its study of more than 200 M&As, brand strategy got low-to-moderate priority in pre-merger talks in nearly two-thirds of deals. Matching photos make the intended organization visible. They do not resolve cultural questions, so pair the shoot with clear internal communication about what is changing and why.

Set the visual standard before you book anything

Write a one-page standard. It is the single most useful document in the rollout, and it should answer these questions:

  • Background and lighting: one look, named and photographed as a reference frame.
  • Framing: head-and-shoulders or three-quarter, aspect ratios for web, LinkedIn and press.
  • Wardrobe guidance: what to avoid (busy patterns, logos) and what to bring.
  • Retouching limits: what gets cleaned up and what stays. Our post on a headshot retouching policy covers where to draw that line.
  • Executive treatment: whether leaders get a distinct style. See executive headshot styles.
  • Naming and file delivery: how files are labeled, so the web team can find them.

For a deeper checklist, our corporate headshot guidelines and employee headshot policy pages go through what to put in writing.

Have one person sign off on the standard, then hold every site to it. Committees produce a different look in each city.

This is the step teams skip, and the one that causes problems later. Employees knowing about a shoot is not the same as permission for external marketing use.

Employment counsel’s guidance, as summarized by Venable, is that written likeness consent should match the jurisdictions and the intended uses. It should separate internal directory use from advertising or promotion and define how opt-outs work. Venable’s analysis of employee right of publicity also points out that disputes often surface after employment ends or when a worker objects to a particular portrayal.

Woods Rogers makes a similar recommendation: get written consent before using an employee’s name, portrait or picture for external purposes, using a standard form. Rules also differ by state. In California, for instance, employer use of an employee’s photo for marketing generally requires prior consent for each use, with very limited exceptions.

For a multi-state rollout, that means:

  1. One release, reviewed by counsel, that works across every state where you have staff.
  2. Named uses and duration. Website, social, investor materials, recruiting, PR and paid ads are different uses. Say which ones apply.
  3. An opt-out path with a named owner and a takedown timeline.
  4. A rule for departures. What happens to photos when someone leaves.
  5. Access controls. Who can download which files.

Send the release with the scheduling invitation, not on the day. People who feel rushed say no, or sign without reading, and neither helps you.

This is general information, not legal advice. Your employment or corporate counsel should review the release, especially if you have staff in California or other states with stricter likeness rules.

Choose a delivery model: on-site, hub, or self-serve

There are three practical ways to cover several locations.

Model How it works Strength Weakness
On-site portable studio A production team sets up in each office Same setup everywhere, minimal downtime Needs a quiet room and a booked day per site
Hub and spoke Staff travel to a central location Fewer shoot days Travel cost, missed people, uneven turnout
Self-submitted photos Employees send their own images Cheap and fast Wildly inconsistent, hard to retouch to a standard

For teams that care how the result looks, on-site is the strongest option. It is how we work: we bring portable studios and production teams to client offices, events and portfolio companies, so the lighting and backdrop match from one city to the next. Staff step away from their desks for a few minutes instead of losing a half day to travel.

If you have remote people spread across the country, read our guide to hybrid team headshots. Remote staff need a plan too, whether that is meeting the team at an offsite or at the nearest scheduled shoot.

Build the schedule

A rollout is mostly calendar work. A workable sequence looks like this.

Weeks 1 to 2: discovery and standard

Define the trigger, audience and uses. Finalize the visual standard. Start the consent review with counsel. We open every project with a strategic discovery call so the photos are built for the uses you actually have, not just filed away.

Weeks 2 to 3: logistics

Pick a site lead in each office. Their job is small but critical: reserve a room, send the schedule, and make sure people show up. Build a roster per site with time slots. Our guide to how to organize employee headshots has a template-style walk-through for this.

Weeks 3 to 6: shoot days

Run the sites in order of priority, with leadership first. Give each person a short slot and keep a buffer for no-shows. Live viewing on the day lets people approve a frame before leaving, which cuts later reshoot requests.

After the shoot: edit and deliver

Standardize retouching across all sites, then publish together. A five-day turnaround on edited images keeps the momentum, which matters if the photos are tied to an announcement date.

The key rule: do not publish site by site. Update every team page, profile and deck at once so the old and new looks never sit side by side.

Where the photos get used

Set a launch checklist so the images get used as soon as they arrive:

  • Website team and leadership pages
  • LinkedIn profiles for executives and sales staff
  • Investor decks and data room materials
  • Recruiting pages and job postings
  • Press kits and speaker bios (see conference speaker headshots)
  • Email signatures and proposals

If your team also needs individual web presences, examples of personal brand websites show how one strong portrait can anchor a profile page, a booking link and a bio.

What a rollout costs

Pricing depends on team size and how often you shoot. These are the published rates for our on-site shoots:

Package Price Best fit
START UP $2,500 per shoot Small teams and early-stage companies (details)
STANDARD from $2,000 per shoot Mid-size teams (details)
ENTERPRISE from $3,500 per shoot Larger organizations and multiple offices (details)
BRANDING ADD-ON $1,000 per shoot Added brand photography alongside headshots

For a rollout, you typically price per site and per shoot day. A three-city program therefore means three shoots, and the more consistent your schedule, the more predictable the budget. Ask for a written scope that lists sites, people per site and deliverables before you commit.

Our perspective: treat it as a program, not an event

We see the same pattern in funded startups, firms that have just closed an acquisition, and companies with several offices. The first shoot goes well because everyone is paying attention. The second, six months later, looks different because nobody wrote down what the first one was.

Our view is that a rollout is the start of a visual system. The goal is not a folder of files. It is a standard that you can repeat for the next hire, the next office and the next portfolio company, with the same lighting, the same crop and the same retouching rules. That is why we begin with a discovery call and ask how the images will be used, from investor communications to recruiting to PR.

Our perspective: treat it as a program, not an event — overview diagram

We also push back on one common shortcut: letting each office pick its own local photographer. The individual photos may be fine. The set will not match, and the mismatch is what visitors to your site see. One production team, one standard and portable studios that bring the same setup everywhere is the simplest way we know to avoid that.

Finally, be honest with your people. If the rollout is part of a merger, explain what is changing and why. Photos signal intent, but employees judge the company by what leaders say and do.

— Kevin

Plan the second wave from day one

The rollout is not finished when the last office is done. Build in:

  • A new hire path: a shoot day every quarter or half year, or a scheduled visit when a site hits a headcount threshold.
  • A reference frame: keep sample images and the written standard in a shared folder.
  • A refresh cycle: many teams update leadership portraits on a set interval or after major changes in appearance, role or brand.
  • A takedown process: when someone leaves or opts out, who removes what and by when.

Our post on company-wide headshots goes deeper on keeping a whole-company set current.

Common mistakes to avoid

  • No owner. Without one accountable person, standards drift by site.
  • Consent as an afterthought. Gather it before the shoot, in writing, with named uses.
  • Publishing in pieces. Launch all at once so mismatched old photos disappear together.
  • Ignoring remote staff. They end up with selfies next to studio portraits.
  • Treating photos as a substitute for integration. Visual consistency supports a merger or rebrand, but does not replace the harder work of building shared identity.

Book a multi-site shoot with us

If you are planning a rollout, we can scope it with you. We handle on-site production in markets including New York, the San Francisco Bay Area, Boston, Miami-Fort Lauderdale, Austin, Dallas-Fort Worth and Houston, with live photo viewing and a five-day turnaround on edits. See our on-site headshot and branding packages or our full services to start the conversation.

FAQ

How many locations make a rollout worth coordinating centrally?

As soon as you have two offices that will appear on the same website or deck. At that point, differences in background and lighting become visible. A single standard and a single production team keep the set uniform.

Yes, for external use. Agreeing to be photographed is not the same as permitting marketing use, and state rules vary. Use a written release that names the uses and the opt-out process, and have counsel review it before a nationwide rollout.

Should we photograph everyone at once or in phases?

Phase it by priority if the timeline is tight: leadership and public-facing roles first, then the rest. Publish all updated pages together so old and new styles do not appear side by side.

What happens to people who cannot attend their office’s shoot day?

Plan a catch-up slot at the same site or at the nearest scheduled location, using the same setup. Avoid accepting self-taken photos, since they break the visual standard.

Can headshots help after an acquisition?

They can support brand integration by making the new organization visible in one consistent look. They do not replace communication with employees about culture and brand direction.

Sources

Get in Touch

Get inspired by more related articles.