Getting Your Camera to Stop Making the Same Mistake Twice
Most people think a troubleshooting guide is just a list of symptoms and fixes. It's not. It's a decision tree that saves you from spending twenty minutes Googling a problem you've already solved once before. I keep one on my desk because I've lost count of the shoots where something broke that shouldn't have, and the only thing standing between me and a missed shot was having already written down what to check first. The first thing to understand is that a cheat sheet isn't a reference document. It's a field tool. If you format it like a textbook, nobody will look at it when they're standing in the dark trying to figure out why their camera won't output to an external recorder. Start with the problems you actually encounter, not the ones you might encounter someday. I organize mine by symptom, not by component. When your footage looks wrong, you don't start by thinking "maybe it's the SD card." You start by noticing the waveform is flat, or the focus is soft, or there's rolling shutter distortion. So your headings should be what you see, not what you touch. A section called "Image is too dark or clipped" gets used way more often than one called "Exposure settings incorrect."
Under each symptom, list the most likely cause first, then work your way down the probability chain. This matters because on a real shoot, you're not doing exhaustive diagnostics. You're checking the thing that's wrong 80 percent of the time, and if that's not it, moving to the next. I've seen people flip through troubleshooting guides in random order because the writer put the obscure causes at the top. That's not a guide. That's a novel nobody reads. Here's the part most people skip: include the workaround, not just the fix. Sometimes the real problem isn't solvable on location. A corrupted media card in the field means you move to backup storage and flag the session for later recovery. Writing that distinction down prevents panic. It also tells you when to stop troubleshooting and start surviving. The format needs to survive being glanced at under stress. One symptom, three causes maximum, one sentence per cause, one line for the fix. If a single entry runs longer than four lines, someone won't read it. I learned this the hard way when I wrote a forty-page troubleshooting document for a client and they used the three-page version I had scribbled on a napkin during setup instead. The napkin worked because it was dense and fast to scan. The document didn't, because density and detail aren't the same thing.
My current cheat sheet lives on a laminated card in my bag and as a note on my phone. The phone version is the one I actually use mid-shoot because I can search it. The laminated card is for when my phone dies or I'm wearing gloves. Both contain the same core entries, but the laminated one has the bigger text and fewer entries. I stripped it down to about thirty-five items. Anything beyond that and the card becomes background noise.
Get the Full Details
Common Entry Structure That Doesn't Waste Your Time
Each entry follows the same pattern without variation. Symptom first. Then a numbered list of probable causes in order of likelihood. Then the fix or workaround. No intros, no context paragraphs, no "you may also want to consider." If something is worth including, it earns its place. If it doesn't fit the pattern, it probably doesn't belong in the sheet. Sometimes I add a small note next to entries that are known issues with specific gear. For example, the Blackmagic 6K Pro has a known firmware bug where the HDMI output drops intermittently when recording to internal CFast cards at high bitrates. I have an entry for "HDMI signal cuts out during recording" that references this specifically. Without that note, a technician might spend twenty minutes checking cables and adapters before finding the real cause. With it, they check the firmware version in thirty seconds.
What Most Guides Get Wrong About Audio Issues
Audio troubleshooting gets treated like an afterthought in most guides I've seen. The entries are vague, the causes are generic, and nobody mentions the stuff that actually breaks on set. I had a shoot last year where the entire audio track came back with a 60Hz hum that was present on both channels. We checked the mic, the preamp, the cables, the ground lift, everything. Turns out the camera was being powered through a different circuit than the lighting rig, and the phase difference was coupling into the XLR inputs. The fix was plugging everything into the same strip or using a ground loop isolator. That problem never shows up in a generic audio guide because it's specific to how venues are wired, not how equipment works. This is the kind of thing that belongs in a real cheat sheet. Not "check your connections" but the actual scenario that produces the symptom and what to try when the obvious checks don't resolve it. I organize these edge cases in a separate section at the back of the sheet, marked with a small symbol so they're easy to skip past when you're in a hurry.
Focus and Exposure Problems Are Where People Waste the Most Time
These two categories account for roughly half the troubleshooting calls I get. Focus issues usually come down to one of three things: the focus assist is set wrong, the lens calibration is off, or the subject contrast is too low for the AF system to lock. Everyone checks the first two. Almost nobody checks the third until they've already replaced a focusing motor that wasn't broken. For exposure, the most common mistake is assuming the histogram is lying when it isn't. A log profile will always look flat and dark on the LCD. Technicians often boost exposure to compensate, which blows out the highlights before they realize what happened. The workaround is simple: trust the histogram and the false color overlay, not the screen brightness. I put this as the second cause under "Image looks overexposed on playback" because it happens constantly. Second cause, not first, because sometimes the meter really is just wrong and you do need to adjust. Rolling shutter is another one people don't know how to diagnose quickly. The symptom is skewed vertical lines or wobble on fast camera movements. The cause is either the electronic shutter speed being too high for the scene, or the scan rate of the sensor itself. I've seen people try to fix this in post with warp stabilizer when the real solution is changing the shutter angle or using a global shutter camera. The cheat sheet entry needs to make that distinction clear because the fix depends entirely on which cause you're dealing with.
Storage and File Corruption Entries Need Exact Error Codes
Generic entries about file corruption are useless. "Check your card" doesn't help anyone. I list the specific error messages cameras produce and what they actually mean. Canon's "CFE01" is a card write protection issue. Sony's "C:ERROR" on an XDCAM card usually means the file system is corrupted, not the card itself. Different manufacturers use the same error numbers for different problems, which is why you need to keep this section updated as you encounter new cameras. I also include the recovery steps that actually work. Most guides suggest running some Windows disk utility. That rarely recovers footage. The practical steps are: stop writing to the card immediately, clone it with a tool like ddrescue or Recover My Files, and work from the clone. If the camera keeps throwing errors on the original, move to a different card format or medium entirely rather than trying to fix the failed one on set.
Where the Cheat Sheet Falls Apart
Let me be blunt about what this doesn't solve. A troubleshooting guide won't help with problems that require diagnostic equipment. If your lens has internal element misalignment, no amount of reading a sheet is going to tell you that. You need a test chart and a technician with a collimator. The sheet can tell you the symptoms of lens misalignment, but it can't confirm it in the field. It also doesn't help with intermittent problems that only appear under specific conditions. I had a camera that would drop frames only when the battery was below 30 percent and the ambient temperature was above 28 degrees Celsius. That's not something a general guide covers. The workaround for those situations is repetition and documentation. Every time you encounter a new edge case, add it. The guide gets better with use, but only if you actually maintain it. Most people write one and never touch it again. Another limitation is that the guide assumes a certain level of technical literacy. If someone on your team doesn't know what a waveform monitor is or how to read false color, the entries about exposure diagnosis will be incomprehensible to them. I've addressed this by adding a glossary section at the front, but the real solution is training. A cheat sheet supplements skill, it doesn't replace it.
Finally, these sheets become outdated fast. Camera firmware updates change behavior. New lenses introduce new focus quirks. Sensor technologies evolve. My current sheet is on version twelve, and roughly a third of the entries have been modified in the last year alone. If you're not willing to maintain it, write a shorter one that covers only the problems you see today and accept that it will become less useful over time. A stale guide is worse than no guide because it gives false confidence.
What to Include When You're Starting From Scratch
If you're building your first version, start with these categories and fill in the details as you go. Image quality problems: dark footage, overexposed footage, color shifts, noise patterns, banding, rolling shutter. Audio problems: hum and buzz, dropout on one channel, clipping, wind noise, RF interference. Connectivity issues: HDMI output failure, USB streaming problems, SD card read errors, timecode sync loss. Focus problems: hunting, soft focus, incorrect subject selection, focus breathing complaints. Power issues: unexpected shutdown, battery drain faster than rated, charging port problems. Playback and file problems: corrupted files, missing media, frame rate mismatch, dropped frames. That's roughly forty entries covering the problems that show up on about ninety percent of professional shoots. Everything else goes in the edge cases section. When you're writing each entry, ask yourself whether a person standing in front of a broken camera at 6 AM would find this useful. If the answer is no, rewrite it or cut it. The only thing worse than a missing entry is a useless one. I keep this document updated in a shared drive so anyone on my crew can access it, but I also maintain a personal copy with my own annotations and recent additions. The shared version stays clean and standardized. The personal version accumulates the messy details that came from actual shoot experience. They serve different purposes, and keeping them separate prevents confusion when someone pulls up the wrong one at the wrong time.
The best troubleshooting guides are the ones that get used until they fall apart. If yours is still in pristine condition six months after you finish it, you're not using it correctly.
