How to Make a Shot List With ChatGPT or Claude (2026): From Script to a Shoot-Ready Board

Key Takeaways

• Storyflow is the best place to make a shot list with ChatGPT or Claude in 2026, because its MCP connector lets the assistant write the setups straight onto a board (shot cards or a table), read them back and reorder them, while every other tool here needs you to copy and paste out of the chat.
• A shot list is one entry per camera setup, not one per scene. A two-person dialogue scene is usually five to eight entries: a master, an over-the-shoulder each way, a single each way and an insert.
• Ask the assistant for the scene breakdown first and the shots second. Doing both in one prompt is where invented coverage and skipped scenes come from.
• Connecting is a one-time step: Claude allows one custom connector even on its Free plan, and ChatGPT needs Plus ($20 a month) or above with developer mode turned on.
• Order the day by what cannot move (talent, daylight, a location window), then by location, then by lighting setup, then wide to tight. Script order is almost never shoot order.
• Budget setups, not shots. In the worked example below, 24 setups at an average of 18 minutes fill 432 of the 495 working minutes in a ten-hour day, leaving 63 minutes of slack.
• Storyflow plans start at $7.99 a month billed annually; there is no free plan during early access, but anyone a paid member invites to a board joins free and can edit.
• StudioBinder is the stronger choice for a crewed narrative production with stripboards and tracked call sheets, and Shot Lister for running the set live from a phone.

Why a Shot List Made in a Chat Window Falls Apart Before the Shoot

You paste a script into ChatGPT or Claude, ask for a shot list, and thirty seconds later you have a tidy table with forty rows. It looks finished. Two days later you are on location, the table is buried six screens up in a conversation, the gaffer has never seen it and nobody knows which of the forty rows were the ones the client cared about. The assistant did the thinking well. It did nothing about where the result lives.

That gap is what this guide is about. The breakdown itself is a job language models are good at. The failures happen after the answer arrives.

The list scrolls away

A chat is a feed, not a document. Every follow-up ("make shot 12 handheld", "add a cutaway for the latte art") produces a new version further down, and the version you shoot from is whichever one you remembered to copy. By the third revision there are three lists in the conversation and none of them is marked as the agreed one.

Nobody else can open a chat

Your DP, your client and your editor do not have access to your ChatGPT history. Sharing a conversation link shares the whole transcript, including the drafts you rejected. So the list gets pasted into an email or a doc, and from that moment the assistant can no longer see the copy people are actually working from.

A table in chat has no frames

A shot list without pictures is fine for a tripod interview. For anything with a look (a product film, a music video, a fashion piece) the crew needs the reference frame next to the setup it belongs to, and a chat table cannot hold one.

The assistant cannot check its own coverage

Ask for "a shot list for this script" in one go and the model will happily skip a scene, merge two scenes into one row, or list a shot that needs a location you never mentioned. It is not lying. It has nothing to check its work against. The fix is to make the assistant work in two passes and to put the result somewhere it can read back.

How We Chose the Tools and Weighted the Criteria

Every tool here was judged on one job: taking a script or a client brief, turning it into a shot list with ChatGPT or Claude doing the breakdown, and carrying that list to the shoot. That is a different job from "best shot list software", where a dedicated production suite should win, and the criteria below are the points where this workflow breaks.

The six criteria and their weights

• Assistant writes into it (25%). Can ChatGPT or Claude put the list into the tool directly, read it back and change it, or do you copy and paste?
• Frames beside setups (20%). Can each setup carry a reference picture in the same place as its specs?
• Crew and client access (15%). Can people open the list by link, and what do they need to sign in for?
• Shoot-day planning (15%). Setup grouping, shooting order, time estimates, a schedule.
• On-set use (15%). Ticking shots off on the day, on a phone, in a hurry.
• Cost for a solo shooter or small crew (10%). What one person and a crew of four pay each month.

Each tool scored 1 to 5 per criterion; the weighted total is out of 100.

What we did not weigh

Script writing, budgeting, call sheet distribution and casting are out of scope. A production that needs those inside one system should read the decision rules further down before choosing anything.

Storyflow wins on the first three criteria and loses on the two that belong to dedicated production software. If your shoot is won or lost on the day's schedule rather than on the plan, weight those two higher and the ranking changes.

Comparison Table: Where to Keep a Shot List You Build With ChatGPT or Claude

Sources for the competitor columns: StudioBinder's plan guide, StudioBinder's shot list page, Shot Lister, Milanote plans, Google Sheets and Google Workspace pricing, all checked on 9 October 2026.

How to Make a Shot List With ChatGPT or Claude, Step by Step

This is the full workflow, from an empty chat to a list the crew can shoot from. Nine steps, and the first one decides whether the other eight survive contact with the shoot.

Step 1: Choose where the list will live (Storyflow first)

Decide this before you type a prompt, because it decides what you ask the assistant to produce. Use Storyflow: connect it to your assistant once, and every list, revision and reorder lands on a board that the crew and client can open by link. The alternatives work if your shoot fits them: StudioBinder for a crewed narrative production where the list feeds a stripboard, Shot Lister for running the day on an iPhone, Google Sheets for a short list with no frames, Milanote for a visual reference board you will type the specs into yourself.

To connect Storyflow:

1. In Claude, open Customize, then Connectors, click Add, then Add custom connector. Name it Storyflow, paste https://mcp.storyflow.so/mcp, click Continue, choose Sign in now, click Add and sign in. Claude's help article on custom connectors confirms Free plans can add one.
2. In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode (on Business and Enterprise an admin does this). Go to chatgpt.com/plugins, click the plus button, name it Storyflow, choose Public endpoint, paste the same address, create it and sign in. OpenAI documents the mode in its developer mode article.
3. When Storyflow asks, pick the project for this shoot and allow changes. Without changes the assistant can only read.

The full steps for Gemini, Grok, Claude Code and other tools are in the connection guide, and the overview is on the Storyflow MCP page.

Step 2: Give the assistant the real source material

Paste the script, the client brief or the treatment. If you have a deliverables list (a 90-second hero film, three 15-second verticals, ten stills), paste that too: on a commercial or social shoot, the deliverables write half the list. Add the shoot facts you already know: the days, the locations, the camera, the lens set, who is on camera and for how long. Everything you leave out, the assistant will either guess or skip, and both are worse than a blank.

Step 3: Ask for the scene breakdown, not the shots

The first pass is scenes only: number, location, interior or exterior, time of day, who is in it and one line on what happens. Read it against the script. This is where you catch a merged scene, a skipped insert or an invented location, and it costs thirty seconds instead of a reshoot. Only when the breakdown is right do you move on.

Step 4: Ask for one entry per camera setup

Now ask for shots, and say the rule out loud: one entry per camera setup, numbered scene-first (1A, 1B, 2A). A setup is a camera position and lighting state; several takes and even several framings can come from one setup, but a new position or a re-light is a new entry. Ask for size, angle, movement, lens, subject and action, and an estimated setup time for each. Ask it to justify coverage per scene in one line, so you can see why it thinks a scene needs six setups rather than three. For interviews, our guide to setting up an interview shoot covers the two-camera coverage, and planning B-roll covers the cutaways an editor will ask for.

Step 5: Build it on the board as cards or a table

Pick the format by the shoot. Shot cards suit anything with a look: Storyflow's create_shot_cards tool builds a left-to-right row with one wall per shot, each holding a frame, the size and light chips, a "Shots required" checklist, the scene direction and the equipment, with an arrow to the next shot. A table suits an interview or a long list read on set: one table per scene, with a checkbox column to tick on the day. Tell the assistant which you want. One limit to plan around: a Storyflow table holds at most eight columns and 50 rows, which is why one table per scene is the default.

Step 6: Put frames on the setups that need them

Through the connector, each shot card starts with an empty frame or takes a picture that is already on the board. If your references are already on the board, ask the assistant to use them as the frames when it builds the cards, and they move into the walls instead of being duplicated. A photo you attach in the chat does not reach Storyflow by itself; the assistant can give you an upload link for the board instead. Inside Storyflow, the built-in AI's shot list workflow can also fill frames with web reference photos (captioned as reference) or, on Pro and Max, generated frames.

Step 7: Reorder the setups into shoot order

Ask the assistant to read the board back and reorder: fixed windows first (talent availability, sunrise, a café that opens at 7), then by location, then by lighting setup, then wide to tight within a setup. Ask it to state in one line which order it used. If you want the day laid out as a schedule, the connector can also build a strip board, one wall per shoot day with a strip per scene; how to make a production schedule covers the multi-day version.

Step 8: Do the time math and cut to an A, B and C list

Add the setup estimates and compare them with the working minutes in the day. If the total is over 90 percent of the day, something has to go before the shoot, not during it. Mark each setup A (the edit fails without it), B (makes it better) or C (only if ahead). Agree the A list with the director or the client, and you know exactly what to drop when the day runs long.

Step 9: Share the board and keep the assistant on it

Send the view-only link. The crew and the client open it with no account, and sign in to comment. Keep the board as the single copy: when the client asks for a change, make it on the board (by hand or by asking the assistant), not in a forwarded PDF. Because the assistant reads the board rather than its memory of the chat, "what changed in the last week?" gets a real answer: Storyflow's connector reports what changed on a board and who changed it.

The Five Tools Ranked for a ChatGPT or Claude Shot List

1. Storyflow

Verdict: the one place in this list where ChatGPT or Claude builds the shot list itself and can keep working on it.

Best for: producers, creators and small crews shooting brand, social, interview and short narrative video.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly) adds AI image generation, Max $39 ($49 monthly) adds a team workspace with roles and permissions. No free plan during early access; a Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. See pricing.

Storyflow is a visual project planning workspace: an infinite canvas board that holds notes, tables, documents, images, storyboards, mood boards and decks, with an AI agent that reads the board. Its MCP connector, launched in October 2026, means the assistant you already use can build on that board. For a shot list that is three tools in particular: create_shot_cards for the card format, tables for the compact format and create_strip_board for the shooting schedule. The assistant also reads the board back, so reordering, renumbering and "add a cutaway after 3C" work on the real list. Paid plans have no MCP limit, and the connector runs on your assistant's model, so it does not spend Storyflow AI credits.

• One wall per shot with frame, chips, coverage checklist, direction and equipment
• Tables with a checkbox column for ticking shots off
• Mood board, storyboard and shot list on the same board, so frames sit beside setups
• View-only link with no account; comments after sign-in
• The built-in AI has its own shot list workflow if you would rather not use ChatGPT or Claude

Limitations: browser only, with no iPhone or desktop app and no offline mode; tables cap at eight columns and 50 rows; no stripboard-to-call-sheet pipeline with tracked confirmations; no free plan during early access.

2. StudioBinder

Verdict: the strongest production suite here, and a copy-and-paste destination for anything your assistant writes.

Best for: narrative productions with a first AD, multiple shoot days and a crew that needs call sheets.

Pricing: a free plan with one project and up to ten shots; Starter, Indie and Professional tiers raise the project limit to 10, 25 and unlimited, per StudioBinder's plan guide. We could not load current prices from its pricing page, so check them there.

StudioBinder's shot list tool does the production side of the job thoroughly: its Shot Tagger adds a shot when you select a line of the script, shots group into camera or lighting setups, time estimates total the day, and storyboard panels sit with the shots. It has view-only links and lets people track completion on a phone. What it does not have is a way for ChatGPT or Claude to write into it, so the assistant's breakdown becomes your typing.

• Script-linked shot tagging
• Setups, shooting order and day totals
• Feeds the rest of the suite: stripboards, schedules, call sheets

Limitations: no assistant connector found; the free plan's ten-shot cap is too small for most real shoots.

3. Google Sheets

Verdict: the honest default for a short list with no frames.

Best for: an interview, a podcast shoot or a ten-row B-roll list.

Pricing: anyone with a Google account can create in Sheets. Gemini in Sheets is not in Workspace Business Starter and is included from Business Standard up, per Google Workspace pricing.

Ask ChatGPT or Claude for the list as a table, paste it into a sheet, and you have something everyone can open. It handles columns, sorting and sharing well. It falls down on frames (images in cells get awkward past a dozen rows) and on keeping the assistant in the loop: once the list is in the sheet, every revision is a new paste.

• Free, familiar, sortable
• Share link with view, comment or edit rights
• Phone app for on-set ticking

Limitations: no frames worth the name; the assistant cannot see the sheet unless you paste it back.

4. Shot Lister

Verdict: the best on-set tool here, and a planning tool you feed by hand.

Best for: directors and ADs who run the day from an iPhone.

Pricing: free download; Pro is $15.99 a month or $99.99 a year inside the app, and Studio starts at $24.99 a month for ten users, per Shot Lister's site.

Shot Lister's Live Mode tracks the day against the plan to the minute and lets you reorganize mid-shoot; its scheduling builds the day shot by shot. Pro adds storyboards, script import and Crew Sync. For this guide's job it ranks fourth because the assistant's output has to be re-entered shot by shot, and the people who are not on the crew (a client, an editor) are outside the app.

• Live Mode with to-the-minute tracking
• Industry formatting and shot numbering
• Crew Sync on Pro and Studio

Limitations: built around its app (iOS and macOS downloads on its site); no assistant connector; client review is not its job.

5. Milanote

Verdict: a lovely reference board that leaves the shot list to you.

Best for: gathering the look before a photo or video shoot when someone else owns the schedule.

Pricing: free for 100 notes, images or links and 10 file uploads; $9.99 a month billed annually per person, or $49 a month billed annually for a team, per Milanote's plans page.

Milanote holds images, notes and links on a board and shares well. Its plans page lists no AI features, and we found no ChatGPT or Claude connector, so the assistant's list arrives by paste, as notes you arrange by hand. For mood boards it is a real competitor; for a shot list built by an assistant it is the weakest fit here.

• Fast, clean reference boards
• Share links; comments after sign-in
• Generous free tier for small boards

Limitations: no shot list structure, no AI, no connector, no scheduling.

Prompts You Can Copy for Each Stage

These prompts assume Storyflow is connected. If you are pasting into another tool instead, drop the parts about the board and ask for a table you can copy.

The breakdown prompts

The board prompts

The revision prompts

Worked Example: A 90-Second Coffee Roaster Film and Three Verticals

Here is an illustrative worked example, run end to end as you would run it; the setup times and the day are estimates, not a recorded shoot. The client is a small coffee roaster. The deliverables are a 90-second brand film for the website (16:9), three 15-second verticals for Reels, TikTok and Shorts (9:16), and a founder interview the editor can cut from. One shoot day, two locations ten minutes apart: the roastery and the café.

The brief and what the assistant got from it

We pasted the client's one-page brief, the deliverables list and the facts: Sony FX3 and FX30, a 24-70mm and a 50mm, one LED panel kit, a lav and a shotgun, the founder available from 8:30 to 12:00, the café opening to the public at 15:00. Claude's scene breakdown came back with seven scenes. One was wrong: it split "roasting" into two scenes because the brief mentioned both the drum and the cooling tray. That is one lighting setup in one corner, so we merged them back into six.

The six scenes

The setups and their times

The coverage pass gave 26 setups. Two were C-grade duplicates (a second street wide, a second bag close-up), which we cut before building. The remaining 24 went onto the board as shot cards, with the client's three reference photos moved into the walls for 1A, 3A and 5C.

Shoot order and the time math

Script order would have started with roasting. Shoot order starts with the interview, because the founder leaves at 12:00 and the interview is the only scene the edit cannot work without.

The arithmetic: a 10-hour day is 600 minutes. Take out the 60-minute lunch and the 45-minute move and you have 495 working minutes. The 24 setups need 432, which leaves 63 minutes of slack, about 13 percent. Under 10 percent and we would have cut two more C setups before the shoot.

What the assistant got wrong, and what fixed it

Three things needed a human. The split roasting scene, already mentioned. A café exterior "at golden hour", when the schedule had the crew inside the café until wrap, so it became a plain street wide. And 5E, a vertical-only medium of the barista, which it had left out entirely until we ran the deliverables-check prompt; a 9:16 crop of a 16:9 wide keeps less than a third of the frame's width, so the verticals need their own setups. All three were caught because the list was on a board we could read against the script, with the frames in place, rather than in a chat reply we had to scroll.

How it ran on the day

The DP and the client opened the view-only link on their phones. The table version of the list (generated from the same setups for the AD) had a Got it column, ticked as we went. At 13:30 we were 15 minutes behind; the C list said drop 1E and 6C, and we did, without a conversation. The client's one comment on the board ("can we see the bag label clearly?") had already been answered by 4B.

What It Costs: Solo Shooter vs a Crew of Four

Solo creator or producer

Claude prices from Claude's pricing page; ChatGPT Plus from OpenAI's help center.

A crew of four sharing the list

On Storyflow, one paid member invites the other three to the board; invited collaborators join free and edit in real time, so the cost stays at $7.99 a month billed annually. Max at $39 a month annual adds a team workspace with roles and permissions, which matters when a producer runs several productions at once. Milanote's per-person price for four is $39.96 a month annual; its team price is $49. Shot Lister Studio starts at $24.99 a month for up to ten users. StudioBinder's tiers include a set number of complimentary users per plan (one on Starter, four on Professional, per its plan guide), with prices on its pricing page.

The real cost is not the subscription. It is the 40 minutes on the day spent finding the current version of the list.

Decision Rules: Which Tool for Which Shoot

A brand film, social batch or interview with a crew under ten

Storyflow, with ChatGPT or Claude doing the breakdown. The frames, the client link and the assistant's ability to reorder the list are what this kind of shoot needs, and none of it needs a production office.

A narrative short or feature with a first AD

StudioBinder for the production side (our StudioBinder alternatives roundup covers the other suites). You can still use ChatGPT or Claude for the breakdown and Storyflow for the look and the frames, but the stripboard, schedule and call sheets belong in a production suite.

A director running the day from a phone

Shot Lister on set, alongside whichever tool holds the plan. Live Mode is the feature that earns it.

A ten-shot interview with nothing to look at

Google Sheets. Ask the assistant for the table, paste it, share the link. Do not buy software for this.

Common Mistakes When You Let an Assistant Write the Shot List

Mistake 1: One prompt for everything

"Make me a shot list for this script" asks the model to read, break down, cover and order in one pass, with nothing to check against. Two passes (scenes, then setups) cut the error rate more than any clever wording.

Mistake 2: One entry per scene

A scene list with a shot size next to each row looks like a shot list and is useless on set. Say "one entry per camera setup" in the prompt, every time.

Mistake 3: Letting it invent facts

An assistant that does not know your call time, location address or crew names will make some up if the prompt implies it should. Tell it to leave unknowns blank and list them as open questions.

Mistake 4: Shooting in script order

Script order is the order the audience sees. Shoot order is the order the day can afford. Ask for the reorder explicitly and ask it to explain the order it chose.

Mistake 5: Forgetting the vertical deliverables

If the brief has 9:16 cutdowns, some setups must be framed for them. A crop from a 16:9 wide rarely works. Run the deliverables-check prompt before the coverage prompt.

Mistake 6: Keeping the list in the chat

The chat is where the list is written, not where it lives. The moment it is right, put it somewhere the crew can open and the assistant can read back.

When Storyflow Is Not the Right Choice

Storyflow earns first place on this job, and it is still the wrong tool for some shoots. Here is where to go instead.

You need a free tool today

Storyflow has no free plan during early access; its Free plan launches before the end of 2026. If your budget is zero, use Google Sheets with Claude's Free plan, or StudioBinder's free plan if the list is ten shots or fewer.

You need the list offline on set

Storyflow runs in a browser and has no offline mode. If your location has no signal, Shot Lister's app or a printed list is the safer choice.

You need stripboards, call sheets and tracked confirmations

Storyflow builds strip boards and its built-in AI drafts call sheets, but it does not send call sheets or track who confirmed. A crewed production that runs on those needs StudioBinder or a similar suite.

You need very large tables

A Storyflow table caps at eight columns and 50 rows. Per-scene tables handle most shoots, but a 300-shot feature with fifteen columns of department notes will be happier in a spreadsheet or a production suite.

Shot List Template You Can Paste Into Your Assistant

Use this as the column spec in your coverage prompt, or ask the assistant to build it as a table on your board.

The standard columns

Swaps by shoot type

If you would rather start from a ready board, the shot list template and the AI shot list generator start from the same structure.

The Bottom Line

ChatGPT and Claude are good at the thinking part of a shot list: breaking a script into scenes, scenes into setups, and arguing for coverage. They are bad at the part where the list has to live somewhere other people can open, with frames beside the setups and one agreed version. Connect Storyflow, run the two-pass breakdown, let the assistant build the list on the board, and send the crew the link. If your production runs on stripboards and tracked call sheets, keep StudioBinder for that half; if your director lives on an iPhone, add Shot Lister for the day. For most brand, social and interview shoots, one board and one assistant is the whole stack. Start with the Storyflow MCP page.