Document Register

Why document control is critical

The number one cause of construction disputes in North America, per Arcadis’s annual analysis, is errors and omissions in contract documents. HKA’s CRUX research across 2,200-plus projects found incorrect, incomplete or late design information affecting 44.8% of them — more than scope change itself. In the Middle East, late design information alone hit 32.1% of projects, nearly double the rate elsewhere.

Under that headline sit the daily costs: about 5.5 hours a week per professional spent just looking for project information, and an estimated $88.7 billion of global rework in a single year caused directly by bad data — the wrong version, the wrong document, the wrong answer.

The role of the register in project performance

• Revision control is the core discipline. Each revision supersedes the last; superseded documents are archived — never deleted — with the chain intact, and holders of controlled copies are notified. The classic site failure needs no elaboration: a printed set in the site cabin at Rev B while Rev D sits in the system. A controlled copy is tracked and updated. An uncontrolled copy — the email attachment, the WhatsApp photo of a drawing — is a snapshot nobody will ever update.

• Status codes say what a document may be used for. Under ISO 19650’s UK conventions: S0 work-in-progress, which never leaves the authoring team; S1–S5 shared for coordination, information or review; the A-series published and accepted for a stage — suitable for construction, for instance. Alongside this lives the separate consultant review system familiar across the GCC: Code A approved, Code B approved with comments, Code C revise and resubmit. Two different systems answering two different questions — what a document is for, and what a reviewer said — and conflating them causes real site errors. Building from a “for information” issue is a failure mode with a body count of budgets.

• The register is delay-claim evidence — in both directions. Under FIDIC-style contracts the engineer must issue drawings in reasonable time, and the register and transmittal log are the contemporaneous proof of planned versus actual release dates when design comes late. A deliverable “issued on time” but returned Code C twice was effectively late — which is why sophisticated registers track approved-for-construction dates, not first issue. And the same register that proves the employer’s late release will just as happily prove the contractor sat on current information for three weeks.

• As-builts are a rolling product, not a closeout scramble. What is installed drifts from the IFC drawings through site instructions, RFI answers and field fixes. Capture redlines against the register as work proceeds, or reverse-engineer an “as-built” fiction at handover — with hidden services buried behind walls as the highest-stakes unknowns, and the facilities team paying for the fiction for a decade.

The CDE, in plain language

The industry term is “common data environment,” and most practitioners have never used it in a sentence. Here is what it actually means: one shared filing system for the whole project, with rules. Every document has one official current version; a status that says what you are allowed to use it for; and a record of everyone who received it. Documents move from work-in-progress to shared to published through checks — not by someone attaching a file to an email.

That is the whole idea. ISO 19650 standardises the naming, the statuses and the gates. The value is the discipline, not the acronym.

How Zepth runs the register

The register is live, not a spreadsheet maintained by heroics. Numbering rules and naming conventions are enforced on upload. Revisions supersede cleanly with full history. Status and review codes are tracked, distribution is recorded, and every document is viewable in the browser — including native CAD and BIM formats — without desktop software.

Bulk upload handles the thousand-drawing tender set. The audit trail handles the questions that arrive two years later.