Identify the batch
- Production, date, unit, camera, operator, and offload batch have unique identifiers.
- Every source card identifier is recorded before copying starts.
- The expected file count and used capacity are captured when the software can report them.
Confirm destination roles
- Copy A and Copy B are different physical devices, not folders or partitions on one drive.
- Each drive has sufficient free space for the complete batch before the job begins.
- Destination labels, folder paths, and responsible operator are written into the record.
Record the copy job
- Application name, version, start time, end time, and copy mode are retained.
- Interrupted jobs, duplicate names, read errors, or destination warnings are documented.
- No source card is modified, formatted, or renamed during the controlled copy stage.
Capture verification evidence
- The method states whether it used counts, inline hashes, destination re-read, or a saved manifest.
- Each required destination has an explicit pass or exception result.
- Manifests and reports are stored with a path that remains understandable after the field handoff.
Release and separate
- Both destinations eject cleanly after all pending writes finish.
- Independent copies move to separate bags, locations, or custody when the plan requires it.
- The source card's release condition and release time are signed or logged before formatting.
Use the checklist with calculations
The checklist does not estimate quantities or duration. Use the Memory Card Quantity Planner before packing, the Media Offload Time Planner to reserve the copy window, and the Memory Card Rotation Planner to test whether the release rule is supported by the available card pool.