Two kinds of tool do the job: general assistants (ChatGPT, Claude, Gemini) that turn pasted script text into breakdown tables, shot lists and call-sheet drafts, and production platforms such as StudioBinder and Filmustage that hold the schedule and crew data. Use either for drafts; check page counts, timings, safety items and contacts by hand before a paid crew sees anything.
Most of what ranks for this topic is aimed at creators working alone: video generators and idea tools. A small paid production is different, because a crew is being paid to be somewhere at a set time, so the paperwork carries money and safety. An AI draft that gets a call time or a hospital address wrong costs more than the hour it saved. The useful split is between what AI drafts well and what a named person must own.
Assistants, platforms or a spreadsheet: which fits which job
Three kinds of tool do this paperwork, and a small production often uses a mix.
| Option | Good at | Falls short | Check first |
|---|---|---|---|
| General assistants: ChatGPT, Claude, Gemini | Turning pasted script text into a breakdown table, a first-pass shot list or call-sheet wording; answering questions about a script | Forgets your schedule unless you keep it in a project; miscounts page lengths; fills gaps with invented detail | Plan terms on training; whether you may upload the script at all |
| Production platforms: StudioBinder, Filmustage | Holding breakdown, schedule, crew contacts and call sheets together, and sending call sheets out | Cost and learning time; AI features differ by vendor and change | Prices, free-tier limits and export limits on each vendor's own page |
| Spreadsheet and templates | Full control, cheap, familiar to every crew | Manual; breaks when the schedule moves | One master file, one person who edits it |
On the two platforms: Filmustage's pricing page, as of October 2026, lists a Free plan with one active project, the non-AI tools (call sheets, schedules, shot lists and storyboards among them) and AI breakdown on only 20% of scenes, and a Director's Cut plan from $49 a month ($408 billed yearly) that adds full AI breakdown and AI scheduling, with AI features paid for from an allowance of credits it calls coins. StudioBinder's own site lists script breakdowns with an element tagger, stripboards, shooting schedules, script sides, shot lists, storyboards, production contacts and a call sheet builder that handles distribution. Its home page does not mention AI, so read its current pages rather than assuming either way; its pricing page would not load for me, so I quote no StudioBinder prices. If you want the wider map of tools by job, best AI filmmaking tools by job for a small production business covers editing, audio and more.
A working rule: a one-day shoot needs an assistant and a spreadsheet. A three- to five-day shoot with a small crew justifies trying a platform's free tier or trial. Ten days or more across several locations is where a platform earns its place, because the schedule changes daily and every change has to reach every call sheet.
Before you upload anything: scripts, NDAs and crew details
A script usually belongs to someone else, and many are covered by an NDA. Read the agreement before you paste a page into any tool, and ask the writer or producer if it is silent. Consumer ChatGPT and Claude plans let you switch off the use of your chats for training, while business plans (ChatGPT Business, Claude Team, Gemini in Workspace) do not train on business content by default. The labels move around, so check the setting you are actually using, not the one in last year's tutorial.
Crew details are personal data. Sort what you paste into three piles.
| Pile | What goes in it |
|---|---|
| Fine to paste | Scene text you are cleared to use, scene numbers, generic location types, equipment lists, the shoot-day times |
| Paste only as codes | Crew names and roles (C1, C2), cast availability, location contact names |
| Keep out of consumer chats | Phone numbers, home addresses, dietary and medical notes, ID or bank details |
The practical routine is to let the AI draft the wording with codes and placeholders, then merge the real names and numbers yourself from a private sheet. My tutorial on GDPR and AI tools: what a small business must do explains why this matters beyond good manners.
Script to breakdown: a three-scene excerpt, run and corrected
A breakdown lists, scene by scene, everything the production has to supply: location, time of day, cast, props, wardrobe, vehicles, sound cues, effects and safety flags. Here is a short original excerpt to run through it.
INT. BAKERY - EARLY MORNING
Flour dust hangs in the light. The BAKER (30s) slides a tray of loaves into the oven. Her BROTHER (20s) argues into a phone in the doorway.
BROTHER
(into phone)
Friday. I said Friday.
The oven timer BUZZES. The Baker ignores it and slips a folded letter into her apron.
EXT. BAKERY - BACK ALLEY - CONTINUOUS
The Brother kicks a crate across the alley. A delivery VAN idles at the kerb, its DRIVER asleep at the wheel.
INT. DELIVERY VAN - MOMENTS LATER
The Driver wakes with a start. Through the windscreen, the Baker walks towards him, letter in hand.
A prompt that works for a first pass, with the rules that stop the worst habits:
You assist a script supervisor. Break down the script below scene by scene.
Return a table with: scene number, INT/EXT, location, time of day, page length in eighths (estimate only), speaking cast, non-speaking cast, props, wardrobe, vehicles, sound or effects cues, stunts or safety flags, and a column called UNSURE.
Use only what is written. If something is implied but not stated, put it in UNSURE instead of guessing. Do not invent props or characters.
Script: [paste]
Here is the kind of table that comes back (illustrative).
| Sc | I/E | Location and time | Pages | Cast | Props and other | Unsure |
|---|---|---|---|---|---|---|
| 1 | INT | Bakery, early morning | 4/8 | Brother (speaking); Baker | Oven, tray, loaves, phone, folded letter, apron; oven timer buzz | Flour dust: practical or added? |
| 2 | EXT | Back alley, continuous | 2/8 | Brother; Driver | Crate; delivery van | Is the van moving? |
| 3 | INT | Delivery van, moments later | 2/8 | Driver; Baker | Letter | Camera inside or outside the van? |
It reads well, and four things need fixing by a person with the script open:
- The page lengths are wrong. The model said 4/8, 2/8 and 2/8, a full page in all. Laid out in screenwriting software, which measures from the formatted page, the excerpt runs to about half a page: 2/8, 1/8 and 1/8, because no scene counts as less than an eighth. The model doubled the length. Scheduling depends on these numbers, so take them from the software, never from the model.
- Time of day drifts. "Moments later" is not a time. Scene 3 is early morning, and scheduling groups scenes by light, so write it in.
- Wardrobe is filed as a prop. The apron belongs with costume, and the letter is a continuity prop that appears in scenes 1 and 3.
- The safety angle is thin. A picture vehicle with a driver on set needs insurance, a driver you trust and a parking and engine-off plan, none of which the table raises.
For longer scripts, work in chunks of about ten pages, because long single passes tend to skip small items, and send a text-based PDF or plain text rather than a scan. Re-run only the scenes that change when a revision arrives; the model does not track revisions, so a call sheet built from an old breakdown is a classic way to send the crew to the wrong place.
From breakdown to schedule: where the AI's day goes wrong
Take a ten-page short with eight scenes, two shoot days and a budget of five script pages a day (my assumption; set yours from your own pace). Ten pages is 80 eighths, so the budget is 40 eighths a day. The scenes, in eighths, are these.
| Scene | Location | Eighths | Cast needed |
|---|---|---|---|
| 1 | Bakery interior | 2 | Baker, Brother |
| 2 | Back alley | 1 | Brother, Driver |
| 3 | Delivery van | 1 | Driver, Baker |
| 4 | Bakery interior | 14 | Baker, Customer |
| 5 | Market stall | 10 | Baker, Customer |
| 6 | Market stall | 18 | Baker, Brother |
| 7 | Bakery interior | 18 | Baker, Brother |
| 8 | Flat interior | 16 | Baker |
Asked to schedule by location alone, a model does the sensible-looking thing and groups the bakery, alley and van on Day 1 (scenes 1, 2, 3, 4, 7: 36 eighths) and the market and flat on Day 2 (scenes 5, 6, 8: 44 eighths). It never asked about availability. The actor playing the Brother can only work Day 1, and he is in scene 6. Day 2 is also 4 eighths over budget. Once you tell it, the plan becomes Day 1: scenes 1, 2, 3, 6, 7 (40 eighths); Day 2: scenes 4, 5, 8 (40 eighths). That fits, but it splits the bakery and the market across both days, which means two extra visits to price, with permits, travel and a second set-up.
The lesson is about the prompt, not the tool. Give the assistant the constraints before it plans: page budget per day, cast availability, location access windows, daylight needs and any scene order that must hold. Then ask for a day-out-of-days table, which lists the days each cast member works, and check it against what you have agreed with them.
Shot lists: what the AI proposes against the time you have
A shot list is a menu of coverage, and a good one is constrained by the clock. Suppose scene 1 has a 90-minute slot. Ask for options, not a plan:
Scene 1 text is below. Propose the shots a director might want, as a table: setup number, shot size, angle or movement, what it covers, and whether it is essential, useful or a cut-away.
Do not choose lenses. Do not assume a crane, dolly or drone. Our kit is one camera, a tripod, a handheld rig and a small lighting kit.
Scene: [paste]
Say it returns 14 setups. At a realistic 15 minutes each, that is 210 minutes against a 90-minute slot. The job is to cut, and a person who knows the location has to do it. Here is what a trimmed list might look like.
| Setup | Shot | Covers | Minutes |
|---|---|---|---|
| 1 | Wide master, tripod | Baker at the oven, Brother in the doorway | 20 |
| 2 | Medium, Baker loading the tray | The opening action | 10 |
| 3 | Medium, Brother on the phone | The argument | 10 |
| 4 | Close-up, Baker slipping the letter into her apron | The continuity prop | 12 |
| 5 | Insert, oven timer | The buzz cue | 5 |
| 6 | Handheld, doorway, Brother | Energy for the argument | 8 |
| Total | 65 |
Six setups take 65 minutes and leave a 25-minute buffer inside the 90. Cut-aways such as flour in the light become a pick-up list for the end of the day, if time allows. The model could not know, for instance, that the bakery's oven is available only until 09:30 or that the owner needs the doorway clear at 10:00. Facts like these live in your location notes, so paste them in before you ask. For a fuller shot-list workflow, see AI shot list generator: build a shoot-day plan from the script.
Call sheets: draft the wording, then check every fact
A call sheet tells every person who is paid to be there when and where to arrive, what is happening and who to call. Ask the assistant for the structure and the wording, and leave the facts as placeholders:
Draft a one-page call sheet for shoot day 1 of 2 from the schedule below. Include general crew call, cast calls, scenes, locations, lunch, estimated wrap, safety notes and contacts.
Leave sunrise, sunset, weather, hospital details and all phone numbers as [bracketed placeholders]. Do not fill them from memory. Flag any time clash you notice.
Schedule: [paste]
The result might include a table like this (illustrative; every bracket is something you fill from a real source).
| Item | Entry |
|---|---|
| Day | Shoot day 1 of 2, [date] |
| General crew call | 06:30 at unit base [address and parking notes] |
| Cast call | Baker and Brother 07:30 for hair and make-up, on set 08:15; Driver 09:00 |
| Sunrise and sunset | [from a sunrise calculator] |
| Weather | [forecast checked the evening before and at 06:00] |
| Scenes | 1, 2, 3 (bakery, alley, van), then 6 (market stall) and 7 (bakery) |
| Lunch | 12:00, 45 minutes |
| Estimated wrap | 18:30 |
| Nearest hospital with an emergency department | [name and address, checked on a map; route from unit base] |
| Safety lead and first aider | [names] |
| Special notes | Picture van: [insurance and driver confirmed]. No street parking outside the bakery. Oven use as agreed with the bakery owner. |
| Contacts | [numbers merged by you, never typed into the AI] |
Here are six things I would expect an AI draft of this to get wrong, each of which a person catches in a two-minute read against the schedule and a map:
- A pickup for sound equipment before the unit base opens.
- A confident sunrise or sunset time that did not come from a calculator.
- A hospital address from memory, wrong or without an emergency department.
- A cast member called on a day they are not in the schedule, because Day 1 was copied into Day 2.
- A wrap time that leaves less rest than your crew agreements allow before the next call.
- A missing dietary requirement, because the crew form was never in the prompt.
Version drift is the classic failure. In an invented but typical case, the day-one call sheet says 06:30 and the day-two version is issued from an older schedule that still says 07:30. Half the crew arrive an hour apart. The fix is boring: a revision number and date on every sheet, one person who issues them and a rule that only the latest version is ever sent.
Use the assistant as a proofreader too, because it is better at consistency than at facts. Paste the schedule and the finished call sheet together and ask:
Compare the schedule and the call sheet. List every inconsistency in times, scene numbers, locations, names and codes. Quote both versions of each. Do not correct anything, and do not comment on anything that matches.
On the example above, a good run might report that the call sheet lists scene 7 before scene 6 while the schedule has them the other way round, or that lunch is 45 minutes in one document and 30 in the other. It cannot catch an address that is wrong in both, which is why the map check stays with a person.
What must be checked by hand on a paid shoot
Several items sit outside anything an assistant can see. This table is the list I would run before issuing a call sheet.
| Item | Why AI cannot settle it | How to check |
|---|---|---|
| Crew hours, meal breaks and rest between days | It does not know your crew agreements or applicable rules | Compare call and wrap times with the agreements; leave margin |
| Child performers | Hours and supervision rules differ by place | Check the rules that apply and the licence conditions |
| Permits, access and parking | Needs a named permission and a contact | Written confirmation from the location owner or authority |
| Hospital, first aid, route | Addresses from memory can be wrong | Look it up on a map; drive or read the route |
| Vehicles, weapons or prop guns, fire, water, heights, animals, stunts | It can flag the words but not manage the risk | Qualified person on set; risk assessment; insurer informed |
| Sunrise, sunset, weather | Figures stated confidently can be wrong | A sunrise calculator and the forecast the night before |
| Dietary and allergy needs | Only in forms you hold | Collect from the crew; give catering the list directly |
| Contacts and revisions | It would be guessing | Merge from your private sheet; issue with a revision date |
Build the review step into the routine, not into your goodwill. A named person, usually the first assistant director or production manager, signs off each call sheet against the schedule and the map. My notes on setting up human review for AI work without slowing down show how to keep that step quick.
Keep one project per production, and one master file
A pile of separate chats is how versions drift. ChatGPT Projects and Claude Projects let you keep one production's script, schedule, location notes and house rules in one place, with the instructions you want applied every time. Gemini Notebook (formerly NotebookLM) can hold the script and schedule as sources and answer questions with references back to them, such as which scenes use the van; check each reference rather than trusting the answer. Whichever you use, keep a single master spreadsheet or platform project as the version that counts, and treat the assistant as a drafting aid beside it.
Add a one-line change log: date, what changed, which documents it affects. When a scene moves, re-run the breakdown for that scene only, update the schedule, regenerate the affected call sheets and issue them with a new revision number. If you later need to show a client or insurer what you knew and when, that log is the record.
What the time saving looks like on a two-day short
Here is a sum for the ten-page short above, using minutes I have assumed for someone who knows the work. Replace them with your own timings from one real job before deciding anything.
| Job | By hand | With AI: run | With AI: check and fix | With AI: total |
|---|---|---|---|---|
| Breakdown of ten pages | 150 | 15 | 60 | 75 |
| Schedule and day-out-of-days | 90 | 20 | 30 | 50 |
| Shot lists for three key scenes | 60 | 10 | 30 | 40 |
| Two call sheets | 90 | 20 | 40 | 60 |
| Total minutes | 390 | 65 | 160 | 225 |
By hand, that is 6.5 hours. With AI it is 3.75 hours, a saving of 165 minutes, or about 42%. The detail to notice is that 160 of the 225 minutes, roughly 71%, go on checking and fixing. That is the right balance for paperwork that a paid crew will act on. If your own numbers show checking shrinking towards nothing, the checks are being skipped, and the saving is borrowed from the shoot day.
Which setup for which size of job
| Production | Setup I would use | What stays by hand |
|---|---|---|
| One-day shoot, crew of five or fewer | An assistant for the breakdown table and call-sheet wording; one spreadsheet | Times, addresses, safety and contacts |
| Three to five days, a crew of ten or so, two or three locations | A platform's free tier or trial for schedule and call sheets; an assistant for first drafts | Page counts from the screenwriting software; daily review of the schedule |
| Ten days or more, many locations, changing availability | A platform as the master; an assistant for breakdown first passes and shot-list menus | Everything above, plus a named person who owns revisions |
Whatever you choose, test on one scene or one day before committing a whole production. Time the manual version and the AI-assisted one, count the corrections the AI draft needed, and keep the tool only if the corrections cost less than the hour it saved. Once the paperwork is in good order, the next questions are usually about money and client sign-off; videographer software for client review, approvals and invoices compares the tools for that stage.
Questions filmmakers ask about AI paperwork tools
Who is responsible if a call sheet is wrong?
You are, or the production company that issues it. An AI draft shares none of the responsibility. That is why times, addresses, safety notes and contacts get checked by a named person, and why the issued version carries a revision date so everyone works from the same one.
Can AI estimate how long a scene will take to shoot?
Only roughly. It can count setups and pages, but the time each setup takes depends on your crew, kit, location and cast, which it does not know. Use it to list the setups, then apply your own minutes per setup from past shoots, and add buffer for company moves and meal breaks.
Can I make a storyboard from the shot list with AI?
Yes, tools exist, but treat the images as a way to communicate with the team, not as the plan. The shot list and your location notes remain the working documents. Check the licence terms of any image generator before using its frames in client material.
Should call sheets go out as PDFs or through a platform?
Either works if everyone receives the same version. A platform can push updates and show who has opened them, while a PDF is simpler and works offline. Whichever you use, put a revision number and date on every sheet and make one person responsible for issuing it.
Further reads
- Best AI for Filmmakers Selling Video Services to Local Businesses — AI for filmmakers who sell video services to local firms.
- How to Price Videography Services: Day Rate, Project Fee or Package — Pricing a shoot once the paperwork shows the real days.
- How Videographers Use AI to Edit, Caption and Quote Faster — Where AI helps after the shoot: edits, captions, quotes.
- Wedding Photographer Timeline Template: A Day Schedule Built With AI — A day-schedule template built with AI for another trade.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Filmustage's home and pricing pages and StudioBinder's home page (checked October 2026; StudioBinder's pricing page would not load, so none of its prices are quoted); the author's own templates and sums.