Plan with beats

Use episode-level beats to express dramatic change without confusing them with scenes or screenplay paragraphs.

Beats are units of change

A beat records a meaningful shift: a decision, reversal, discovery, escalation, or new obstacle. Beats belong to the current episode and can be arranged or reviewed as a list. They help test progression before the screenplay is fully written.

Do not use beats as duplicate scene records. One scene may contain several beats, and one planned beat may later require more than one scene. Scenes are derived from screenplay headings; beats are planning entities.

Write actionable beats

A strong beat identifies cause and result. “Mara investigates” is vague. “Mara plays the damaged tape to prove the voice is fake; the tape answers with a secret only her father knew” contains an action, intent, and reversal.

Arrange beats so pressure accumulates. If two beats can swap places without changing the story, the causal chain may be weak. Use the outline for higher-level structure and beats for the sequence of dramatic changes inside that structure.

Work with the AI assistant

Ask the assistant to read the current outline and beats before proposing changes. Specify whether it may edit beats or should only advise. For example:

Read episode 2's outline and beats. Identify the three beats with no causal link. Suggest replacements, but do not edit yet.

After approval, request a bounded update. Broad structural rewrites should keep the outline and beats consistent before expanding into screenplay pages.

Check the result against the script

Beats are plans, not proof. Once scenes are written, verify that each promised change is visible in action or dialogue. Delete obsolete beats or revise them rather than leaving a second, contradictory version of the episode.