Quick Answer
Most film prep software is racing to generate shot lists from scripts using AI. But cinematography prep is a series of last drafts — every entry is a decision you’re committing to on set. The real problem isn’t writing speed. It’s that your documents don’t talk to each other. Headroom is a non-AI shot list tool that connects your prep into a single production structure, so when the schedule moves, everything updates from one place.
Why does shot list generation solve the wrong problem?
A shot list is basically a decision record. It’s not just about what shots you want, but the order, the focal length, and the reason why. Writing it out is literally how you find the problems. You realize a dolly move won’t survive the location. Or a close-up needs a lens you haven’t even asked for yet.
The process of writing the list IS the thinking.
Cinematography prep is a series of last drafts. AI is good at first drafts. But every shot list entry, every gear flag, every brief is the final version of a decision you’re committing to on set. That’s not something you outsource — that’s the exact job you’re being paid to do. A director hires you for your perspective, your taste, and how you specifically solve visual problems. Prep is where you make those choices.
But honestly, even if the output was a perfect reflection of your style, it still wouldn’t fix the real issue. The problem isn’t that shot lists take too long to write. It’s that they don’t connect to anything.
What does connected prep actually look like?
You write a shot list for Scene 14. Then you make a gear request that references Scene 14’s lighting setup. Then you build a brief to show the director what the scene should look like. Then the schedule changes and Scene 14 moves from day 3 to day 7. Now it’s on the same day as a scene that needs a crane, which your gear request didn’t account for. And the brief you gave your gaffer is already out of date.
The tools trying to automate your shot list are just solving for speed. But the actual problem is fragmentation. And that fragmentation turns you into a bottleneck — manually translating the same prep data into different formats for different departments, then re-translating it every time something changes. You stop being a creative lead and start doing data entry for your own ideas.
The way I see it, the scene is the atom, not the shot. A scene has a location, a schedule day, a set of required gear, a look and story considerations. The shot list comes from the scene. The brief comes from the scene. The gear request comes from the scene.
When something changes at the scene level, everything else should cascade from it. That’s connected prep. It’s not a bunch of standalone documents — it’s a single model of your production where the documents are just different views.
On Bambai Meri Jaan, I had a 440-page prep document. Every time the Dongri location — our main exterior build — shifted its schedule or access, it forced me to dig through four different spreadsheets and update the gear flags by hand. I literally lost a full week of prep just trying to keep the paperwork synced up. That’s the problem I built Headroom to solve. Not slow writing. Disconnected structure.
How does Headroom build a shot list differently?
In Headroom, you build from the scenes. For narrative projects, you drop in your AD’s schedule and it builds a master scene list — the Loom — organized by location, day, and unit. Your shot list lives inside that structure, in each scene’s Thread. Your briefs pull directly from it. Your gear flags tag the scenes themselves.
So when Scene 14 moves, you aren’t manually re-sorting a list. When a location changes, the gear flags on every scene at that location update in one spot. The brief your gaffer is looking at pulls current data, not some static export from last Tuesday.
Headroom is built around a specific boundary: it won’t generate your shot lists, suggest your gear, or decide your look. The art stays yours.
You write your own list, and your thinking stays yours. You’re just writing it into a structure that actually holds together when the production inevitably changes around you.
John Schmidt is a working cinematographer (Glory, Netflix; Bambai Meri Jaan, Amazon Prime Video; Summertime, Sundance 2020) and the founder of Headroom.
FAQ
Will Headroom write my scenes or generate shots for me?
No. Headroom is a non-AI shot list tool — it won’t make creative decisions for you. You write everything. The tool organizes it, connects it to your prep data, and produces the documents — briefs, exports, filtered views — that your crew actually needs. The prep thinking stays entirely yours.
How does Headroom read my schedule?
There’s a built-in importer (the + Schedule button) with step-by-step instructions and a downloadable template right in the app.
I am deliberately NOT using AI to scan a PDF of your schedule. AI guessing at a PDF is exactly how quiet errors end up buried deep in your breakdown. Instead, Headroom reads a specific data export directly from Movie Magic Scheduling (MMS). It requires a bit of exactness, but it guarantees absolute structural parity with your AD. It’s a small ask: a one-time, 5-minute template setup in MMS, and then maybe 60 seconds to export every time the strips move.
Can I import an existing shot list into Headroom?
Headroom builds your shot list inside the scene structure. For narrative projects, this pulls right from your AD’s schedule. If you’ve already written shots somewhere else, you’ll have to add them into the scene framework manually. Honestly, the scene-first structure forces a pretty useful re-evaluation anyway — the order your shots were written in isn’t always the order they need to live in.
Do I need to start my prep from scratch to use Headroom?
No. On a narrative project where you already have dates, the fastest way is just to drop the AD’s schedule in. Headroom scans it and builds the master scene list automatically. Since the framework exists the second the schedule is imported, you get the utility right away.
If you’re pre-schedule, you can still start building. Pulling references is one of the first things most DPs do, and now you actually have a place to put them, organize them, and tag them. So when they’re ready to go somewhere, all you do is sort by tag and link them to your scenes.
We’re also building a script-led prep flow. This’ll let you annotate a script directly, so your notes are already in place when the schedule arrives. And when you want to see your script notes on the shoot day, they’ll be sitting right next to everything else for that scene.