A shot code lets two people refer to the same planned camera setup even when its position on the page changes. A panel’s displayed order is not a reliable identity after reordering. Agree on a convention before distributing the first board.
Define a house convention
For this exercise, 12-A means scene 12, shot A. R1 means the first review revision, and a take number is recorded during shooting rather than used to identify a storyboard drawing. Productions use different conventions; this example is not an industry mandate.
A storyboard may have several panels for one moving shot. Give those panels suffixes such as 12-A.1 and 12-A.2, and explain that they depict one shot. Otherwise a reader may schedule them as two setups.
Six cells and a controlled insertion
To insert a detail between B and C without exceeding the free six cells, omit E and add 12-B1 for the ribbon detail. The R2 order becomes A, B, B1, C, D, F. The missing E is intentional and belongs in the change log. Never reuse E silently for unrelated action.
| Initial code | Planned content | After revision R2 |
|---|---|---|
| 12-A | Courier enters workshop | Retain code |
| 12-B | Blue parcel on workbench | Retain code |
| 12-C | Courier notices ribbon | Retain code |
| 12-D | Ribbon tied around parcel | Retain code |
| 12-E | Courier checks the knot | Remove, record as omitted |
| 12-F | Parcel ready for handoff | Retain code |
Apply codes manually in Creator
Put the code in each cell heading and action in its caption. Keep headings enabled for the visual export. The internal cell id is application data, not a crew-facing scene/shot code. Creator does not enforce uniqueness, reserve omitted codes or reconcile a published shot list for you.
Save a JSON backup before changing order. Move F earlier temporarily and confirm that its heading remains 12-F. Restore the intended narrative order. If you manually overwrite a heading, the application cannot know whether that was a rename or an error.
Separate revision from identity
Use a board title such as “Workshop — R2 — 2026-10-29” and a small external change log: B1 added, E omitted, F unchanged. Save the approved visual file and editable JSON with that revision. Avoid filenames like “final-final”; include the revision and date instead.
If a setup changes fundamentally, discuss whether it needs a new code. A tighter drawing of the same planned shot may be a revision, while a separate camera position may deserve a new shot identity. The production team makes that decision, not the lettering scheme.
Reconciliation before distribution
Check that all six visible headings are unique, that B1 appears in both the board and the handoff list, and that everyone has the same R2 file. Do not renumber automatically to close the gap at E. If renumbering is unavoidable, distribute an old-to-new mapping and retire the earlier version explicitly.
Reopen the JSON and compare headings and captions with the visual file. This local exercise verifies a small editing path; it does not establish camera metadata, VFX tracking integration or a production-wide version-control system.
Sources and verification
First-party product verification record. Open Storyboard Creator. Primary craft reference.
These sources support terminology and the inspected implementation. They do not endorse CineoBoard. The examples and suggested review process are original fictional exercises, not measured production outcomes.

