Quick Answer
When you’re briefing a crew you’ve never worked with, in a city you don’t know, you can’t rely on shared history. Everything in your head (the philosophy, the visual grammar, the specific asks) has to live in documents that can travel. This is what that process actually looks like.
What does briefing a crew actually mean for a DP?
The brief isn’t a call sheet. The AD handles the call sheet. The brief is the transfer of visual intent (your philosophy, your grammar, your specific asks) into something a gaffer, an art director, or a director’s assistant can act on without you in the room.
Most DPs don’t distinguish between prep and a brief. Prep is what you build for yourself: the document that proves you’ve thought through every scene. A brief is what you build so that someone else can do their job correctly. Those are different things, and the gap between them is where a lot of well-prepared shoots fall apart.
Why doesn’t one big prep document work as a brief?
For Bambai Meri Jaan (Bombay My Beloved), a 10-episode Amazon Prime series I shot in Mumbai, I built a 440-page prep document. Visual philosophy, lensing strategy, color theory, lighting references, camera diagrams, location notes, continuity stills of costumes on actors. Everything.
It was useful. But it wasn’t a brief. It was an empire: my attempt to impose control over a production spanning multiple decades of story, hundreds of locations, and a crew I’d largely never worked with before.
A 440-page document is not briefable. A gaffer doesn’t need the color theory chapter. A production designer doesn’t need the section on camera movement. Handing everyone the full document is the same as handing them nothing. What’s theirs is buried, and the document trains people to stop looking.
The problem isn’t the depth of the document. The problem is that a brief has to be shaped for its recipient.
What actually goes in a DP brief?
The philosophical layer
Before anything technical, the crew needs to understand the why. On Bambai, the central question was: how do you visually tell the story of a man’s quest for absolute control, born from absolute chaos? Every choice (lens, light, movement, color) had to express that duality. If the gaffer doesn’t understand that every controlled, composed setup needs one wrong note to signal the tension underneath, the lighting is just pretty. It needs to mean something.
This layer isn’t abstract decoration. It’s what lets a department head make the right call when you’re not standing next to them.
The visual grammar layer
Once the why is established, you translate it into specifics. For Bambai: wide lenses for hope and command, long lenses for focus and moral distance. Camera movement motivated by emotion: every dolly earning its place, nothing casual. Color built on a deliberate wrong-note principle: one element in every frame that doesn’t quite fit the palette, registering as subconscious unease rather than obvious discord.
These specifics are briefable. A gaffer can act on “this setup needs one light that works against the room’s logic.” A production designer can act on “the background should feel wrong for this character.”
The location and set layer
This is where the brief gets operational. For Bambai, I worked from a Google Slides document built around the stripboard. Scene numbers and descriptions became live links into specific slide sections, so the document had a navigable index rather than a scroll. Each scene slide carried scout photos, historical references, rough storyboards from location visits, sun path maps with live links to GPS coordinates, and “this not that” comparisons: two visual directions circled next to each other, so the team could see exactly what I was choosing between.
For set dressing and art decisions I’d leave specific asks in the slide notes. Not vague direction. Specific direction. “Can we make this wall red? Reference: [image].” Camera diagrams sat beside scout photos. Continuity stills of costumes sat beside lighting references. You could read the full visual intention of a scene without hunting for it.
How do you make sure each department gets only what they need?
The Slides system had one structural problem: everyone saw everything.
The gaffer navigated the same document as the production designer. There was no way to give someone a view shaped for their role. If I needed the gaffer focused on sun paths and lighting references, I had to manually tell them which slides were theirs. That filtering was never finished. It just accumulated.
What a proper crew brief needs is for each recipient to see exactly what they need to execute their part of the vision, without having to navigate through everyone else’s. The gaffer’s brief and the art director’s brief are built from the same source. They shouldn’t look the same.
What does a strong brief actually change on set?
A crew without a shared brief improvises. With one, they interpret.
Improvisation is reactive. It responds to what’s in front of it. Interpretation is active. It applies a shared understanding to a new situation. On a series shooting across months and dozens of locations, interpretation is what keeps the visual language consistent. The gaffer on day 47 shouldn’t be guessing what you meant on day 3.
On Bambai, the brief was the reason a specific wall got painted red before I arrived on set. Not because I happened to be there when the decision was made. I wasn’t. The ask was documented, referenced, and visible to the person who needed to act on it.
That’s the actual value. Not organization for its own sake, but decisions made correctly while you’re three setups away.
How do I build crew briefs now?
The Slides system was the right instinct: centralize the vision, make it navigable, use specific references over descriptions. The gap was always in distribution: one view of everything, for everyone, with no filtering by role.
What I was building toward, without quite having it, was a system where the same prep source produces different outputs for different recipients. Where the gaffer’s view and the production designer’s view come from the same place, but are shaped for the job.
That’s what Headroom’s Brief does. Built once (visual references, diagrams, location notes, scene breakdowns), and each role sees what’s relevant to their work. The gaffer sees the lighting intent, the sun paths, the electrical reads. The art department sees the color references, set notes, and continuity stills. One source, every department, without six manually curated documents.
The 440-page prep document and the Slides index were the right instinct. The gap was always in the last step.
FAQ
What should a DP brief include?
A DP brief covers three layers: the visual philosophy (the why behind the look), the visual grammar (lens strategy, movement approach, color and light intent), and scene-level specifics (set asks, location notes, references, camera diagrams). The depth varies by project; the structure should always be shaped for whoever’s receiving it.
How do you brief a crew you’ve never worked with before?
Start earlier than you think you need to, and be specific rather than directional. Show references rather than describing them. The philosophy layer matters most: department heads making decisions without you present need to understand the intent behind the look, not just the instructions.
What’s the difference between a call sheet and a DP brief?
A call sheet tells a crew when and where. A DP brief tells them why: the visual intent, the specific asks, the context behind each setup. The AD owns the call sheet. The DP owns the brief.
How do you communicate visual intent to a gaffer?
Specific reference images plus the emotional logic behind each setup. A gaffer can execute almost anything if they understand what the light is supposed to mean in the scene, not just where it goes.
How long should a pre-production brief be?
As long as it needs to be, and no longer than its recipient will read. A 440-page prep document is useful for the DP building it. A gaffer needs ten pages. The right ten. Length is less the problem than whether the document is shaped for the person reading it.
What tools do cinematographers use for pre-production briefs?
Historically: Google Slides, spreadsheets, PDFs, and apps like Concepts. The friction is always in distribution, getting the right information to the right person without manually curating six separate documents. Headroom handles the filtering at the source: one prep built once, with role-specific views for each department.