Principal Contractor Site Inspections: Frequency, Focus Areas, and Records That Stand Up

TL;DR

• Set principal contractor site inspections how often and what to record using a risk-led baseline: daily task-focused checks, a structured weekly inspection, and a monthly trend review.
• Increase inspection frequency during mobilisation, peak trade interfaces, higher-risk activities (WAH, lifting, excavations, hot works), and after incidents, near misses, or repeat issues.
• Focus inspections on practical themes: welfare, housekeeping/fire, work at height, traffic management, temporary works, services/isolation, permits, and RAMS in practice.
• Keep records audit-ready: precise location, observed facts, priority, clear actions, named owners, due dates, verified close-out, and before/after photos where useful.
• Align your process with principal contractor duties cdm 2015 by showing monitoring through disciplined action tracking, not tick-box forms.

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

On one busy refurbishment job, a site manager introduced a “daily walk” but kept writing the same three lines in a notebook: “All OK. Housekeeping good. No issues.” A month later, a repeat issue cropped up in the same area and nobody could show what had been checked, what was expected, or who owned the fix. The supervision was happening, but the evidence wasn’t. That’s the gap this guide closes.

This article focuses on the Principal Contractor duties under CDM 2015 for non-domestic projects, specifically how to set a sensible inspection cadence and keep inspection records that demonstrate real supervision and monitoring without drowning the team in paperwork. CTC supports compliance; legal duty remains with duty holders.

Principal Contractor Advisory Support

Need a Competent Health & Safety Advisor for Your CDM Project?

Practical CDM support for Principal Contractors — advice, documentation, and structured systems to help you run organised, compliant projects.

If you’re managing the Principal Contractor role alongside running the job, we provide the expert guidance and support that keeps your Construction Phase Plan, RAMS, and site records properly organised and ready when clients or auditors ask to see them.

Experienced construction safety advisors supporting SME Principal Contractors across the UK.

What “site inspections” should achieve for a Principal Contractor

For a Principal Contractor (PC), site inspections are one of the clearest ways to evidence that the site is being properly managed, monitored and supervised. A good inspection regime should:

• Spot emerging risks early (before they become incidents or programme delays).
• Confirm controls are in place and working (not just written in RAMS).
• Drive corrective actions to completion (not just observations).
• Create a simple, auditable trail that links finding → action → owner → close-out.

Principal contractor site inspections: how often?

There isn’t a single “right number” that fits every site. Under CDM 2015, frequency should be set by risk, complexity, and the phase of work. A practical approach is to define a baseline and then scale up or down.

A workable baseline (then adjust for risk)

• Daily: short, task-focused supervisory checks (often linked to permits, briefings, high-risk activities, and housekeeping).
• Weekly: structured PC inspection covering site-wide controls, interfaces, and recurring issues.
• Monthly: management review / trend review (what’s repeating, what’s overdue, what’s changing).

When to increase inspection frequency

Increase cadence when risk or change increases, for example:

• Early mobilisation and first trades on site (systems bedding in).
• Multiple contractors working simultaneously (interfaces and overlap).
• Higher-risk activities (e.g., work at height, lifting operations, excavations, temporary works, hot works).
• Constrained environments (tight access/egress, occupied buildings, live services).
• After a near miss, incident, or repeated non-conformance.
• Major programme changes, sequencing changes, or new subcontractors.

When you can reduce frequency (carefully)

You may be able to reduce structured inspection frequency where work is stable and lower risk, controls are proven, and performance is good. If you do, keep the rationale simple and recorded (e.g., stable phase, low trade density, good close-out performance, no repeats).

Example inspection cadence by phase and risk

Project phase / condition	Typical risk picture	Practical inspection cadence
Mobilisation & set-up	Changing layout, new controls, onboarding	Daily focused checks + weekly structured PC inspection
High interface / peak trades	Overlap, congestion, shared access	Daily focused checks + 1–2 structured inspections per week
Higher-risk activity windows	Control-critical tasks	Pre-start checks for each activity + spot checks during works
Stable fit-out / finishing (lower risk)	Predictable tasks, fewer interfaces	Daily supervisory checks + weekly structured inspection
Close-out / demob	Changing access, temporary protections removed	Daily checks on changing controls + weekly structured inspection

What to focus on during inspections (site-practical checklist themes)

Avoid trying to inspect “everything” every time. Instead, use a consistent set of themes and rotate emphasis based on what’s happening on site. Common PC focus areas include:

• Site set-up and welfare: access/egress, lighting, signage, welfare condition, cleanliness.
• Housekeeping and fire safety: waste routes, combustible storage, hot works controls, extinguishers, clear exits.
• Work at height: edge protection, scaffold tags/status, MEWP use, exclusion zones, dropped object controls.
• Traffic management: segregation, banksman arrangements, reversing controls, delivery coordination.
• Excavations and groundworks: support/battering, edge protection, services controls, spoil placement.
• Lifting operations: lift plans briefed, exclusion zones, supervision, accessories inspection, communications.
• Temporary works and stability: installed as designed, inspections to schedule, changes controlled.
• Electrical and services: temporary electrics, isolation/lock-off, cable management, live service interfaces.
• Permits and control-critical systems: hot works, confined spaces (where relevant), isolations, plant checks.
• RAMS in practice: evidence that work matches the agreed safe system, not just what’s written.
• Competence and supervision: right people on the task, inductions, briefings, ongoing oversight.

What to record so inspection records stand up

Strong inspection records are specific, traceable, and closed out. The goal is not volume; it’s clarity. A record should allow someone not on site that day to understand what was checked and what happened next.

Minimum fields to capture

• Date and time (and the working shift if relevant).
• Area/zone (be precise: level, gridline, room, compound, external elevation).
• Who inspected (name/role) and who was present (if joint inspection).
• What was being inspected (theme or activity: e.g., “work at height—MEWP operations, Level 2”).
• Findings written as observed facts (what you saw, not what you assume).
• Risk rating or priority (simple categories work: High/Medium/Low, or Immediate/Short-term/Planned).
• Required action (clear instruction: what “good” looks like).
• Action owner (named person/role and company/trade where helpful).
• Due date/time appropriate to the risk.
• Close-out: completed date/time, what was done, who verified.
• Evidence: photos (before/after), annotated where needed, plus references to permits, briefings, or method statements if relevant.

How to write findings that are actually usable

Aim for “observable + location + impact”. Compare these:

• Weak: “Scaffold not safe.”
• Strong: “North elevation scaffold, lift 2: missing toe boards to open edge on bay 3; materials stored on platform. Risk of materials falling to access route below.”

Then make the action equally specific:

• Action: “Install toe boards to bay 3 lift 2 and remove loose materials until edge protection complete. Maintain exclusion below until rectified.”

Photos: when they help and how to keep them meaningful

Photos can strengthen inspection records, particularly for close-out. Keep them useful by:

• Including context (a wider shot) and detail (a close-up).
• Adding a short caption: area, what it shows, and whether it’s before/after.
• Avoiding photo-dumps; link each image to a specific finding or action.

Action tracking: the difference between “we inspected” and “we managed”

Inspections without action tracking quickly become tick-box evidence. For PC records that stand up, ensure your process shows:

• All findings have an outcome: closed, accepted with controls, or escalated.
• Overdue actions are visible and followed up (with notes of chase/escalation where needed).
• Repeat issues are flagged and addressed at the right level (supervision, sequencing, training, supply chain).

A simple weekly review of open actions (top risks first) is often more valuable than adding another inspection form.

Free Resource for Principal Contractors

Principal Contractor Toolkit: 37 Essential CDM Templates

A practical set of ready-to-use forms designed to help SME Principal Contractors keep their projects organised and properly documented.

Includes key construction phase records, inspection forms, registers, and supporting templates commonly required on CDM projects — all structured so you know when and how to use them.

Built for real construction projects — not generic paperwork.

Common pitfalls (and how to avoid them)

• Tick-box inspections: lots of “OK” with no detail.
  Fix: require at least a few specific observations each time (what was checked, where, what standard applied).
• No ownership: actions assigned to “subbie” or “site team”.
  Fix: name an owner (role + person where possible) and confirm they’ve accepted the action.
• No close-out evidence: actions marked “done” with no verification.
  Fix: record who verified, when, and add an after-photo for significant items.
• Too much paperwork: long forms that don’t get completed properly.
  Fix: keep the core record short; add detail only where risk demands it.
• Inspections don’t match the programme: checking the wrong things at the wrong time.
  Fix: align inspection themes to the lookahead and today’s high-risk activities.
• Findings not linked to controls: observations float without reference to RAMS, permits, or site rules.
  Fix: where relevant, reference the control (e.g., “hot works permit not displayed at point of work”).

Showing supervision and monitoring without over-paperworking

To evidence effective PC supervision under CDM 2015, use a “few strong signals” approach:

• Short daily checks captured as brief notes tied to high-risk activities and site standards.
• One structured weekly PC inspection that is consistent and covers core controls and interfaces.
• Action log discipline: owners, due dates, close-out verification, and repeat-issue tracking.
• Trend snapshots once a month: top recurring findings, overdue actions, and what changed as a result.

This combination usually produces better evidence than doing more forms with less follow-through.

FAQs

How often should a principal contractor inspect a construction site?
Set frequency based on risk, complexity, and project phase. A common baseline is daily task-focused supervisory checks, a structured weekly PC inspection, and a monthly review of trends and outstanding actions—then increase checks during high-risk activities, peak trade interfaces, and periods of change.

 

What should be recorded in a principal contractor site inspection?
Record the date/time, precise location, inspector, what was inspected, specific findings, priority, required actions, named owners, due dates, and close-out details (completed date/time, who verified, and evidence such as before/after photos). The record should clearly show “finding → action → owner → verification”.

 

Are photos required in site inspection records?
Photos aren’t always essential, but they’re very useful for demonstrating conditions at the time of inspection and confirming close-out—especially for significant issues. Keep photos relevant, captioned, and linked to individual findings rather than adding large unstructured photo sets.

 

What’s the biggest mistake with site inspections?
The biggest mistake is treating inspections as a tick-box exercise: vague “all OK” notes, actions without owners, and no close-out verification. Strong PC evidence comes from specific observations and disciplined action tracking, not from longer checklists.

 

How do you demonstrate monitoring and supervision under CDM 2015 as the Principal Contractor?
Use a consistent inspection routine that matches site risk, keep records that show what was checked and why, and maintain an action log with ownership and verified close-out. Add periodic trend review to show you’re learning from findings and improving controls over time.

Summary

A sensible PC inspection regime under CDM 2015 is risk-led: keep a steady baseline (daily focused checks and a structured weekly inspection), increase frequency when the work is higher risk or changing, and make records stand up by capturing specific findings, clear actions, named owners, and verified close-out—supported by relevant photos. The strongest evidence is usually fewer, better inspections with disciplined action tracking.

How we can help: If you want to tighten up inspection frequency, action tracking, and audit-ready site records, speak to CTC about practical CDM 2015 support (CTC supports compliance; legal duty remains with duty holders).

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.

Principal Contractor Support

Running a CDM Project as Principal Contractor?

Get the structure, advice, and documentation support you need to manage the role properly.

When you take on the Principal Contractor role, the responsibility for the Construction Phase Plan, site safety records, RAMS, and CDM compliance usually lands on the desk of a busy director or site manager.

CTC South West provides practical advisory support and structured systems that help you keep your documentation organised, your responsibilities clear, and your projects ready for client checks or audits.

Expert CDM support, site-ready documentation, and organised compliance records — all built around how construction projects actually run.

• Construction Phase Plans structured and ready for client review
• RAMS and project documentation tailored to your actual work
• Ongoing competent person support for Principal Contractors

Practical advice from experienced construction safety advisors — supporting SME Principal Contractors across the UK.