How to Do a Script Breakdown and Shoot Schedule With Claude or ChatGPT (2026): Scene Index to Strip Board

Key Takeaways

• Storyflow is the best place to keep a script breakdown and shoot schedule that you build with Claude or ChatGPT, because its MCP connector has a dedicated strip board tool (create_strip_board) that lets the assistant write the whole schedule onto a shareable board in one call, and we found no ChatGPT or Claude connector on the pages we read for Movie Magic Scheduling, StudioBinder, Filmustage or Celtx.
• Work in five passes, never one prompt: scene index, element breakdown, page counts in eighths, strip board, day-out-of-days. Each pass is checked against the one before it.
• The scene count is your first test. Ask for a coverage receipt (pages, scenes, speaking parts) before any table is built, and compare the scene count with your script.
• On the strip board, Storyflow sets the strip colours from the INT/EXT and day/night code and adds up each day's pages itself. The assistant only supplies scenes and their grouping, so the arithmetic is not left to a language model.
• Group by location first, then by light. In the illustrative example below, an 18-scene, 14 5/8-page short goes from 7 location moves in script order to 3 moves across 4 shoot days.
• Storyflow has no day-out-of-days report, no conflict detection and no call sheet sending. The assistant can build a day-out-of-days table from the strips, but it is a table you re-run after a reshuffle, not a live report.
• Storyflow plans start at $7.99 a month billed annually ($9.99 monthly). There is no free plan during early access, and anyone a paid member invites to a board joins free.
• Movie Magic Scheduling is the stronger choice for a bonded or union feature. Its standard price is $299.88 a year, per Entertainment Partners' store.

Why a Breakdown Done in a Chat Window Does Not Survive Pre-Production

You paste eighteen pages into Claude or ChatGPT and ask for a script breakdown and a shooting schedule. A minute later you have a table of scenes, a list of props and a three-day plan. It reads well. Then the director rewrites scene 9, the motel is only available on Thursday night, and the schedule you were proud of is four screens up in a conversation that nobody else on the crew can open.

The assistant is good at the reading. What fails is everything around it, in four specific ways.

The model answers once, and a schedule changes daily

Filmustage, which sells AI breakdown software, makes this argument against chatbots in its own article on ChatGPT breakdowns: a chatbot produces an answer, while pre-production runs on connected data, and a revision means re-running the prompt. That criticism is fair when the answer stays in the chat. It stops being true once the assistant writes its work to a board and reads that board back before the next change.

Page counts in eighths are easy to get wrong in prose

A schedule lives on page totals. Ask a model to add 1 3/8, 7/8, 4/8 and 5/8 in its head and you will sometimes get a wrong number stated with complete confidence. The fix is to keep the arithmetic out of the model: Storyflow's strip board tool computes each day's total from the strips it is handed.

Scenes get merged, skipped or invented

Two scenes with the same slugline (INT. DINER - DAY, pages apart) are the classic merge. A long script is the classic skip. A prop that "would obviously be there" is the classic invention. None of these is visible unless you ask the assistant to report what it read before it builds anything.

Nobody else can open your chat

The first AD, the DP, the producer and the client need the schedule. A shared chat link exposes every rejected draft. A pasted copy in an email is a version the assistant can no longer see. The schedule has to live somewhere that both the crew and the assistant can read, and that is the whole reason to put it on a board.

How We Chose the Tools and Weighted the Criteria

This guide judges one job: breaking down a script with Claude or ChatGPT and carrying the result to a schedule the crew works from. That is narrower than "best scheduling software". On the general question, for a studio feature, Movie Magic Scheduling wins and it is not close. Our longer comparison of dedicated suites is in script breakdown and scheduling in one tool. The weights below are for the assistant-led workflow, on a short, an indie feature, a commercial or a branded film.

The six criteria and their weights

Scores are our editorial judgement from the vendor pages linked in this post and from Storyflow's own product. They are not lab measurements.

How the five tools scored

Storyflow scores 3 on reports and that number is honest: it has no day-out-of-days report, no one-line schedule export and no conflict detection. It ranks first only because the heaviest criterion is whether your own assistant can do the writing, and it is the one tool here where that works.

What we did not weigh

We did not weigh budgeting, payroll integration, multi-unit scheduling, episodic boards or union rule checking. Those decide the purchase on a large production and they all favour Movie Magic Scheduling and the production suites. If any of them is on your list, skip to the decision rules.

The Five Passes: What Each One Produces

A breakdown and a schedule are five documents that feed each other. Knowing what each one contains is what lets you check the assistant's work.

The scene index

One row per scene, in script order: the script's own scene number, the slugline as written, INT or EXT, time of day, the speaking cast, the length in eighths and a one-line synopsis. This is the spine. Everything after it cites a scene number from this table. If you are new to the document itself, start with what a script breakdown is.

The element breakdown

One row per scene again, now listing what the scene needs: cast, props, wardrobe, vehicles and animals, special effects and stunts, location, notes. On paper this is done with highlighters, one colour per category, as described in StudioBinder's breakdown guide. The elements live in the action lines, not the dialogue, so the assistant has to read the scene, not just its heading.

Page counts in eighths

A script page is divided into eight parts and every scene is measured in them: 3/8, 1 4/8, 2 5/8. The rule of thumb that a page runs about a minute on screen is what makes eighths useful for both screen time and shooting time. A scene never measures less than 1/8.

The strip board

Each scene becomes a strip. Strips are grouped into shoot days and coloured by a shared code: by convention white for a day interior, yellow for a day exterior, blue for a night interior and green for a night exterior, as StudioBinder's stripboard guide lays out. A filmmaker reads the colours before the text, which is why a run of green strips on one day tells you it is a night shoot at a glance.

The day-out-of-days

A grid with cast down the side and shoot days across the top, showing who works when: start, work, hold, finish. It exists to answer money questions. If the waitress works day 1 and day 4 in your first schedule, the day-out-of-days is what shows you two bookings where a reorder could make it one.

Comparison Table: Script Breakdown and Scheduling Software for a Claude or ChatGPT Workflow

Prices and plan details are from each vendor's own pages, read on October 10, 2026, and linked in the reviews below.

How to Do a Script Breakdown and Shoot Schedule With Claude or ChatGPT, Step by Step

Nine steps. The first is setup and happens once. Steps 2 to 8 are the five passes plus two checks. Step 9 is what keeps the schedule alive after the first reshuffle.

Step 1: Connect the assistant to a Storyflow board

Create a project in Storyflow for the film and open its board. Then add the connector to your assistant, using the address https://mcp.storyflow.so/mcp.

• In Claude: Customize, then Connectors, then Add, then Add custom connector. Name it Storyflow, paste the address, continue, and sign in to Storyflow. Claude's Free plan allows one custom connector, per Anthropic's connector guide.
• In ChatGPT: you need ChatGPT Plus or above with Developer mode. Turn Developer mode on in Settings under Security and login, open chatgpt.com/plugins, press the plus button, name it Storyflow, paste the address and sign in.

At sign-in you choose which projects the assistant may open and whether it may make changes. Pick this film's project and allow changes, or it can read the board but not build on it. The full walkthroughs are in connect Claude to your project board, connect ChatGPT to your project board and the help article on connecting AI assistants.

Step 2: Lock the draft and hand over the real script

Break down a locked draft with scene numbers on it. A breakdown of an unlocked draft is a breakdown you will do twice.

You have two ways to give the assistant the script. Attach it to the chat: Claude accepts PDF, DOCX and TXT among other formats, per its upload documentation. Or drop the file on the Storyflow board and ask the assistant to read it there; the connector reads PDF, DOCX, plain text and Final Draft .fdx files that sit on a board. A long file can come back cut short, and the tool says so when that happens. If it does, attach the script to the chat instead, or work one act at a time.

Do not paste a summary. Every later pass depends on the assistant having the actual pages.

Step 3: Ask for a coverage receipt before anything is built

Your first prompt asks for three numbers and nothing else: pages read, scenes found, speaking parts found. Compare the scene count with the last scene number in your script. If the script ends on scene 18 and the assistant found 17, stop and find the missing one before a single row exists.

No other check in the process costs so little. Two scenes sharing a slugline is the usual cause of a short count, and a scene heading with a typo (EXT without a full stop, a missing time of day) is the second.

Step 4: Build the scene index as a table

Now ask for the scene index on the board: one row per scene, in script order, with these columns in this order.

Keep each table to about 50 rows. A feature gets one table per act or per run of 40 to 50 scenes, titled for its range, placed left to right. Smaller tables stay readable on a canvas and are easier to check against the pages.

Step 5: Build the element breakdown, scene by scene

Ask for a second table: Scene, Cast, Props, Wardrobe, Vehicles and animals, SFX and stunts, Location, Notes. Add one instruction that matters more than the rest: every cell must come from the script's own action lines, and a cell with nothing named in the script stays empty.

An empty cell is honest. "Period costumes" written into a scene the assistant never read is how a wardrobe department ends up prepping for something that is not in the film. Most scenes name very little, and a breakdown that looks sparse is usually a correct one.

For a feature, run this pass act by act and spot-check two scenes per act against the pages. Then walk the table with the department heads; they will add what a script never says (the second hero prop, the matching stunt double wardrobe). Use the script breakdown checklist for the categories people forget.

Step 6: Decide the two scheduling questions yourself

Before the assistant groups anything, answer two questions in your prompt, because both are yours and not the model's.

1. How many shoot days? Give a number, or tell it to balance days to roughly equal page totals and to say what target it used.
2. What order? Grouping by location, with the fewest company moves, is the industry default and the reason a strip board exists. Script order is right only for a shoot that runs in continuity.

Add the constraints the script cannot know: the location that is only free on one night, the actor who leaves on Thursday, the child who can work limited hours. And tell it not to invent dates. A day is "Day 1" until you supply a real one.

Step 7: Have the assistant build the strip board in one call

Ask Claude or ChatGPT to build the strip board on the same board, from the scene index table and not from memory. Through the connector this is one tool, create_strip_board, and the assistant passes every day and every strip at once.

What lands on the board:

• A wall per shoot day, titled Day 1, Day 2 and so on, with an arrow from each day to the next.
• A strip per scene, in shooting order, carrying the scene number and slugline as the script prints them, the page count, the cast and at most one line of synopsis.
• A colour on every strip from the INT/EXT and day/night code, set by Storyflow and mapped to the board's colour themes so it reads in light and dark mode. Dusk and dawn scenes get their own pair of colours.
• A Day total note at the top of each wall: the number of scenes and the pages in eighths, added up by the tool. If a strip has no page count, the total reads "at least" that many pages.

One call takes up to 30 shoot days and up to 40 strips per day. A scene stays whole: a strip is a scene, never half of one.

Step 8: Check the heavy day, the light and the turnaround

Read the day totals before you read anything else. For narrative work, 4 to 6 pages a day is a common planning range; a day far above that needs a reason or a split. Then check three things the page count hides.

• Light. A day that has dawn scenes and dusk scenes is a day that runs from before sunrise to after sunset. Two dusk scenes on one day share a window of well under an hour.
• Turnaround. A night shoot followed by a morning call breaks the rest period. Put night work at the end of a block or before a day off.
• Cast days. Ask for the day-out-of-days table (step 9) and look for an actor booked on two days that are far apart.

To move a scene, drag its strip to another day's wall. The board is yours to reshuffle. One thing to know: the Day total note is text written when the board was built, so after you drag strips, ask the assistant to read the board and recount the totals.

Step 9: Build the day-out-of-days and keep the assistant on the board

Ask for a table with one row per cast member and one column per shoot day, built from the strips as they now stand on the board. Use the standard marks: SW for start and work, W for work, H for hold, WF for work and finish, SWF for a single day.

From here the board is the source of truth and the chat is a tool. When something changes, tell the assistant to read the board first. It can also report what changed on a board in the last day, the last week or the last month, and who changed it, which is how you catch a strip somebody moved without telling you. Share the board with the crew by invite, and send the client a view-only link that opens with no account.

The Five Tools Ranked for This Job

Each review follows the same shape: the verdict, who it fits, the price, why it ranks where it does, strengths and limits.

1. Storyflow

Verdict: the one tool here where Claude or ChatGPT builds the breakdown tables and the strip board directly, on a board the crew opens by link.

Best for: producers and directors on shorts, indie features, commercials and branded films who already plan in an assistant.

Pricing: Plus is $7.99 a month billed annually ($9.99 monthly), Pro is $14 a month annual ($19 monthly) and Max is $39 a month annual ($49 monthly), per the pricing page. Storyflow is paid-only during early access; its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now.

Storyflow is a visual project planning workspace: an infinite canvas board that holds tables, notes, documents, images, storyboards and slide decks. Its MCP server, launched in October 2026, lets an assistant read boards and build on them. For this job the relevant part is the strip board tool, which takes days and scenes from the assistant and owns the layout, the colours and the page arithmetic itself.

There is a second route that needs no outside assistant. Storyflow's built-in AI agent has a script breakdown workflow and a strip board workflow. Attach a script in its chat (PDF, Final Draft .fdx, Fountain or plain text) and it parses a scene index mechanically from the sluglines: scene numbers, INT/EXT, time, estimated length in eighths and speaking parts. It opens with a coverage receipt, asks whether you want the scene index, the full breakdown or both, and for the strip board asks how many days and which order. Given two drafts, it can report which scenes were added, cut or changed. That route spends your plan's AI usage; the connector route runs on your own assistant and does not.

Strengths

• The assistant writes the scene index, the breakdown and the strip board onto the board, and reads them back before a change.
• Day totals in eighths are computed by the tool, not by the model.
• The schedule sits beside the moodboard, the shot list and the storyboard on the same canvas.
• A view-only link opens with no account. Invited collaborators edit in real time on any paid plan.
• The connector has no usage limit on Plus, Pro and Max and does not spend Storyflow AI credits.

Limitations

• No day-out-of-days report, no one-line schedule export, no conflict detection. The assistant can build tables that cover the first two, but they do not update themselves.
• No calendar tool, and a table on the canvas cannot be sorted. Dates live in table cells and wall titles, and rows are kept in date order by hand.
• It does not send call sheets or track confirmations.
• Browser only. No offline mode for a location with no signal.
• Over the connector, page lengths are the assistant's estimates from the script it read. Over either route, eighths are estimates until a human measures the pages.

2. StudioBinder

Verdict: the best single suite when the breakdown has to flow into a stripboard, a shot list and a call sheet that tracks who confirmed.

Best for: crewed narrative productions and production companies that run several projects a year.

Pricing: the Starter plan is $29 a month with one user and 10 projects, per StudioBinder's Starter plan article. Indie is $49 a month with two users and 25 projects, and extra users are $25 each a month, per its Indie plan article. Check its pricing page for annual rates.

StudioBinder's breakdown tool imports PDF, Final Draft, Fountain or TXT, lets you tag elements from a drop-down with colour-coded categories, and syncs breakdown changes to the stripboard, shot lists and call sheets. It assigns cast IDs automatically when characters speak. The page describes no AI tagging of other elements and no ChatGPT, Claude or MCP integration, so with an assistant-led workflow you tag by hand or retype the assistant's output.

The free plan is a real trial but a tight one: one project, 10 breakdown elements and 10 scenes on the stripboard or 50% of a screenplay import, per its plan comparison.

Strengths

• Breakdown, stripboard, shot list and call sheet share one set of data.
• Day-out-of-days reports and filterable breakdown reports.
• Call sheets with delivery and confirmation tracking from the Indie plan.
• Auto-ordering of strips by set or time of day on Indie.

Limitations

• We found no connector for ChatGPT or Claude, so the assistant cannot write into it.
• Tagging is manual apart from cast IDs.
• The free plan caps the stripboard at 10 scenes.

3. Filmustage

Verdict: the strongest automatic breakdown, with the schedule, day-out-of-days and budget generated from it, using Filmustage's own AI and not your assistant.

Best for: line producers and ADs who want the tagging done for them on a full feature script.

Pricing: a Free plan with all non-AI tools, one active project and a partial AI breakdown covering 20% of scenes. Director's Cut is listed from $49 a month, or $408 a year billed annually, with 1,000 coins per billing cycle for AI features, per Filmustage's pricing page.

Filmustage tags cast, props, locations, VFX and wardrobe with its own AI, then feeds a stripboard, a calendar, day-out-of-days reports, call sheets and a budget. If your question is simply "which software breaks down a script by itself", this is the direct answer, and it ranks third here only because this guide weighs whether your own assistant can do the writing. Its AI features draw down coins, so heavy use on a long script has a cost beyond the plan price.

Strengths

• Automatic tagging across a whole script.
• Schedule, day-out-of-days and conflicts on the Free plan for one project.
• Budget line items generated from the breakdown and schedule.

Limitations

• We found no connector or MCP server for ChatGPT or Claude.
• AI features are metered in coins, which makes the real cost harder to predict.
• Its AI works inside Filmustage; the context you built up in your assistant stays behind.

4. Movie Magic Scheduling

Verdict: the industry reference scheduler, and the right answer for a union feature, a bonded picture or a series.

Best for: first ADs, UPMs and line producers on productions where the schedule is a contractual document.

Pricing: $299.88 a year with a 12-month commitment, per the annual store page, or $42.99 a month, per the monthly store page.

Movie Magic Scheduling from Entertainment Partners offers an on-screen day-out-of-days that can show rehearsals, fittings and travel, conflict detection, multi-episode management, sub-boards for units, real-time multi-user editing with view or edit permissions, and transfer of elements to Movie Magic Budgeting. Nothing else in this list matches that depth. It ranks fourth here for one reason: its page mentions no AI features, and we found no way for Claude or ChatGPT to write into it, so in this workflow the assistant's breakdown has to be entered by hand.

Strengths

• Deepest scheduling feature set: units, episodes, conflicts, customisable reports.
• One-line report export to PDF or Excel.
• The format financiers, bond companies and studios expect.

Limitations

• No AI features mentioned and no connector found.
• No call sheets in the product page's feature list.
• Its page describes View or Edit access for users in the schedule; we found no view-only link for a client without the software.

5. Celtx

Verdict: a sensible choice if the script is already written in Celtx, because the breakdown and stripboard read the script directly.

Best for: writers and small teams who want writing and pre-production in one account.

Pricing: Celtx's pricing page lists breakdown, schedule, call sheets and budget as included on its Team tier and as optional add-ons on the Writer plans. The page we fetched showed no dollar amounts, so see Celtx's pricing page for current prices.

In Celtx, each scene becomes a strip, strip colours follow the interior or exterior and day or night combination, and you place an end-of-day strip below the last scene of a shoot day, per its stripboard help article. Tagged characters appear in the stripboard's character column. It is a conventional, competent stripboard tied to the script editor.

Strengths

• Script, breakdown and stripboard in one place, so a rewrite carries through.
• Call sheets built from shoot days on the stripboard.
• A free plan with one project to start a script.

Limitations

• Production tools are not on the free tier.
• We found no AI features on its pricing page and no connector for ChatGPT or Claude.
• Prices were not shown on the page we could read, so compare before you commit.

Prompts You Can Copy for Each Pass

Each prompt is a single instruction. Run them in order and wait for each result before sending the next. Replace the bracketed parts.

The reading and index prompts

The breakdown prompts

The scheduling prompts

Worked Example: SALT ROAD, an 18-Scene Short Scheduled Into Four Days

This is an illustrative example. The script, the counts and the assistant's mistakes are invented to show the method, and nothing below is a measured result.

The script and the coverage receipt

SALT ROAD is a short with two leads, MARA and JOE, three day players (WAITRESS, COOK, CLERK) and four base locations: a coast road, a diner, salt flats and a motel. We attach the PDF to Claude and ask for the receipt. The first answer says 15 pages, 17 scenes, 5 speaking parts. The script's last scene is numbered 18.

The follow-up finds it in one message: scenes 3 and 14 share the slugline INT. DINER - DAY and had been counted as one. The corrected receipt reads 18 scenes, and only then do we ask for the table.

The scene index (Worked Example)

The index check returns 18 rows and 117 eighths, which is 14 5/8 pages. That matches a 15-page script with a short last page closely enough to trust the estimates for scheduling.

The breakdown, and what an honest one looks like

The breakdown table comes back sparse, which is correct. Scene 3 lists a coffee pot, two mugs and a road atlas, each quotable from an action line. Scene 7 lists Mara's car under vehicles and nothing under props. Scene 11 lists a motel register and a room key. Nine of the eighteen rows have an empty Props cell because the script names no prop in them.

The spot check on scene 9 earns its keep: the first pass had listed "suitcase" under props, and the assistant cannot quote a line for it. It comes out. The art department adds it back a day later as their own note, in the Notes column, which is where an unscripted item belongs.

Script order against location order

In script order the company would travel like this: road, diner, road, salt flats, motel, diner, road, salt flats. That is 7 moves between base locations for 18 scenes. Grouped by location it is 4 blocks and 3 moves. We ask for four days, grouped by location, with the motel last because it is a night shoot.

The strip board the assistant built

The eighths add up: 35 + 24 + 28 + 30 = 117. The average is a little over 3 5/8 pages a day, below the common 4 to 6 page planning range for narrative work, and that is deliberate. Three of the four days are tied to a light window (dawn, dusk, night), and a light window shortens the usable day.

What the first pass got wrong

Two things, both caught by reading the board back.

First, the assistant had put scene 13 (EXT. MOTEL PARKING LOT - DAWN) on Day 1 with the diner, matching on the words "parking lot". The day check listed a dawn scene on a day block, which made no sense, and one dragged strip fixed it.

Second, Day 3 holds two dusk scenes, 8 and 18, totalling 1 2/8 pages in one fading window. The assistant flagged it when asked to name days with dawn or dusk scenes. We kept both on Day 3 but set the order: scene 18 first, because it is one actor inside a parked car and can be lit to cheat a few minutes, then scene 8 for the real sky. That decision is a note on the Day 3 wall, written by a person.

The day-out-of-days (Worked Example)

Every day player works exactly one day and there are no hold days. In script order the waitress would have been needed for scene 3 and again for scene 14, with the motel in between. The location grouping removed that second booking, and the grid is what makes the saving visible.

What It Costs: Solo Producer vs a Crew of Five

Prices are from the vendor pages linked in the reviews above, read on October 10, 2026. Assistant subscriptions are separate and are not priced here.

One producer, one shoot

A crew of five on the same schedule

With Storyflow, one person holds the paid plan and invites the director, the AD, the DP and the producer to the board. Anyone a paid member invites joins free today, and invited collaborators edit shared boards in real time. A team workspace with roles and permissions is on Max at $39 a month billed annually. There is no per-user pricing.

With StudioBinder, Indie at $49 a month covers two users and each extra user is $25 a month, so five full users on Indie come to $124 a month on those published figures. For Movie Magic Scheduling, Filmustage and Celtx, check the vendor's page for multi-seat pricing, because the pages we read did not itemise five seats.

Price is 10% of our weighting for a reason. A schedule that costs a company move it did not need is more expensive than any of these subscriptions.

Decision Rules: Which Tool for Which Production

Pick by the document your production is judged on, not by the feature list.

A short, a commercial or a branded film with a crew under fifteen

Use Storyflow with Claude or ChatGPT. The schedule is a handful of days, the people who need it are a mix of crew and client, and the same board already holds the references and the shot list. Follow the nine steps above, then build the shot list beside the strips with the shot list guide for ChatGPT or Claude.

An indie feature with no first AD

Use Storyflow for the breakdown and the first schedule, and decide at lock whether to move. If the shoot is under about 20 days with a small cast, the strip board and an assistant-built day-out-of-days table will carry it. The system in pre-production without a first AD covers who owns each document.

A crewed production that sends call sheets to forty people

Use StudioBinder. Delivery and confirmation tracking on call sheets is the feature you are buying, and Storyflow does not have it.

A union feature, a bonded picture or a series

Use Movie Magic Scheduling. Multi-unit boards, episodic management and reports in the format a bond company expects are not optional at that scale. Shot Lister vs Movie Magic Scheduling covers how the two divide the work on set.

A 110-page script and no time to tag it

Use Filmustage for the automatic breakdown, then decide where the schedule lives. Its free plan covers one active project with manual tools, and the full AI breakdown needs Director's Cut.

Common Mistakes When an Assistant Does the Breakdown

Each of these looks fine in the chat and costs you on the day.

Mistake 1: One prompt for the breakdown and the schedule

Asking for everything at once removes every checkpoint. The scene count is never verified, the props are never traced to a line, and the schedule is built on a list nobody read. Five passes take a little longer and give you five places to catch an error before it reaches the set.

Mistake 2: Letting the model add the eighths

If the assistant states a day total in prose, treat it as unverified. Have it read the totals from the board, where the strip board tool did the sum, or add the column yourself.

Mistake 3: Accepting props the script never names

A full-looking breakdown is a warning sign. Ask for the quoted line behind any element that surprises you, and delete what cannot be quoted. Unscripted needs go in Notes with a name beside them.

Mistake 4: Scheduling in script order

Script order is for the edit. Unless the film genuinely shoots in continuity, every return to a location is a company move you chose to pay for. Our guide to making a production schedule goes deeper on ordering.

Mistake 5: Trusting the schedule from memory after a rewrite

When pages change, the assistant's memory of the old draft is a liability. Tell it to read the new draft, list the scenes that were added, cut or changed, and update the index first. The strips follow the index, never the other way round.

Mistake 6: Treating the day-out-of-days table as live

The table the assistant builds is a snapshot. Drag one strip and it is out of date. Rebuild it after every reshuffle, and put the date it was built in the table's title.

Mistake 7: Inventing dates and rest days

A model asked for "a schedule" will happily supply Monday the 12th and a day off on Sunday. Neither came from you. Keep days numbered until production gives real dates, then put them in the wall titles yourself.

When Storyflow Is Not the Right Choice

Storyflow is our product, and for some productions it is the wrong tool. These are the cases.

You need generated reports

There is no day-out-of-days report, no one-line schedule and no conflict detection in Storyflow. An assistant can build tables that answer the same questions for a small cast, but they are rebuilt on request, not generated from live data. Past 15 or so cast members or 20 shoot days, use Movie Magic Scheduling, StudioBinder or Filmustage.

You need call sheets sent and confirmed

In Storyflow the call sheet is a page deck on the board that you edit and export as one PDF. It is not sent to recipients for you and nobody's confirmation is tracked. Our guide to making a call sheet with ChatGPT or Claude shows that route and where it stops.

You need a free tool today

Storyflow has no free plan during early access. Invited collaborators join free, but someone on the production holds a paid plan. If the budget for software is zero, Filmustage's Free plan (one active project, non-AI tools) and StudioBinder's free plan (one project, 10 scenes on the stripboard) are the real free options.

You schedule in a field with no signal

Storyflow runs in a browser and has no offline mode. If the AD reshuffles the board in a valley with no coverage, print the schedule or use a desktop tool.

Your production needs union rule checking or multiple units

Storyflow knows nothing about turnaround rules, meal penalties or child working hours, and it has no concept of a second unit. You can note them. It will not warn you.

Template: The Columns and Strip Fields to Paste Into Your Assistant

Copy these structures into your first message so the assistant builds the same shape every time.

Scene index columns

Scene, Slugline, INT/EXT, Time, Cast, Pages (eighths, estimated), Synopsis (one factual line).

Breakdown columns

Scene, Cast, Props, Wardrobe, Vehicles and animals, SFX and stunts, Location, Notes. Add Extras, Makeup and hair, Set dressing or Sound as separate columns only if your script uses them in more than a few scenes.

Strip fields

Day-out-of-days marks

SW start and work, W work, H hold, WF work and finish, SWF a single day. One row per cast member, one column per shoot day, a final column for total work days.

The pre-lock checklist

1. Scene count in the index equals the last scene number in the script, allowing for lettered scenes.
2. Total eighths in the index roughly equal the script's page count.
3. Two scenes per act spot-checked against the pages.
4. No day mixes dawn and dusk without a written reason.
5. No night shoot is followed by a morning call.
6. No day player works two days that a reorder could make one.
7. The day-out-of-days table was rebuilt after the last strip moved.

The Bottom Line

A script breakdown and a schedule are five documents that have to agree with each other: the scene index, the element breakdown, the page counts, the strip board and the day-out-of-days. Claude and ChatGPT are good at producing each one and unreliable at keeping them consistent inside a chat. Put them on a Storyflow board, make the assistant read the board before every change, and let the strip board tool do the colours and the arithmetic. For a short, an indie feature, a commercial or a branded film, that is the most direct route from a locked script to a schedule your crew can open.

When the production is bigger than that, say so early. Movie Magic Scheduling for union features and series, StudioBinder for tracked call sheets, Filmustage for automatic tagging at feature length. To set up the connector, start at the Storyflow MCP page.