Category Archives: Principal Contractor Compliance

Note to the reader: The information on this page is for general guidance only. For project specific advice, consult a competent professional.

On many projects, the paperwork isn’t the hard part—keeping controls alive when the programme shifts, new trades arrive, and the site changes daily is. A fictional example: a site manager on a small commercial refurb had a “complete” Construction Phase Plan, but the working sequence changed after a late design tweak. The plan stayed in a folder, RAMS weren’t re-coordinated, and two trades ended up stacked in the same tight area. Nothing catastrophic happened, but it created the exact question clients and auditors ask: can you show that the Principal Contractor is actively planning, managing and monitoring, not just filing?
This guide explains principal contractor duties CDM 2015 for UK non-domestic, non-HRB projects, with a clear “what to do” and “how to prove it” focus—site-practical and proportionate.

Scope and what this article covers

Focus: Principal Contractor duties under CDM 2015 on non-domestic projects.
Exclusions: HRB work and Building Safety Act gateway topics; domestic clients/self-build.
Lens: PC-only (we won’t drift into Principal Designer or Client duty sets).
Factual position: CTC supports compliance; legal duty remains with duty holders.

The core CDM 2015 Principal Contractor duty set (plain English)
Under CDM 2015, the Principal Contractor is appointed where there is more than one contractor. In practice, your role is to plan, manage and monitor the construction phase and coordinate contractors so work is carried out without risks to health and safety.
On site, that duty set typically translates into these control areas:

Construction Phase Plan (CPP): prepare (or ensure preparation), implement, and keep it live.
Site rules and arrangements: set, communicate, and enforce.
Cooperation and coordination: organise trades, sequencing, interfaces, and information flow.
Induction and briefings: ensure everyone understands site-specific controls.
Secure site and welfare: ensure suitable welfare is provided and maintained; control access.
Worker engagement: consult and involve the workforce in health and safety matters.
Ongoing monitoring: inspections, supervision, close-out of actions, and learning from issues.
Information management: ensure relevant design and pre-construction information is used and shared as needed for safe delivery.

What “good” looks like in practice (without bureaucracy)
Clients and auditors rarely want “more documents”. They want confidence that your controls are active, used, and proportionate to the risk. Aim for a system that is:

Current: reflects the actual sequence and conditions this week, not the tender programme.
Used: referenced in briefings, planning meetings, and supervision.
Joined up: CPP, RAMS, permits, logistics plans, inspections and actions all point the same way.
Traceable: decisions and changes have a simple evidence trail.

Duty-by-duty: what to do and what evidence is usually requested

1) Construction Phase Plan: make it a live control document
What to do: Ensure the CPP sets out your management arrangements and the key site controls (logistics, traffic, lifting, temporary works interfaces, high-risk activities, emergency arrangements, welfare, supervision, and monitoring). Keep it updated as the job changes.
Evidence commonly requested:

CPP with version control (simple revision table is fine).
Site set-up plan / logistics plan aligned to the current phase.
Meeting notes showing decisions that drive CPP changes (e.g., sequencing changes, access changes).
Records showing the CPP is communicated (induction content, briefings referencing controls).

2) Coordinate contractors and manage interfaces
What to do: Put predictable coordination points in place: daily/weekly planning, interface reviews, and clear rules for working in shared areas (e.g., ceiling voids, risers, loading bays, live environments).
Evidence commonly requested:

Lookahead programmes (2–6 weeks) and coordination meeting minutes.
Trade allocation/area control (who is where and when).
Delivery management records (booking-in, banksman arrangements, loading restrictions).
Change control notes (what changed, why, and how risks were re-controlled).

3) RAMS coordination: consistency beats volume
What to do: Ensure contractor RAMS match the way the job is actually being delivered, and that they align with site rules and logistics. Prioritise interface RAMS where trades overlap.
Evidence commonly requested:

RAMS register (status, approval/acceptance date, review triggers, linked permits if used).
Records of briefings/toolbox talks against the relevant RAMS (not just “issued”).
Evidence of re-brief when conditions change (design change, access change, different kit, new sequence).

Common RAMS failure
What good looks like on site
Simple evidence

Generic method statement, not site-specific
Method matches access, working hours, constraints, and logistics
Site-specific addendum + briefing record

Two trades rely on different exclusion zones
One coordinated plan for the area and sequence
Interface note + updated area plan

RAMS signed once at start then forgotten
Review triggers used (change, incident, new gang, new kit)
RAMS register with review entries

4) Inductions and ongoing briefings: prove understanding, not attendance
What to do: Induct everyone so they understand the site-specific controls. Follow up with short, targeted briefings when higher-risk work starts or conditions change (deliveries, excavations, lifting, isolations, work at height, hot works, live environments).
Evidence commonly requested:

Induction content (site rules, emergency arrangements, welfare, reporting, key risks).
Induction register (names, employer, date, signature) and re-induction triggers.
Briefing records referencing specific controls (e.g., revised pedestrian route, new exclusion zone).

5) Site inspections, supervision, and closing out actions
What to do: Set an inspection rhythm that fits the risk profile and site pace. Use findings to drive action, and then verify close-out on site (not just “completed” in a spreadsheet).
Evidence commonly requested:

Inspection schedule (daily supervisor checks, weekly formal inspections, targeted checks for high-risk activities).
Inspection reports with photos where helpful and clear actions/owners/dates.
Action tracker showing close-out and verification.
Learning/briefing notes when recurring issues appear.

6) Welfare, access control, and keeping the site secure
What to do: Ensure welfare is suitable and maintained. Control access so only authorised people enter. Keep pedestrian/vehicle routes clear and workable as the site evolves.
Evidence commonly requested:

Welfare checks and maintenance logs where relevant (simple tick sheets can be enough).
Site set-up photos/records at key changes (phase changes, new access points).
Visitor and delivery controls (sign-in/out, permits where used, escort rules).

7) Competence, supervision, and contractor control
What to do: Ensure contractors have appropriate capability for the work and that supervision matches the risk. For higher-risk activities, check specific qualifications/cards and experience rather than relying on a single “competence file”.
Evidence commonly requested:

Contractor appointment and scope clarity (who is doing what).
Key role competence records (supervisors, plant operators, slingers/signallers, first aiders, fire marshals as applicable).
Training/briefing records relevant to the job’s risk profile (e.g., asbestos awareness where required by scope, not as a blanket).

8) Managing change: the hidden test of CDM compliance
What to do: Treat change as routine: design tweaks, sequencing changes, access constraints, and substitution of materials/plant. The PC’s day-to-day duty is to keep controls aligned with the reality of the build.
Evidence commonly requested:

Short change notes (what changed, risks introduced, control updates required).
Updated RAMS/briefings and confirmation the workforce was re-briefed.
Updated logistics/traffic plans where routes or delivery strategy change.

Running Principal Contractor controls day-to-day (a simple operating rhythm)
A light but consistent cadence usually outperforms occasional “big” reviews:

Daily: supervisor walk, start-of-shift coordination, brief the day’s high-risk activities, check housekeeping/segregation/access.
Weekly: coordination meeting with a forward look; formal inspection; review RAMS status; review delivery plan; close-out actions.
At change points: re-plan interfaces, update CPP sections that matter, refresh briefings, and reset site layout controls.

Minimum evidence trail: what clients and auditors typically ask for
While expectations vary, a PC is commonly asked to produce a coherent pack showing the controls are in place and operating. This is a practical “minimum” list for many non-domestic projects:

CPP (current version) + site rules + emergency arrangements.
Site layout/logistics and traffic/pedestrian management arrangements.
RAMS register + selected high-risk RAMS + briefing records.
Induction records + ongoing briefing/toolbox talk records.
Inspection reports + action close-out tracker.
Meeting minutes showing coordination and interface management.
Competence evidence for key roles and high-risk activities.
Accident/near-miss reports and learning actions where applicable.
Welfare/access/security checks where relevant to site conditions.

Tip: if you can show how one change (e.g., a revised access route) flowed through CPP → layout plan → briefing → inspection, you’re demonstrating active management rather than passive filing.

Common pitfalls (and what to do instead)

Pitfall: CPP written once and never referenced.Do instead: treat the CPP as the “index” to your live controls; update only the parts affected by change.
Pitfall: RAMS accepted but not coordinated across trades.Do instead: run an interface check for shared areas and simultaneous operations.
Pitfall: Inspections produce actions, but no verification.Do instead: close out actions on site with a named verifier and date.
Pitfall: Briefings become generic and repetitive.Do instead: brief what’s different this week: sequence, access, exclusion zones, deliveries, isolations.

FAQs: CDM 2015 principal contractor duties (PC-only)
Do Principal Contractor duties under CDM 2015 transfer if I use an external safety adviser?The PC can get support with systems, coaching, inspections, or document review, but the legal duty remains with the duty holders. In practice, that means you should still be able to explain and evidence how controls are implemented, monitored, and improved on site.

Is the Principal Contractor responsible for every contractor’s RAMS being perfect?The PC’s role is to coordinate contractors and manage the construction phase so work is carried out safely. A practical way to meet this duty is to ensure RAMS are suitable for the site, aligned with site rules and logistics, briefed to the workforce, and reviewed when conditions change—especially where trades interface.

What does “plan, manage and monitor” mean day-to-day for a Principal Contractor?It means setting up workable arrangements (CPP, site rules, logistics, welfare), coordinating planned work and interfaces (lookahead planning, sequencing, deliveries), and actively checking performance (supervision, inspections, action close-out). The “monitor” part is evidenced by routine checks, clear actions, and verification that issues are fixed.

What’s the most important evidence a client wants to see from the Principal Contractor?Usually, it’s consistency: a current CPP, coordinated RAMS, inductions and briefings that match site conditions, inspection records, and closed actions. Clients often look for a clear thread showing that when the job changes, controls and communications change with it.

How often should a Construction Phase Plan be updated?There isn’t a single fixed interval that suits every site. A practical approach is to review and update the CPP when there are meaningful changes to sequencing, access, logistics, high-risk activities, or emergency arrangements—and to confirm those changes have been briefed and implemented.

Summary and next step
Meeting principal contractor duties CDM 2015 on non-domestic projects is less about producing more documents and more about running a simple, repeatable control system: keep the CPP live, coordinate RAMS and interfaces, brief what matters, inspect what’s happening, and close out actions with proof. If your evidence shows that change on site triggers change in controls, you’re demonstrating the “plan, manage and monitor” duty in the way clients and auditors recognise.
How we can help. See Principal Contractor Compliance for practical support options.

Disclaimer
This resource is provided for general guidance only. Always consult a competent professional for project specific advice. No warranty or guarantee is given or implied regarding completeness, accuracy, or compliance.