A Photo Release Card for Staff Pictures You Want to Reuse on Your Website

Team photos get taken once and reused for years: the About page, a proposal, a social post. The risk is not the first use but the quiet drift into places the person never discussed. This article proposes a simple internal card that records what was agreed for each photo. It is a process suggestion for your own record keeping, not advice about what any law requires; if you need that, ask a qualified adviser.

The inputs you need

For each photo, write down:

The file name and the date it was taken.
The person pictured, and who else appears.
The uses discussed, listed one by one rather than as "marketing".
The person's answer for each use: yes, no, or ask me again.
A review date, so the answer is not treated as permanent.
Who recorded the answer and how it was given.

The branching decisions

When a new use comes up, check the card.

Use is listed with a yes: proceed, and note the date it was used.

Use is listed with a no: do not use it. Offer a different photo or no photo.

Use is not listed: treat it as not agreed. Ask the person, and add a line to the card with the answer.

Use is listed with "ask me again": ask before each use, and record the new answer.

Review date has passed: ask again, even for listed uses, and update the date.

The person has left the team: pause new uses. Decide with them, not for them, whether existing pages keep the photo, and record the outcome.

A group photo: record each person separately. One person saying no means the group image is not used in that place, or it is cropped only if everyone agrees.

A hypothetical worked example

Imagine a small accounting practice with a photo of three colleagues. On the card, the first colleague agreed to the About page and the printed brochure, but not social posts. The second agreed to all three. The third said ask me again. The practice wants to use the photo in a newsletter. That use is not listed for anyone, so it counts as not agreed. The office manager asks each person. The first says yes, the second says yes, and the third says yes for this issue only. The card is updated with the newsletter line and a note that the third answer applies once. Later, a social post is proposed. The first person's no blocks the group photo, so the practice uses the second colleague's individual portrait instead.

Stop conditions

Stop and do not publish if the card is missing, if anyone's answer is unclear, if the only record is someone's memory, or if the request came through a manager in a way that makes refusing feel hard. A yes should be easy to withdraw, and the card should say how to do that.

Small acceptance checks

Before a photo goes live, confirm:

Every person visible has a card line for this exact use.
No answer is older than its review date.
The record shows how the answer was given.
A named person can remove the photo from the page quickly if asked.
The card itself is stored where only the people who need it can read it.

Keep the card short enough that people actually fill it in. If it takes more than a minute per photo, remove fields rather than skipping the card.