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.

37 Critical document templates for Principal Contractors: User Manual Index

Purpose and outcome

What it’s for: The Building Control Inspections & Queries Log is your single place to plan inspections, request them, and record what Building Control (BC) said and what you did next.

What “good” looks like: At any time you can show (1) what’s been inspected, (2) what’s coming up, (3) what issues are still open, and (4) the exact evidence that closed each issue. Nothing important is only in someone’s inbox.

Why it matters: It supports a controlled compliance trail and makes completion smoother. It also helps demonstrate proper planning, oversight, and evidence management expected under Building Safety Act 2022 dutyholder working (plain English: you can prove what you did and why).

Who uses it (simple roles)

Role	What they do in the log	Typical frequency
Log owner (usually Site Manager)	Keeps the log up to date, raises inspection requests, records outcomes, chases actions/queries, keeps evidence references tidy.	Daily updates + weekly review
Working Supervisor / Foreperson	Flags “before cover-up” items, confirms what was installed, supplies photos and site details, confirms fixes are done.	Before/after key work stages
QS / Contracts / Admin support (if you have it)	Files emails/letters, labels evidence, maintains the evidence pack structure.	As items come in
Subcontractor leads (e.g., drainage, fire stopping, M&E)	Provide certificates, test results, manufacturer details, photos, commissioning records; confirm dates and locations.	At install + completion
Project Lead / Director	Checks open actions/risks, supports escalations, agrees approach on tricky compliance points.	Weekly/fortnightly
Principal Designer / Lead Designer (where involved)	Supports technical responses and design clarifications; helps with queries and “what detail applies here?” issues.	When queries/design changes arise

When to use it (trigger points)

At start of job: set up project details and an initial inspection plan.
Before key stages: when work is about to be covered up (e.g., drainage, DPM, fire stopping).
Every time you contact BC: inspection booking, phone call that changes an approach, email advice, site visit.
Every time BC raises actions: log them as actions and track them to closure with evidence.
When you need a decision: substitutions, awkward details, “is this acceptable?”, deviations, or where drawings/spec are unclear.
Weekly: do the 10-minute snapshot review in your site meeting.
At completion: use the log to confirm all actions are closed and evidence is findable.

Before you start (what you need to hand)

BC details: Building Control Body name, surveyor contact, reference/application number, preferred booking method and notice period.
Programme: key dates and sequence (so you can plan inspections without holding the job up).
Latest drawings/spec: including revisions that affect compliance.
Common evidence sources: photo process (who takes them, where stored), certificates route (who collects), and where tests/results are saved.
Site location naming: a simple way to describe locations (plot number, floor/room, gridline, elevation) so entries aren’t vague.

Tip: Decide early how you will label evidence (e.g., EV-01, EV-02). It saves hours later.

How to complete it (step by step)

Step 1: Set up the header details (once, then keep current)

Fill in project name/address, client, PC/PD details, BC contact, reference number, start and planned completion.
Nominate a log owner (name + role). One person should “own” updates.
Set the version/date issued. If you update the template structure, bump the version.

Step 2: Build the Inspection Plan (what you expect to need)

List likely inspection items for your project and add trigger points (e.g., “before concrete pour”, “before backfill”, “before boarding”).
Add planned dates based on the programme, then update “requested date” when you book it.
Keep it live—if the programme moves, update the plan so BC isn’t called at the last minute.

Good practice: Add a note for anything “must not be covered” until inspected (or until you have photos/test evidence agreed).

Step 3: Log each inspection request and the outcome (main record)

Create a new inspection entry as soon as you request a visit (don’t wait for the inspection date).
Use a clear Area/location (e.g., “Plot 3, GF rear extension, drainage run to MH2”).
In “What was inspected”, write what BC actually saw (not just “drainage”).
Record the outcome (Pass / Actions / Revisit) and the key comments.
If BC gives you actions, create an Action ID for each issue and link it back in the inspection row.

Rule of thumb: If it could cause rework, delay, or an argument later, it goes in the log.

Step 4: Raise actions and close them out with evidence (noncompliances & actions)

For each issue, create an Action ID with date raised, exact location, and a clear description of what’s wrong.
Add the owner (named person or subcontractor lead) and a realistic due date.
Track status: Open → In progress → Closed.
When closing: write what was done and record evidence provided (photos, certs, test results, marked-up drawing, etc.) with an evidence reference.
Record accepted by and the acceptance date (BC, design lead, or competent person as appropriate).

Keep it tight: Avoid “sorted” or “done”. Write what changed and what proves it.

Step 5: Use the Queries & Decisions section to stop “lost in emails”

Raise a query when you need a decision or acceptance (substitution, alternative detail, unclear spec, non-standard build-up).
Write the question so it can be answered Yes/No or with clear conditions.
List exactly what you sent (drawing number, photo set, datasheet, marked-up detail).
When the response comes back, copy the key wording into the decision notes and record any conditions (e.g., “provide photo before closing”, “install to manufacturer detail X”).

Practical tip: If a call happens, email BC straight after: “As discussed today, you confirmed X is acceptable provided Y.” Then log it and file the email.

Step 6: Maintain the Evidence Index so you can find things fast

Give each evidence item a simple reference (EV-01, EV-02…).
Use the same EV reference in inspection/action/query entries.
Write where it is filed (folder path, file name, binder section).

Minimum standard: Anyone on the team should be able to find the evidence in under 2 minutes using the reference.

Step 7: Do the Weekly Snapshot (10 minutes, no excuses)

Confirm inspections done this week and what’s booked for the next 2 weeks.
List open actions and who owns them.
List queries awaiting response and chase dates.
Call out anything that will be covered up soon and needs photos/BC sign-off first.

Output: A short, clear list of what must happen next week to avoid rework or delays.

Review and sign-off (what to check)

This log is mainly a working record, but it still needs basic governance.

Weekly review: Site Manager + Supervisor (and subcontractor leads if actions are piling up).
Monthly/phase gate check: Project Lead/Director reviews open actions, repeated issues, and any risky “verbal agreements”.
Before cover-up: Supervisor confirms photos taken and filed (with EV refs) for anything that will be hidden.
Before completion/final: Project Lead confirms: no open actions, all BC decisions captured, evidence pack complete and tidy.

Escalate when: BC rejects an approach, you can’t meet a condition, a response is delayed and will stop the programme, or an issue could affect sign-off/completion.

Recordkeeping (storage, version control, retention)

Where to store: Keep the log in the project’s Building Regulations evidence pack (digital folder and/or site file). Use one controlled location.
File the proof: Save emails/letters, photos, certificates, test results, drawings, and sign-offs in the same evidence pack and link them with EV references.
Version control: Only one live copy. If you issue an updated version, note the version/date and replace the old one (or archive it clearly).
Retention: Keep it with project handover/completion records for as long as your organisation retains Building Regulations compliance evidence (follow your company policy and any client/contract requirements).

How often to update

Immediately after an inspection is requested (so bookings aren’t forgotten).
Same day as an inspection outcome or BC contact that changes what you’re doing.
Within 24–48 hours of receiving certificates/test results (log the EV ref and file it).
Weekly minimum using the snapshot review, even on small jobs.

Common mistakes (and how to avoid them)

Leaving it until the end: you’ll miss dates, actions, and evidence. Fix: update as you go; make it part of the weekly site meeting.
Vague locations: “bathroom” or “rear” isn’t enough. Fix: use plot/floor/room/gridline/elevation.
One row covering lots of issues: things get lost. Fix: one issue = one Action ID.
No evidence reference: you “know you’ve got it” but can’t find it. Fix: every closure needs an EV ref and a filed location.
Relying on phone calls: decisions disappear. Fix: confirm by email, paste key wording into the Decision Notes, then file the email.
Closing actions without acceptance: you think it’s done, BC doesn’t. Fix: record who accepted it (BC or competent person) and when.
Not spotting “before cover-up” moments: leads to opening up finished work. Fix: use the weekly snapshot question “Anything that must be evidenced before cover-up?”

Worked scenario (what good looks like in practice)

Scenario: Drainage installed to rear extension. It will be backfilled tomorrow.

Inspection plan: You already listed “Drainage (pre-cover)” with trigger “before backfill”.
Request: You create an inspection entry when you book BC in (date requested + planned inspection date + location “Plot 7, rear run to MH1”).
Outcome: BC attends and says: “Provide photo of bedding and confirm fall; also fit rodding access at change of direction.” You record “Actions”.
Actions: You create two Action IDs (one for rodding access, one for photo/fall confirmation). Owner = drainage subcontractor lead. Due date = today.
Evidence: You take dated photos with a tape measure and level/fall note, save them, and log them as EV-03. You also photo the new rodding access and log EV-04.
Close-out: You update the close-out table: what was done + EV refs. BC confirms acceptance by email; you paste the key line into the decision/notes and file the email under the EV reference.
Weekly snapshot: You list the inspection ID, confirm actions closed, and note “OK to backfill” with evidence filed.

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.