Appointment evidence
Prepare appointment drafts and keep the actual issue, acknowledgement and supporting evidence separate. A prepared document is one part of the record.
CDM 2015 COORDINATION · PILOT
Software for CDM Principal Designers.
Keep information requests, design review records and communication evidence connected as the project develops.
Make coordination easier to follow.
A Principal Designer’s coordination work involves people, information and decisions that change over time. A document in a folder may show what was prepared, but it can leave questions about who reviewed it, what remains unresolved and who received the relevant information.
CDMlogic supports that project record with a PCI tracker, design risk register, linked evidence, actions and dutyholder records. Your team can identify an outstanding question, record responsibility for the next action and retain the information that supports the review.
HSE describes the CDM Principal Designer’s role in coordinating health and safety during the pre-construction phase. Read HSE’s Principal Designer guidance →
Follow the information through the project.
Pre-construction information
Record information items, missing sources, owners and reviews. Link evidence so the team can consider what is available and what still needs checking.
Design coordination
Record design responses and significant residual information. Keep actions and evidence alongside the relevant risk entry as the design develops.
A coordination record should answer practical questions.
- Which design decision depends on information that has not yet been reviewed?
- Who owns the next action and when should it be reviewed?
- What changed since the last review?
- What residual information does another designer or the construction team need?
- Which file or communication explains the decision?
Use the PCI guide to organise information gaps, and the worked design risk example to connect an entry to review and communication records.
Continue the record into handover.
Health & Safety File tracking, construction interfaces and project actions help keep handover information visible. Project reports bring together the recorded workflow and evidence references; CSV and JSON exports support further review.
The right information still has to be assessed, communicated and kept up to date by the project team. A status in software reflects the recorded workflow and does not establish that a statutory duty has been fulfilled.
Which Principal Designer role does this cover?
The current core workflow supports the CDM 2015 role in Great Britain. England’s Building Regulations Principal Designer role has a separate purpose. Original Building Regulations templates are available as drafts, but a complete Building Regulations or higher-risk building workflow is outside the current core product.
Read the guide to the two Principal Designer roles and the product’s regulatory scope before assessing its fit.
Explore the pilot with your team.
Owner, admin, editor and viewer roles allow colleagues to share workspace access appropriately. You can walk through a fictional project before discussing pilot access and your team’s requirements. General availability and commercial plans have not yet been announced.
EXPLORE THE WORKFLOW
See where CDMlogic fits.
CDM software for architects
A shared routine for information, design reviews and project records across a practice.
Explore the practice workflow →CDM Principal Designer software
Connect information gaps, design coordination, appointments and handover actions.
Explore coordination records →Pre-construction information software
Keep information gaps, owners, reviews and supporting evidence connected to the project.
Explore the PCI tracker →