Skip to content
Astera Technology

Specify a supplier-exit data pack

Define the export snapshot, linked records and unresolved work needed to continue after the outgoing supplier leaves.

Keep relationships and pending work in the pack

Synthetic exit snapshot X-5 contains two customers C-1/C-2 and three bookings B-1/B-2/B-3. B-1 and B-2 link to C-1; B-3 links to C-2. A pending correction belongs to B-2. This is a data-pack specification, not a completed export.

Filled synthetic worksheet; editable CSV
Pack partSynthetic contentsReceiving check
Snapshot identityX-5; snapshot point and agreed included period recordedAll files refer to X-5, not mixed dates
Linked datasetsCustomers C-1/C-2; bookings B-1/B-2/B-3 with customer IDs2 customers, 3 bookings, all three links resolvable
Unresolved workB-2 correction pending with owner and original valueReceiver can identify the outstanding task
Download editable CSV ↓

Row counts alone do not establish continuity

The receiver gets two customer rows and three booking rows, but no customer IDs on bookings. Is X-5 complete under this pack?

Show the worked answer

No. Counts match but relationships cannot be resolved. Request booking customer IDs and the B-2 correction record before closing the receiving check.

An exit pack describes operational continuity, not entitlement to extract, transfer or delete data. Agree actual permitted scope and retain the broader handover inventory for code, accounts and recovery materials.

Related resources