Guides

Part of Image consent guide: purpose, people, capture, editing, publication, reuse, withdrawal, retention, and records

How to plan and document consent for a photo or video project

Plan and document image consent with a practical workflow for project scope, participant choices, releases, shoot-day checks, approvals, withdrawal, and records.

What to take away

  • Draft the use plan before drafting a release.
  • Give participants separate choices for capture, publication, promotion, reuse, and sensitive edits.
  • Use plain spoken explanations as well as a record that can be retrieved later.
  • Reconfirm on shoot day when the setting, people, wardrobe, script, or intended use changes.
  • Connect each response to the correct person and files without exposing identity records unnecessarily.
  • Route every later use through a scope check.

A useful consent process lets a participant decide and lets the project team prove what was decided. The process begins before the shoot, continues when the camera is operating, and follows each selected file through approval, publication, reuse, and retirement.

This workflow applies to planned projects involving identifiable people. It is not a substitute for legal review, location permission, safeguarding, union rules, employment requirements, or a valid copyright license.

Hands hold a smartphone displaying a camera interface in bright outdoor light.
Photo: Shixart1985, March 1, 2026, CC BY 2.0, via Wikimedia Commons. The photograph shows hands, a phone, and a visible camera interface. It does not show whether an image was captured, who controls the device, what is in its frame, or whether any person agreed to recording or use. This credited media will be removed at the author's request.

Step 1: Write the use plan

Create a one-page scope before approaching participants. Name the commissioning party, creators, subjects, project purpose, recording types, locations, dates, intended story, channels, audiences, territory, publication window, paid promotion, partners, editing, archival plan, and contact.

Mark unknowns. If the client has not decided whether footage may become an advertisement, do not bury that possibility in generic "all media" language. Resolve it or make advertising a separate optional choice.

Classify risks. Children, medical information, intimate settings, political activity, immigration status, homes, workplaces, religious practice, trauma, and unequal power can require specialized review or a decision not to record.

Step 2: Design real choices

Separate participation in the activity from appearance in content. Then divide image use into meaningful options, such as:

Decision Example choice
Capture stills, video, audio, or none
Identification named, first name only, pseudonym, or unnamed
Publication project site, organic social, print, press, or internal only
Promotion unpaid post, boosted post, paid ad, or no promotion
Editing routine correction, retouching, composite, synthetic change
Reuse one campaign, portfolio, related annual campaign, or new permission

Do not offer an option the production system cannot honor. If every clip includes audio, the form should not promise video without audio unless the team can mute and verify it.

Step 3: Prepare layered information

Start with a short spoken explanation and a one-page summary. Offer the full terms and privacy information in an accessible format. Identify who makes use decisions, not only the camera operator. State how to ask a question, decline, or withdraw.

Use concrete words: "two paid Instagram ads through June 30" is clearer than "digital promotion." Explain material editing and foreseeable distribution. Translate or interpret where needed. Give people enough time to ask questions without a camera waiting inches from their face.

The University of Oregon's institutional practice calls for releases in deliberate shoots and advises teams to discuss intended use and platforms before photographing. Its model release guidance for planned photography is useful as an operational example, but its university form and rules do not determine legal requirements for another organization or jurisdiction.

Step 4: Capture an attributable response

Use a signed form, secure electronic choice, recorded oral statement, or another method appropriate to the governing rules. Record the version of the notice and the exact options selected. For oral agreement, retain the script and an authorized record of the response.

Assign a participant code. Link it to shoot and file identifiers while storing contact details and identity evidence in a more restricted location. Never label a whole memory card "cleared" when different people selected different terms.

For a representative or guardian, record their identity, relationship, and basis of authority. Do not assume that the adult standing beside a participant can authorize every use.

Step 5: Reconfirm at the shoot

Before capture, restate the project and point out changes. Show where someone can wait outside the frame. Give a clear stop signal. The person obtaining consent should know how to halt recording without arguing about schedule or sunk cost.

Reconfirm when:

  • a new creator, client, or partner joins;
  • the location or degree of privacy changes;
  • wardrobe, script, pose, or topic becomes more sensitive;
  • audio, livestreaming, or behind-the-scenes capture is added;
  • a commercial endorsement replaces editorial or community use;
  • the team proposes a composite or synthetic edit.

Record a decline with as little personal detail as possible. The operational need is to prevent capture or publication, not to build a list explaining why people said no.

Step 6: Control files after capture

Ingest files into a controlled folder. Apply participant codes, scope labels, review status, expiration, and restrictions. Quarantine frames containing people without a matched record. Keep unselected raw files away from teams that only need approved masters.

Before editing, compare the planned treatment with the response. Before publication, verify person, file, channel, audience, dates, caption, tags, sponsor, crop, and accessibility text. A reviewer should be able to trace every "yes" back to the words and choices behind it.

Step 7: Handle changes and withdrawal

Give requests one monitored route. Log receipt, authenticate proportionately, identify affected files and uses, pause scheduled publication, and notify the people who control downstream placements. Respond in the time and form required by applicable law or contract.

If the project seeks a new use, describe the difference and request a new choice. Never rewrite the old record. Preserve both versions and the date on which the later one became active.

At project close, remove unnecessary raw files, retain records for a defined reason and period, revoke access, and document what remains in print, archives, backups, or third-party systems.

Common questions

Should consent always be written?

Writing is often easier to prove, but the required method depends on the right, law, context, and risk. Some rules require a writing or an explicit statement. Record any permitted oral process carefully.

Who should obtain the response?

A trained person who can explain the project, answer questions, recognize pressure or uncertainty, and stop the shoot. The photographer should not have to manage every record alone.

What if someone changes one choice on shoot day?

Update the record before capture or use. Identify the changed field, time, person confirming it, and files affected. Preserve the earlier version.

Can one release cover photos and video?

It can address both if the language and choices are clear and legally effective, but a combined form should still separate recording, audio, editing, publication, and reuse decisions.

More in Guides

Guides

Image consent guide: purpose, people, capture, editing, publication, reuse, withdrawal, retention, and records

Image consent guide covering purpose, participants, capture, edits, publication, reuse, withdrawal, retention, and records for responsible projects.

Rules

Vague permission, bundled terms, changed context, silent withdrawal, missing records, and indefinite reuse

Image consent problems explained, from vague permission and bundled terms to changed context, missed withdrawal, weak records, and unjustified indefinite reuse.

Reviews

Consent, permission, notice, release, license, contract, and legitimate legal basis compared

Consent, permission, notice, releases, licenses, contracts, and legal bases compared so creators can identify what each instrument does and leaves unresolved.

Maintenance

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

Image consent checklist for people, authority, purpose, capture boundaries, channels, edits, reuse, withdrawal, retention, contacts, and review records.