Work through the decision
Define the recipient, purpose and records actually authorised for export. Include stable identifiers, versions, relationships, source/rights metadata and permitted objects in documented formats. Remove unrelated clients, private values and unnecessary personal information. Verify links and reconstruction usefulness; exporting metadata without required object payloads may leave an incomplete handover.
A fictional worked example
A fictional asset owner exports an assembly passport and permitted care instructions for a new custodian. Private provider quotes stay excluded. The recipient can connect components to their evidence and version without gaining access to unrelated files.
Evidence and authority limit
A local download does not prove a shared-engine export, data transfer consent or continued access after revocation.
Put it into practice
Create an export manifest listing included records, excluded fields and three usefulness checks.
Keep this record: A scope-aware handover with portable IDs, versions, objects and verification notes.
- Recipient and authority are explicit.
- Linked records and rights survive export.
- Private fields remain excluded.
