The single source of truth for project documents.
RETRO.DCS replaces the shared drives, email chains, and spreadsheet trackers that let controlled documents slip out of control. Every document lives in one register with enforced numbering; every revision is reviewed, marked up, and dispositioned with a review code; every issue goes out on a transmittal and lands on the record. When the client asks who approved revision C and when, the answer is on the audit trail — not in someone’s inbox.
What DCS manages
The whole document lifecycle, in one place
Register & revisions
Controlled numbering, metadata, folders, and full revision history with a definitive current revision.
Review & markup
Reviewer assignment, PDF markup, threaded comments, consolidation, and coded dispositions.
Approvals & transmittals
Routed approvals, formal transmittals out and in, and distribution to every party.
Access & audit
Multi-party access for owner, consultant, and contractor teams, with a full audit trail.
Document register
One register, one numbering discipline.
Every project document lives in a controlled register: folders, categories, types, and disciplines, document numbers enforced unique, and search and filters that find the right sheet in seconds. The register is the single source of truth the whole project works from.
- Controlled numbering with enforced uniqueness
- Categories, types, disciplines, and tags
- Search, filters, and full metadata
Revisions & version control
The current revision is never in doubt.
Each document carries its full revision history with a definitive current-revision pointer. New revisions supersede the old on the record, so nobody builds from a superseded drawing.
- Full revision history per document
- Definitive current-revision pointer
- Superseded revisions kept on the record
Review & markup
Review it on the drawing, not in an email.
Assign reviewers to a revision, mark up the PDF directly, and discuss in threaded comments. Reviews are consolidated into one returned set, so the originator gets a single, coherent answer instead of five conflicting emails.
- Reviewer assignment with notifications
- PDF markup and threaded comments
- Consolidated review returned as one set
Approval workflow & review codes
Every revision leaves with a disposition.
Revisions move through a controlled lifecycle from submission through review to approval, and every review concludes with a coded disposition — approved, approved with comments, or revise and resubmit — so status is never a matter of opinion.
- Controlled lifecycle from submission to close
- Coded dispositions (Code 1, 2, 3)
- Routing to the right approvers
Transmittals & distribution
Nothing is issued without a record.
Documents go out and come in on formal transmittals, with recipients, acknowledgements, and closing transmittals recorded. Distribution rules put each issue in front of the right parties automatically.
- Outgoing and incoming transmittals
- Acknowledgements and closing transmittals
- Distribution to the right parties
Multi-party access & audit trail
Owner, consultant, contractor — one register, right access.
Owner, PMC, EPC, and consultant teams work the same register with access scoped to their role, and every action lands on the audit trail: who submitted, who reviewed, who approved, and when.
- Role-scoped access for every party
- One shared register across organisations
- Full who-what-when audit trail
The review cycle
Submitted, reviewed, coded — every time.
Document control lives or dies on the review loop. In RETRO.DCS a submitted revision is assigned, reviewed, and consolidated, and comes back with a coded disposition the whole project understands — the same discipline on document one and document one hundred thousand.
Cloud-delivered, multi-tenant by design.
RETRO.DCS is delivered as a multi-tenant cloud platform: every organisation works at its own address, in its own isolated workspace, with nothing to install and nothing to maintain on site.
- Your own address and isolated workspace per organisation
- Nothing to install — teams work from the browser
- Access scoped by role, project, and party
- Every action recorded on the audit trail
Questions, answered
What evaluators ask first
How is RETRO.DCS deployed?
As a multi-tenant cloud platform. Your organisation logs in at its own address and works in its own isolated workspace, with nothing to install or maintain on site.
Does it support review codes?
Yes. Every review concludes with a coded disposition — approved, approved with comments, or revise and resubmit — so document status is standardised across the project.
Can multiple organisations work on one register?
Yes. Owner, PMC, EPC, and consultant teams share the same register with access scoped to their role and party.
Does it handle transmittals?
Yes. Documents are issued and received on formal transmittals with acknowledgements and closing transmittals, all on the record.
Can reviewers mark up the PDF?
Yes. Reviews happen on the drawing — PDF markup with threaded comments — consolidated into a single returned set.
Can you migrate our existing register?
Yes. We migrate your document register, revision history, and metadata as part of implementation.