← craft library

Scene Budget

craft.scene_budget

Runtime divided by scene length is how many scenes you can afford.

Structure frameworksbeginnerprojectstructurebeat
You are doing it wrong if

The beat board carries more beats than the runtime supports, so scenes get written short, entered early and exited late to fit. Nothing is individually wrong and the whole thing feels rushed, which is diagnosed as pacing and treated by cutting frames rather than by cutting scenes.

Why

Scene count is arithmetic, and doing the arithmetic early prevents a specific and expensive failure: a board that cannot fit its runtime.

The calculation is trivial. Runtime in seconds, divided by the average scene length for the format, gives the number of scenes available. A twelve-minute short at fifty seconds a scene is roughly fourteen scenes. Not twenty. Not "however many the story needs".

The reason this matters more than it sounds: a board with too many beats does not announce itself. It produces a film where every scene is slightly too short to land, entered slightly too early because there was no room to establish, and exited slightly too late because the next one needs setting up. Every individual scene reads as almost right, which is the hardest kind of problem to diagnose.

The budget also allocates. Not every scene should be average length — the ones carrying the turn want more, and the connective ones want less. Deciding that distribution consciously is the difference between a film with rhythm and a film with a mean.

When the board exceeds the budget, the correct response is to cut beats, not to shorten scenes. Shortening is how a fourteen-scene film becomes a twenty-scene film in which nothing has room. Cutting beats is how it stays a film.

How

  1. Multiply runtime in minutes by sixty. Divide by the format's average scene length. That number is the budget.
  2. Count the beats on the board. If beats exceed the budget, you are already over, because most beats become at least one scene.
  3. Allocate: mark the three or four scenes that carry the film and give them double length. Subtract that from the budget before counting the rest.
  4. Check the shortest scenes are doing one thing each. A short scene with two jobs is a long scene compressed.
  5. When over budget, cut whole beats and redistribute their work. Resist trimming across the board — it degrades everything equally.
  6. Re-run the arithmetic after the breakdown exists, against actual estimated durations rather than the average.

Notes for AI film

This card is more binding in generated film than anywhere else, because scene count multiplies directly into shot count and shot count multiplies into cost. A board fifty percent over budget is a project fifty percent over budget, and the overrun is invisible until the shots are being generated.

The estimated duration on each scene contract is the input to this check. Treat those numbers as a real budget rather than a field to fill in, and re-total them before approving a breakdown.

In practice
Locke2013

Eighty-five minutes, one location, and a scene count in single figures. The budget was decided first and the film was built to it.

Dunkirk2017

Three timelines at different scene densities, cut together so the audience experiences one pace. The arithmetic is doing structural work.

Whiplash2014

Short scenes, high count, and a deliberate choice — the density is the pressure the film is about.

Related
Surfaces at
structure.act_math_warninghealth.scene_efficiencybeat.midpoint.openagent.story_architect.systemagent.editor.system

content/craft/scene-budget.md · 6 steps · sha 39d48e2c019b