How it works

A structured path from evidence upload to submission confidence.

Six steps. One workflow. No disconnected handoffs.

How it works

1

Create a project and deliverable

Choose your regulatory channel (AMCP, EU JCA, DE AMNOG, CDA-AMC), select a template, and configure your strictness profile. DossierDock loads the matching rulepack automatically.

DossierDock onboarding wizard showing six guided steps from project creation to first preflight run. — Six guided steps with resume state and undo safety.

2

Upload and map evidence

Upload your artifacts as PDFs, DOCX, XLSX, CSV, or RIS/BibTeX. Map them to template sections using the checklist. Mark sections N/A with a recorded justification when they don't apply. Progress and save state are visible at the section level.

Deliverable checklist showing EU JCA sections with mapped and missing status badges and progress snapshot. — Section-level mapping with progress snapshot. Complete 3, Missing 17, Optional 19.

3

Run preflight validation

One click. DossierDock evaluates your pack against the active rulepack and any stacked overlays. Results are grouped by severity: blocking, warning, and advisory, with remediation guidance for each finding. You'll see specific issues, including which sections are missing, which dates are inconsistent across documents, which PDFs are password-locked, and which filenames won't pass portal gates.

Preflight findings report showing Blocking 0 and Advisory 18 defects with per-section summary. — Preflight result: PASS. Blocking 0, Advisory 18. Findings grouped by severity with remediation guidance.

4

Resolve defects and iterate

Assign defects to team members. Fix artifacts and re-upload. Re-run preflight. The defect lifecycle tracks resolution status with a full state machine. If a mapping or artifact changes after governance approval, the approval is automatically invalidated. No stale sign-offs.

Governance Workbench showing readiness metrics, approval status, and member roles. — Governance Workbench with readiness gates, approval tracking, and role-based access in one pane.

5

Approve and export

When all blocking defects are resolved (or explicitly overridden with recorded justification), approve the deliverable. Export a submission-grade ZIP with manifest, SHA-256 checksums, preflight certificate, HTML index, and traceability matrix.

Export builder showing governance gate enforcement, with export blocked until approval is recorded. — Export blocked until governance approval is recorded. Signature verification and manifest hash included.

6

Maintain the audit trail

Every action, including upload, mapping change, preflight run, approval, override, and export, is recorded in an immutable audit log. When a reviewer asks "who approved this and when," the answer is one click away. When an auditor asks "what changed between these two exports," the lineage is there.

See this workflow in a live demo.

Request a Demo