A project adds a record class; revise scope, QC criteria and acceptance authority before receiving new batches.
Trusted Records · Platform
Projects and readiness
Translate contractual scope into verifiable operational configuration before go-live.
Inputs and starting conditions
Scope/SOW, volumes/milestones, sources, file plan, AI/QC/preservation profiles, sites/devices/staff and connectors.
Workflow and control gates
- 01Agree scope
- 02Configure profiles
- 03Check sites / connectors
- 04Review readiness
- 05Go live and close
SLA and acceptance criteria must be measurable; readiness covers staff, devices, data and integration. Scope changes retain versions, approvals and cost/schedule impact.
Exceptions and recovery
Unready connectors, unapproved profiles or missing staff block affected go-live scope with remediation owners/deadlines. Closure retains outstanding items and handover evidence.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| Project administrators coordinate; owners approve SOW/acceptance; technicians verify readiness; operations supervisors execute. | SOW/profile versions, readiness checks, go-live approvals, change logs and closure evidence. States: setup → readiness review → approved → active → handed over. |
Scenario and acceptance criteria
Complete only when
Scope and criteria are linked to the correct project version.
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
Assessment and pilot
Use representative records to verify process, quality and integration before scaling.
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