People, purpose, boundaries, channels, edits, reuse, withdrawal, retention, and contact checklist

What to take away

• Use the checklist to expose missing decisions, not to declare automatic compliance.
• Verify the person, their authority, the project owner, and every outside recipient.
• Describe capture, editing, publication, paid promotion, licensing, and reuse separately.
• Make refusal and withdrawal routes visible before recording.
• Attach choices to specific files and preserve the wording and date.
• Recheck the record whenever purpose, audience, platform, partner, or edit changes.

A checkbox cannot make a pressured or uninformed decision valid. This review is a project-control tool for planned photography and video. Adapt it to the governing law, contract, platform, employment relationship, safeguarding rules, and actual risks.

Use one row per participant when choices differ. Use a separate project sheet for facts shared across the shoot. Mark an item "not applicable" only with a short reason.

Project and people

• Unique project, shoot, and campaign identifiers exist.
• The commissioning organization is named.
• Every creator, production company, client, publisher, and independent recipient is identified.
• The person depicted or recorded is correctly matched to a participant code.
• An adult participant can decide for themself, or a verified representative's authority is recorded.
• A child's willingness, guardian authority, and safeguarding review are handled separately.
• Interpreters, accessibility support, and a private question route are available when needed.
• Declining will not produce an undisclosed penalty or loss unrelated to the image project.

Purpose and legal review

• The purpose is concrete enough to distinguish this use from a later campaign.
• The team has identified relevant copyright, likeness, privacy, data-protection, contract, confidentiality, location, labor, and safeguarding questions.
• Each required legal basis, permission, release, or license is assigned to an owner.
• High-risk uses have received qualified local advice.
• The team can explain what will happen without relying on jargon such as "content purposes."

Under UK data-protection guidance, an organization relying on consent should keep evidence of who consented, when, how, what they were told, and whether they withdrew. The ICO's consent recording and management guidance also calls for named controllers, purposes, activities, active opt-in, and review as processing changes. Apply that description only where the UK regime and consent basis are relevant, and recheck the live guidance for amendments.

Capture boundaries

• Stills, video, audio, livestreaming, screen recording, and behind-the-scenes capture are separate fields.
• Locations, dates, approximate duration, activities, and expected crew are stated.
• Sensitive topics, spaces, clothing, medical details, documents, screens, addresses, and identifiers are flagged.
• The participant can stop a take and can wait outside the recording area.
• Bystanders and people who decline have a practical no-recording path.
• Raw files containing out-of-scope material will be isolated or deleted under a written rule.

Channels and audience

• Website, organic social, paid social, display advertising, print, press, broadcast, email, events, portfolio, and internal use are separately named where relevant.
• Public, members-only, customer, employee, classroom, press, or partner audiences are described.
• Territory and language versions are identified.
• Publication start, campaign end, archive status, and takedown expectations are stated.
• Downloading, embedding, syndication, resale, licensing, and partner reposting are addressed.
• Platform terms have been reviewed by date rather than recalled from memory.

Editing and presentation

• Routine crop, exposure, color, sound cleanup, captioning, and subtitles are described.
• Beauty retouching, body alteration, background replacement, composites, dubbing, synthetic voice, face swaps, and generated scenes require distinct review.
• Names, captions, tags, handles, quotations, affiliations, and endorsement language are approved where necessary.
• Accessibility text is factual and does not reveal private traits or invent context.
• The approval process identifies who may accept edits and what happens after a rejection.

Rights and asset records

• The photographer or other copyright owner is identified.
• A license states work, rights, media, purpose, territory, term, exclusivity, sublicensing, editing, and credit.
• The participant release describes only rights the signer can authorize.
• Property, artwork, music, wardrobe, trademark, and performance permissions are checked where needed.
• Each final asset carries rights metadata that points to the controlling records.

The University of Arizona describes an institutional workflow in which release status is tied to asset records and images are categorized by permitted use. Its rights and releases guidance is a helpful example of connecting documentation with photographs, but its categories and university practices do not establish permission for another publisher.

Reuse and change control

• Current use is compared with the original purpose, audience, channel, partner, term, and edit.
• A changed sponsor or commercial endorsement triggers review.
• A new dataset, model-training use, synthetic transformation, product, or merchandise use triggers review.
• Fresh permission is obtained when the new use falls outside recorded authority.
• Old terms are preserved; updated terms have a new version and activation date.

Withdrawal, contact, and retention

• One monitored contact accepts questions, objections, and withdrawal requests.
• The notice explains the request process in plain language.
• Staff can pause scheduled posts and locate published copies promptly.
• The response plan distinguishes consent withdrawal, contract termination, privacy rights, and courtesy removal.
• Raw, rejected, selected, published, release, identity, and backup records have separate retention rules.
• Access is limited, exports are logged where proportionate, and team access ends at offboarding.
• Any limits on print recall, archives, backups, search caches, or third-party copies are explained accurately.

Final release gate

• The selected file matches the participant and record.
• The exact channel, account, audience, caption, crop, date, sponsor, and paid status fit the scope.
• No withdrawn, expired, refused, or unresolved item appears.
• A second reviewer signs off on high-risk publication.
• The public contact and response owner are active.

Common questions

Does completing every box prove that a use is lawful?

No. The checklist improves review and evidence. It cannot resolve unknown law, bad authority, coercion, unfair terms, or facts recorded incorrectly.

Should the release be stored with the image?

Store a secure reference or status with the asset. Keep identity and contact documents behind stricter access rather than embedding them in widely shared files.

What should happen when a field is unknown?

Pause the affected capture or use, assign an owner, and resolve it. Do not convert uncertainty into a broad assumption.

How often should the record be reviewed?

At selection, before editing, before publication, before reuse, after a participant request, and whenever a purpose, party, platform, or legal rule changes.