Shot list software
Every shot, accounted for.
Shot lists with size, angle and movement on every row, a frame from the storyboard beside each one, and a presentation view that goes out with the job's cover on it.
No credit card needed. Set up in minutes.
Storyboard · Sunday morning
6 frames, sketch to final
Shot list
0 shots
The problem
The shot list lives in a spreadsheet, the storyboard lives in a PDF, and on the day nobody is sure which row goes with which frame. The two documents describe the same shots and have never met.
A shot list that reads like a shot list.
Every shot is a row, with the columns a crew actually reads: what it is, the size, the type and the camera move. Pick from the standard terms or type your own, and give each shot its code and day.
The columns that matter
Description, shot size, shot type and camera movement, each in its own column.
Standard terms, or your own
Pick Close-up or Dolly in from the list, or type something the list does not have.
Codes and days
Give each shot its number (1A, 2B) and the day it shoots on.
Undo and redo
Every edit can be taken back, on Cmd or Ctrl Z.
Shot list · Day 1, the ridge
Every shot, as a row
A picture on every shot.
A shot list is easier to shoot from when every row shows what the shot looks like. Pick a frame from the project's assets, upload one, or pull the whole board's frames onto the list in one click.
From the project's assets
Choose any image already on the job for a row.
Or upload one
Drop a reference straight into the row.
Pull frames off the storyboard
Add frames to every row in one click, matched by shot number, so 1B gets frame 1B.
Only fills the gaps
Rows that already have a picture are left alone, so it is safe to run again.
Shot list · Day 1, the ridge
A picture on every shot
The treatment becomes the shot list.
The client sends a treatment or a script as a PDF. Instead of retyping it, drop it in: the app reads it and proposes the shots, and you choose which ones go on the list.
Reads decks and scripts
The beats of the cut become rows, and the look described on the visual pages is picked up too.
The right cut
When a script has a :30 and a :15, it reads the longest one, so shots are not listed twice.
On-screen text kept apart
A super or a title card is not mistaken for a shot.
You choose
Every proposed shot is a tick box. Nothing goes on the list until you add it.
Import from a PDF
A treatment or a board becomes rows
HINT · :30 SCRIPT
Treatment_v3.pdf · 9 pages
Every day of the shoot, sorted.
Keep one list per day, per location, or however the job splits. Move shots between lists in bulk, and when the list is ready, the shooting schedule builds itself from it.
As many lists as you need
A list per day or per location, each with its own shot count.
Select and act in bulk
Tick several shots and duplicate, move them to another list, or delete them together.
The schedule builds from it
The schedule page lays out each day from your lists' day column, with setups between shots and lunch placed for you.
On the project's front page
The shot count sits on the project hub, one click from anywhere.
Shot lists · Bright Water
As many lists as the job needs
+ New shot list
Present it, print it, get it signed off.
Fill in the job details once and every export carries them. Print a PDF with a proper cover, or share the list for review and let the client pin notes on the exact shot.
A cover block
Client, agency, director, job number and more, filled in once and printed on the shot list, the storyboard and the binder.
One-click PDF
A clean export with the frames, ready to hand out or send.
Share for review
A link with no login, where the client pins a note on the shot they mean and approves the list.
Email it
Send the review link from the app, with a respond-by date if you want one.
Export one list or all
Print a single day's list or every list on the job.
Shot list · Day 1, the ridge
Present it, print it, get it signed off
Cover · client, director, job number
Not filled inClient
Agency
Director
Job no.
Filled in once, printed on the shot list, the storyboard and the binder.
The difference
One import, both documents.
A director's package is routinely one PDF holding a board and a list. Drop it in once: the storyboard gets the frames, the shot list gets the rows, and each row points at the frame it was printed next to. Nobody declares what the file is; the app reads it and shows you.
- The confirm step shows each row's matched frame before anything is written
- Unmatched rows arrive honestly blank, one click to fix, never guessed
- The original PDF is filed in Documents either way, so the source survives the import
More the shot list does
PDF import
A treatment or deck becomes rows: description, size, movement read out of the text.
Undo and redo
Snapshot history on every edit, keyboard shortcuts included.
Codes and days
Shot codes survive import; day tags split the list for the schedule.
Present selector
Export all lists or just one.
Review pipeline
Send the list into the project's review page beside the assets.
Hub card
Shot count on the project's front page, one click from anywhere.
Works with
Storyboards
Frames that keep their shape
See how it worksWorks with
Schedule
Times that cascade, day by day
See how it worksThe whole toolkit
You just read about one of seventeen.
The rest is already in the box: every plan carries the whole toolkit, and the tiers buy room, never permission. This is the part a point solution cannot say.
Run your next job in Studio Flows.
Your first project is free, with no card and no countdown.
No credit card needed. Set up in minutes.