Camera card offload guide
What belongs in a camera card offload receipt
A useful offload receipt lets another person answer four questions: what was expected, where it was copied, which bytes matched and which promises were deliberately not made.
Identify the source inventory
Include the confirmed source name, source-volume identity, inventory timestamp, regular-file count, total bytes, relative paths and SHA-256 values. Record skipped symbolic links instead of silently following them.
Identify both destination volumes
Record a stable volume identifier and human-readable name for each destination, plus the product-owned job folder. This makes it clear whether the claimed copies were actually on different volumes.
Keep outcomes at file level
List the source hash, destination hash and state for every expected relative path at both destinations. Verified, resumed, missing, mismatched, failed and source-changed outcomes should remain distinguishable.
Make the overall state mechanical
Mark the receipt VERIFIED only when the final source sweep passes and every expected file matches at both destinations. If either side is partial, the top-level result must say NOT VERIFIED.
Export human and machine evidence
Pair a readable PDF or Markdown handoff with structured JSON and a portable manifest. Hash the generated artifacts too, and state plainly that the receipt does not erase the card, provide cloud backup or guarantee hardware health.