Implementation, acceptance and handover
Bind implementation milestones to deliverables, approvers and inspected evidence.
Design to go-live
Scope/SOW → configuration/file plan → pilot → readiness → go-live approval → operations. Verify AI/QC/preservation profiles, permissions and connectors before production. Changes retain versions and impacts.
Delivery package
Content, metadata, manifests, physical–digital mappings, QC, exceptions/rework, custody, acceptance and evidence verification. Paper/archive transfers have separate receipts; exports preserve permissions/policy.
Partial acceptance
Record accepted, correction/disputed sets, manifest versions and decisions. QC passed, accepted, billable and invoiced differ. Closure receipts identify preservation/support obligations and decided outstanding work.
Continue the workflow
Two 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 detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment