A handoff should give the next organisation enough context to use and challenge the material account without opening the sender's entire workspace. Selection and approval are part of the record.
Define the recipient's decision
Ask whether the recipient needs to verify the delivered lot, assess a specification, continue traceability or investigate an exception. Include the lot identity, relevant quantity and units, transformation links and the evidence needed for that decision. Do not share unrelated files by default.
Make the snapshot reviewable
Record the source identifiers, included and omitted evidence, version, approval and recipient organisation. A checksum can help detect changes to a published package. The recipient accepts a copy in its own workspace; it does not gain access to underlying sender tables.
- Lot and consignment identifiers
- Quantities and relationship history
- Selected evidence and review state
- Version, approver and recipient
Handle withdrawal and correction
An unaccepted package may be withdrawn. Once accepted, a correction needs a new approved version; the recipient's earlier copy remains part of its own history. The receiving organisation records physical receipt and custody separately from accepting the information.
What this looks like in practice
A processor shares an output lot, its two documented blend inputs and a final assay, but omits unrelated plant reports. The customer accepts the package, records a lower received mass and asks for clarification. Neither organisation edits the other's account.
An approved information package does not certify the truth of every upstream claim or transfer legal custody by itself.
Primary references
These sources inform the general traceability or due-diligence context. The worked example and operational recommendations above are Atlas editorial guidance.