Why Document Control is Still Failing UK Construction Projects — and What Needs to Change

1 Poor information management
2 The Scale of the Problem
3 What ISO 19650 Requires in Practice
4 Where Manual Transmittal Processes Break Down
5 Why CDE Platforms Haven’t Fully Solved It
6 What Effective Document Control Actually Looks Like
7 The Emerging Role of Automation in Document Control
8 Conclusion
9 About the Author

[edit] Poor information management

Poor information management sits behind a significant proportion of construction disputes, delays, and cost overruns in the UK. Yet the discipline of document control is still widely under-resourced, misunderstood, and dependent on processes that have barely changed in two decades.

[edit] The Scale of the Problem

Construction is one of the most document-intensive industries in the world. A single medium-sized project — a £30–50 million commercial fit-out or school build — can generate tens of thousands of documents over its lifetime: drawings, specifications, RFIs, submittals, inspection records, test reports, warranties, and O&M manuals. Every one of them needs to be issued, tracked, responded to, and archived in a way that is auditable and defensible.

The transmittal is the mechanism that underpins all of this. It is a formal record of document issue between parties: what was sent, to whom, when, at what revision, and for what purpose. Done correctly, it creates the audit trail that protects every party on the project. Done poorly, it creates ambiguity, disputed liability, and hours of wasted time chasing information that should have been traceable from the start.

Research from the Construction Industry Training Board (CITB) suggests rework caused by poor information management can account for up to 5% of total project costs. On a £50m scheme, that figure reaches £2.5m.

Despite the emergence of Common Data Environment (CDE) platforms and BIM-mandated workflows, the actual practice of issuing and tracking transmittals on many UK sites still relies on email threads, shared drives, and manually maintained spread sheets. The gap between policy and practice on information management remains wide.

[edit] What ISO 19650 Requires in Practice

Since the UK mandate for BIM Level 2 on centrally procured government projects in 2016, and with the adoption of BS EN ISO 19650 as the national information management standard, there has been greater pressure on project teams to handle information in structured, auditable ways.

ISO 19650 sets out a framework for managing information across the project and asset lifecycle. In operational terms, this translates to:

Appointing an Information Manager with defined responsibility for the CDE and information flows
Establishing an Exchange Information Requirements (EIR) at the outset of each project
Producing a Master Information Delivery Plan (MIDP) with agreed issue milestones for all parties
Ensuring every document issue is traceable with revision histories, purpose codes, and delivery confirmation
Maintaining a structured archive accessible throughout the asset lifecycle for O&M and future works

The gap between this framework and live site practice is significant. ISO 19650 compliance is frequently treated as a procurement checkbox rather than an operational discipline. Document Controllers on active projects are often under-staffed, under-briefed on the standard's requirements, and using tools that were not designed for the complexity of modern construction information flows.

[edit] Where Manual Transmittal Processes Break Down

It is worth being specific about the failure modes of manual document control, because the cumulative cost is easy to underestimate until you see it mapped out on a live project:

Version control errors: When drawings are distributed by email rather than through a controlled CDE, superseded revisions remain active in inboxes and on local drives. Contractors build from the wrong revision. This is one of the most consistent causes of rework across UK projects of all sizes.
Incomplete audit trails: When a dispute arises over what information was available to a subcontractor at a given point in time, a manually maintained spread sheet log rarely holds up. Missing timestamps, unconfirmed receipt, and absent revision records are common findings in adjudication.
Response tracking failures: RFIs and submittals issued without a formal tracking mechanism fall into inboxes and go unactioned. Chasing responses manually consumes significant Document Controller and PM time that could be better spent.
Contractor coordination gaps: On projects with multiple subcontractor packages, ensuring all parties hold current-revision documents in a traceable way is logistically difficult to manage by email and spread sheet, particularly as the project programme accelerates.
Onboarding friction: When a new subcontractor is appointed mid-project, issuing the full set of current-revision documents in a controlled, traceable format typically requires hours of manual effort that falls to an already stretched Document Controller.

“We knew the drawing had been updated. The problem was we couldn’t prove the subcontractor had received the new revision before they started the works.” — a scenario that recurs across UK projects and illustrates exactly where audit trail failures become financial liability.

[edit] Why CDE Platforms Haven’t Fully Solved It

Platforms such as Autodesk Construction Cloud, Procore, and Asite are now widely deployed on larger UK projects. These tools provide cloud-based document storage, workflow automation, and audit functionality that represent a meaningful step forward from shared drives and email.

But CDE adoption has not resolved the transmittal problem for the industry at large, for several structural reasons:

Pricing and complexity exclude smaller firms: Enterprise CDE platforms are priced and configured for major contractors and large projects. Tier 2 and Tier 3 contractors, specialist subcontractors, and consultants on projects below around £5m often cannot justify the cost or the implementation overhead.
Transmittal is one module among many: Within large platforms, the document issue workflow is one feature among dozens. Configuration is non-trivial, and teams frequently default to email for day-to-day transmittal, bypassing the system that was intended to create the audit trail.
Cross-platform document issue: Main contractors and subcontractors operating on different platforms must still agree a mechanism for document handover across platform boundaries. In practice, this defaults to email — which means the audit trail lives outside either CDE.
User adoption is inconsistent: A CDE is only effective if every party in the information chain uses it correctly and consistently. Site-based teams in particular frequently operate outside platform workflows, especially under programme pressure.

The practical result on many UK projects is a two-tier information system: a CDE in place contractually, and an informal parallel process running alongside it in practice. The audit trail that would matter in adjudication is frequently the one that was never properly maintained.

[edit] What Effective Document Control Actually Looks Like

Good document control is not simply a matter of software. It requires clear process, defined responsibilities, and consistent execution from project mobilisation through to handover. In operational terms, that means:

A single authoritative source of truth for current-revision documents, accessible to all parties with appropriate permissions and version visibility
Formal transmittal records for every issue — generated consistently, with timestamped delivery confirmation and unambiguous purpose codes
A live response tracker for any documents requiring formal action, with visible escalation for overdue items
Regular document status reporting so information bottlenecks are visible to the project team before they become programme risks
Structured close-out and archiving that produces an O&M-ready document set without requiring significant retrospective effort

The projects where document control works well share a common characteristic: it is set up properly at mobilisation, not retrofitted after problems emerge. When a dedicated Document Controller is appointed early, given clear authority over the information management process, and provided with tools that match the workflow requirements, the downstream benefits are measurable: fewer RFI delays, fewer version control errors, and a cleaner audit trail that holds up when it needs to.

[edit] The Emerging Role of Automation in Document Control

The construction industry is beginning to see purpose-built automation tools that sit alongside or beneath enterprise CDE platforms. These are lightweight, workflow-specific applications targeting individual pain points — transmittal generation, response tracking, distribution management — without requiring full CDE adoption or configuration overhead.

Whether througH automation or simply through better process discipline, the direction is clear: construction information management needs to become more structured, more traceable, and less reliant on individual effort and memory. The projects that manage risk most effectively over the next decade will be those that treat document control as a first-class project management discipline — not an administrative afterthought.

[edit] Conclusion

Poor document control is not a new problem in UK construction — but it is an increasingly costly one. As contracts grow more complex, programmes more compressed, and disputes more frequent, the audit trail created by a properly managed transmittal process carries more weight than ever.

The framework exists in ISO 19650. The technology exists across a growing range of platforms and tools. What the industry still needs is a cultural shift: one that recognises document control not as administrative overhead, but as active risk management

If your current transmittal process depends on a shared spread sheet and a hope that everyone received the right revision, it is worth asking what that trail would look like under scrutiny — and whether it would hold up when it matters most.