Why you need a reference document before you ever pick up a camera
A style guide for photography isn't some artistic manifesto you write once and frame. It is a living technical document that exists between your vision and the people who execute it. Most photographers I talk to skip this step because they want to just shoot. Then three months later they are confused why their client or their own future self keeps misremembering what was agreed upon. The cheat sheet version is smaller, denser, and meant to be printed or pinned next to your monitor during a session. I built my first actual cheat sheet around 2016 after a corporate headshot job went sideways because the retoucher treated skin smoothing as optional. The client was furious. I had never written anything down about that specifically. From that point forward, every project got a one-page reference that covered exposure targets, color direction, retouching levels, and output format. Not the whole mood board. Just the stuff that gets missed.
Style Guide For Photography Cheat Sheet
Here is how I structure mine now. It takes about twenty minutes to produce and saves you roughly two hours in post and revision rounds. The Style Guide For Photography Cheat Sheet is a condensed technical brief. It captures exposure strategy, color grading direction, lighting ratios, wardrobe notes, retouching standards, file delivery specs, and any client-specific quirks that you learned the hard way. It lives at roughly one page. Larger guides exist. They are helpful during pre-production but nobody reads them on set. Beginners often conflate a mood board with a style guide. A mood board tells you what something should feel like. A style guide tells you what settings, decisions, and deliverables to use. They serve different purposes and you should not try to merge them into one document.
How I build one before a shoot
First, I gather anything from the client or art director: reference images, brand guidelines, previous deliverables, and shot lists. Then I strip away everything that is decorative. What remains gets categorized into five sections. Exposure and dynamic range targets. I note where the histogram should sit, whether highlights are blown intentionally, and what ISO ceiling is acceptable. For example, a fashion editorial might allow clipped whites on specular highlights while a product shoot requires shadow detail all the way to the sensors' noise floor. Color direction. This includes white balance intent, saturation levels per skin tone or object category, and any specific LUT or grading preset if one already exists. I also write the target color space. Rec.709 for video. Adobe RGB or ProPhoto RGB for print. sRGB only when the client explicitly requests web delivery.
Get the Full Details

Lighting ratio and quality notes. I do not draw diagrams anymore. I write numbers. Key to fill ratio in stops. Hard or soft source. Flagging expectations. If a shoot uses a specific modifier like an OCTA or grid, I name it so the assistant can replicate it the next day without guessing. Retouching and post standards. This is where most breakdowns happen. I specify skin treatment level, whether textures stay, frequency separation expectations, dent removal on products, background replacement tolerance, and what counts as a final deliverable versus a work-in-progress. I also include the file naming convention because people ignore that until the archive is a mess. Output and delivery specs. Resolution targets, compression levels, web sizing, print bleed requirements, and turn-around time. I add the format: RAW + JPEG, or TIFF only, or both with embedded ICC profiles.
A specific edge case that taught me to add sensor data
About two years ago I shot a low-light restaurant campaign on the Sony A7S III at base ISO 800. The client approved the look quickly. Six months later they asked for a different color grade on the same footage. I pulled the original files and realized I had no note about how much grain I intentionallyed versus how much came from the sensor. The new grade introduced more luminance noise and ruined the texture they liked. I lost a revision round and had to reschedule because re-creating that exact low-key setup cost more than I wanted to absorb. After that, I started adding a small field to the cheat sheet for every shoot that documents the camera body, lens lineup, ISO target, and any in-camera grain or noise settings I planned to lean into. Now my team knows whether grain is creative or accidental before we even open Lightroom.
Common pitfalls I see constantly
Pitfall one: writing everything instead of choosing what matters. People paste their entire creative brief into the cheat sheet. It becomes unreadable and nobody checks it. The cheat sheet should be the opposite. It should contain only the decisions that have already been made and the ones that need to stay consistent across the timeline. Pitfall two: treating it as static. If something changes on set, update the document. I keep a live version open on a second monitor and annotate it with quick asterisks when we deviate. Otherwise you end up delivering files that do not match the guide you signed off on. Pitfall three: ignoring the retoucher or editor in the creation process. A style guide written entirely by the photographer often misses post-production reality. A good cheat sheet is co-authored with whoever handles color and retouching. If you skip that, you will get feedback that contradicts your intention and spend money fixing it later.

What a finished cheat sheet looks like in practice
Here is a typical layout for a commercial portrait session: Project name and date. Camera body and lens list. Key light: 1/4 power Octa, 5600K, ratio 3:1 key to fill. Fill: large silk bounce, no additional fill light. ISO 200. Target highlight clipping: none. Shadow lift: +0.3 in post only if needed. Color grade: warm midtones, neutral shadows, target Adobe RGB 1998. Skin retouching: frequency separation, texture above 50 percent on face, blemish removal only. Product retouching: dust removal, no shape distortion beyond 2 percent. File naming: Client_Firstname_Lastname_Date_V1. Delivery: 300 DPI TIFFs plus web JPEGs at 1800px long edge. Turnaround: 5 business days. That is roughly seventy words. You could fit it on a index card.
When a cheat sheet fails you
They are not a silver bullet. If your project involves dozens of stakeholders, rapid creative pivots, or an unpredictable location, a single page becomes insufficient. In those cases, keep the cheat sheet as the primary reference but attach a secondary document that covers shot-by-shot callouts and contingency plans. Also, the cheat sheet assumes you have time to write it. On a same-day gig with a rushed turnaround, you may not. In that scenario, I fall back to a verbal confirmation and an email summary sent before the shutter fires. That summary becomes the cheat sheet after the fact. Send the cheat sheet to your team three days before the shoot. Include a one-line note explaining what each section covers. Keep the file in a shared cloud folder with version control enabled. If you work in StudioBinder or ShotLister, you can export the cheat sheet directly. If you use Google Docs or Notion, export to PDF and name it with the date. Do not send it as an attachment inside a chain of emails. It gets lost. I also print a physical copy for the assistant. Screens crack. Batteries die. Paper does not require charging.
Download option
There is no single downloadable file I control here because the format changes depending on your workflow. What I recommend is building a base template and duplicating it per project. I use a simple table structure in Google Sheets with columns for section, target value, notes, and revision history. You can copy that structure into Notion, Adobe Illustrator, or a plain text editor. The important part is consistency, not the tool. If you want a ready-made starter, I keep a minimal template on my site that includes the five sections I listed earlier plus a revision log. It is free and updates occasionally when I find gaps in the original version.

Why this matters beyond client work
Even if you shoot purely for yourself, a cheat sheet forces you to make decisions before you are in the environment. Most bad outcomes happen under pressure. When you pre-decide exposure targets, color intent, and post standards, you remove guesswork from the moment. That alone is the primary value. Everything else is a side benefit.