All guides

Brand Work line · stop 09 of 14 · 26 min · members

Storyboards as prompt sets, with continuity built in rather than patched

Writing a board so that each frame is already a prompt, with continuity built in rather than patched.

Free with an account

Sign in to read.

Membership is free: an account opens all 86 script pages. The Lab, Studio Canvas and the paid guides need the $99 pass, paid once. Already signed in on this browser? The page opens by itself.

Create a free account →What the $99 pass opens
01

The idea

Write the board so each frame is already generatable.

Then approval and production stop being two separate translations.

The usual sequence is: draw or describe a board, get it approved, then translate each frame into a prompt. The translation step is where continuity dies, because each frame gets prompted independently and the shared elements drift.

Writing the board directly as a structured prompt set removes the translation. Each frame carries its full prompt, assembled from blocks that are shared across the sequence, so continuity is a property of the document rather than something you maintain by hand.

It also makes the board honest: if a frame cannot be prompted, you find out while boarding rather than in production.

02

The structure

Three blocks: sequence, scene, shot.

Nested constants, so shared elements are written once and cannot vary.

Sequence block — everything true of the whole piece. Treatment, optics, grain, palette, the character description, global exclusions. Written once.

Scene block — everything true of this location or setup. The space, the light, the time of day. Written once per scene.

Shot block — what is specific to this frame. Framing, subject action, camera move.

Each frame's prompt is sequence + scene + shot, assembled rather than typed. Change the sequence block and every frame updates; that single property is what keeps a twenty-shot board coherent.

03

The sheet

Keep it as a table, not as prose.

A board is data, and treating it as data is what allows assembly.

shot | scene | framing  | action        | camera
01   | S1    | wide     | subject still | static
02   | S1    | medium   | turns head    | slow push
03   | S1    | close    | looks down    | static
04   | S2    | wide     | walks in      | static

Only the shot-specific columns are filled in. The scene column points at a scene block; the sequence block applies to everything.

From here, generating the full prompt for any row is mechanical, and generating all of them is a loop. The board and the production queue are the same document.

04

Continuity

Continuity failures are almost always block failures.

When something drifts across shots, look at which block it should have been in.

If the character's jacket changes between shots, the jacket was described in the shot block instead of the sequence block. If the light shifts within a scene, the light was in the shot block instead of the scene block.

The diagnostic is reliable: anything that should be constant across a range and is not was written at the wrong level. Move it up and regenerate.

This is why the nesting matters more than the prompt wording. A well-nested board with mediocre prompts holds together; a flat list of excellent prompts does not.

One exception

Deliberate changes — a costume change, a time jump — need their own scene block rather than a shot-level override. Overrides in the shot block are how continuity errors get introduced accidentally later.

05

Order of production

Generate the anchor shot first, then everything else against it.

Not shot one. The shot that best represents the sequence.

Pick the frame that carries the most of the look — usually a medium shot in the main location — and produce it to a finished standard before anything else.

That frame then becomes the style reference attached to every other generation in the sequence, alongside the block structure. Between the shared text and the shared reference, the set has two independent forces holding it together.

Producing in script order instead means the look evolves as you go, and shot one belongs to a different film from shot twenty.

06

Approval

Show the board, keep the sheet.

The client sees frames; you keep the mechanism.

Present the board as images with brief captions. The block structure is your working document and showing it invites comments on prompts rather than on the work.

What is worth showing is the shot list itself — the table without the prompt columns — because it demonstrates that the sequence has been thought through as a sequence rather than as a collection of nice frames.

When a change comes back, it lands in exactly one block, and everything downstream updates. That is the return on the structure, and it arrives during revisions rather than during the first pass.