How to control consent before publishing employee photographs
Illustrative scenario
An operating scenario connecting photographs, consent, territories, channels, and expiry before marketing publishes.
This is an operating scenario, not legal advice or a customer case. No tool can remove 100% of legal risk. The goal is to make the information required for responsible review visible.
Marketing prepares an employer-brand campaign using photographs from an internal convention. One image contains seven people. Some authorized internal communication, others allowed social channels, and one former employee requested removal.
The photograph cannot simply be marked “approved.”
Define what permission must prove
Legal should decide the required basis and evidence. The operating record may include identified people, consent reference, permitted purpose, channels, territory, start and expiry dates, restrictions, revocation, reviewer, and latest review date.
Do not expose unnecessary personal information to the whole team. Apply access control and data minimization under the organization's legal policy.
Use precise states
A useful model:
- Identity pending
- Verification pending
- Limited usage
- Approved for this use
- Do not use
“Approved for this use” is more accurate than “approved forever.”
A pre-publication example
Marketing filters assets for a September LinkedIn campaign in Spain:
- Image A: seven people; six compatible permissions and one pending.
- Image B: internal use only.
- Image C: approved for Spanish social channels until December.
- Image D: one person requested removal.
Only C can proceed directly to creative review. A needs identification, B needs replacement, and D remains blocked.
Search gathers candidates. It does not interpret law or replace accountable approval.
Connect derivatives and publication
When a photograph becomes a banner and carousel, preserve their relationship to the original and permission. A changed original status should make derivatives and published uses discoverable.
Record the original, variants, campaigns, publication URLs or channels, and removal date where applicable.
Revocation is difficult to manage when the team knows only a JPG name and not where it was used.
Add a control gate
- Marketing selects the asset.
- Required fields are checked.
- The accountable person reviews identity, purpose, channel, and validity.
- Legal joins cases defined by policy.
- Approval is recorded for that publication.
- Evidence records which version appeared and where.
A missing field should trigger the agreed warning or block, never an assumption of permission.
Measure process, not “eliminated risk”
Track unidentified photographs, publications stopped for missing evidence, review time, detected expiry, and completed removals.
These figures reveal process failures. They do not prove compliance.
An asset library can keep photographs, versions, and rights context together. Policy, legal interpretation, and the publication decision remain with the organization and its advisers.