A record reaches retention expiry while an active hold applies; retain it for an authorized decision.
Retention, legal hold and disposition
Expiry does not authorize deletion. Check retention triggers, all active holds and authority before disposition.
Inputs and starting conditions
Record classes, versioned retention schedules, trigger events, hold scopes, grounds and approvers.
Workflow and control gates
- 01Calculate retention
- 02Check all holds
- 03Preview impact
- 04Review / approve
- 05Transfer or dispose
Multiple holds may coexist; lifting one does not release others. Recheck policy/holds immediately before execution and record the selected records and applicable versions.
Exceptions and recovery
Overlapping holds, unclear trigger dates or erasure conflicting with retention obligations block action and require authorized review. AI may assist detection but cannot decide.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| Owners define schedules/authority; legal teams impose/release holds; records managers prepare; independent approvers decide; operators execute. | Impact previews, policy/hold versions, decisions, results and evidence packages. States: review eligible / held / approved / executed / reconciled. |
Scenario and acceptance criteria
Complete only when
Disposition cannot proceed while a hold or unresolved duty remains.
Interfaces for this workflow
Integration handoff
End-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsErrors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsContinue the workflow
Long-term digital preservation
Maintain readability, integrity verification and record context over time; backup is only part of recovery.
Read detailsTwo journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment