RAMS for London Construction Sites

By the Riskora Editorial Team · Written to our editorial standards

London is the most regulated construction environment in the UK. Beyond the standard CDM 2015 and HSE expectations, every site sits inside at least one borough's planning conditions, often a TfL red-route permit zone, frequently a Section 61 prior consent area for noise, and increasingly the Ultra Low Emission Zone (ULEZ) for plant and deliveries. A RAMS that doesn't acknowledge this layered framework rarely makes it past induction.

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 in seconds

Describe the job — we'll start the RAMS for you

Free plan — generate, review and download one PDF. No card needed.

What's different about RAMS for London projects?

London RAMS need to address the borough's planning conditions, any Section 61 noise consent, TfL highway permits where the site abuts a Red Route, ULEZ-compliant plant declarations, and (for many central sites) Considerate Constructors Scheme commitments. The HSE-aligned core is the same — what changes is the planning, environmental and traffic-management layer wrapped around it.

Why generic RAMS fail in London

A boilerplate UK construction RAMS will get rejected on most central London sites. Principal contractors and CDM coordinators look for explicit references to the local conditions: TfL lane rental fees, the borough's permitted working hours, NRSWA Section 50 licences for any utility opening, ULEZ-compliant vehicle declarations for deliveries, and (for sites near the Underground) LU Asset Protection consultations. Without these, a competent reviewer will assume the contractor hasn't read the planning conditions — and bounce the RAMS back.

Working in London means satisfying HSE duties under HASAWA 1974 and CDM 2015 plus the borough's planning conditions, the Mayor of London's NRMM standards (since 2015 across Greater London), and any TfL or LU asset-protection requirements where applicable. RAMS that name these explicitly are far more likely to be approved on first submission.

How Riskora Helps

Use a structured RAMS that lets you bolt on the London-specific layer without rewriting the core. Riskora's builder applies the standard hierarchy of controls and HSE-aligned hazards, then leaves space for the project-specific Section 61 number, CLP reference, ULEZ plant list and traffic-management plan. Pair it with our Working at Height assessor and the 5×5 risk score calculator to get the standard parts right before you layer the London context on top.

Who it's for

  • Subcontractors working in zones 1-2 fit-out and refurbishment
  • Groundworks and utility contractors operating on Red Routes
  • Mechanical & electrical installers in occupied commercial buildings
  • Roofing and façade contractors near Underground or rail corridors
  • Out-of-hours specialists working under Section 61 consent

Do I need a Section 61 consent for noisy work in London?

Section 61 of the Control of Pollution Act 1974 is a voluntary prior consent — you apply to the borough's Environmental Health team for agreed working hours and noise limits. It's not mandatory, but without one the borough can issue a Section 60 notice mid-job that stops work. Most central London principal contractors require a Section 61 to be in place before site mobilisation, and your RAMS should reference the consent number and agreed hours.

Does a London site need different RAMS for each borough?

The core risk assessment doesn't change between boroughs, but the wrapper does. Westminster, Camden and the City of London have stricter quiet-hours and out-of-hours restrictions than outer boroughs. Tower Hamlets and Southwark have specific construction logistics plans (CLPs) for many wards. Your method statement should reference the borough's specific conditions rather than a generic 'comply with local authority requirements' line.

Key Risks and Considerations

  • •Section 60 notice issued mid-job because no Section 61 prior consent was in place
  • •Lane rental and overrun charges on TfL Red Routes — currently up to £2,500/day on key corridors
  • •Plant rejected at the gate for not meeting ULEZ / NRMM (Non-Road Mobile Machinery) emissions standards
  • •LU Asset Protection objections delaying deep excavation near Underground tunnels
  • •Considerate Constructors Scheme deductions affecting framework eligibility
  • •Borough enforcement of out-of-hours working triggering complaints and stop-work notices

Worked example: 4-week shopfront refurb in Westminster

A small fit-out contractor wins a £38k shopfront refurbishment on Marylebone High Street. The unit is on a borough-controlled (not TfL) road, but Westminster's quiet hours apply: no noisy work before 08:00 or after 18:00 weekdays, none before 09:00 Saturdays, none on Sundays. The principal designer requires RAMS submitted at least seven days before mobilisation.

The contractor uses Riskora's Refurbishment / Strip-Out preset for the standard hazards — manual handling of glazing, work at height for the new fascia, dust suppression for plaster removal, electrical isolation under BS 7671. They then add the London layer: Westminster pavement licence number for the small skip and welfare unit, a NRMM declaration for the petrol-driven cut-off saw (Stage V compliant), the agreed delivery window (06:30 unloading direct to van, finished by 07:45 to clear the loading bay before retail trading), and a Section 61 reference for the two days of hammer-action drilling.

The RAMS is approved on first submission. Three weeks in, an Environmental Health officer responds to a noise complaint — because the Section 61 is in place and being followed, no notice is issued and work continues uninterrupted.

Common Mistakes (and How to Avoid Them)

1. Listing 'comply with local authority requirements' without naming the borough or condition

Why it fails: Westminster and the City of London review RAMS for their high-profile sites. A generic line tells the reviewer the contractor hasn't read the planning consent.

Fix: Quote the planning condition number and reference the specific borough Environmental Health contact or planning officer name.

2. Submitting plant lists with no NRMM declaration

Why it fails: Greater London has required Stage IIIB minimum (Stage IV/V on larger sites) for non-road mobile machinery since 2015. Non-compliant plant gets refused at the gate on most central sites.

Fix: Include a plant register with engine make, model, Stage rating and (where required) the NRMM Register reference number for each unit.

3. No Construction Logistics Plan reference for sites that need one

Why it fails: Most planning consents in zones 1-2 condition a CLP. Without referencing the approved delivery windows, vehicle types and route, principal contractors can't sign off the RAMS.

Fix: Reference the CLP document number, agreed delivery window, and any holding-bay arrangement explicitly in the method statement.

Key Features

  • Generate the CDM-aligned core in minutes
  • Add London-specific fields without breaking the structure
  • Re-use site templates across multiple borough projects
  • Version-control consent numbers and CLP references
  • Download PDF ready for principal contractor review

Example Structure (UK Standard)

  1. Project address, borough and ward
  2. Planning condition references and Section 61 number (if applicable)
  3. Highway authority — TfL Red Route, borough road, or private estate
  4. NRMM declaration: plant make, model, Stage IV/V emissions compliance
  5. Construction Logistics Plan (CLP) reference and approved delivery windows
  6. Standard hazard identification and control measures (CDM 2015)
  7. Method statement — sequence of work referencing approved hours
  8. Emergency arrangements — nearest A&E, LU station closures, exclusion zones

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, 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 lifetime safety document · Upgrade when you need more

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.

"London-specific compliance — Section 61, CLPs, NRMM and TfL permits — is what separates an approved London RAMS from a rejected one. The HSE core is necessary but not sufficient."
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

No — it's a UK-wide RAMS builder. London projects benefit because the structured fields make it straightforward to add the borough, Section 61, NRMM and CLP context that London principal contractors look for.

No. Section 61 applications go through the borough's Environmental Health team and require detailed noise modelling outside the scope of a RAMS builder. Riskora references the consent in the RAMS once you have it.

The core can be reused, but the wrapper — borough name, planning conditions, working hours, CLP reference — must be updated per project. Riskora makes this fast by separating the reusable core from the project-specific layer.

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.

Describe your job — your draft is one paragraph away.

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

Start in seconds

Describe the job — we'll start the RAMS for you

Free plan — generate, review and download one PDF. No card needed.

References & Further Reading

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

Free safety-document builder

Create your London 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.