Who executes and who decides?
Intake, preparation and scanning staff execute tasks; AI reviewers confirm data; QC assesses outputs; shift leads approve exceptions and handovers. Access is bound to assigned projects and stations.
Trusted Records · Platform
Digitization Operations Portal
Coordinate paper records from intake to handover: preserve order, assess quality and resolve discrepancies at each station.
Roles and authority
Portal outputs
Source images, approved metadata, QC reports, sheet–image links and a versioned delivery manifest. Acceptance begins only after outstanding discrepancies receive a decision.
Follow one task
- 01Receive
- 02Preserve dossier boundaries
- 03Scan and reconcile
- 04Review OCR and QC
- 05Deliver by manifest
- 01Detect a missing side
- 02Keep the batch incomplete
- 03Locate the paper sheet
- 04Rescan with lineage
- 05Repeat QC and reconciliation
Reference journey for business review; the website does not process records or connect devices.
Interfaces by task
Cross-portal handoff
DIG hands validated packages to GOV; CUS reviews deliverables for acceptance; ADM governs permissions and station configuration.
Intake and handover
Bring every records box into a controlled process: establish sender, receiver, condition and the portion accepted.
Read detailsScanning and reconciliation
Bind each sheet to its scan images, processing attempt and routing result so recovery preserves the physical–digital link.
Read detailsQC and output quality
Verify completeness, image quality and metadata before acceptance.
Read detailsDevice/Edge and recovery
TURAPING Flow R is the selected device. Sheet-level compatibility and deployment configuration require separate validation.
Read detailsFollow the same dossier
synthetic-dossier-001 • Reference journey, not a real record
DIG · Sheets and images / QCGOV · Registration / access / preservationADM · Configuration / audit / serviceCUS · Acceptance / costs / invoice
Paper–image discrepancies remain under review; failed QC requires correction; missing permissions deny access; partial acceptance retains outstanding items; invoice failure does not reverse payment confirmation.
Preservation handoff and responsibility
DIG retains QC and sheet–image mappings. GOV selects profiles and registers/reviews evidence. ADM manages connectors, failed jobs and audits within authority. CUS sees permitted statuses and delivery packages. New LTANS content is a reference design rather than a released product screen.
LTANS — long-term evidence preservation
Connect records lineage to Mobile-ID’s published LTANS capability; agree the Records configuration in a contract and profile.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsSample package export and verification
Check synthetic-package hashes before delivery; distinguish byte integrity from authenticity, signatures and legal status.
Read detailsWorkspace
Active batches; pending reviews; interrupted stations; sheets awaiting reconciliation; QC results and outstanding items before delivery.
Role-based workflows
Intake and handover
Bring every records box into a controlled process: establish sender, receiver, condition and the portion accepted.
Read detailsPreparation and arrangement
Preserve original dossier structure before scanning instead of treating every stack as a single document.
Read detailsScanning and reconciliation
Bind each sheet to its scan images, processing attempt and routing result so recovery preserves the physical–digital link.
Read detailsAI/OCR and human review
Turn images into searchable data, with human decisions when confidence or business rules are insufficient.
Read detailsQC and output quality
Verify completeness, image quality and metadata before acceptance.
Read detailsDigitization control tower
Coordinate queues, stations and staff against actual capacity; expose whether work is waiting for paper, devices, AI or QC.
Read detailsPhysical records archive
Digitization does not end responsibility for paper. Manage location, custodian and every transfer by BoxID/DossierID.
Read detailsDevice/Edge and recovery
TURAPING Flow R is the selected device. Sheet-level compatibility and deployment configuration require separate validation.
Read detailsContinue 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