Rolling out portraits across a company is a queue problem, not a photography one

The interesting parts of company photography are all operational, and none of them appear in the tooling comparisons.

The concurrency spike

Everyone starts within an hour of the same email. That means your load profile is not steady traffic, it is a single spike on rollout morning followed by a long tail of stragglers.

Ask any vendor for p95 under concurrent load rather than an average. p50 is comfortable; p95 is the colleague who emails you about it.

The opt-out is a data model problem

There is always someone who declines. Camera-shy, religious reasons, a period they would rather not document.

A single boolean does not cover it, because consent has a scope: internal directory and public marketing site are different permissions, and getting that wrong in the permissive direction means somebody finds their face in a campaign they never approved.

photo_consent_scope   internal | public_site | marketing
photo_opt_out         boolean, with a placeholder that is not a broken image
photo_taken_at        not uploaded_at, they differ by years

Design the placeholder deliberately. Initials on a colour works. A grey silhouette reads as "person missing", which is exactly the attention someone opting out was avoiding.

The leaver question

Decide before you need to: keep forever, delete on exit, or keep on historical content and remove from current pages. All three are defensible. Not deciding is not, and someone will eventually ask.

Related and often assumed rather than checked: who owns the files. Photographers frequently license rather than transfer, so "we have the photographs" is narrower than "we can use them anywhere".

The security review nobody runs

For tools rather than people, the questions that matter are what is retained, what is derived from the uploads, and who else is in the chain. Deleting a record and removing a person's influence from trained weights are different operations, and the honest answer to the second from most vendors is "we delete the adapter".

That is fine. It should be stated. What to ask about data in team tools is the checklist version, and it is short.

The reading

The team write-up covers the process, the comparison of team-oriented tools covers the options including us, and the corporate conventions cover what the output should look like.

One adjacent case worth knowing: offering this as a benefit rather than mandating it changes the reception entirely, and it ranks well against other things companies buy for staff. Corporate gifts, compared.

The thing that actually decides success

Turnover. Under a tenth a year, an event works. Over it, you need a process, because a session cannot photograph someone who has not joined yet, and the grid decays one arrival at a time.