Why Setup Decides the Cross-Examination
Photographic evidence is rarely attacked head-on. Nobody argues the water damage is not in the picture. The attack goes after the record around the picture: the camera clock that disagrees with the field notes, the missing originals, the hash log that exists only on the photographer's own laptop. Every one of those weaknesses is created, or prevented, before and immediately after the shoot. None of them can be repaired later.
This checklist collects the setup decisions that matter. It is written for photographers doing documentation work for legal cases, insurers, authorities or scientific studies, and it assumes ordinary professional equipment. Our chain of custody guide covers the full path from capture to courtroom; this article is about the part you control at the camera and the card.
One note before the list. The requirements that actually bind you come from the people running the case. Ask the attorneys or the study lead what they need from the photographs, ideally in writing, before the first shoot. That protects the work and it protects you.
Clock, Date and Time Zone
Set the camera's date, time and time zone before every shoot, against a reliable reference such as a network-synced phone. All three matter. A correct time in the wrong time zone puts your files hours away from your field notes, and inconsistent camera clocks are among the easiest targets in cross-examination, because they require no expertise to exploit. A questioner does not need to understand hashing to ask why the camera says 14:03 and the sampling log says 09:03.
If you shoot with more than one body, synchronize them to each other as well, so a sequence assembled from both cameras stays in order. Recheck after travel across time zones, after daylight saving changes, and after any battery removal long enough to reset the clock. Write the reference you synced against into your field notes; a one-line entry closes the question before it is asked.
The camera clock never becomes proof by itself. It becomes consistent with proof, which is what testimony needs.
Record RAW Plus JPEG
Set the camera to record RAW and JPEG together. The RAW file is the sensor's record and the anchor for any later forensic comparison; the JPEG is the working file that gets viewed, shared and eventually delivered. Keeping both from the moment of capture means every delivered image can be traced back to sensor data, which is the basis of RAW verification.
Keep the originals as originals. Cull and edit on copies, never in place, and preserve the full take, including the frames that did not work. A gap in the numbering invites the question of what was in the missing frames; the boring answer, that they are all preserved and available, is only possible if they are.
Color Reference and In-Camera Processing
For documentation work, photograph a color reference at the start of each setup: a gray card or a color checker in the scene, under the light you are working in. It gives any later viewer an objective anchor for what the colors were, and it gives you a defensible basis for white balance.
A common worry is whether adjusting camera settings compromises the originals. It does not. White balance, a custom color temperature measured from a gray card, picture styles and similar settings are in-camera processing. The JPEGs the camera writes with those settings are still camera originals, produced by the manufacturer's firmware at capture time, and they verify cleanly against their RAW. What matters is the line between processing settings applied at capture and content edits applied afterwards.
Card Handling After the Shoot
When the shoot ends, flip the card's write-protect switch before the card leaves the camera bag workflow. The switch does not make the files immutable, no mechanism on a memory card does, but it prevents accidental writes from cameras and readers, and it marks a clean boundary in your handling record: from this point, the card was read-only.
Only SD cards carry that physical switch; CFexpress and CompactFlash cards have none. For those, the same boundary is drawn procedurally: offload the card, then retire it straight into labeled storage and note the time, so nothing writes to it after the backup.
Use a fresh card per case or per shoot day where the work justifies it, and do not reuse cards from an open matter until it is closed. A card that still holds the original files, offloaded and write-protected, is the closest thing to a sealed original that digital photography has.
Offload and Anchor the Same Day
Back up the card the same day with a professional transfer tool such as OffShoot, Silverstack or ShotPut Pro. These tools copy the card and write a manifest, a checksum list of every file, which is the document your whole chain of custody hangs on. Two settings matter: verify-after-copy stays on, and the checksum type is set to C4, the one option that can bind file contents. The checksum settings guide explains why the default is not enough.
Then give the manifest a date that does not depend on you: upload it to Lumethic Offloads, which has it countersigned by an independent timestamp authority. The receipt states that every file on the card existed, exactly as it is, no later than that day. This is the step that converts good habits into checkable proof, because a hash list on your own disk carries your date, and an anchored manifest carries a third party's. The reasoning is laid out in how to prove a photo existed on a certain date.
Done the same day, the provable date of the files is the shoot date itself, which is exactly the claim documentation work needs.
Field Notes That Match the Files
Keep a simple log per shoot: location, subject, start and end times, cards used, the clock reference you synced against, and the time of the offload. The times in the notes must be reconcilable with the times in the files; that agreement, across independent records, is what makes testimony solid.
Frame-level annotation is rarely required, and this is worth knowing because it changes what a shoot costs. The offload receipt covers every frame on the card at once. Detailed attention concentrates on the selects later: the frames that go to the legal team, into the report, or become exhibits are the ones that get individually verified against their RAW. Dozens to a few hundred images per case is typical, not thousands. The legal evidence workflow shows that full path.
What This Checklist Does Not Do
Photographs are normally admitted because the photographer testifies that they show what they claim to show. Nothing here replaces that testimony. What the setup does is remove the standard ways of attacking it: the clock objection is answered by the sync habit, the fabrication objection by the anchored manifest, the manipulation objection by RAW verification of the selects. The testimony stays; the record around it stops being the weak point.
Setup FAQ
Does setting a custom white balance make my JPEGs less authentic? No. A custom color temperature set in the camera is in-camera processing. The resulting JPEGs are camera originals and verify against the RAW like any others.
Do I need a forensic camera or special hardware? No. Ordinary professional cameras are fine. What makes the work defensible is the discipline around clocks, originals, offloads and anchoring, not special capture hardware.
What if I forgot to sync the clock before a shoot? Record the offset as soon as you notice: photograph a reliable clock with the camera, note the difference, and keep that note with the shoot records. A known, documented offset is a footnote; an unexplained one is a cross-examination topic.
Can I use tethered capture instead of cards? Tethering works and pairs well with this checklist; writing to card and laptop simultaneously gives you two originals whose hashes should match. Treat the manifest of whichever copy is offloaded as the record to anchor.
How fast after the shoot should the offload happen? Same day. The anchor date is the earliest date you can ever prove for the files, so every day between shoot and anchor is a day the record cannot cover.
