Shot By Shot Analysis Example

Breaking Down Shots Individually

Most editors I work with do a rough cut first and go back to fix problems later. That usually means they catch issues in post when the schedule is already compressed. The alternative is going through footage shot by shot before you even start assembling anything. It sounds tedious, but it saves real time when things get complicated. Here is a Shot By Shot Analysis Example so you can see how the workflow actually looks in practice rather than reading a theoretical explanation of it.

Shot By Shot Analysis Example

I had a commercial shoot last year where the director wanted three versions of the same scene — day, dusk, and night — all captured in a single afternoon. The problem was that the color timer sent over a LUT that looked fantastic on a calibrated rec709 monitor but completely flattened the skin tones when played back on the client's reference TV. I caught it during my shot-by-shot pass because I kept comparing adjacent takes side by side instead of watching the sequence in order. If I had just done a regular offline edit first, that discrepancy would have showed up on delivery day instead. The workaround was straightforward. I built a simple spreadsheet with columns for shot number, take number, lighting setup, lens, camera movement, and a notes field. For each entry I logged the frame where the exposure felt right and the frame where it drifted. Then I color-matched each version against the day version as the baseline. It took me about forty minutes per scene, which is slower than just editing, but it meant we delivered exactly what the client wanted without a single revision pass. Going back to the example itself. Here is the breakdown:

Shot 012A — Day version. Wide shot, ARRI Alexa Mini with a 35mm prime. Exposure sits at about 0.3 over on the waveform. The actor's key light is a 650W Fresnel bounced off a frame. No drift observed. Shot 012B — Dusk version. Same framing and lens. I swapped the 650W for a 1K with a ¼ CTO gel. Exposure pushed to around +0.6 to compensate for the practicals in the background. The waveform shows the highlights on the window starting to clip around frame 147 when the sun flare hits. That was a real problem I had to flag for the gaffer before we kept rolling. Shot 012C — Night version. Same setup again. Key changed to a 1K with full CTO. Background practicals at full brightness. Here the issue was subtle — the shadow detail under the actor's chin got crushed because the fill was too low. I noted it in the log and we re-ran the take with a negative fill adjustment on the opposite side. Caught it early enough to fix it on set.

The point of the example is not the specific gear or numbers. It is the habit of logging each shot against the others so you can spot inconsistencies before they compound. Most people skip this because it feels like extra work. It is extra work, but it is the kind of extra work that prevents problems three days later when nobody remembers what the lighting setup was supposed to look like.

How to Set Up Your Own Analysis

You do not need fancy software for this. A spreadsheet and your editing timeline are enough. I use DaVinci Resolve for the visual comparison part and Google Sheets for the logging, but whatever tool you are comfortable with will work. Start by creating columns for the basics. Shot number is the most important one. I include take number, scene number, camera setup, lens choice, and any lighting modifications. Then I add a column for "issue found" and another for "resolution." The resolution column stays blank until you actually fix something, which makes it useful for tracking how many shots required changes versus how many were clean from the start. When I go through footage, I watch each shot at least twice. The first pass is just watching it normally to get a sense of pacing and performance. The second pass is where the analysis happens. I scrub through the waveform and vectorscope at key moments — especially at the beginning, middle, and end of the shot. Lighting changes over time in a single take all the time. A bulb aging, a sun moving behind a cloud, a practical lamp flickering. These things show up clearly if you are looking at the scope instead of just the image.

I also compare adjacent shots head to head. Put shot 013A next to shot 013B in Resolve's compare viewer and watch them back to back. If the exposure or color temperature jumps noticeably between them, you have a continuity issue. You can fix it in post, but it is cheaper to fix it before you lock picture.

Things That Are Not Obvious

The first thing people miss is that shot-by-shot analysis is not the same as a normal editorial review. In an editorial pass you are looking at rhythm, performance, and story flow. In a shot-by-shot pass you are looking at technical consistency and problem prevention. Mixing the two up leads to either spending too much time on perfect shots that do not need attention or skipping past flawed shots because the emotional content feels fine. The second thing is the order you watch the footage matters. Going sequentially through a scene makes problems harder to spot because your eye adapts to gradual shifts. Watching out of order — or jumping between versions of the same shot — makes discrepancies stand out much more clearly. I always group by scene and then sort by shot number within each scene. It takes a minute to set up but it changes how accurate your analysis is. There is also a limit to how far this approach scales. For a thirty-second commercial with maybe twenty shots, it is very manageable. For a feature film with hundreds of setups across dozens of locations, it becomes a massive undertaking. I recommend using this method selectively rather than universally. Pick the scenes that have complex lighting changes, multiple versions, or tight continuity requirements. Leave the straightforward dialogue scenes alone and move on. You will save hours and still catch the problems that actually matter.

I keep a template I reuse across projects. The column headers stay the same, and I just drop new shot data into the rows. It cuts down the setup time to roughly five minutes per project and keeps my notes consistent so anyone on the team can read them without confusion. You can build your own version quickly if you want one. I do not link a download because the structure is simple enough that recreating it takes less time than hunting for a file that might not match your workflow anyway. One more thing worth noting. Shot-by-shot analysis only works if the person doing it has access to the original camera files or at least good quality proxies with accurate color representation. If you are working off heavily compressed web downloads or badly transcoded intermediates, the waveform and scopes will lie to you. I learned that the hard way on a project where the dailies server had misconfigured its color management pipeline. Every shot looked fine in the browser until I pulled the original RAW files and checked the scopes. The "perfect" shots were actually slightly overexposed and the "dark" ones were properly exposed. Three days lost because someone thought the dailies were reliable. Do not skip checking your source quality before you start analyzing.