Define the release decision
The primary workstation fails while the storyboard package is still needed. A drive labeled backup exists, but no one has verified that it holds the current approved deck or can be opened.
Restore and open a separate copy before a review deadline exposes an untested package.
Run the control sequence
- 01Use a fictional deck or an authorized test packet in an isolated restore location.
- 02Retrieve the recovery copy without relying on the primary package device.
- 03Open it using the documented method; do not assume sync history or credential reset restores the approved deck.
- 04Compare folders, file counts, dates and selected checksums with the safe manifest.
- 05Record the result, remediation owner and next drill 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 cloud badge or backup label is not evidence that the correct storyboard copies are complete, readable, current or recoverable.
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.