A presentation board communicates the intended story and look. A shooting board adds enough coverage and camera information for a crew to discuss how to film it. Neither should hide important constraints. A polished panel is not automatically a feasible setup, and six panels do not necessarily mean six camera positions.
Separate story order from setup order
Keep the audience's sequence on the board. In a separate crew document, group compatible shots by camera position, lighting and access. A setup can supply several shots, and a moving-camera shot can require more preparation than a fixed one. The example below proposes two fixed positions; it is not a completed schedule or a safety assessment.
A complete six-cell coverage map
A woman moves a yellow cube to the right on a table. The four-panel image compresses this original six-cell plan.
| Code | Story-order image | Proposed setup |
|---|---|---|
| S1 | Wide: woman, table and cube | A, front three-quarter view |
| S2 | Medium: right hand approaches cube | A, tighter framing |
| S3 | Detail: fingers contact cube | B, table-height detail |
| S4 | Detail: cube moves right | B, same side and height |
| S5 | Medium: hand releases cube | A, tighter framing |
| S6 | Wide: new cube position | A, original framing |
Add what a crew needs to resolve
Put S1–S6 in Creator headings. Use captions for setup letter, action boundaries, intended movement and unresolved lens or access questions. A shot-size field is not a lens calculator. Record the cube's start and end marks, the actor's right hand and any reset required between takes. Do not imply that a rough diagram proves lighting, focus or camera clearance.
Preserve the pitch and make a working copy
Save the presentation JSON under a revision filename before making the coverage pass. Importing Creator's own JSON can restore an editable board, but this source inspection does not establish native project branching or automatic history. Save separate files for separate revisions. If the coverage pass changes the story or budget assumptions, bring that change back to the presentation discussion explicitly.
Prepare a manual production handoff
Create a separate shot-list document with the same codes. Group S1, S2, S5 and S6 under A; group S3 and S4 under B, subject to the crew's practical assessment. Keep a story-order reference alongside that grouping. Creator PNG/PDF output is a visual board reference, not a synchronized CSV schedule or an editable production database. Missing reverse angles, sound coverage and extra takes should be written as open decisions.
Reproduce the consistency check
Compare the six codes in JSON, the exported visual board and the crew document. Change S4's endpoint and confirm each reference is manually updated. Ask whether S6 still shows the intended result. This proposed exercise claims no filmed coverage or measured savings. Free visual exports are watermarked; retain JSON backups outside browser storage and rehearse actual camera access before relying on the plan.
Sources and verification
Adobe's shot-list guide provides first-party guidance on camera setups and useful shot information. The setup mapping here is an original editorial exercise. The dated product-source record documents actual inspected fields and export limits, without claiming an independent production review.

