RAMS for Manchester & Greater Manchester Sites
By the Riskora Editorial Team · Written to our editorial standards
Manchester construction has its own rhythm. The city centre's tram network, the ongoing Mayoral Development Corporation regeneration zones, and the ten-borough Greater Manchester Combined Authority (GMCA) road-permit framework all shape what a principal contractor expects to see. RAMS that read like they were written for a generic UK site rarely survive review on a city-centre or tram-corridor project.
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.
Full version
What do Manchester principal contractors look for in a RAMS?
On top of the CDM 2015 core, Manchester reviewers want to see explicit acknowledgement of the GMCA Permit Scheme for any street works, Metrolink (TfGM) interface arrangements where the site is within ~3m of the tram corridor, the borough's specific licensing for hoardings and skips, and — for occupied retail / mixed-use sites — agreed quiet hours that reflect Manchester City Council's noise complaints policy.
Why Manchester sites need more than a generic RAMS
Greater Manchester runs a single permit scheme across all ten boroughs (Manchester, Salford, Trafford, Stockport, Tameside, Oldham, Rochdale, Bury, Bolton, Wigan) — but each council still applies its own conditions on hoardings, scaffold licences, skips and pavement closures. A RAMS that says "comply with local authority requirements" doesn't tell a Trafford CDM coordinator anything they can sign off. The reviewer wants to see the actual permit reference, agreed hours, and named highways officer.
Greater Manchester operates under the same HSE / CDM 2015 framework as the rest of England, but the Combined Authority permit scheme and Metrolink asset-protection requirements add a layer that London-style boilerplate doesn't cover. RAMS that explicitly name the permit, the borough conditions and the Metrolink interface land cleanly with reviewers.
How Riskora Helps
Riskora's structured builder gives you a CDM-aligned starting point in minutes, then leaves the project-specific fields for the GMCA permit number, borough conditions, Metrolink permit (if applicable), and NRMM plant declaration. Pair it with the Working at Height assessor for the access decision and the risk score calculator for hazard banding before you add the Manchester-specific context and complete competent review.
Who it's for
- Civils contractors on GMCA-permitted street works
- Façade and roofing contractors on city-centre regeneration sites
- Subcontractors working in MediaCityUK, NOMA, Mayfield and similar managed estates
- Utilities contractors on Metrolink-adjacent corridors
- M&E contractors on retail and mixed-use refurbishments
Understand the Fundamentals
Before you generate your document, these guides cover the knowledge that underpins every good RAMS, risk assessment, and method statement.
RAMS for Construction
The CDM 2015 core that Manchester sites are built on.
RAMS for Road Works
Essential for any GMCA-permitted street works.
RAMS for Track Maintenance
Covers tram and rail corridor working principles.
RAMS for Excavation Near Utilities
Manchester's Victorian utility network makes this a near-universal hazard.
RAMS for Work Near Railways
Network Rail principles applicable to Metrolink and heavy-rail interfaces.
Does the Manchester Clean Air Zone affect construction RAMS?
The Greater Manchester Clean Air Zone proposal was paused in 2022 and is being reviewed for an investment-led scheme. There's currently no charging zone, but the direction of travel is toward Stage V NRMM (Non-Road Mobile Machinery) and Euro VI delivery vehicles being preferred or required on major framework sites. RAMS should declare engine emissions standards even where a charge isn't yet in force — many Manchester principal contractors require it on framework jobs.
Do I need a special permit for working near Metrolink?
Yes — any work within Transport for Greater Manchester's (TfGM) Metrolink corridor requires asset-protection engagement. For work within roughly 3m of the running line, you'll need a Metrolink permit, an approved methodology, and often a possession / isolation arrangement. The RAMS should reference the permit number, the agreed track-side controls, and the Metrolink emergency contact.
Key Risks and Considerations
- •GMCA Permit Scheme overrun charges where street works exceed agreed duration
- •Metrolink possession overruns triggering significant compensation events
- •Salford Quays / MediaCityUK estate-specific access protocols not referenced
- •City-centre noise complaints triggering enforcement under EPA 1990
- •Hoarding licence / scaffold licence delays from Manchester City Council Highways
- •Heritage / conservation area conditions overlooked in Northern Quarter and Castlefield
Worked example: kerb replacement on a Metrolink-adjacent street, Salford
A small civils contractor wins a £22k footway and kerb replacement on Chapel Street, Salford — directly adjacent to the MediaCityUK-bound tram line. The work involves breaking out 60m of failed kerbs, installing new HB2 kerbs, and reinstating the footway. Salford City Council requires a GMCA permit; TfGM requires a Metrolink asset-protection sign-off because the work is within 2.5m of the running rail.
Using Riskora's Kerbing preset, the contractor pulls in the standard hazards: manual handling of kerbs (each ~80kg), HAVS exposure from the breaker, dust silica from cutting, and pedestrian / cyclist segregation. The structured method statement sequences the work to keep one footway open at all times. The contractor then adds the Manchester layer: GMCA permit number, agreed hours (07:00–18:00 weekdays, no work during morning peak tram service of 06:30–08:00 within 1.5m of rail), Metrolink permit reference, named TfGM Asset Protection contact, and Stage V declaration for the breaker and excavator.
The RAMS is approved on first submission by both the principal contractor and TfGM. The job runs to programme; a single tram operator query about banksman positioning is resolved on site by reference to the documented exclusion zone in the method statement.
Common Mistakes (and How to Avoid Them)
1. Treating the GMCA permit scheme as the borough's job, not the contractor's
Why it fails: The permit applicant under NRSWA 1991 is the works promoter — usually the principal contractor or the utility. Reviewers want to see the permit number in the RAMS, not a vague reference to 'street works permission'.
Fix: Apply for the permit through Street Manager at least 3 working days ahead, then quote the reference in the RAMS before submission.
2. No Metrolink consultation for tram-adjacent work
Why it fails: TfGM treats unauthorised work near the running line as a serious safety breach. After-the-fact engagement is much harder than pre-job notification.
Fix: Engage Metrolink Asset Protection at the earliest opportunity. Reference the consultation outcome and any agreed isolation in the RAMS.
3. Using a London or generic boilerplate that mentions Section 61
Why it fails: Section 61 is widely used in London but rarely the practical route in Manchester — the boroughs use noise abatement notices under EPA 1990 instead. A boilerplate Section 61 reference signals the RAMS wasn't written for Manchester.
Fix: Reference the borough's Environmental Health contact and agreed working hours rather than a Section 61 number.
Key Features
- Structured CDM 2015 hazard library applies in seconds
- Project fields capture GMCA permit, Metrolink reference and borough conditions
- Reuse the core across multiple GM10 borough projects
- Version-control plant lists as NRMM standards tighten
- PDF / PDF download for principal contractor and TfGM submission
Example Structure (UK Standard)
- Project address, borough (one of the GM10), and ward
- GMCA Permit Scheme reference and agreed working window
- Metrolink permit / asset-protection reference (where within ~3m of tram corridor)
- Hoarding / scaffold / skip licence numbers from the borough
- NRMM plant declaration with engine Stage rating
- Standard CDM 2015 hazard identification and control measures
- Method statement aligned to agreed working hours
- Emergency arrangements — nearest A&E (MRI, Salford Royal, Wythenshawe etc.)
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 FreeNo card required · 1 lifetime safety document · Upgrade when you need more
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.
"A Manchester RAMS that names the GMCA permit, borough conditions, Metrolink interface (where applicable) and Stage-rated plant lands cleanly. Boilerplate that doesn't acknowledge any of these signals lack of project-specific work."
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.
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.
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.
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.
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.
- 1Paste 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.
- 2Riskora structures the document
Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.
- 3Review, edit and download
You stay in control of every section. Tweak anything, then download a clean PDF or share a link.
- 4Brief the team and record sign-off
Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.
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
Describe your job — your draft is one paragraph away.
No training. No complex setup. Just select your trade and go.
Related Pages
References & Further Reading
Primary UK sources covering the legal and practical framework behind RAMS, risk assessments and method statements.
Create your Manchester 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.