How long does implementation take?

The typical 12-week arc

Implementation follows a consistent pattern regardless of customer size, though the volume inside each week varies:

Weeks 1–2 — Design workshops. For each document type in scope: template structure, metadata schema, approval-flow patterns, distribution lists, expiration cadences. Output is a design document that every subsequent phase references.

Weeks 3–6 — Configuration and pilot. Build the templates, set up approval flows, load a pilot document type, run real approvals through the system with a small group of users. Adjust based on what surfaces.

Weeks 7–9 — Training and parallel operation. Train document owners (2 hours), approvers (1 hour), end-users (30 minutes or less). Begin parallel operation where new documents flow through the new system while existing documents stay where they are for the moment.

Weeks 10–12 — Cutover and remediation. For hybrid/bulk migration strategies, bulk-migrate high-criticality documents. Fix issues surfaced during parallel operation. Official go-live.

What makes implementations take longer

• Bespoke template design — if your document types have no existing templates to inherit from, design takes more time.
• Multi-site coordination — implementations spanning 5+ sites need more training and change-management time.
• Parallel validated-system scope — if your QA team needs to run IQ/OQ/PQ on the deployment, that validation lives in a parallel track that extends the timeline.

What makes them shorter

• Smaller scope — 3–5 document types, one site, minimal compliance scope — can complete in 6 weeks.
• Existing usable templates — if your current document templates are structured enough to inherit from, design phase accelerates.
• Executive sponsorship — when change management is resourced properly, parallel operation shortens.

See the migration pillar guide for the full 12-week walkthrough.