Module · Documents
Project documents with the audit trail you'd want six months later.
Revision control, status (Draft / Issued / Superseded), shareable issue trail - wired to the project record so when a dispute lands you can show what was issued, when, and to whom.
Why most consultancy DMS strategies fail
A shared drive is not a document control system.
Most consultancies start a project on SharePoint, OneDrive or a shared network folder. By month six the folder structure is a mess, file naming has drifted, and nobody knows which version is current.
Versions multiply silently
"Drawing_001_REV_C_FINAL_FINAL_v3.pdf" is in three folders. Two of them are stale; nobody knows which. The site team is working off the wrong revision.
Issue history is email forensics
When the dispute asks "did the contractor receive Rev C before pour?", the answer lives across 200 emails between five people.
Status is always wrong
Was that document issued? Pending QA? Superseded? Hover-over file properties don't tell you. The truth is in someone's memory until they leave.
What's inside
A DMS sized for consultancy projects, not enterprise infrastructure.
Revision control
Each document carries a revision history. Promote a new revision; the previous becomes Superseded with a clear "what changed" note. The trail is automatic.
Status workflow
Draft → Issued → Superseded with role-aware permissions on each transition. Site teams can't accidentally work off a Draft. Auditors see the gate every revision passed through.
Project linkage
Every document lives against a project record. No orphan files in a generic shared drive. The project closes; the documents archive together.
Issue trail
Per-revision record of who it was issued to, when, and via what channel. The receipt the dispute six months later asks about - already there.
Document types
Workspace-managed taxonomy (drawings, specs, RFIs, instructions, contracts). Filter by type; report by type; archive by type.
Client-facing views
Push selected documents to the client portal as a curated, redacted document pack.
Who uses it
Built for the people who issue documents - and the ones defending the audit.
Project Managers
A clear status on every document. Issue a revision, the previous goes Superseded automatically. The client always sees the current document.
Construction Managers
No risk of working off a stale revision. The Draft is gated; the Issued is current; the Superseded is dimmed.
Directors / Quality
When the dispute lands, the issue trail is one click. Auditable, dated, signed.
See document status work the way it should.
A 20-minute walkthrough on a real project - bring a doc, we'll show you the issue trail.
Frequently asked questions
Will this replace SharePoint / OneDrive?
For project documents - yes. Projavio's DMS is purpose-built for project lifecycle. For general firm-wide knowledge, SharePoint is still the right tool.
Can we bulk import an existing project?
CSV import handles bulk metadata. Files upload via drag-and-drop in batches.
How does the audit trail work?
Every revision, every status change, every issue event is timestamped, attributed, and immutable.
Can clients receive documents via the portal?
Yes - the Client Portal carries a curated document pack. You control which documents and which revisions appear.
What about CDE-style federated drawing review?
Projavio is consultancy-grade DMS - not a full CDE. For BIM federation, a CDE like Asite, Aconex or Trimble Connect is still appropriate.
Connects to
Other Projavio modules that work alongside this one.
Project Reports
Composable monthly project report packs combining cost report, programme, variations, risks and narrative - branded per workspace.
Client Portal
A redacted client-facing view of the project: programme, cost summary, variations, documents - controlled per project, per client.
Project Workspace
The project workspace every internal user lives in. One project record - every other module hangs off it.
Your project documents - in their right place, with their right status.
Stop running document control out of file naming.