How to Respond to Principal Contractor Comments on a RAMS
Getting a RAMS sent back with comments is frustrating, especially when you are ready to mobilise. But understanding why principal contractors (PCs) review your documents, and how to respond properly, will save you time and reduce the chance of it happening again.
Why the Principal Contractor Reviews Your RAMS
CDM 2015 applies to all construction work, not only to larger projects that must be notified to the HSE, and a principal contractor must be appointed whenever more than one contractor is involved. It places specific duties on that principal contractor to plan, manage and monitor the construction phase. Part of that role is ensuring that every contractor working on site has suitable controls in place before they start. Reviewing your RAMS is not a bureaucratic exercise; it is a legal function.
Your risk assessment sits under the Management of Health and Safety at Work Regulations 1999, regulation 3. The method statement is the operational companion that shows how those controls are applied on the ground. The PC needs confidence that both are suitable and sufficient for the specific site and task.
Common Reasons a RAMS Gets Sent Back
Understanding the typical reasons for rejection helps you address the right problem:
- Generic content. A template that has not been adapted to the actual site, task or environment. If your RAMS could apply to any job anywhere, it needs more work.
- Vague controls. Statements like "operatives will take care" or "PPE will be worn" without specifying what, when or how.
- Hierarchy not followed. Controls jump straight to PPE without considering elimination, substitution or engineering measures first.
- Missing site-specific hazards. Nearby services, overhead cables, public interfaces, confined spaces or specific substances not addressed.
- Substance hazards not covered under COSHH. If your work involves hazardous substances, the RAMS should reference a suitable assessment under the Control of Substances Hazardous to Health Regulations 2002.
- Work at height not addressed properly. The Work at Height Regulations 2005 require that work at height is avoided where reasonably practicable, then that collective protection is prioritised over personal protection. If your method goes straight to harnesses, expect a question.
- Signatures or version control missing. Many PCs require named supervisors, operative sign-off records, and a revision number.
How to Read the Comments Carefully
Before you respond, read every comment in full. Some feedback will be a hard stop, meaning you cannot start work until the point is resolved. Other comments may be requests for clarification or minor additions.
Categorise the feedback:
- Points where the PC is right and you need to revise the content.
- Points where your document is actually adequate but poorly explained.
- Points that reflect a misunderstanding of your scope, which you can resolve with a short written clarification.
Do not send a one-line reply saying "updated." Address each comment directly, either by revising the document or by explaining in writing why the existing approach is suitable.
Making the Revisions
When you revise, be specific. Vague language is the most common reason a RAMS fails review.
Replace this: "Workers will wear appropriate PPE." With this: "All operatives will wear EN 388-rated cut-resistant gloves, safety boots to EN ISO 20345 S1P, and safety glasses to EN 166 during cutting operations."
Apply the correct hierarchy. For each significant hazard, work through:
- Can you eliminate the hazard entirely?
- Can you substitute a safer method or material?
- Can an engineering control reduce the risk (guarding, local exhaust ventilation, edge protection)?
- Can administrative controls reduce exposure (permits, task rotation, exclusion zones)?
- Only then, PPE as a last layer.
If you are keeping PPE as a control, state the standard it must meet and confirm it is provided and checked before work starts.
For site-specific hazards flagged by the PC, do not just add a line to a generic list. Write a short paragraph addressing the actual hazard on that site, the realistic likelihood of harm, and the specific control you will apply.
Submitting the Revised RAMS
When you send the revised document back:
- Include a short covering note or comment log that maps each PC comment to your response. This saves the reviewer significant time and shows you have engaged properly.
- Increase the version number and update the revision date.
- If the method has changed materially, brief your team again and get fresh signatures before work starts.
- Keep a copy of the original submission, all comments, and the revised version. If there is ever a dispute or an incident, that audit trail matters.
If You Disagree with a Comment
If you believe the PC's comment is based on a misunderstanding of your trade or scope, say so professionally and in writing. Explain the technical reason your existing control is appropriate. Reference the relevant regulation or guidance if it helps, for example citing HSE guidance or a relevant British Standard.
What you should not do is ignore the comment or submit an unchanged document hoping it slips through. That approach wastes time, damages the working relationship, and could leave you exposed if something goes wrong on site.
Avoiding It Next Time
The best way to handle PC comments is to reduce how often you receive them. Before you submit:
- Confirm the site-specific hazards with the construction phase plan or a pre-start visit.
- Check whether the project involves notifiable work, public proximity, or specific hazards that need extra treatment.
- Have a competent person review the RAMS before it goes in, not after it comes back.
A well-prepared, site-specific RAMS that follows the correct control hierarchy rarely comes back with significant comments. When it does, a clear and direct response resolves it quickly.