Review and refine the shot list

Use structured shot data for coverage review, continuity, and downstream visual generation.

Use the table for comparison

The shot list exposes episode shots in a structured view. It is useful for checking lens or framing choices, camera logic, repeated coverage, and whether each shot belongs to the correct scene. The panel is better for sequential reading; the canvas is better for spatial arrangement.

Give every shot a job

A shot should change what the audience knows, feels, or anticipates. Record concrete visual information rather than vague mood alone. Keep dialogue and action aligned with the screenplay, and use canonical character identities.

Review a scene in layers:

1. Geography: can the audience understand the space?
2. Dramatic ownership: whose objective shapes each moment?
3. Reveal: what information is withheld or exposed by framing?
4. Continuity: do screen direction, props, light, and performance states connect?
5. Economy: can two redundant shots become one stronger shot?

Work with AI without overcoverage

Ask the assistant to read the scene and existing shots before adding more. State the production constraint and desired visual grammar. If you only need analysis, say “do not edit.” For a rewrite, specify which shots may change and which must remain.

Keep downstream assets traceable

Generated storyboard or scene images should originate from the real shot and entity data where the workflow supports it. Review generation results as references, then return to the shot record for the production decision. Deleting an asset does not automatically rewrite the shot plan.