Why your videography project needs a style guide before anyone touches a camera
I spent three weeks on a commercial shoot where every department had a different idea of what "natural light" meant. The DP wanted soft overcast, the colorist insisted we grade through a golden-hour LUT, and the client's art director had pinned reference images from a completely different era of filmmaking. We spent most of the budget fixing it in post. A properly written Style Guide For Videography Handbook prevents that kind of collision by giving everyone a single source of truth before rolling begins. It's not a checklist of camera settings. Settings change based on location and schedule. What it actually covers is the creative and technical constraints that stay consistent regardless of equipment. This means frame rate targets, resolution ceilings, aspect ratio preferences, color science boundaries, lens character notes, and grading references. It also covers audio approach, B-roll philosophy, lower-third treatment, and how you handle motion graphics integration. I once built a handbook section for a documentary series where we filmed handheld and steadicam simultaneously. The problem was the edit suite couldn't decide whether to match or contrast the two looks. I added a rule: handheld gets slight grain overlay and 1/2 stop cooler temp, steadicam stays clean. It wasn't about artistic preference. It was about giving the editor a concrete decision tree instead of forcing them to guess what "feels right" at 2 AM on a deadline.
Building the document without wasting everyone's time
Start with the deliverables. List what needs to be produced in what format, at what resolution, for what platform. If the client needs 4K HDR for broadcast and a 1080p SDR cut for social, that changes your entire workflow. Write that down first. Everything else flows from those constraints. Next, lock the visual reference set. This is where most teams go wrong. They attach ten vague mood boards. Pick three images maximum. One for color tone, one for framing density, one for motion style. I keep mine as sidecar .xmp files next to the footage so anyone opening the project in Premiere or DaVinci can load them instantly. Having 10 Pinterest links doesn't help. It creates analysis paralysis. Define the lens language. Tell people whether anamorphic flares are welcome or forbidden. Specify prime versus zoom preferences for different scenes. I learned this the hard way on a wedding video project where the lead shooter used a 24-70mm f/2.8 for almost everything and the second unit had been told to go for "cinematic bokeh" with a 85mm. The final product looked like two different filmmakers shot it. After that, every handbook I write includes a lens assignment table with minimum and maximum focal lengths per shot type.
Audio section matters more than people expect. Specify mic types for dialogue scenes, ambient recording requirements, and whether you want room tone captured at every location change. A lot of videographers treat audio as an afterthought and then spend four hours in post trying to fix inconsistent background noise. It takes 20 extra minutes on set to record proper room tone. The difference in post-production time is enormous.
The parts nobody writes down but should
Your style guide needs a section on what to avoid. Blank space, silence between takes, unblacked lenses, expired media cards. I used to think this was obvious. Then I reviewed a project where the client rejected 40 percent of the coverage because the director kept leaving black frames between shots thinking they were "atmospheric." They weren't. They were accidental. Writing down the boundaries saves more time than writing down the aspirations. Also include a metadata standard. Camera names, scene codes, take numbering, file naming conventions. This sounds tedious until you're hunting for a specific clip across five drives and three hard drives labeled differently. My current standard is: ProjectID_Scene_Take_Camera.mp4. Simple. Scannable. Searchable. Frame rate rules deserve their own section too. Don't just say " shoot in 24fps." Say when to deviate. When do you go to 60fps for slow motion? When is 30fps acceptable? I worked on a product commercial where the client shot the hero shot at 24fps but the cutaway B-roll at 60fps, then wanted it all slowed down in post. The result was a jarring speed mismatch that no amount of optical flow could fix cleanly. The workaround I now insist on: any footage intended for slow motion gets flagged at the top of the log sheet during the shoot.
Where style guides break down
A Style Guide For Videography Handbook does not solve poor communication. If the person writing it never spoke to the DP or the editor, the document will contain rules that are technically correct but practically impossible. I've seen handbooks that specify T-stop consistency across lenses when the production was using zoom lenses with variable T-stops. The rule was pointless. They also create a false sense of security. Teams tend to assume that having a style guide means creative problems are solved. They're not. A style guide reduces ambiguity. It doesn't remove the need for creative decision-making on set. If anything, it shifts that pressure slightly earlier in the process, which is usually a good thing, but not everyone handles pre-production decisions well. For very small productions with budgets under ten thousand dollars, a full handbook is overkill. A one-page shooting brief covering format, deliverables, and three visual references does the same job with less friction. The handbook format scales best for projects involving multiple shooters, post teams in different time zones, or clients who want review rounds before final delivery.
Practical steps to get started this week
Open a single document. Fill in the deliverables table first. Then paste your three reference images. Add the lens assignment table. Write the audio requirements. List the metadata convention. Add the avoid section. That's it. You now have a working style guide. Refine it on the next project. Don't try to make the first one perfect. The first version of any handbook is always wrong in ways you only discover after the shoot ends.
