Dataset preparation

Dataset delivery manifests: a checklist

A delivery manifest explains what a defined package contains. It can help identify missing or changed files, but it does not establish that a transfer is authorised.

Last checked

Plan the package description first. Integrity checks, security arrangements and permission to transfer are different decisions.

Define the package without sending it

An initial licensing discussion should not begin with an archive attachment. First describe the broad material and the questions that need review. A manifest becomes useful when an authorised team needs to identify a particular package consistently, not as a reason to send real records earlier.

Our suggested planning sheet records the proposed package identity, responsible team, covered period and intended purpose. Keep its status explicit: proposed, checked or approved for a defined action. Do not let a technically complete file list imply that legal, commercial or security decisions have already been made.

Use the buyer due-diligence guide for the separate question of who is asking for access. This article deals with package description, not the selection of a buyer or the terms of a licence.

Understand what a checksum can prove

The BagIt format described in RFC 8493 uses manifests that associate file paths with checksums. This provides a concrete example of packaging information used to check file integrity. The RFC is informational, not an IETF standards-track requirement, and adopting BagIt is not a prerequisite for an enquiry.

A matching checksum can support a check that bytes match a particular reference. It does not prove that the content is correct, anonymous, owned by the sender or permitted for the intended use. Those questions need their own evidence and review.

If a technical team uses checksums, ask it to record the algorithm and the reference manifest being compared. A result labelled passed without the relevant package identity is difficult for another person to interpret later.

Connect files to their explanation

A file list should distinguish records from supporting documentation. Identify the data dictionary, selection notes, version history and any processing explanation associated with the package. Check that these describe the same version rather than a nearby export with a similar filename.

Our practical checklist includes:

  • Package identifier and covered collection period.
  • File roles, formats and counts using an explained method.
  • The dictionary and processing notes for this version.
  • Expected relationships between files.
  • Known exclusions and unresolved checks.

Keep filenames suitable for the approved audience. They can contain personal names, customer references or internal project details even when a file's visible content appears innocuous. Do not circulate a real manifest externally before that disclosure has been reviewed.

Check that the package matches the intended scope

Ask an authorised colleague to compare the proposed package boundary with the written scope. Are backup copies, temporary exports, logs or unrelated attachments included? Does a documentation link lead to a broader private folder? A tidy archive can still contain more than the intended collection.

Record whether counts refer to files, rows, observations or distinct entities. Compression changes file size, not the number of independent examples. Keep excluded material and the reason for exclusion understandable without placing that material into a new distribution folder.

The dataset versioning guide explains how to identify revisions. If files change after a manifest is produced, have the package and its checks reviewed again rather than retaining a receipt that refers to an earlier state.

Leave transfer approval as a separate step

Any eventual transfer needs agreed recipients, purpose, access controls and handling arrangements, alongside the relevant rights and commercial review. A manifest is supporting documentation for that process. It is not a substitute for it, and this guide does not recommend a particular transfer service.

Do not create public links or upload records to demonstrate readiness. An initial Fairlode description can say that the collection can be inventoried, that versions are identifiable and that certain checks remain outstanding. Use an invented outline if an example is helpful.

Fairlode starts with descriptions only. Preparing a package plan does not establish a buyer, an offer or permission to disclose files. The immediate goal is a clear account of the material and the decisions still needed before any access could be considered.

General information, not legal advice, a valuation or a buyer offer. Illustrative examples are not customer case studies.

Sources and further reading

Sources checked 16 November 2026. Historical research is background, not evidence of current buyer demand.

Put the questions into practice.

Start with a description. No files, customer records or source code.

Describe your recordsBack to the blog →