Define the release decision
A storyboard review has closed, but approved masters, working exports, reviewer copies, acknowledgements and restore evidence may have different retention triggers.
Map each storyboard version to client, contract, copyright and production milestones before disposal.
Run the control sequence
- 01Identify the record class and the client, contract, copyright or production policy controlling retention.
- 02Record the event that starts the period, such as approval, release, supersession or project closure.
- 03Separate source masters, working copies, acknowledgements and reviewer communications.
- 04Apply active legal, contractual, rights, dispute and production holds before disposal.
- 05Verify authorized disposition across devices, removable media, email and synchronized folders.
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
Deleting a package item does not guarantee erasure from backups, reviewer systems, SSD blocks or provider retention layers.
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.