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
This form is a simple gate check to make sure a subcontractor’s RAMS (Risk Assessment & Method Statement) is good enough for this job, on this site, at this time—before anyone starts.
Good completion looks like:
- The RAMS matches the actual scope, location, programme and site rules.
- Real hazards are listed and controls are practical (not just “wear PPE”).
- Permits, drawings, certificates and plans are identified and attached where needed.
- Clashes with other trades and the public are planned out.
- Any required changes are clearly written, owned, and closed out.
- A clear decision is recorded: ✅ approved / ⚠️ approved with conditions / ⛔ not approved.
Who uses it (roles and responsibilities)
| Role | What they do |
|---|---|
| Main contractor site supervisor / foreman | Leads the check, walks through the RAMS against site conditions, records Pass/Fix/N/A, sets start conditions, and controls the “no start until approved” rule. |
| Project/Site manager | Supports the supervisor, checks higher-risk items, confirms programme/interfaces, and signs off if your company rules require manager approval for higher risk work. |
| Subcontractor supervisor (lead person) | Provides the RAMS and evidence, accepts actions, updates/reissues RAMS when required, briefs their crew, and signs acknowledgement. |
| H&S advisor (if you have one) | Helps with higher-risk/complex works, checks that controls are suitable and proportionate, and advises on permits and documentation. |
| Operatives | Must be briefed before starting and follow the agreed method. They should understand the stop-work rule if the job changes. |
When to use it (workflow and triggers)
- Before the subcontractor starts on site (ideal: 48–72 hours before start so there’s time to fix issues).
- Before any high-risk activity begins (e.g., hot works, excavation, lifting, roof work, isolations).
- Whenever the job changes: scope, sequence, access, work area, programme, people, plant, materials, weather, or another trade clashes.
- After an incident/near miss where the method or controls may need changing.
Simple rule: if you wouldn’t be comfortable briefing it to a new starter, it’s not ready.
Before you start (what you need to hand)
- The subcontractor RAMS document (with title/reference, version and date).
- Scope info: drawings/marked-up plan, work location/area, start date, duration, working hours, and any restrictions.
- Site rules and constraints: access route, traffic plan, welfare, deliveries, noise/dust limits, neighbours/public areas, fire arrangements.
- Programme and coordination info: what other trades are doing nearby and when.
- Evidence/attachments where relevant (as applicable to the work):
- Training/tickets list for the crew (and copies if you require them).
- Plant/equipment details and current inspection records (e.g., LOLER/PUWER, harness checks, MEWP records).
- COSHH/SDS for products and the planned controls (storage, ventilation, spill kits, etc.).
- Permit requirements and supporting plans: hot works permit, permit to dig and service scans, lifting plan, rescue plan for work at height/confined space, isolation plans.
- Asbestos survey / confirmation where there is any chance of disturbing the fabric.
How to complete it (step-by-step)
Step 1: Fill in the job and RAMS details (Section 1)
- Use the same site name/area that your programme and permits use (avoid vague locations like “site”).
- Check the RAMS version/date. If it’s undated or “template” style, treat it as a red flag.
- Confirm the subcontractor supervisor name and number of operatives—this matters for supervision, rescue plans and welfare.
Step 2: Do the quick gate check against real site conditions (Section 2)
Work through each line and tick Pass ✅, Fix ⚠️ or N/A. Keep notes short but specific.
- Scope matches the job: correct work content, exact area, dates, and constraints.
- Sequence is clear: it should read like “what we do first, then next…” not a generic paragraph.
- Interfaces covered: ask “who else is near us?” including deliveries, occupied areas, the public, and other trades.
- Hazards and controls: controls must be doable on your site (space, access, power, working at height equipment).
- Permits and attachments: if the RAMS says “permit as required” then confirm exactly which permit and when it will be issued.
- Programme fits: check the RAMS method matches the plan (e.g., curing times, access closures, lifting windows).
If anything is “Fix”: do not approve to start. Log the change in Section 6 and request a revised RAMS.
Step 3: Check high-risk activities (Section 3)
- Tick what is in scope. If it’s in scope, confirm a permit/plan is needed and will be in place.
- Use the notes line to record the key control that makes it safe (e.g., “Permit to dig + CAT scan results attached + trial holes by hand”).
- If multiple high-risk items apply, consider a short pre-start meeting with the subcontractor supervisor and your site manager.
Step 4: Confirm documents/attachments are present (Section 4)
- Tick “Provided” only when you’ve actually seen it (not “they’ll email it later”).
- If something is genuinely not relevant, tick N/A (don’t leave blanks).
- If you require specific formats (e.g., LOLER within 6 months), check dates and keep copies with the RAMS pack.
Step 5: Set briefing and start conditions (Section 5)
- Make sure the subcontractor will brief their whole crew, not just the supervisor.
- Write any “start restrictions” clearly (e.g., “No cutting/grinding until hot works permit issued” or “No breaking ground until scan completed and marked out”).
- Agree daily coordination: who controls changes, and how clashes are raised (especially on small sites where plans change quickly).
Step 6: Record changes and close them out (Section 6)
- Write actions so there’s no doubt what you want changed (avoid “improve WAH controls”; instead write “Specify edge protection type, installation method, and rescue plan”).
- Assign an owner (named person) and a due date.
- Only tick “Done” when the revised RAMS is received and checks are satisfied.
- Record the new RAMS version/date so everyone is using the same document.
Step 7: Make the approval decision (Section 7)
- Approved to start ✅: everything is acceptable and all required permits/plans are ready.
- Approved with conditions ⚠️: use this only for minor conditions that don’t change the safe method (e.g., “briefing must be completed before start”, “barriers to be installed first”).
- Not approved ⛔: use this if the method is unclear, hazards/controls are weak, permits/attachments are missing, or the job clashes with site constraints.
- Record where the approved RAMS pack will be kept on site (so supervisors can access it during checks).
Step 8: Sign-off and acknowledgement (Section 8)
- Main contractor reviewer signs to confirm the gate check is done and the decision is clear.
- Subcontractor signs to confirm they accept the method/conditions and will brief their team.
- Use the reminder: if the job changes, stop and review before continuing.
Review and approval (what “good” looks like)
- Reviewer checks: Does the RAMS fit the site, the programme and the real risks? Are controls specific and workable? Are high-risk items properly planned?
- Escalate for extra review if any of these apply:
- Multiple high-risk activities (e.g., excavation + lifting + work at height).
- Unclear responsibilities (who is in charge on the day).
- Public/occupied building interface, tight city-centre logistics, or live services.
- RAMS is generic, copied, or doesn’t mention your site rules.
Golden rule: if you can’t describe the safe sequence in a short briefing, it’s not ready to approve.
Recordkeeping (storage, version control, retention)
- Keep the approved RAMS and the completed RAMS Review & Approval Form together as one “RAMS pack”.
- Store a copy where it is easy to access during the job (site file/folder) and keep a controlled copy in your project records (digital folder).
- Version control: only one RAMS version should be live on site. Remove/mark old versions as superseded to avoid confusion.
- Retention: keep with the project H&S file for a period that matches your company/client requirements (commonly the full project plus a set retention period). Be consistent across jobs.
- Audit readiness: the pack should show: what was checked, what was changed, who approved, and what conditions applied.
How often to review or update
- At minimum: once before start, and again whenever there is a change to the job or conditions.
- For longer jobs: re-check at key stages (e.g., new phase, new work area, different plant, change of supervisor/crew).
- After any near miss/incident: confirm the RAMS is still suitable and brief the update.
Common mistakes (and how to avoid them)
| Common pitfall | How to avoid it |
|---|---|
| Approving generic RAMS that doesn’t match the site | Check the work area, access, site rules, and interfaces. If it could be used on any job, send it back for site-specific detail. |
| PPE listed as the main control | Look for higher-level controls first (segregation, edge protection, extraction, isolation). PPE should be the last line, not the plan. |
| “Permits as required” with no clarity | Make permits specific: which permit, who issues it, and what must be in place before work starts. |
| Missing attachments (tickets, LOLER, COSHH, plans) | Use the attachments section as a hard check. Don’t tick “Provided” until you’ve seen it. |
| No clear sequence or setup steps | Insist on a step-by-step method including setup, exclusion zones, checks before start, and end-of-day make safe. |
| Changes agreed verbally but not recorded | Write actions in the changes section with owner and due date. Get a revised RAMS version/date. |
| Work starts before briefing is done | Make briefing a start condition and check it happened (sign-on/brief record). No brief = no start. |
| Old versions left in the site folder/van | Keep one “live” RAMS pack. Remove or stamp old versions as superseded. |
Worked scenario (what “good” looks like on a real site)
Job: Subcontractor to core drill and install new pipework supports in a live commercial unit. Other trades working nearby.
- The supervisor reviews the RAMS using the form. The scope is mostly right but the hazards section is generic and doesn’t mention dust control or neighbours.
- Gate check marks Fix ⚠️ for: dust/noise control, work area setup, and interface with occupants.
- Actions are written: “Add wet drilling/vac extraction and RPE selection; specify screening and signage; agree noisy works time window; include waste removal route.” Owner is the subcontractor supervisor, due next day.
- Revised RAMS received with a new version/date. Attachments include SDS for resin anchors and details of extraction equipment.
- Approval decision is Approved with conditions ⚠️: “Barrier and signage must be up before drilling; supervisor to brief all operatives; noisy works only 10:00–12:00.”
- RAMS pack is kept in the site folder and used for the pre-start briefing. Supervisor checks compliance during the shift.
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
