Operations & Systems

A File Delivery Manifest: Find Missing and Extra Files Before Accepting a Handoff

Six files are expected. Six files arrive. The receiver marks the delivery complete.

One diagram is missing. An unapproved draft occupies its place in the count. Another document has a different name.

A file delivery manifest makes those differences visible. Agree on the package inventory before transfer. Compare the expected relative paths with the received relative paths. Give every exception an owner before recording acceptance.

The worksheet below adapts an inventory principle from RFC 8493, the BagIt File Packaging Format, version 1.0. It is a lightweight business worksheet, not a conforming BagIt package. The examples are fictional and propose no particular software purchase.

Agree on the Package Boundary

Name the thing being delivered before listing its files. A package might contain one documentation release, one approved research submission, or one set of export files.

Record a package identifier and version. Give the package a root directory so paths have one reference point. State whether the inventory describes extracted files or the transfer archive itself.

For example, docs-17-v1/ can be the root. The manifest then records procedures/intake.md rather than a sender's full computer path. A receiver can find the same relative path under a different download location.

Write the included scope and exclusions in the package heading. Identify the delivery owner who proposes the inventory and the receiving owner who agrees to it. Keep approval of the list separate from acceptance of the delivered work.

Package heading Entry to agree
Package identifier and version Stable identifier plus a specific release version
Root and inventory stage Directory root; before packaging or after extraction
Purpose Task the receiving team will use these files for
Included scope Named outputs and supporting files
Exclusions Material deliberately outside this delivery
Delivery owner Person responsible for assembling the package
Inventory approver Person authorized to agree to the expected list
Receiving owner Person who reconciles the received package
Acceptance authority Person authorized to accept the business deliverable

The same person can fill several roles. Record each responsibility anyway. A person checking filenames does not automatically have authority to accept the underlying work.

Build the Expected Inventory Before Sending

Use one row per expected file. Record the relative path, version, expected byte size, and the reason the file belongs in the package.

If an expected size is unknown, leave it unknown. Resolve it before claiming a measured size comparison. Do not type a plausible number to complete the table.

Agree on path spelling, directory structure, and extensions. For this worksheet, compare exact relative path strings. Record any proposed mapping separately when a name differs. This rule keeps the first comparison reproducible without guessing what the sender meant.

RFC 8493, section 2.1.3, requires a payload manifest to list each payload file exactly once with its checksum. This worksheet borrows the explicit inventory idea. It adds business roles and review decisions, while leaving BagIt conformance outside scope.

Choose a location for the worksheet outside the counted payload, or explicitly include it. State that decision in the heading. Otherwise two receivers can disagree because one counts the inventory document and the other excludes it.

For the example below, the inventory and receipt are outside the six-file payload. Working drafts and earlier releases are excluded. The receiver preserves the package as received while reviewing it.

Set Up a Fictional Six-File Handoff

Suppose a fictional documentation team submits package DOC-17, version one, for a supplier intake procedure. The approved inventory contains six files under docs-17-v1/.

Every path, version, size, and role in this example is synthetic. The sizes are illustrative byte counts, not measurements of actual PDFs or diagrams. They demonstrate reconciliation arithmetic only.

Expected relative path Version Expected bytes Purpose
README.md v1 840 Package guide
docs/overview.pdf v1 12,400 Reader overview
diagrams/intake.svg v1 2,300 Process diagram
procedures/intake.md v1 1,980 Operating procedure
registers/decisions.csv v1 560 Recorded decisions
templates/review.md v1 720 Review worksheet

The expected total is 18,800 bytes across six files. Keep that total as a quick comparison, with the individual paths as the governing inventory.

The receiving directory contains these six paths:

README.md                         840 bytes
docs/overview.pdf              12,400 bytes
procedures/intake-v1.md          1,980 bytes
registers/decisions.csv            560 bytes
templates/review.md                720 bytes
drafts/overview-notes.md         1,120 bytes

The received total is 17,620 bytes. The equal file counts conceal differences in membership. The unequal byte totals add another observation, but they do not identify which files are wrong.

The receiver has not yet checked whether any file opens correctly or contains suitable content. Those checks remain pending.

Reconcile the Two Sets Explicitly

Call the expected path set E and the received path set R. Compare their members before interpreting possible replacements.

Paths in both sets are exact path matches. Expected paths absent from R are missing. Received paths absent from E are unexpected.

Set result Paths
Exact path matches, four README.md; docs/overview.pdf; registers/decisions.csv; templates/review.md
Missing expected paths, two diagrams/intake.svg; procedures/intake.md
Unexpected received paths, two procedures/intake-v1.md; drafts/overview-notes.md

The first comparison therefore reports four matches, two missing paths, and two unexpected paths. Six expected and six received do not mean six matched.

The renamed procedure is a candidate explanation for one missing path and one unexpected path. It remains a candidate until the delivery owner confirms its identity and version. Equal sizes do not establish equal bytes or equivalent contents.

Ask the owner whether procedures/intake-v1.md is intended to satisfy procedures/intake.md. Retain both path strings in the receipt. If the owner confirms a rename, record the supporting version evidence and any required byte comparison separately.

Even after that mapping is accepted, the diagram remains absent and the draft remains outside scope. A rename explanation cannot resolve unrelated exceptions.

Avoid merging everything into a single folder before comparison. That can erase the directory distinctions the agreed inventory uses. Inspect the original package structure first.

Keep Four Checks Separate

Presence asks whether the agreed paths arrived. Byte integrity asks whether the corresponding files match approved reference bytes. Usability asks whether the receiving team can use the documents for their intended task. Business acceptance records an authorized decision about the deliverable.

RFC 8493, section 3, distinguishes a complete bag from a valid bag. Validity requires completeness and successful verification of its manifest checksums. Those technical terms do not establish business acceptance.

For this worksheet, give each check its own outcome:

Check Evidence to record Example limitation
Presence Expected and received path comparison A named file can contain the wrong version
Byte integrity Approved and observed digest comparison Matching bytes can preserve unsuitable content
Usability Receiver opens and inspects the required output A readable document can omit an agreed section
Business acceptance Authorized decision against agreed conditions An inventory checker may lack acceptance authority

Keep CSV row checks within a separate data review. Counting files does not reconcile records inside decisions.csv. Keep procedure training within the operations handover. This manifest verifies delivery membership.

Use the consulting deliverable acceptance criteria guide to define the evidence needed for acceptance. The manifest points to those conditions without replacing them.

Fill In the Delivery Receipt

Copy the agreed inventory into a receipt for the received package version. Add actual received paths, exception reasons, owners, and acceptance decisions. Preserve the original expectation.

Use this blank row structure. Put the comparison time and receiving root above the table.

Package version Expected path Received path Status Exception reason Owner Acceptance decision
[Identifier and version] [Agreed relative path or none] [Observed relative path or none] [Matched, missing, unexpected, or mapped] [Observed gap or none] [Confirmed person] [Pending, accepted, rejected, or held]

For DOC-17 version one, the initial receipt has eight reconciliation rows. Four rows pair exact matches. Two record missing expectations. Two record unexpected arrivals. Eight rows do not mean eight received files.

Package version Expected path Received path Status Exception reason Owner Acceptance decision
DOC-17 v1 README.md README.md Path matched Content review pending Receiver Pending
DOC-17 v1 docs/overview.pdf docs/overview.pdf Path matched Content review pending Receiver Pending
DOC-17 v1 diagrams/intake.svg None Missing Required diagram absent Delivery owner Held
DOC-17 v1 procedures/intake.md None Missing Possible rename unresolved Delivery owner Held
DOC-17 v1 registers/decisions.csv registers/decisions.csv Path matched Content review pending Receiver Pending
DOC-17 v1 templates/review.md templates/review.md Path matched Content review pending Receiver Pending
DOC-17 v1 None procedures/intake-v1.md Unexpected Possible renamed procedure Delivery owner Held
DOC-17 v1 None drafts/overview-notes.md Unexpected Working draft excluded Delivery owner Held

The role names stand in for confirmed people in a real receipt. Add a response date for each unresolved exception. Leave package acceptance held while required evidence is absent.

If the agreement permits partial acceptance, record its exact boundary. Accepting the four matched paths would still require their other checks. It would not accept the missing diagram or silently revise the scope.

Keep the Receipt Attached to Its Inventory Version

Give the agreed list its own version identifier. A receipt should name that identifier as well as the package version. This prevents a later list revision from changing the meaning of an earlier result.

Record the receiving root and the comparison stage. Checking paths inside an archive and checking an extracted folder are different observations. If extraction changes a name, retain both observations and ask the delivery owner to resolve the difference.

Do not treat the worksheet row order as file identity. Sort the two inventories for review if that helps. Keep the full relative paths in each row so sorting cannot detach a filename from its directory.

For unresolved mappings, record the proposed pair and its evidence. A similar title supplies a question for the owner. It does not authorize substituting one document for another.

Before signing the receipt, compare its listed version with the directory still under review. If another package arrives during review, start a separate receipt. Do not combine new files with earlier exceptions and call the mixture a release.

Resolve Exceptions Without Erasing the First Delivery

The delivery owner can supply a corrected package with a new version. Preserve version one's inventory and receipt so the reason for replacement remains visible.

In this fictional resolution, version two includes the missing diagram, uses the agreed procedure path, and excludes the draft. The receiver repeats the comparison against version two's agreed inventory. The old receipt stays attached to version one.

With the same six expected paths present, the new set comparison has six exact matches, zero missing paths, and zero unexpected paths. That result closes the membership exceptions. Integrity, usability, and acceptance still need their own evidence.

If the owner proposes changing the expected list instead, send that proposal to the inventory approver. Record why the changed scope is suitable. Never delete a missing row solely to make reconciliation pass.

An unresolved extra file also needs a decision. Keep it outside accepted scope until the owner explains its purpose. Preserve the original delivery evidence according to the team's retention rules.

A backup restore drill answers whether retained material can be recovered. This receipt answers which delivery version was reconciled and what the receiver found.

Agree on the list. Reconcile the paths. Record the decision.

Sources

Topic map: Spreadsheets, CSV files, and data handoffs

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Spreadsheets, CSV files, and data handoffs

Neighbor: Business reporting and statistics

Neighbor: Records, access, and continuity

Neighbor: APIs, webhooks, and automation