Docuvas.
Features

Engineering document control, end to end

Docuvas is an on-premise document management system for engineering and EPC teams. Register and revise documents, route them for approval, transmit them to partners, and prove every change — all in one controlled system.

01

Capture & control

Bring every controlled document into one register with automatic numbering, clean revisions, and a file history you can trust.

Document register

Every controlled document gets a unique, auto-generated number from your project's numbering recipe and discipline and type codes (for example RVP-ACME-ST-DWG-0042). One register, one source of truth.

Revision control

Work-in-progress drafts (P01.01, P01.02) become clean official revisions (P01) the moment they're shared. Supports P/C, A/B/C, and numeric schemes.

Immutable file storage

Files are content-addressed and never overwritten. Upload a new version and the previous one stays intact, hashed, and verifiable.

Full version history

Every revision is preserved and restorable. Never lose work, and never wonder which copy is current.

02

Review & approve

Move drafts through controlled approval chains, with everyone's pending work in one place and feedback captured as structured comments.

Approval workflows

Document controllers build reusable templates of ordered review and approval steps, then launch them on any draft. Steps run in series or in parallel.

My Tasks inbox

Every reviewer and approver gets one prioritised queue of what's waiting on them, with due dates and overdue flags front and centre.

Structured comments

Reviewers raise comments as structured rows — reference, body, and category (technical, quality, editorial) — with optional marked-up PDF attachments.

Discipline-check routing

An Initiation Discipline Check (IDC) matrix maps each document type and originating discipline to the disciplines that must review and the discipline that must approve.

03

Transmit & deliver

Issue approved revisions to external parties as formal, numbered transmittals — without ever exposing your wider register.

Formal transmittals

Send approved revisions to external parties as sequentially numbered, immutable transmittals (for example TRN-RVP-0118), each with an auto-generated PDF cover sheet.

Purpose codes

Issue For Construction, For Approval, For Information, or For Review — each purpose drives the right downstream behaviour.

Cross-organisation isolation

Recipients see only the revisions you transmit to them — never your wider register or your work in progress. Access is granted one revision at a time.

Delivery & acknowledgement tracking

Watch each recipient move from pending to delivered to acknowledged, with overdue badges when responses run late.

04

Respond & resubmit

Close the loop with external reviewers through structured verdicts, tracked comment dispositions, and linked resubmissions.

Response cycles

For-Approval and For-Review transmittals open a structured feedback loop per document and recipient, each with its own due date and reminders.

Clear verdicts

Recipients return a coded decision — Approved, Approved with comments, Revise & Resubmit, or Rejected — backed by their comment sheet.

Comment disposition

Answer each incoming comment as accepted, clarified, or not accepted, and the system records how every point was resolved.

Linked resubmissions

Issue a resubmission transmittal tied back to the original cycle, so the full revise-and-resubmit history stays traceable.

05

Find & prove

Locate any record in seconds and reconstruct its entire history on demand — turning audits from a scramble into a routine.

Full-text search

Search across document metadata and the text inside your PDFs, ranked and filterable by discipline, type, status, and date. Built in — no separate search appliance to run.

Immutable audit trail

Every register, upload, share, workflow step, transmittal, and response is logged automatically at the database level — who did what, when, and what changed. It can't be edited or skipped.

Audit-ready in a click

Reconstruct the complete history of any document on demand, with a time-stamped trail that stands up to scrutiny.

06

Access & administration

Put the right capabilities in the right hands, host partners alongside your own teams, and run it all on your own infrastructure.

Role-based access

Five cumulative project roles — viewer, reviewer, contributor, document controller, and project admin — put the right capabilities in the right hands.

Multi-organisation tenancy

Host your own organisation alongside partners and contractors on a single instance, with strict isolation between them.

Configurable to your standards

Set numbering recipes, status schemes (ISO 19650 or IFX), disciplines, document types, discipline leads, and approval policies per project.

Notifications & diagnostics

A background worker emails the right people when tasks, transmittals, and responses need attention, while admins watch database, storage, and worker health from one page.

Built for control and compliance

Docuvas runs on your own infrastructure, so your most sensitive engineering records never leave your control. Every action is logged, every file is immutable, and access is enforced at every layer.

On-premise deploymentEncryption in transit & at restImmutable audit trailSeparation of dutiesDiscipline-scoped accessCross-organisation isolation

See Docuvas on your documents

Book a 30-minute demo and watch version chaos and lost files disappear.