How a Principal Contractor Should Review Subcontractor RAMS (A Practical Workflow)

TL;DR

• Use a consistent, recorded workflow to stop “silent acceptance” of unsuitable subcontractor RAMS and reduce interface clashes on live sites.
• Log and version-control every submission (scope, area, dates, revision), then triage quickly for missing basics before detailed review.
• In the detailed check, focus on site specifics, sequencing and trade interfaces, supervision/competence, plant–pedestrian segregation, permits and verifiable controls.
• Record a clear outcome (accepted / accepted with conditions / returned), then gate the start on briefings and pre-start checks that prove controls are in place.
• Align the process to principal contractor duties cdm 2015, and manage mid-job changes through revision control and re-briefing.

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

On busy non-domestic sites, subcontractor RAMS can arrive late, look polished, and still miss the one detail that matters on your project: how the work interfaces with everyone else. One site manager told a familiar story—two trades turned up to the same corridor with incompatible plans for pedestrian routes. The RAMS were “signed off”, but nobody had checked the interface or briefed the revised segregation on the morning. The fix wasn’t complicated; it was having a consistent, recorded review process.

This guide sets out a practical principal contractor RAMS review process under CDM 2015, focused on how a PC can receive, check, accept, brief and control subcontractor RAMS once work is live. 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.

Where the RAMS review fits in PC duties (CDM 2015)

On non-domestic projects, the Principal Contractor should plan, manage and monitor construction work so it is carried out, so far as is reasonably practicable, without risks to health and safety. A consistent RAMS review process helps you:

• Confirm subcontractor proposals are workable in the site-specific context.
• Coordinate sequencing and interfaces between trades.
• Set clear expectations for supervision, plant and pedestrian segregation, permits and controls.
• Capture evidence of acceptance and briefing, then manage change control.

End-to-end principal contractor RAMS review process (workflow)

Use this workflow consistently across packages. It keeps decisions clear and prevents “silent acceptance” of unsuitable RAMS.

1) Receive and log the RAMS

• Allocate a unique reference (package / area / revision number) and record received date/time.
• Confirm it includes both the risk assessment and the method statement (plus supporting docs where relevant).
• Check it is the correct scope for the planned works, location and dates.
• Hold the start date until the RAMS are reviewed and briefed (avoid “start while reviewing”).

Evidence to keep: RAMS register entry, email trail / transmittal, revision history.

2) Triage for completeness (quick reject/return if needed)

Before you spend time on technical detail, confirm the basics are present and readable.

• Named subcontractor, responsible manager, and competent supervisor for the activity.
• Clear task description (what, where, when) and who is affected.
• Risk controls stated in a way that can be checked on site (not generic statements).
• Plant/equipment, access equipment, and any substances identified.
• Emergency arrangements aligned to site (first aid, fire, evacuation routes, muster point).

Outcome options: Accept for detailed review / Return for amendment / Reject as not applicable.

3) Detailed technical review (the “PC checks”)

This is the core of the principal contractor RAMS review process: verifying the RAMS work in your live site environment.

Site specifics and constraints

• Correct work area, access points, welfare, storage, and laydown arrangements.
• Known site constraints covered (restricted headroom, fragile surfaces, loading limits, noise/dust constraints, neighbours where relevant).
• Utilities and services interface: permit-to-dig, scans, isolations, temporary supplies.
• Work at height arrangements match site rules (edge protection, MEWP zones, rescue plan where relevant).

Sequencing and interfaces (trade coordination)

• Sequence is aligned to your short-term plan (lookahead) and other packages.
• Interfaces are explicitly addressed: who controls the area, who installs/removes protection, and when handovers occur.
• Simultaneous operations: what happens if other trades are present, and what triggers stopping work.
• Clear exclusion zones, signage, barriers, and who maintains them.

Supervision and competence

• Named supervisor on site and their responsibilities (briefing, checks, permits, stop-work triggers).
• Operative competence requirements fit the task (tickets/certs where relevant) and are checkable at induction or start-of-shift.
• Arrangements for new starters, agency labour, or substitution (how they will be briefed and recorded).

Plant, lifting and pedestrian segregation

• Plant routes and pedestrian routes are defined, feasible and match site layout and current conditions.
• Reversing controls, banksman requirements, and visibility constraints addressed.
• Loading/unloading, deliveries, and laydown: who manages traffic, booking-in, and peak times.
• Lifting plans/appointments addressed where lifting is involved (and referenced documents identified).

Permits, controls and verification

• Permits required are listed (e.g., hot works, confined space, excavation, energisation/isolation) and link to your site system.
• Controls are specific and measurable (e.g., barrier type, inspection frequency, air monitoring if applicable).
• Inspection/maintenance requirements are stated (scaffolds, MEWPs, lifting accessories, temporary works where relevant).
• Environmental controls are practical (waste, spills, dust suppression, noise management).

4) Decide the outcome: accept, accept with conditions, or return for revision

Avoid vague “approved” language. Record a clear outcome and any conditions.

• Accepted: Suitable as written for the planned date/area.
• Accepted with conditions: Suitable provided specified conditions are met (e.g., “only after barrier line installed and signed”, “only during agreed access window”).
• Returned for revision: Not suitable; list required changes, assign actions and a resubmission date.

Evidence to keep: marked-up RAMS, acceptance email/record, conditions list, action tracker.

5) Briefing and communication (make the RAMS real)

Acceptance is not the end. The PC needs to ensure the people doing and affected by the work understand the controls.

• Deliver a task briefing (ideally at the workface) covering key steps, controls, interfaces and stop-work triggers.
• Confirm who attended (including subcontractor supervisor) and how late arrivals will be briefed.
• Communicate interface impacts to others: logistics, neighbouring trades, and anyone affected by route changes or exclusion zones.

Evidence to keep: briefing record (names, signatures/confirmation, date/time, RAMS revision), photos of set-up (barriers/signage), daily coordination notes.

6) Control the start: pre-start checks on site

Before work begins, check that the controls described in the RAMS are actually in place.

• Work area set up as stated: barriers, signage, segregation, access/egress.
• Plant and lifting arrangements match the RAMS and any related plans.
• Permits raised and displayed/communicated as per site system.
• Correct PPE and equipment present and in serviceable condition.
• Supervisor present and actively managing the activity.

Evidence to keep: pre-start checklist note, permit references, photos, supervisor confirmation.

7) Monitor during delivery (RAMS-to-reality checks)

Monitoring should focus on whether critical controls remain effective as conditions change.

• Targeted inspections at change points: start-of-shift, after breaks, after deliveries, when interfaces change.
• Check exclusion zones are maintained and not “shrunk” for convenience.
• Confirm housekeeping, waste control and access routes remain clear.
• Record deviations and corrective actions promptly; close them out.

Tip: Use your inspection notes to reference the RAMS revision and the specific control being verified.

8) Change control: manage RAMS changes after work starts

Most RAMS issues arise mid-job when the plan changes. Treat changes as a controlled process, not informal tweaks.

• Define triggers for review: change of area, sequence, plant, access route, supervision, design detail, or simultaneous operations.
• Stop and reassess: pause the affected activity if the existing RAMS no longer matches reality.
• Update and re-brief: new revision issued, old versions withdrawn from use, and everyone re-briefed.
• Record the reason: what changed and why, plus who authorised the change and when.

Evidence to keep: revised RAMS, change log, re-brief record, photos of revised set-up.

What “good” acceptance evidence looks like (without paperwork overload)

You do not need unnecessary documents; you do need a clear trail that shows the PC reviewed, coordinated and communicated.

Process step	Useful evidence	What it proves
Receipt & logging	RAMS register with revision/date	You controlled versions and timing
Review	Marked-up RAMS / review notes	You checked site specifics and interfaces
Acceptance	Acceptance record with conditions (if any)	You made an explicit decision
Briefing	Attendance record + RAMS revision referenced	People were informed of controls
Pre-start	Photos and short pre-start note	Controls were in place at start
Monitoring	Inspection notes tied to critical controls	You monitored delivery, not just paperwork
Change control	Change log + re-brief record	You managed changes safely and traceably

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 failure points (and how the workflow prevents them)

• Generic RAMS: solved by site-specific checks and clear “return for revision” rules.
• Interfaces missed: solved by explicit sequencing and simultaneous ops checks.
• “Signed but not briefed”: solved by making briefing evidence a gate before start.
• Controls drift during the shift: solved by targeted monitoring and supervisor accountability.
• Changes unmanaged: solved by defined change triggers, revision control and re-briefing.

FAQs

What is the principal contractor RAMS review process meant to achieve?
The purpose is to confirm subcontractor RAMS are suitable for the specific site conditions, coordinated with other trades, and communicated so the work can be delivered as planned. For a PC under CDM 2015, it also creates a clear evidence trail of planning, management and monitoring in practice.

 

Can a principal contractor “approve” subcontractor RAMS?
In practice, PCs commonly record RAMS as accepted (sometimes with conditions) or returned for revision. What matters is that the decision is explicit, recorded, and linked to a specific revision, and that the RAMS are then briefed and monitored. Acceptance does not remove the subcontractor’s responsibility to work safely or the PC’s duty to manage and monitor.

 

What should a PC check first when reviewing RAMS?
Start with applicability and completeness: correct scope and location, clear sequence, named supervision, and site emergency arrangements. Then move to the high-impact checks: interfaces with other trades, plant and pedestrian segregation, permits/isolation requirements, and whether the controls are practical and verifiable on your site.

 

How do we record RAMS acceptance and briefings without creating admin overload?
Keep it simple and consistent: a RAMS register (including revision), a short acceptance record (and any conditions), and a briefing record that references the RAMS revision and attendees. Add a few photos of the initial set-up and short monitoring notes tied to critical controls. This creates a credible trail without duplicating documents.

 

What happens if the subcontractor changes the method mid-job?
If the method, sequence, area, plant, routes, supervision or interfaces change, treat it as a change control event. Pause the affected work if the RAMS no longer reflect reality, get a revised RAMS issued with a new revision, withdraw older versions, and re-brief those involved and affected before restarting.

 

Do we need to brief other trades on a subcontractor’s RAMS?
Where the activity affects others—routes, exclusion zones, deliveries, noise/dust, access restrictions, or simultaneous operations—yes. The PC’s coordination role includes ensuring impacted parties understand what will change and when, so the site plan remains workable and controlled.

Summary

A robust principal contractor RAMS review process is less about paperwork and more about consistent gates: receive and log, check site specifics and interfaces, record acceptance clearly, brief the workforce, verify controls at pre-start, monitor delivery, and manage changes through revision control and re-briefing. That workflow is what turns RAMS into real control on site under CDM 2015.

How we can help. If you want to tighten up your PC RAMS review workflow and evidence trail, CTC supports compliance; legal duty remains with duty holders.

Related reading: RAMS and Method Statements

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.