Corporate Teams: How to Roll Out Professional Headshots Across Your Organisation

Every company website eventually hits the same problem. The team page shows a patchwork of photos. Some from a studio day three years ago. Some taken on someone's phone at the company offsite. Some with the washing up visible in the background because it was a hasty remote hire. A few people have no photo at all.

It reads as disorganised. It undermines the "one team, one brand" message the rest of the site is trying to make. And the usual fix — book a studio day for everyone — is the kind of project that gets proposed, budgeted, and quietly dropped every January.

There's a better way now. This post walks through how to do it at scale.

Why consistency matters more than perfection

A slightly imperfect photo of every single team member beats a polished studio shot of half the team and inconsistent phone photos of the rest. Visitors to your careers page, your About page, or your press kit are forming a quick impression: is this a proper company with its act together, or is it a loose collection of individuals?

The goal is a team page that looks coherent. Same lighting style, same background tone, same crop, same expression energy. That's what "professional" looks like at company scale, not one perfect CEO headshot surrounded by variable others.

The old way and why it doesn't work

The traditional rollout:

1. HR books a photographer for a day at head office

2. Email goes out asking everyone to come in on that day

3. Half the team is remote or on leave and can't make it

4. Another third is in client meetings or can't leave the deal room

5. Photographer turns up, does 40 people out of 120

6. Six months later someone tries to schedule a catch-up day and it gets cancelled

You end up with an expensive half-finished team page. The people who got photographed look great. Everyone else has a placeholder or nothing.

The scalable rollout

The newer approach is to let each person take their own photos from wherever they are, and have a central process turn them into a consistent gallery.

Step 1: Brief the team. A one-page guide with the rules. Natural daylight, plain background, 10 to 15 selfies mixing angles, no sunglasses or hats, company-appropriate clothing. Two minutes of work.

Step 2: Everyone uploads through the same portal. A UK-hosted, GDPR-compliant service where each person submits their own selfies.

Step 3: Each team member gets a professional gallery back within a couple of hours. They pick the one they want and submit it to the central Comms or HR inbox.

Step 4: Comms uploads to the team page. Same style across the whole company because everyone went through the same pipeline.

Total time per person: about 15 minutes, including choosing their favourite from the gallery. Total time for the company: no studio day, no scheduling nightmare, no half-done rollout.

What the brief should cover

A good internal brief for a headshot rollout includes:

• Wardrobe guidance. "Smart-casual, plain solid colours, no bold patterns" covers 90% of companies. More formal for legal/financial, more relaxed for creative.

• Background guidance. Plain wall if possible. Avoid kitchens, beds, and anything busy.

• Light guidance. Near a window with soft daylight. Not under direct sunlight, not under harsh overhead lights.

• Angle guidance. Ten to fifteen selfies. Mix of straight-on, slight left, slight right. Mix of neutral expression and small smile.

• Deadline. Two weeks tends to be realistic. Longer than that and momentum dies.

• What happens next. Which service, what the output will be, where the final photo lands.

One internal page or Notion doc, clearly written. The brief is the part most companies skip, and it's why their rollouts become inconsistent.

Data, privacy, and why it matters at scale

When you're processing photos of 50, 200, or 2,000 employees, data handling matters. A few things to check before picking a service:

• UK or EU data centres. Not US consumer apps with unclear handling.

• ICO registration and UK GDPR compliance. Not optional for a company process.

• Deletion policy. Original selfies should be deleted within 30 days.

• No model training. Your employees' faces should not be feeding anyone else's product.

Profyle meets all four as standard. For a corporate rollout, this is the difference between a smooth process and a difficult conversation with your DPO.

What it costs compared to a studio day

A studio day for a UK team typically costs £3,000 to £8,000 depending on size, travel, and how long the photographer is on site. That's before you count the time cost of getting everyone there.

A per-person model via Profyle runs at £29 to £49 depending on the package. For a 50-person team, that's £1,450 to £2,450 — and you don't lose the day.

More importantly, the coverage is 100%. Every remote worker, every parent on flexible hours, every team member who joined last week — all included.

Keeping it consistent over time

The other reason most team pages drift out of sync is that new hires don't get the same treatment as the original cohort. The fix is to bake the headshot step into onboarding.

"Take 10 selfies, upload here, gallery back by the end of the day, send your chosen photo to HR" — added to the first-week checklist alongside laptop setup and payroll. No more "we'll sort your photo next time we do a studio day".

The maintenance rhythm

Once a company has a consistent team page, a light annual refresh cycle keeps it that way. Roles change, people change, fashion slowly shifts. An annual two-week window where anyone who wants a refreshed photo can submit new selfies is a gentle way to keep the page current without another big coordinated push.

A consistent, up-to-date team page is one of the few website improvements that quietly lifts every other page it sits beside. It's also one of the easiest to let slide. The newer workflow turns it from a project into a process — and for most organisations, that's the difference between doing it and not.

Ready to sort your team page? Contact us about team packages → or see pricing →