Use one identifier for the exact release
Assign a release such as inspection-2026-10-v1 and a cutoff date. List the included assets and exclusions. Keep the review documents separate from the transferable package when they contain confidential agreements or personal details. Confirm that the delivered collection matches the approved scope before preparing the transfer.
List files and explain the schema
For each file, record its relative path, media type, byte count, and record or asset count. State whether row counts include a header. For each field, document meaning, type, units, allowed values, and missing-value rules. Record text encoding and date/time conventions. A field called size without a unit or reference object is not a complete schema.
Document joins and version relationships
Show which keys connect files to labels, captions, product variants, or source groups. Record duplicate keys and unmatched references as counts with a denominator. State whether identifiers persist between releases and how removed records appear in later updates. If files are split into shards, include the expected shard count and order only when order matters.
Compute checksums from the final bytes
Generate a SHA-256 checksum after the files stop changing; record the algorithm alongside each value. Have the recipient recompute it after transfer. Matching hashes help check byte integrity, but do not establish accuracy, lawful use, ownership, or safety. Keep the manifest available through an agreed trusted channel; do not treat a checksum in an untrusted package as authentication.
Run a small rehearsal before handoff
Extract an archive into an empty location, open a sample from each file type, and run the intended schema and join checks. Compare actual counts with the manifest. Agree the transfer method, named recipients, expiration of temporary access, and how to acknowledge receipt. Credentials belong in an appropriate secret-sharing channel, never in the manifest.
Define the correction boundary
Record who receives discrepancy reports and the review date. A corrected file should have a new version and checksum plus a short change note; do not silently replace bytes under the same release identifier. Specify whether the proposal concerns a one-time snapshot or future updates. This manifest documents delivery and does not itself create acceptance terms or a license.
| File | Count definition | Companion documentation |
|---|---|---|
| images/part-001.png | 1 image; byte count measured after export | Image metadata and SHA-256 value |
| labels.csv | Data rows excluding header | Field dictionary; image_id join rule |
| README.txt | Release notes | Exclusions, checks performed, correction contact |
Delivery manifest worksheet
Edit this outline, then copy or download it. It stays in this page and is not submitted or saved by this tool. Keep confidential records and personal information out. Save your work before leaving or reloading.
You can select and copy the text manually. This is a preparation worksheet, not a legal agreement.