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.
37 Critical document templates for Principal Contractors: User Manual Index
Purpose and outcome (what it’s for)
The Daily Site Supervisor Logbook & Safety Notes is your day-to-day record of what happened on site and what you checked as Principal Contractor (PC) supervisor.
Good completion looks like: a short, factual record that shows who was on site, what work was done, what risks were checked, what changed, what permits/plant were used, and what actions were raised and closed. It should be clear enough that someone not on site that day can understand the key decisions and controls.
It supports day-to-day coordination and provides evidence for CDM 2015 monitoring, and it helps if you need to look back after a complaint, near miss, incident, or programme dispute.
Who uses it (roles and responsibilities)
| Role | What they do | What “good” looks like |
|---|---|---|
| Site Supervisor / PC Supervisor | Completes the logbook daily, raises actions, records changes and decisions. | Written as you go; clear facts; names, times, locations; actions owned and dated. |
| Site Manager / Contracts Manager (if you have one) | Reviews key issues, supports escalations, checks close-out. | Knows what changed, what risk controls were used, and what needs follow-up. |
| Subcontractor supervisors | Provide headcount, work areas, plant use, permits needed, and briefings delivered. | Information is consistent with their RAMS and what happened on site. |
| Client / Agent (if required by contract) | May sign or review specific days (high-risk work, changes, incidents). | Sign-off is selective and meaningful (not just a tick-box habit). |
| Administrator / Document controller (if applicable) | Files, scans, and keeps versions/records tidy. | Records are easy to find by project and date; nothing missing. |
When to use it (trigger points and frequency)
- Every working day you have people on site (including short visits if work is happening).
- Start of day: set up the day’s record (site details, emergency arrangements, plan for the day).
- During the day: update when things change (weather, interfaces, deliveries, permits, plant/lifting, stop work, issues).
- End of day: summary, actions, handover to tomorrow, and sign-off/filing.
- Always use it when you have: changes to sequence/access/design, high-risk work, new starters, lifting, hot works, digging, service isolations, or any near miss/incident.
Before you start (what you need to hand)
- Today’s plan: work schedule, deliveries, key interfaces (two trades in one area), any client constraints.
- RAMS in force: latest method statements/risk assessments for the tasks planned.
- Permits system (if used): permit pads/templates and permit references (hot works, dig, isolation, confined space, work at height, etc.).
- Site arrangements: emergency info, first aid provision, fire points, welfare setup, access/egress.
- Plant and lifting info: who is operating what, pre-use checks, any lift plan, slinger/banksman details, exclusions.
- Service info: drawings, CAT/Genny info, permits to dig, isolations/lock-off details.
- Contact chain: who to escalate to (manager, client/agent, temporary works designer/coordinator if applicable).
How to complete it (step-by-step on a real site)
Step 1 — Set up the day (2–3 minutes)
- Fill in site/day details (project, date, supervisor, start time).
- Confirm emergency arrangements are still correct for today (assembly point, access clear, first aider/fire marshal where applicable).
- List visitors (names/company) and why they’re there. If it’s a client visit, note any instructions given.
Step 2 — Record attendance and inductions (as people arrive)
- Record everyone on site, their company, trade, and work area.
- For new starters or anyone moved to a new work area/task: note they were inducted/briefed (and what was covered if it matters).
- If someone leaves early or a team changes, note it (helps explain programme changes and supervision levels).
Practical tip: keep the logbook with your sign-in sheet/board so you’re not trying to remember names at the end of the day.
Step 3 — Note weather and site conditions (and what you did about it)
- Write what matters: rain/wind/heat/frost and how it affected the job (e.g., “wind picked up 11:30 — stopped sheet lifting”).
- Record ground conditions and access (mud, ice, blocked routes) and any actions (grit, mats, reroute pedestrians).
- Confirm welfare is usable (toilets, water, drying/heating as needed).
Step 4 — Record work activities and areas (planned vs actual)
- List the main tasks and where they happened.
- Use the “what changed” notes for anything different (sequence change, different access, different kit, late delivery).
- If two trades share an area, note how you controlled it: time slots, barriers, one-at-a-time rule, spotter, separate access routes.
Step 5 — Do the key risk checks and write the findings
Ticking boxes isn’t enough on its own. Add short notes that show what you actually checked and what was done if something wasn’t right.
- Working at height: edge protection in place, scaffold tag status, ladder condition/angle/tie-off where relevant, MEWP checks, drop zone controls.
- Excavations & services: CAT scan done, permit to dig, edge protection, spoil placement, access/egress, supports/battering.
- Temporary works: props/needles in place, no unauthorised changes, exclusion where required.
- Traffic & plant: pedestrian routes, banksman, reversing controls, segregation, deliveries managed.
- Housekeeping: clear walkways, waste removed, nails/screws controlled, material stacked safely.
- Dust/noise/vibration: wet cutting, extraction, RPE use, restricted cutting times, neighbour controls.
Write actions like this: “Found trailing lead across access route at 10:15 — moved and taped; reminded team. Re-checked 14:00 OK.”
Step 6 — Record permits and authorisations (if any)
- For each permit issued/checked, record type, reference number, who it was issued to, time, and whether it was closed out.
- If you attach a permit copy, make sure the logbook references it (so you can match them later).
- If a permit was not needed (e.g., no hot works), leave blank or write “N/A” depending on your site rules—don’t invent entries.
Step 7 — Plant, equipment and lifting activity
- List key plant used (telehandler, excavator, dumper, MEWP, breakers, etc.) and the operator.
- Record pre-use checks and any defects (and what happened next: isolated, tagged out, repaired, replaced).
- For lifting: note lift plan in place, exclusion zone, and who acted as banksman/slinger. Record any changes made on the day.
Step 8 — Toolbox talks, briefings and changes to RAMS
- Record what briefing happened, who led it, and who attended (crew names or “all on site” if genuinely everyone attended).
- If RAMS changed: write what changed and how you briefed it. Note who approved it if approval was needed (e.g., manager, PC, temporary works coordinator).
Rule of thumb: if the way you do the job changed, the logbook should show how you kept it safe.
Step 9 — Issues, near misses, incidents and stop work
- Be factual: what happened, where, who was involved (names/companies), and the immediate action.
- Record who you reported to and when (especially for anything that could be RIDDOR, client-notifiable, or programme-critical).
- If you stopped work: note the reason and the controls agreed before restart (e.g., “new exclusion zone,” “revised lift plan,” “re-briefed RAMS”).
Step 10 — Actions list (keep it tight)
- Write actions so they can be closed: what, who owns it, due date, and closure (date/initials).
- Carry actions forward each day until closed. Don’t let the list reset daily.
- If an action becomes a bigger issue (design change, temporary works, service risk), escalate and note that escalation.
Step 11 — Supervisor summary and handover (end of day)
- Summarise the main controls that mattered today (not every small detail).
- Record what changed and why (weather, access, delivery delays, client request).
- Note key decisions and who agreed them (names, not “we decided”).
- Write the handover to tomorrow: what’s left, what needs checking first thing, and any restrictions.
Step 12 — Sign-off and file it
- Supervisor signs/initials at the end of the day.
- If your job requires it, get client/agent sign-off for specific days (major change, incident, high-risk work), not necessarily every day.
- Record where it’s filed and the record reference (so you can find it fast).
Review and approval (what checks are expected)
- Daily: Supervisor sign-off after the end-of-day summary.
- Weekly (recommended): Site manager/contract manager reviews for patterns and close-out:
- Repeated housekeeping issues
- Repeated permit gaps (e.g., digs without clear references)
- Recurring plant defects
- Actions overdue
- Frequent changes to RAMS (may signal planning problems)
- Escalate the same day if you record: unplanned service strikes/near strikes, uncontrolled work at height, lifting problems, temporary works concerns, or any injury/incident with potential for serious harm.
Recordkeeping (storage, version control, retention)
| What to do | Practical approach for small teams |
|---|---|
| File by project and date | Use a simple structure: Project > 04 Site Records > Daily Logs > YYYY-MM. |
| Keep originals readable | Write in pen, avoid jargon, don’t scribble over errors; cross out with a single line and initial if needed. |
| Scan/photograph daily (recommended) | If paper-based, take a clear photo at end of day and upload the same day. Name files YYYY-MM-DD_DailyLog. |
| Link related records | Reference permit numbers, lift plans, briefings, and incident report IDs so they can be matched later. |
| Retention | Keep for the project duration and a sensible period after completion for claims/incident review. Follow your company/client retention rules. |
How often it should be updated
- Minimum: once per day with end-of-day sign-off.
- Best practice: update it in short bursts:
- after the morning start/briefing
- after any permit is issued
- after any lift/dig/hot works activity
- when plans change
- after any issue/near miss
Common mistakes / pitfalls (and how to avoid them)
- “Ticked but no notes” — Add one short line of evidence for key risk checks, especially if something was fixed.
- Writing it all at the end of the day from memory — Keep it with you and write times as they happen (even rough times are better than none).
- No names / no owners — Decisions and actions need a person attached (who agreed, who will do it).
- Not recording changes to plan — If sequence/access/plant changes, write what changed and how it was controlled (and whether RAMS were updated).
- Permits recorded without references — Always include permit numbers/refs and whether they were closed.
- Actions list gets ignored — Review actions daily; carry forward until closed; set realistic due dates.
- Too much waffle — Keep it short and factual: what/where/when/who/what you did.
Worked example (quick scenario)
Scenario: Small refurbishment. Bricklayers and electricians both need the rear corridor. Weather turns wet and windy. A delivery arrives late. Hot works needed for a small steel bracket, and a near miss occurs with a trailing lead.
What good logbook notes look like:
- Work activities: “Brickwork to rear corridor AM. Electrician 13:00–15:30. Corridor one trade at a time; barrier at both ends.”
- Weather: “Heavy rain from 12:00 — moved cutting station inside; wet floor signs and mopping rota.”
- Permits: “Hot works permit HW-014 issued to J.Smith 14:10, fire watch set, extinguisher in place, closed 15:05.”
- Plant/tools: “110v transformer and leads checked; one damaged plug top found 10:15 — removed from service.”
- Near miss: “Trailing lead across access route at 10:10 — no injury. Lead rerouted overhead; briefed team; re-check 14:00 OK.”
- Actions: “Replace damaged plug top (Owner: electrician supervisor, Due: today, Closed: 15:30 JS).”
- Summary: “Main controls: segregation in corridor, wet weather controls, hot works permit/close-out, defective lead removed. Handover: corridor clear 08:00 tomorrow; check floor dry; confirm delivery slot.”
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
