Quick Answer
Most film prep software races to generate shot lists from scripts with AI. But 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 connects your prep into one place, so when the schedule moves, everything moves with it. You still write every shot. The tool keeps it in sync.
Why does shot list generation solve the wrong problem?
Writing a shot list is arguing with yourself before anyone’s on the clock. The order, the focal length, the reason why. Putting it on the page is how you find the problems. You realize a dolly move won’t survive the location. Or a close-up needs a longer lens than anything on your order. 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. Shot lists just 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, your prep should be organized around the unit you actually work in. On narrative projects that’s the scene, not the shot. A scene has a location, a schedule day, a set of required gear, a look and story considerations. The shot list, the brief, the gear request all come off the scene. On commercial and short-form work, where there’s no script, the shot is that unit instead, grouped into setups and sequenced into shoot days.
When something changes at the scene level, everything else should cascade from it. That’s connected prep. It’s one prep. The shot list, the brief, the gear flags are just windows onto it.
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, and there are two ways in. The first is the script. You read it and mark it up directly, before any schedule exists. A lighting instinct on this scene, a lens idea on that one. Every mark, note, and reference pins to its scene and travels with it, into your prep and into the brief your crew reads on the day.
The second is the schedule. You drop your AD’s export in and the master scene list builds itself (the Loom), organized by location, day, and unit. When it lands on top of script work you’ve already done, it fuses with that work instead of wiping it. Either door, the scene is the unit everything hangs off. Your shot list lives inside it, 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) who built Headroom.
FAQ
Will Headroom write my scenes or generate shots for me?
No. It won’t make creative decisions for you. You write everything. The art stays yours. The tool organizes it, connects it to your prep data, and produces the documents (briefs, exports, filtered views) that your crew actually needs.
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’m not having a model guess at a PDF of your schedule. That’s how quiet errors end up buried in your breakdown. Instead, Headroom reads a specific data export directly from Movie Magic Scheduling (MMS). It requires a bit of exactness, but it means your breakdown matches the AD’s strips exactly, line for line. 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. If you’re starting before there’s a schedule, the way in is script-led prep. You annotate the script directly, so your notes are already in place when the schedule arrives, and on the shoot day they sit right next to everything else for that scene.
Once you have dates, dropping the AD’s schedule in is the fastest path. Headroom scans it and builds the master scene list automatically, and the framework exists the second the schedule is imported.
Either way, pulling references is one of the first things most DPs do, and now you have a place to put them, organize them, and tag them. When they’re ready to go somewhere, you sort by tag and link them to your scenes.