Define the release decision
The same storyboard deck exists as an email attachment, browser download, shared-drive copy and platform export. A controlled package needs one verified version without avoidable plaintext residue.
Remove duplicate frames, internal comments, production metadata and unrelated references before packaging.
Run the control sequence
- 01Compare source, review round, date, size and checksum before selecting the authoritative copy.
- 02Inspect annotations, embedded notes, hidden layers, filenames, metadata and linked production references.
- 03Remove details unrelated to the approved review task and minimize unreleased script or scheduling information.
- 04Preserve source masters when copyright, contract, client or legal rules require them.
- 05Record authorized cleanup and inspect downloads, export folders and sync locations for residue.
Preserve enough evidence
Record the package identifier, production, review round, export date, version, manifest, responsible custodian, named reviewers, delivery route, recovery result, retention rule and next review date. Do not put credentials, recovery secrets or unnecessary scene details in the decision record.
Keep the manifest, custodian, approved reviewer, key-separation decision, playback result and retention owner together without copying confidential production details into the record.
Keep surrounding controls visible
Cleanup does not prove deletion from cloud systems, email servers, backups, reviewer devices or solid-state storage.
Storyboard distribution can create copies on laptops, removable media, email, review platforms and synchronized folders. Copy protection does not grant copyright, validate licensing, approve a reviewer or prevent every screenshot or downstream recording. Document the approved deck hash, protected location, named recipients, version label, review expiry, backup location and recovery result. Recheck these controls after software updates, platform migrations, permission changes or deck revisions; an earlier successful test does not prove the present package remains controlled or recoverable.
Questions to ask
Should the package credential travel with the storyboard?
No. Send the package and credential through separate approved channels, and verify the named reviewer before release.
Does copy protection establish review rights?
No. It does not establish copyright, licensing, client approval, reviewer authority or permission to retain the deck.
Primary references
References support specific controls and do not imply endorsement.