Expert article
CDE and the construction phase: what belongs in the project room — and what does not
The common data environment holds the documents. The site produces tasks. The most expensive mistake is to take one for the other.
Expert article by Open Experience GmbH. As of: September 2026
What is a common data environment?
A common data environment (CDE), in German "gemeinsame Datenumgebung", is the central environment in which the information of a construction project is collected, managed and distributed. What characterises it is less the storage location than the release procedure: information passes through defined statuses — work in progress, shared, released, archived — and everyone involved can see which version is binding. Alongside it, the works produce a continuous stream of tasks with a processing status: defects, daily reports, inspections, captures. The two worlds belong together but hold different things — and the way they are divided decides whether it remains traceable later what was built on what basis.
Legal framework: Germany (Civil Code BGB, construction contract rules VOB/B, fee schedule HOAI). Other countries have different rules, and contractual agreements take precedence over the standard periods named here.
Two systems, two jobs
The dividing line does not run between the office and the site but between documents with a version and tasks with a status.
| Information | Common data environment | Site documentation |
|---|---|---|
| Drawings and drawing revisions | Leading — with release status and version | A reference to the revision built |
| Models and discipline models | Leading | The reference point for locating findings |
| Contracts, variations, correspondence | Leading | Not held |
| Defects with a deadline and a responsible party | The resulting document once closed | Leading — as a task with a status |
| Daily site reports | The filed result | Leading — carried forward daily |
| Photographs and 360° captures | A selection for the records | Leading — complete, located, dated |
| Acceptance minutes | Leading once released | The source of the findings |
Why the release status is the real heart of it
A common data environment is not a folder with a lot of accounts. What distinguishes it is the question it answers at any moment: which version applies?
- Work in progressWorking versions from one discipline, not binding on anyone else. Whoever takes them and builds from them does so at their own risk.
- SharedReleased for coordination with the other parties, coordinated, but not yet binding for the works.
- ReleasedThe binding version for the works. That status is precisely the reference that site documentation needs later.
- ArchivedCompleted versions stay traceable. Without an archive there is no way months later to establish what applied at the time of execution.
The sentence that counts in a dispute: "built to drawing XY, revision 3, dated 12 May" — and not "to the drawing that was in the folder at the time".
The three transitions where it jams
Between the project room and the site there are three recurring break points. They can be solved organisationally, but not with more accounts.
- From the drawing to the worksOn site, what is to hand gets built — not necessarily what has been released. Recording the drawing revision along with the finding saves you the reconstruction later.
- From the finding to the documentA defect is a running task; only the schedule once sent is a document. Keeping both in the same filing system makes the task unusable and the document unreliable.
- From the end of the project to operationsAt handover what counts is the completeness of the as-built records — including documentation of what is concealed today.
What this means for site supervision
For service phase 8 the common data environment is not an end in itself but the source of the basis for the works — and site documentation is the evidence of how that basis was carried out.
- Evidence the basisFor every documented item of work it should be apparent on what basis it was carried out. That is the point at which a CDE and site documentation actually meet.
- Record deviations earlyWhere construction departs from the released version, that is a finding — with a photograph, a date and a reference to the revision.
- Settle responsibilitiesWho releases, who distributes, who documents the works? Those three roles belong named at the start of the project, not in the first conflict.
This article describes ways of working; the requirements for a common data environment follow in the individual case from the contract and the client's information requirements.
How Open Experience solves this
Open Experience holds the tasks of the construction phase — defects, daily reports, photographs, inspections — with place, time and project reference. The project room holds drawings, documents and models. The two work together through a clear division of work, not through duplicate filing.
- Tasks instead of filesA defect has a status, a deadline and a responsible party. As a PDF in a folder it loses exactly that.
- A partnership since 2016PAVE by PMG is a collaboration platform for drawings, documents and models and hosts exclusively in Germany. Which routes are possible on a particular project is something we work out together.
Frequently asked questions
Is a CDE the same as a project room?
In everyday use the terms are often treated as identical. The difference lies in the claim they make: a project room is the shared filing system, while a common data environment combines that filing system with a governed release procedure and traceable statuses. Without statuses it is a filing system, not a CDE.
Does a CDE replace site documentation?
No. It holds documents with versions, while the works produce tasks with a status: open defects, running deadlines, daily reports. Filing tasks as files loses precisely the properties that matter.
Do smaller projects need a CDE?
Not necessarily. What matters is whether several parties work on drawings and documents at the same time and whether released versions can drift apart. Where that is the case, the missing structure costs more time later than introducing it would.
How do we record which drawing revision was built?
By creating the reference as you document: the designation, the revision and the release date are noted with the finding or on the daily report. After the event it can hardly be evidenced, because the archive holds several versions side by side.
Where is the data hosted?
That depends on the system in use and is one of the points to be settled before the project starts. According to the supplier, PAVE by PMG hosts exclusively in Germany; for Open Experience we settle hosting and data processing within the contract.
Sources and legal basis
The legal statements in this article are based on the primary sources listed below. The article is not a substitute for legal advice in an individual case.
- BIM Deutschland — common data environment: tasks and status model
- BIM Deutschland — standards, norms and guidelines at a glance
- HOAI, Annex 10.1 — basic services of service phase 8
- § 650g BGB (German Civil Code) — establishing the condition of the works where acceptance is refused
- PAVE by PMG — collaboration platform for drawings, documents and models
Settle the responsibilities before construction starts.
In the demo we look at your project structure and sort out what belongs in the project room and what belongs in the site documentation.