Define the release decision
A verified storyboard package must remain available through the review deadline and later client questions without turning one laptop or sync folder into the only recoverable copy.
Create a bounded review package while keeping editable masters, credentials and recovery material separate.
Run the control sequence
- 01Test the current software release with a fictional storyboard deck on a supported Windows system.
- 02Import only manifest-approved files and inspect temporary folders for plaintext exports.
- 03Protect, reopen and compare file counts and selected checksums with the source manifest.
- 04Store a separately controlled recovery copy and keep credentials away from the package media.
- 05Record package identifier, software version, custodian, recovery location and next test date.
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
A protected package does not replace endpoint security, reviewer authorization, a separately stored backup or a tested recovery method.
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.