A Video Privacy SOP for Small Organizations

A small organization needs a video process people can actually follow. Give each recording a purpose, keep sources separate from public exports, and make one person responsible for approving the exact file that gets posted.

The same employee may hold several roles. What matters is that the decisions do not disappear between filming, editing, and publication.

Step one: record the purpose at capture

The capture owner notes the event or activity, intended audience, relevant visibility decisions, and where the source is stored.

Use the organization's existing consent and recording rules. Keep sensitive participant information in the appropriate internal system rather than exposing it in a public filename.

If the purpose is unclear, resolve it before collecting more footage.

Step two: give the editor specific instructions

Identify which people may remain visible and which appearances need treatment or removal. Include text, screens, names, and audio where relevant.

The editor makes the cut, applies face treatment in an approved tool such as Unseen, and uses other editing tools for details outside its face features.

Record the working source and export version. Keep the original intact under the organization's retention rules.

Step three: review a real output

The reviewer opens the downloaded file, watches the full clip, and checks the hard moments: entrances, cuts, profiles, crossings, and reflections.

They also inspect the cover, caption, and other publishing assets. A review of the main video does not automatically cover a later teaser.

Issues should have timestamps and clear descriptions. “00:19, name badge readable” is actionable; “privacy concern” is not.

Step four: hand over one approved version

Use a short note with these fields:

• File and version: the exact export.
• Destination: where it may be used.
• Visibility: who remains recognizable.
• Edits: face treatment and other material changes.
• Review: who checked it and when.
• Restrictions: anything a later editor needs to know.

Store approved exports in the publishing folder. Keep originals and rejected drafts elsewhere.

Step five: handle changes and mistakes

A new crop, soundtrack, cover, or audience can require another check. Do not treat approval as permission for every future derivative.

If the wrong file is posted, use the available platform controls promptly, inform the responsible person, preserve enough information to understand the error, and correct the source of the mix-up. Removal from one platform does not ensure all copies disappear.

Keep the procedure short enough to use regularly. The publication checklist can serve as the final review page, while this SOP defines who owns each decision.