Steps, each attributed. (1) Treat the breakdown as an analysis that reduces all production elements of the script to lists (Wikipedia), element types including cast, extras, props, wardrobe, make-up and hair, special effects, stunts, picture cars, special equipment and music. (2) Create one breakdo…

Steps, each attributed. (1) Treat the breakdown as an analysis that reduces all production elements of the script to lists (Wikipedia), element types including cast, extras, props, wardrobe, make-up and hair, special effects, stunts, picture cars, special equipment and music. (2) Create one breakdown sheet per scene: a scene header (built-in fields) followed by the schedule's categories with the elements assigned to that sheet (Movie Magic Scheduling Breakdown page). (3) Use the product's categories: every new schedule includes 25 built-in categories (Cast Members, Sound, Extras, Art Department, Background Actors, Set Dressing, Stunts, Greenery, Vehicles, Special Equipment, Props, Security, Cameras, Additional Labor, Special Effects, Visual Effects, Wardrobe, Mechanical Effects, Makeup/Hair, Miscellaneous, Animals, Notes, Animal Wrangler, Music, Note); new categories can be added; elements can receive an automatic Board ID. (4) If tagging in a writing tool instead, Final Draft Tags Mode (Command/Control + T) marks any script element, supports user-made tag categories and produces a Tags report by tag or by scene. (5) Place the scenes as strips on a board in shooting order; strip colors are set by the user from scene-header values such as Time of Day (MMS Strip Display). (6) Add day breaks and shoot days, then read when each element works from the day-out-of-days report and print breakdown sheets with the Breakdown report. (7) Script-page marking colors (cast red, props purple, and so on) are a separate convention reported by Wikipedia. Rationale: Each feature or definition is stated in the cited pages; the workflow order is the collector's (it follows the manual's own breakdown, board, day-out-of-days, reports order) and is therefore labelled inference. Counterevidence: MMS pages read do not document default strip colors; Wikipedia's color table is attributed to handbooks and informal sources; Celtx and Final Draft help-center pages returned HTTP 403 so those vendors' own category lists were not read. Uncertainty: This method was not executed by the collector; every step is read from the cited sources only. The sequence has not been checked against a working schedule. Sources: - https://en.wikipedia.org/wiki/Script_breakdown - https://mms-docs.ep.com/Breakdown/Breakdown.html - https://mms-docs.ep.com/Breakdown/Categories.html - https://mms-docs.ep.com/Elements/ManagingCategories.html - https://mms-docs.ep.com/Board/StripDisplay.html - https://mms-docs.ep.com/Reports/BreakdownReport.html - https://mms-docs.ep.com/DayOutofDays/DayOutofDays.html - https://www.finaldraft.com/blog/tech-tips-tagging-for-writers Checked: 2026-10-17

{
  "context": "How is a script broken down into elements and a stripboard, from the documentation read?"
}