Shot Logs: The Crew’s Forgotten Lifeline
You’d be amazed how many sets I’ve watched unravel in post because nobody bothered with a shot log. The DP calls, “That’s a keeper!” Script Sup scribbles something halfway legible, and 80% of takes end up marked as “good.” Weeks later, in the edit bay, there’s panic. What was actually the circle take? Why’s there a shot labeled only “wideshot4?”
Shot logs aren’t sexy. They’re not going to light up your Instagram. But ignore them and you’ll pay—usually in lost time digging through hundreds of useless takes, or endless group texts with crew begging for context. On a branded doc we did last summer, the client wanted every soundbite cross-referenced to b-roll. Imagine matching quotes to eight hours of footage, zero notes. Never again.
Good Logs Save Edits—Bad Ones Waste Days
Here’s where it all breaks down: Most logs are wishful thinking. Someone with spotty attention and coffee hands tries to jot down what they heard, half the details getting lost between action and cut. The result? Every editor’s nightmare—ambiguous shorthand, no metadata, and just enough info to be dangerous, not helpful.
Contrast that with sets where every roll gets logged meticulously—scene, slate, good/bad, take notes, sometimes jokes or warnings (“Talent coughs at 1:32” or “Grip argues off camera”). When you sit down to cut, you know which takes were gold, what rolling resets to ignore, which slate was the director’s real pick. I’ve seen a shot log save two days on a commercial cut just because the log had, “client requested another for safety—use take 4.”
Here’s the secret: Editors hate calling the production coordinator to track down forgotten details. Nobody wants to relive the day two months later, especially when someone else could have spent three minutes logging it on set. Shooting is expensive. Logging is not. That’s the mismatch.
The Right Way (and Tools) to Do It
So who actually owns the log? You can say it’s script sup, but on many small sets it’s whoever’s closest to the camera. The trick is picking a method everyone will actually use. Pen and paper works, but God forbid you lose the notebook. Lately, I’m a convert to apps like Shot Lister or a shared Google Sheet on an iPad that autosaves. I watched an AC log 3 cams simultaneously while reference-coding clips—the editor fell in love before the first rough cut.
Don’t overcomplicate it. Scenename, take, circle or not, short note (“Boom in frame,” “Director loved take,” whatever). If your log starts needing its own workflow, you’re overthinking it. Even on a run-and-gun doc, you jot basics after each scene while dumping cards. If nobody writes, record quick voice memos—anything is better than staring at 200 clips, all called “A001C002” with no context.
On a food shoot for a chain last winter, production gave me a log with camera, lens, shot, timestamp, and even exposure mods. I turned out a first cut in a day because I knew exactly which slow-mo pasta fall the client wanted. That’s time back in your life.
Why Nobody Actually Does It (And Why You Should)
Most crews still treat shot logs as a throwback, or assume, "Eh, the camera files are organized, that’s enough." They’re not. Video file names don’t capture the frustration on set, the magic moment, or the director’s forgotten offhand compliment (“That was perfect”). Maybe it feels too old school, or nobody wants to babysit paperwork in the chaos of production.
But every single time I’ve skipped it (or watched a team do the bare minimum), we paid on the backend. Scrubbing endless dailies, labeling footage by sight, missing out on gems hiding in the noise. On narrative projects, it’s even riskier—you forget which take had clean audio, which slate had the actor’s first real tears. It’s not a nostalgia thing. It’s about giving future-you (and your editor) the power to tell the story, not just piece it back together.
You never hear anyone complain about having too much context in the edit. But I’ve never forgotten the chaos of trying to hand over a project with zero decent logs. If shot logs sound boring, trust me: You only need to salvage one near-disaster to see why the "boring" stuff saves the coolest work.