Delivery preparation
Make the release unambiguous.
A file list should tell the next person which edition to use, what remains open and what they need to accept.
Before you send
- Identify the exact files and version labels you intend to deliver.
- Resolve missing metadata, repeated rows and competing versions of the same file name.
- Confirm the intended recipient, purpose and permission to share.
- Carry source references and unresolved questions with the release.
- Agree how the recipient confirms receipt and what review establishes acceptance.
A made-up metadata example
These are invented file names and recipients. No files are uploaded, inspected or delivered by this page.
| File name | Version label | Intended recipient | Question |
|---|---|---|---|
| working-note.txt | v1 | Project reviewer | Is this the intended release? |
| working-note.txt | v2 | Project reviewer | Resolve the competing label; no preferred edition is inferred. |
| source-list.csv | Not supplied | Project reviewer | Name the edition before handoff. |
Sent, received and accepted are different
- Sent
- You dispatched a defined release by the agreed channel.
- Received
- The intended recipient confirms the files arrived and can be opened.
- Accepted
- The agreed review or acceptance question has been answered by the responsible person.
The worksheet records none of those events automatically. Its CSV contains your raw metadata and diagnostics; it is not a receipt or a completion certificate.
Keep the service relationship
Use Landman Review to compare supplied readings. For a project issue, prepare a note at Landman Support. A research or delivery scope belongs with Landman Services.