Most project emails sit outside your Common Data Environment (CDE), creating risk and non-compliance with ISO 19650. Learn how to close the gap.
Your CDE Isn’t Complete…
Your BIM models are in the Common Data Environment (CDE).
Your drawings and document register are in the CDE.
Your contract management system is in the CDE.
But the email that approved a scope change?
The message that confirmed an instruction?
The thread that resolved a dispute?
They’re still buried in personal inboxes.
And that’s a problem.
The Hidden Risk Sitting in Your Inbox
Across construction and infrastructure projects, email remains the default system of record for critical decisions, despite not being managed like one.
This creates three major risks:
1. Commercial exposure
Key decisions with contractual implications often exist only in fragmented email threads. When disputes arise, teams waste time reconstructing history, or worse, miss critical evidence.
2. Lack of auditability
A core principle of a CDE is transparency and traceability. Email chains in personal inboxes are neither structured nor visible across the project team.
3. ISO 19650 non-compliance
Many organisations believe they are aligned with ISO 19650, but overlook one of its most practical requirements: managing project correspondence.
What ISO 19650 Actually Says About Email
ISO 19650 guidance — particularly Guidance Part C — explicitly identifies correspondence (including email) as part of the Common Data Environment.
It goes further:
Communications that carry contractual or project significance should be captured and managed within the CDE.
This isn’t theoretical. It’s a clear expectation.
Yet in practice, most organisations:
- Do not systematically capture email into the CDE
- Rely on individuals to manually upload messages (which rarely happens)
- Have no consistent audit trail for correspondence
Why This Gap Still Exists
If the requirement is clear, why hasn’t the industry solved it?
Behavioural friction
Project teams live in email. Asking them to change tools or duplicate effort (e.g. uploading emails manually) is unrealistic.
Technology limitations
Traditional CDE platforms were not designed to capture live communication flows, such as email threads, in a structured, automated way.
False sense of compliance
Many firms assume that having documents in a CDE equals full compliance, overlooking the role of communication in decision-making.
What a Complete CDE Should Include
A truly effective Common Data Environment should not just manage files; it should manage decisions.
That means:
- Capturing who said what, when, and why
- Linking correspondence to documents, models, and workflows
- Creating a searchable, auditable record of project communication
- Ensuring all stakeholders have visibility of critical exchanges
Without this, your CDE is only telling part of the story.
Closing the Gap Without Changing How Teams Work
Det er her PentagonMail-assistent kommer inn.
Rather than forcing teams to adopt new behaviours, it works with existing workflows:
- Automatically captures relevant email correspondence
- Structures and links it within your CDE
- Flags communications with contractual or commercial significance
- Creates a clear, auditable trail of decisions
All without asking project teams to leave their inbox.
The Commercial Advantage of Managing Email Properly
Organisations that address this gap are already seeing benefits:
- Stronger dispute defence with complete communication records
- Improved project transparency across stakeholders
- Reduced risk of missed instructions or approvals
- Faster information retrieval during project delivery and handover
In short, they move from fragmented communication to controlled project intelligence.
The Bottom Line
If your email sits outside your Common Data Environment, your project information is incomplete.
And if your information is incomplete, your risk is higher than you think.
ISO 19650 doesn’t just apply to models and documents; it applies to the decisions that shape them.
Want to See How Leading Teams Are Solving This?
We’ve created a practical guide that breaks down:
- Where the biggest gaps exist in typical CDE setups
- What ISO 19650 guidance really requires in practice
- How organisations are solving email management without disrupting delivery
Chat with the team and start closing the gap in your CDE.
Kontakt oss
"*" indikerer obligatoriske felt
