Why Your Current CDE Setup Could Cost You 

By

Anna K. Cottrell

Last Updated Aug 6, 2026

By

Anna K. Cottrell

Do you know that organising your Common Data Environment (CDE) in traditional digital folders could cost you millions? It sounds sensationalist, but it isn’t. The current regulatory environment in the UK construction industry operates in a different way - and within very different timeframes - than the pre-BSA (Building Safety Act) system. According to the most recent data from BCIS, the median Gateway 3 processing time is now 34 weeks against a statutory target of eight weeks. As the number of applications has continued to grow since October 2023, the Building Safety Regulator has struggled to keep up with the mounting caseload.

However, the problem isn’t solely the BSR’s limited operational capacity. The ongoing confusion about what kind of documentation trail is required and how it should be organised is a contributing factor. Worryingly, 70% of applications are currently being rejected ‘due to missing legal documentation or failure to meet safety and quality standards’, and a staggering 40% is being rejected at the validation stage ‘due to missing basic information’. In other words, the majority of rejections are not due to fatal flaws with the design of the building, but with the way the applicant has (or rather has not organised the required information, which can easily lead to oversights. 

Being rejected means going back to square one, means going to the very back of the queue - and such a setback will cost you - easily in the millions, depending on how long the resulting delay is. Let’s imagine a realistic (and terrifying) scenario: A £150M project reaches Practical Completion. The BSR demands a specific suite of fire damper commissioning certificates. In a folder-based system, a missing file takes 3 weeks to identify, holding up £7.5M in retention monies and incurring over £230,000 a week in pure debt servicing.

There is good news here, though. You can prevent an unnecessary delay and ultimate rejection by the regulator by changing how your project data is organised from the beginning of your project. If you’re still relying on files in random folders, now is the time to make a change. What that means, in a nutshell, is that you should be building a CDE that doesn’t just store files but actively governs them. 

Let’s drill deeper into why not upgrading your CDE can be such a big issue - and how new data organising tools differ from what construction professionals have used in the past. 

Why Passive Folders Fail the Gateway Audit

Let’s imagine an average legacy project management system in place at a hypothetical construction firm. We’re most likely talking about a series of project folders on a drive or cloud, each folder containing an enormous amount of disparate files. From RFIs to contracts to project notes, it’s all dumped in the same repository. Essentially, it’s an old-fashioned filing cabinet in digital form. 

What is the issue here? Why is this traditionally acceptable organisation system likely to fail the Gateway audit? There’s a simple answer: because it relies on where files are located (in the project folder) not on what they actually are, or how many of each type there are. This can very easily lead to duplicate files, missing files, and (every project manager’s nightmare) ‘version control’ chaos that inevitably occurs when supply chain partners bypass complex folder rules. For example, someone at some point changed something on a contract - let’s say they changed or omitted the name of a PC, but they either didn’t have access to the folder or they simply forgot or neglected to replace the existing file with the updated version. 

A small mistake, but from the Regulator’s point of view, crucial information about a dutyholder has been omitted or is inconsistent across multiple documents, which creates confusion and could stall the application. 

Or imagine that a critical fire-stopping certificate has been buried in a siloed file directory and, as a result, was omitted from the application. When the BSR demands proof of compliance, digging through folders stalls handovers, delays final payments, and exposes the main contractor to regulatory breach. 

Relying on human input alone to manage vast amounts of project data - especially data will be amended at some point during the process - is a recipe for making costly mistakes. And it’s not that construction firms are any less or more organised that before, it’s just that the new regulatory regime has exposed some of the weaknesses. In truth, traditional project management processes were almost invariably riddled with errors. It just wasn’t as much of an issue because the regulatory compliance environment wasn’t as stringent. Small defects in how data is handled now have bigger consequences.

And those consequences aren’t just about potential trouble with the Regulator. Disconnected and poorly organised systems cost construction professionals in lost labour and friction with other team members and external contractors. Disconnected project management tools cause up to 17% of labour hours to be lost to rework and miscommunication, directly contributing to the validation-stage rejections by the BSR.

Why a Metadata-Based CDE Is The Answer

Fortunately, there is a solution, and it is simple: switching from a filing folder-based system to a metadata-based system. The most basic definition of metadata is that it’s ‘data about data’. Basically, metadata describes what an existing data unit (in our case, let’s say a document) is and what characteristics it has. So long as the document exists and is tagged, it can be found - not based on where it’s located but on what it contains and its relevant properties (for example, who created and owns the document, or who amended it and when). Relevance is key here: a metadata-based CDE automatically sorts through and organises all your project information; it can’t ‘forget’ that a document is important or was amended, or where it is. 

True enterprise data cannot be passive; it must be active. By replacing folder-based chaos—and the fragmented folder hierarchies it relies upon—with metadata-driven governance, documents are automatically tagged with their attributes. This creates a provable, searchable, ISO 19650-compliant audit trail from day one, turning regulatory compliance from a severe operational bottleneck into an automated byproduct of daily work.

Coming Up Next in the Series...

Now that we’ve covered the financial and compliance pitfalls of legacy folder structures—and established why metadata provides the missing foundation for an active, audit-ready data environment—how does it actually work on the ground?

Read our next piece: How Metadata Transforms CDEs for Construction Companies, where we break down how to deploy a metadata schema, maintain a friction-free supply chain, and help to ensure a Building Safety Act-compliant "Golden Thread" across your projects.

Written by

Anna K. Cottrell

Writer and Editor | Freelance

14 articles

Anna K. Cottrell is a writer and researcher with an expertise in the property and finance sectors.

View profile