Common RAMS Mistakes UK — Avoid These 8 Errors

By the Riskora Editorial Team · Reviewed against our editorial standards · Last reviewed

Principal contractors reject RAMS submissions every day for the same avoidable mistakes. Here are the eight most common errors — and how to make sure your documents don't get sent back.

Under 5 minutesNo training neededPDF download

UK (RAMS) example document — Two-Storey Rear Extension — 14 Birchwood Lane, Reading. Client: Mr & Mrs A. Whitfield (Private Client). Site: 14 Birchwood Lane, Reading, RG1 5JT. Scope: Construction of a two-storey rear extension (6.4m × 4.2m) to an existing semi-detached dwelling. Works comprise breaking out of existing rear elevation, trench-fill foundations to 1.0m, traditional cavity blockwork to first floor, pre-stressed concrete lintels, timber roof structure with natural slate finish, plus alterations to existing rear wall to form structural opening with rolled steel joist (RSJ 203×102 UB23). Works programmed over 9 weeks with a peak site team of 6 operatives. Hazards assessed: Manual handling — blocks, lintels, plasterboard, Working at height — independent scaffold & roof structure, Buried services strike during excavation, Collapse of excavation / trench wall, Hand-arm vibration (HAVS) — breaking out, drilling, Silica dust — cutting blocks, brick, concrete, Vehicle/pedestrian segregation — narrow domestic street.

Example UK (RAMS) front cover produced by Riskora
Try the new compact mode. Same document, just more compact

Full version

Start Your RAMS Now — It's Free

Takes less than 5 minutes

No card required · 1 free PDF · Upgrade any time (completely free)

What are the most common RAMS mistakes?

The most common RAMS mistakes are: 1) Using generic templates without site-specific adaptation, 2) Copy-pasting from previous projects without review, 3) Missing key hazards for the specific work type, 4) Vague control measures ('work safely'), 5) No method statement steps, 6) Wrong project details, 7) Missing sign-off sections, 8) Not reviewing after changes.

Rejected RAMS Cost You Time and Money

A rejected RAMS means delayed site access, wasted admin time, frustrated clients, and potential loss of work. Most rejections are for basic errors that could have been avoided — wrong project details, missing sections, or clearly generic content that wasn't adapted for the actual job. Understanding the complete guide to RAMS in the UK helps frame why proper documentation matters.

How Riskora Helps

Riskora's structured builder prevents the most common mistakes by guiding you through each required section. Pre-loaded hazards ensure you don't miss critical risks, and the step-by-step method builder creates a proper work sequence rather than vague safety statements. Try the RAMS generator to see how quickly you can produce professional documentation.

Who it's for

  • Contractors whose RAMS have been rejected
  • Teams wanting to improve document quality
  • New contractors learning RAMS requirements
  • Anyone tired of resubmitting documents

Why do RAMS get rejected?

RAMS are typically rejected because they're too generic (clearly a template that hasn't been adapted), missing site-specific hazards, contain incorrect project details (copied from a previous job), lack a proper method statement with sequential steps, or are missing required sections like emergency procedures.

How do I avoid RAMS being rejected?

Make every RAMS specific to the actual project: correct site details, hazards relevant to the work and location, control measures that are practical (not just 'be careful'), method steps that describe your actual work sequence, and a complete sign-off section. Using a guided builder like Riskora ensures all sections are covered.

Key Risks and Considerations

  • Using another project's RAMS without updating details
  • Generic hazards that don't match the actual work
  • Vague control measures with no practical detail
  • Missing emergency procedures or contact information
  • No version control or review dates
  • Incomplete sign-off sections
  • Method statement that doesn't match risk assessment
  • Outdated regulatory references

Key Features

  • Guided builder prevents missing sections
  • Pre-loaded hazards reduce omissions
  • Project details captured upfront
  • Method statement step builder
  • Professional formatting throughout
  • Review checklist before download

Example Structure (UK Standard)

  1. ✗ Bad: 'Workers will work safely at height'
  2. ✓ Good: 'Edge protection (minimum 950mm guardrail) installed before roof access. Workers to wear full harness with twin-tail lanyard clipped to designated anchor points. Exclusion zone established 2m from building perimeter at ground level.'
  3. ✗ Bad: 'PPE will be worn'
  4. ✓ Good: 'Hard hat (EN397), hi-vis vest (EN20471 Class 2), steel toe boots (EN20345 S3), safety glasses (EN166), gloves (EN388 Level 4)'
  5. ✗ Bad: 'Work will be carried out in accordance with regulations'
  6. ✓ Good: 'Scaffolding erected to TG20 standards by CISRS-carded scaffolders. Scaffold inspection by competent person before first use and every 7 days thereafter (recorded on ScafTag)'

Common Questions Before Getting Started

Will this take long?

Under 5 minutes. Select your trade, pick hazards, download.

Is it complicated?

No training needed. The guided builder walks you through every step.

Do I need experience?

If you know what work you're doing, you can use Riskora.

Is it free to try?

Yes. The Free plan needs no card — generate, review and download one free PDF. Upgrade any time for branding, DOCX, sign-off and higher limits.

Create your RAMS in under 5 minutes

No onboarding or setup needed — start generating documents instantly

Try Riskora Free

No card required · 1 free PDF · Upgrade any time (completely free)

Used by contractors and professionalsNo learning curveDocuments ready in minutes
Built for real job scenarios · Used by UK contractors and professionals

All documents generated by Riskora should be reviewed by a competent person before use on site. Riskora provides structured templates — professional judgement is always required.

Inside the document

What your RAMS actually contains

Riskora builds a structured, client-facing document — not a generic AI paragraph. Every section is shaped around your job, your site and your team.

  • Hazards

    Task-specific hazards for the job, captured row by row — not a generic list pulled from an old RAMS.

  • Controls

    Control measures mapped to each hazard with residual risk scoring after controls are applied.

  • PPE

    PPE requirements tied to the activity and site, ready to brief to the team.

  • Method steps

    Step-by-step method statement structured around how the work is actually sequenced on site.

  • Emergency arrangements

    First aid, rescue plan, emergency contacts and site-specific escalation routes.

  • COSHH prompts

    Substance prompts when the work involves chemicals, dusts, fumes or sealants — flagged early, not missed at review.

  • Sign-off

    Operative sign-off captured against the document — names, dates and acknowledgement of the brief.

  • Version history

    Every change tracked so you can show what was issued, when, and which version the team signed.

  • Approval status

    Clear approval state on every document — draft, in review, approved, issued — visible across the team.

  • Audit trail

    Who created it, who reviewed it, who signed it. A complete trail you can hand to a principal contractor or auditor.

Before & after

From copied-and-pasted to site-specific

The reason RAMS get rejected is rarely the format — it's that the document is obviously generic. Riskora rebuilds it around this job, this site and this task.

Before

Generic template copied from an old job.

  • • Hazards and controls that don't match this site or task.
  • • Method steps written for a different sequence of work.
  • • No emergency arrangements specific to the location.
  • • Client flags it as generic and asks for a rewrite.
After

Site-specific document structured around this job, site and task.

  • • Hazards captured from the actual scope you pasted in.
  • • Method steps sequenced for how the work runs on site.
  • • Emergency arrangements and rescue plan tied to the location.
  • • Approved internally, briefed to the team, signed off and stored.
How it works

From job details to signed-off document

A four-step workflow used by contractors, consultants and safety teams to turn informal job details into client-ready safety paperwork.

  1. 1
    Paste job details

    Drop in a client email, a WhatsApp from the site manager, a scope of works or a tender note. Anything that describes the job.

  2. 2
    Riskora structures the document

    Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.

  3. 3
    Review, edit and download

    You stay in control of every section. Tweak anything, then download a clean PDF or share a link.

  4. 4
    Brief the team and record sign-off

    Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.

Built for site reality

Built by people who've written this paperwork on real sites

Riskora is built by a founder with hands-on site and document experience — designed for contractors, consultants and safety teams who need to issue, brief and prove safety paperwork without losing a day to admin.

  • Built for contractors, consultants and teams
    Solo trades, principal contractors and in-house safety teams all run on the same workflow.
  • Supports multiple countries
    UK, Ireland, Australia, New Zealand, US and Canada — wording and document types match the local standard.
  • Not just documents
    Sign-off, approvals, version history and an audit trail — the management workflow around the paperwork.

Frequently Asked Questions

Specific enough that someone reading it could understand what work is being done, what hazards exist on that particular site, and what controls are in place. If your RAMS could apply to any project without changes, it's too generic.

Yes. The guided builder ensures all required sections are completed, pre-loaded hazards prevent omissions, and the structured format produces consistent, professional output every time.

RAMS as a single document is not named in UK law, but the underlying duties are. The Management of Health and Safety at Work Regulations 1999 require a suitable and sufficient risk assessment, and CDM 2015 effectively requires a written method statement on most construction work. A RAMS satisfies both in one document, which is why principal contractors expect to see one.

Anyone competent to assess the risks of the work. Most subcontractors write their own RAMS for the tasks they carry out — formal qualifications aren't required, but the writer needs to genuinely understand the hazards, the controls and the site. Principal contractors will reject documents that look like they were written by someone who hasn't done the job.

Long enough to cover every hazard and method step honestly — usually 4 to 12 pages. Short, vague RAMS get rejected. Padded ones get skim-read on site, which defeats the point. Aim for specific, not lengthy.

At minimum: before each new site, after any significant change to the work, and after any near-miss or incident. Many principal contractors also expect a documented annual review even if nothing has changed.

Ready? It takes less than 5 minutes.

No training. No complex setup. Just select your trade and go.

Start Your RAMS Now — It's Free

No card required · 1 free PDF · Upgrade for branding, DOCX, sign-off and audit trails (completely free)

Already have a RAMS? Upload and rebuild it

References & Further Reading

Primary UK sources covering the legal and practical framework behind RAMS, risk assessments and method statements.

Free RAMS builder

Create your RAMS free — preview before sign-up

Generate a preview first. Sign up only when you want to save, edit or export.

Final RAMS must be reviewed and approved by a competent person before use.

Riskora is an assistive document preparation tool. All documents generated must be reviewed, verified, and approved by a competent person before use on site. Riskora does not replace professional safety judgment, and no output should be treated as a legal compliance guarantee.