Scene breakdown template
Use this as a practical starting point. A useful version is one your team can scan quickly during prep, not one with the most fields.
From a named character to a cast requirement
In the public Real Friends sample project, Breakdown turns a named character into a cast entry with ownership, availability, status, and scene context. This is a real product surface; no screenplay prose is reproduced in the guide.
Scene 12 breakdown
Illustrative example for a fictional short film.
What a useful breakdown should track
The point is not to mark up a script for its own sake. The point is to make decisions easier for scheduling, department prep, location planning, and shot design. A strong breakdown keeps creative intent and practical requirements attached to the same scene.
Scene number, page count, time of day, interior or exterior, location, story day, and short scene purpose.
Track on each sceneSpeaking roles, background, doubles, stand-ins, minors, special skills, and any approval or scheduling notes.
Track on each sceneProps, wardrobe, makeup, vehicles, set dressing, practical effects, picture vehicles, animals, food, and hero objects.
Track on each sceneWeather, stunts, weapons, intimacy, minors, water, fire, night work, company moves, and anything that needs extra prep.
Track on each sceneA simple breakdown workflow
Common mistakes to avoid
Treating a breakdown like a shopping list instead of a production risk map.
Add the scene purpose, department owner, and risk note beside every practical requirement.
Marking every object mentioned in dialogue, even when it never appears on screen.
Only track objects the camera, actor, continuity, or department team needs to prepare.
Waiting until scheduling to discover that one scene needs six departments involved.
Flag cross-department scenes during the breakdown pass before shoot days are locked.
Keeping continuity notes separate from the scene breakdown.
Attach continuity state directly to the scene so wardrobe, props, makeup, and script notes agree.
Using vague notes like "special setup" without naming the actual constraint.
Name the constraint in production language: sound, safety, rigging, reset, access, permit, or time.