A wedding day is one of the least forgiving environments in the industry: several cameras rolling at once, narrow windows between getting-ready, ceremony and reception to swap and offload cards, and zero possibility of a reshoot if something goes wrong. Here's a protocol that holds up under that pressure.
A practical protocol
- Label and number your cards ahead of time. On a multi-camera day it's easy to lose track of which card came from which body — a simple numbering scheme means nothing gets skipped or offloaded twice by mistake.
- Offload the moment a card comes off the camera, not in a batch at the end of the day. A card sitting in a pocket for six hours is six hours where it can be lost, dropped, or run through a washing machine with the rest of the outfit.
- Never reformat a card in-camera until you have at least two verified copies. "Copied" and "verified" are different things — see our guide on checksum verification for why that distinction matters.
- Keep the destination structure identical every time. At 2am with a rough cut due, nobody wants to guess which folder has the ceremony audio from camera B.
The real bottleneck isn't the copying — it's the attention it demands
The actual data transfer isn't usually the slow part; watching over it is. Standing next to a laptop babysitting a progress bar between the ceremony and the reception is time not spent shooting, and stepping away to shoot means either delaying the offload or hoping nothing goes wrong unattended.
Where an "arm and leave" workflow fits: arm the project once before the day starts, and every card handed to you afterward — from any camera — gets recognized, copied, verified and ejected on its own, while you're back out shooting or an editor is already cutting the footage that landed ten minutes ago. That's the specific situation ShotGrab was built around: a multi-camera day with live editing already underway, where stopping to manually import a card is the moment things get missed.