Freeze scope
Agree record/revision/component scope between both parties.
MOBILE-ID · TRUSTED LTANS
Provider Exit & Preservation Continuity
Prepare provider exit with inventories, recipient verification and an acknowledged custody-handover point.
Problem and records to preserve
Contract expiry does not mean the recipient has enough material to continue preservation.
SYNTHETIC CASE
Synthetic provider-exit package
EXIT-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Data owners, procurement, legal and migration architects |
| Source system | Current provider / recipient |
| Revision | Freeze inventory, responsibility, timing and external dependencies before retiring the source. |
| Record relationship | Source/target mappings and package revision are frozen before acknowledgement. |
Sector-specific record journey
Export inventory
Export a manifest identifying included/external components, digest algorithms and policy material.
Recipient checks
The recipient checks inventory, digests, syntax and trust material; discrepancies bind to the package.
Acknowledge custody
Bind acknowledgement to transferId and the agreed responsibility-transfer point.
Separate source disposition
Disposition the source separately under retention/hold/backup rules; record residual custody.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Manifest, authorized content, evidence material and custody acknowledgement. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Recipient acknowledgement differs from source disposition; holds remain effective.
Agree export, bandwidth and migration-support charges up front; avoid undefined exit fees.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: Provider-exit scope and recipient agreed by both parties.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Wrong digest or transferId cannot complete handover. |
Scope a PoC for this dossier
Test missing files, digest mismatch and absent receipt; source retains responsibility until the agreed handover point.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | Provider-exit scope and recipient agreed by both parties. |
| Revision / decision | Freeze inventory, responsibility, timing and external dependencies before retiring the source. |
| Test and expected result | Missing recipient evidence blocks transfer completion; source data is not automatically deleted. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | EXIT-SYN-001 |
| Source system | Current provider / recipient |
| Revision relationship | Source/target mappings and package revision are frozen before acknowledgement. |
| Recipient and output | Manifest, authorized content, evidence material and custody acknowledgement. |
| Rights and authority | Recipient acknowledgement differs from source disposition; holds remain effective. |
| Required rejection test | Wrong digest or transferId cannot complete handover. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.