Define the release decision
A protected storyboard package will not open and several similarly named exports exist. Repeated guessing can waste time and risk the only usable source.
Identify the exact package, software version, media and authorized recovery path before changing the only copy.
Run the control sequence
- 01Stop repeated attempts and preserve the original media before troubleshooting.
- 02Confirm package identifier, path, size, date and software version against the manifest.
- 03Test on a copy in the documented supported environment, never on the only source.
- 04Distinguish wrong file, incomplete transfer, incompatible version, damaged media and missing credential.
- 05Use the separate recovery path and record each attempt, outcome and next decision.
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
Credential reset or copy protection cannot reconstruct overwritten frames, deleted annotations or an earlier approved storyboard version.
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.