Identify every delivered artifact
List the relative path, stable identifier, format, size, and relevant record or page count for each file. Include checksums when agreed so the receiver can verify transfer integrity. Separate source artifacts from derived text, labels, and documentation rather than making the buyer infer their roles from filenames.
Explain relationships and versions
Document which annotation file belongs to which document, which table keys connect exports, and which release supersedes an earlier batch. A predictable directory structure helps, but a machine-readable manifest makes those relationships explicit. Record withdrawn or replaced items so incremental updates do not create ambiguous duplicate records.
Include coverage and exception summaries
Provide counts by document type, source period, language, or other agreed dimensions. List known missing artifacts, unreadable pages, unresolved labels, and excluded records separately. A delivery summary should describe what is present and uncertain, without presenting completed processing as confirmation that every source is suitable for every use.
Reconcile against acceptance criteria
Compare manifest totals with the sampling plan and inspect representative linked artifacts. Check that identifiers resolve and that documentation matches the actual fields. Discuss these expectations with Fiund at the briefing stage so prospective source and delivery plans can be reviewed against a shared, concrete definition of completeness. Run a reconciliation on one document bundle: locate the original file, its extracted text, the label file, and the associated coverage entry. Check that each identifier agrees and that the manifest points to the delivered revision. This small trace can expose packaging problems that aggregate file counts alone cannot reveal.
Review checklist
- List files with stable identifiers
- Map source and derived artifacts
- Summarize coverage and exceptions
- Reconcile totals with agreed scope