Skip to main content

How it works

A structured path from triage to governed export.

Six steps. One working path. Fewer late-cycle surprises.

1

Triage the queue

Start in the workspace or project dashboard to see which deliverable needs work next, what last ran, and whether approval or export state is stale.

Project dashboard showing deliverable pressure, readiness, and latest export context.
Project dashboard keeps operators oriented before they enter deliverable work.
2

Create the project and deliverable

Use guided onboarding to create the project, move into deliverable setup, and keep the remaining steps visible from the start. Template, channel checks, and review threshold choices stay inside one controlled sequence instead of getting scattered across setup screens.

Onboarding wizard showing the guided setup flow from project creation to first upload.
Guided onboarding makes the full path to first preflight visible before checklist work begins.
3

Map in the checklist

Upload PDFs, DOCX, XLSX, CSV, or RIS/BibTeX, map them to template sections, and record N/A justification where needed. Progress and save state stay visible at the section level.

Checklist showing mapping status and progress across dossier sections.
Checklist work stays focused on mapping completeness and section status.
4

Run preflight and review the report

One click. DossierDock evaluates the pack against the active lane checks, then produces a report with must-fix issues, lower-priority notes, named checks, and fix guidance.

Preflight report showing current findings and workflow actions.
Report review is the working surface for understanding what failed and what changed.
5

Resolve and approve in governance

Assign work, review unified findings, and approve readiness. If mappings or artifacts change after approval, the approval is invalidated automatically so stale sign-off does not survive.

Governance workbench showing readiness, findings, and approval controls.
Governance keeps findings, approvals, and invalidation logic tied to current inputs.
6

Build a frozen-review or submission export

When the deliverable is ready, build a governed export. Draft, review-snapshot, and submission flows stay tied to approval state, package records, file fingerprints, export history, and direct traceability downloads.

Exports view showing governed build actions gated by readiness state.
Exports stay gated by governance state and selected run context.

See this workflow on your own deliverable path.