Prepare the package
Use a ZIP of PDFs and a CSV manifest with stable source keys and exact file references.
ONBOARDING & PORTABILITY
Bring the library.
Keep the accounting clear.
A guided path from a collection of PDFs and metadata to reviewed QA intake, followed by normal release controls.
V2 investor-demo baseline available · Production qualification remains in progress. See product status
Bulk onboarding, step by step
Bulk import is a V2 demo showcase. Production-volume and provider qualification remain pending.
Map your metadata
Review source columns, target fields, types, and normalization before committing.
Run a dry run
Inspect missing files, duplicates, validation findings, warnings, and the eligible selection without publishing forms.
Commit selected items to QA
Intake uses the governed form and validation path. Import does not bypass approval or publish straight to Production.
Retry affected items
Correct failures and preserve completed work, with lineage between attempts.
Reconcile the result
Account for committed, skipped, failed, pending, and unresolved items before sign-off.
Make adoption a shared plan
Onboarding includes organizational and integration work, not just uploading files.
People and responsibilities
Agree who prepares forms, validates releases, administers metadata, and approves Production.
Portal integration
Connect the API in your backend, select environments and audiences, and test retrieval.
Customer acceptance
Validate representative forms, metadata and access rules against your own processes before a production decision.
Portability and exit planning
The V2 demo is limited to non-destructive preflight and export preview. Complete production offboarding is not claimed.
Portable information model
The planned export covers permitted PDFs, versions, metadata, schemas, release state, and evidence with a verification manifest.
Preflight before closure
Inventory dependencies, access, scheduled work, retention obligations, and holds before any destructive operation.
Explicit production gates
Legal review, provider adapters, destructive rehearsals, backup aging, and independent verification remain required.