Definition
In an APC context, a computerised central project database (CCPD) is a structured electronic system in which all project-related information — drawings, specifications, correspondence, cost data, programmes and reports — is stored and accessed from a single controlled location. CCPDs may be hosted on a firm's server, a project extranet, or a cloud-based Common Data Environment (CDE) compliant with ISO 19650. The defining characteristic is that all participants work from the same authoritative record.
Why this matters for Data Management
- Level 1 knowledge: you must be able to explain what a CCPD is, give examples of what it stores, and describe the benefits it delivers to a project team.
- CCPDs directly address one of the most common causes of construction disputes: different parties working from different versions of the same document.
- ISO 19650 mandates a CDE on BIM-enabled projects; understanding CCPDs is foundational to understanding BIM.
- Access controls and audit trails within CCPDs support both GDPR compliance and professional indemnity risk management.
Key principles
What a CCPD stores
A well-configured CCPD holds drawings and specifications with version control; cost plans, bills of quantities and tender documents; the contract and correspondence; programmes, risk registers and meeting minutes; and financial reports including interim valuations and final accounts. The system must be structured so that the current version of any document is instantly identifiable and its history is preserved.
Access control and version control
A CCPD operates with role-based permissions: the client may view cost reports but not internal working files; a subcontractor may access only drawings relevant to their package. Under ISO 19650, information passes through defined workflow states — work in progress, shared, published and archived — ensuring only current approved versions are in use. Failure to control versions is a common source of construction error and dispute.
Benefits and limitations
The principal benefits are reduced duplication, faster retrieval, improved audit trails and better coordination. Limitations include setup cost, the need for training, and the risk that participants bypass the system if it is cumbersome. A CCPD is only effective if used consistently; a poorly adopted system can create a false sense of security about information quality.
Relevant RICS guidance and legislation
- ISO 19650-1 and ISO 19650-2 — define the CDE concept and the workflow states through which information passes on BIM-enabled projects.
- RICS Rules of Conduct (effective 2 February 2022) — Rule 5 requires members to manage information in a way that supports reliable advice and risk management.
- Data Protection Act 2018 / UK GDPR — where personal data is stored in the CCPD, the firm must have a lawful basis, implement appropriate security and comply with retention requirements.
- Construction (Design and Management) Regulations 2015 — requires that health and safety information is maintained and accessible; a CCPD is an appropriate vehicle for this.
Ethics and Rules of Conduct angle
Maintaining a disciplined CCPD is an expression of the Competence and Responsibility rules. A surveyor who allows project information to become disorganised risks providing advice based on wrong information and is unable to defend their professional conduct if a dispute arises. Retrospectively altering or deleting entries to manage a dispute is a serious ethical and potentially criminal matter.
APC-style Q&As
Q (Level 1)What is a computerised central project database and what does it typically contain?
A computerised central project database is a single electronic system in which all project information is stored and accessed by the project team from a controlled, authoritative location. It typically contains drawings, specifications, cost plans, the contract and correspondence, programmes, risk registers and financial records, all subject to version control and access permissions.
Q (Level 1)What is version control and why does it matter on a construction project?
Version control tracks changes to documents so that the project team always knows which is the current, approved version. It matters because construction work done from a superseded drawing revision is a common cause of rework and cost overrun. A well-managed CCPD ensures only current revisions are in use and that superseded versions are archived but accessible if needed.
Q (Level 2)How does a Common Data Environment differ from simply storing project files in a shared folder?
A shared folder provides storage but no workflow management. A CDE under ISO 19650 adds structured workflow states, role-based access permissions, audit trails and defined approval processes. Information only reaches the broader project team once checked and approved, reducing the risk of erroneous information being acted upon.
Q (Level 2)What data protection considerations arise when personal data is stored in a project database?
Under the Data Protection Act 2018 and UK GDPR, personal data must be processed with a lawful basis, kept securely, retained only as long as necessary, and not shared beyond the project team without authority. Access controls in the CCPD help enforce these obligations, and the firm should document its retention policy including when personal data will be deleted at project close.
Q (Level 3)You join a project mid-construction and discover the team has been issuing drawings by email rather than through the project's designated CDE. How do you address this?
(example) First I would establish the scale of the problem — how many documents have been issued outside the CDE and whether any have been acted upon. I would upload all identified documents retrospectively with the correct revision status and actual issue dates. I would call a team meeting to reinforce the protocol and get agreement to use the CDE exclusively going forward, document the corrective action in writing, and flag the issue to the client if any construction work may have been done from an uncontrolled revision.