Generic RAMS might tick a box, but they don’t control risk. When a method statement doesn’t match the workface, people improvise, supervision is on the back foot, and controls slip. Too many near-misses start with “We used last job’s RAMS.” The fix is not more paperwork—it’s making the document describe this site, this sequence, this plant, this crew, today.
TL;DR
/>
– Walk the actual workface and routes, then draft RAMS around what you saw, not what you did last month.
– Name the plant, materials, interfaces and hold points; avoid vague phrases like “use suitable extraction” or “secure edge.”
– Build the brief into the shift plan: who does what, with which kit, under which permit, and where the stop/go decisions are.
– Update when something changes—weather, deliveries, trades overlap, or kit swaps—and re-brief, not just reissue a PDF.
Make RAMS do the real work on site
/> A good RAMS turns risk control concepts into practical steps for one job, not a theoretical list. Start with the simple hierarchy: plan to avoid the risk, if you can’t avoid it then isolate it, and only then rely on admin and PPE. That means setting out physical controls such as temporary edge protection, barriers, mechanical extraction, and engineered access methods before you talk about briefings and gloves.
Site-specific means you capture local realities: access routes, where plant turns, where waste goes, where services are, and which floors or areas are live. It names the equipment by type and, where relevant, model; it describes consumables (disc types, fixings, anchors) and sets the standards (e.g. M-class extraction on a specific tool). It maps interfaces—adjacent trades, public/occupied areas, deliveries, and temporary works—and ties work to permits and hold points. And it states who is in charge at the workface and when they must stop to get a supervisor or permit authority.
How it plays out when you tailor it to the job
/> Consider a city-centre office fit-out. A ductwork gang needs to cut new openings in a riser wall and install fire sleeves. The subcontractor turns in with a generic RAMS for “core drilling and installation,” light on detail. It doesn’t mention the live retail unit below, the building’s fire alarm strategy, or the fact that the only waste route is via a shared passenger lift. Day one, a drilling vacuum trips the local alarm and a bucket of slurry is parked in a corridor as the lift is delayed—two complaints and a stop notice.
The fix is quick but specific. The supervisor walks the riser and routes, identifies the alarm isolation window, and books the lift for timed slots. The RAMS now names the drill and extraction unit, the exact fixing system, and the slurry containment method; it shows the corridor exclusion zone sketch and names the banksman. It builds in a hold point to confirm alarm isolation and lift booking before starting, and sets the clean-down, waste transfer, and reactivation sequence. The re-brief is done on the floor, next to the riser, with everyone pointing at the controls they will actually use.
Where RAMS go wrong on live projects
/>
Vague kit and vague controls
“Use appropriate MEWP” or “fit suitable dust extraction” invites improvisation. Name the category, reach, and constraints, plus the extraction class, hose size, and filter checks.
# No mention of neighbouring work
/> Copy-paste RAMS ignore other trades, public interfaces and traffic routes. If the programme and interfaces aren’t mapped, your controls will clash with someone else’s.
# Missing hold points and supervision moments
/> If there’s no “stop and confirm” in the method, people press on when conditions change. Build in triggers such as “do not proceed until isolation lock is confirmed” or “await TW check.”
# Briefing treated as a signature ritual
/> Handing out a PDF at the canteen door is not a briefing. Toolboxes need to be done at the workface, with kit in hand and the exclusion line marked out.
Checklist for a site-specific RAMS that crews will actually follow
/>
– Walk the workface, approach routes and waste paths; photograph pinch points and capture service locations you can verify.
– Identify adjacent works, public interfaces, temporary works and live services; record how your activity will avoid, isolate, or sequence around them.
– Specify plant, tools and consumables by type (and model if critical), including attachments, guards, extraction and maintenance checks.
– Draw the exclusion zones and access/egress on a simple plan; note barriers, signage, banksman positions and communication signals.
– Tie tasks to permits, isolations, and inspections; state who issues them, who verifies them, and the stop/go criteria.
– Name the supervisor at the workface and the competent persons for high-risk stages (e.g. slinger, scaffolder, hot works fire watcher).
– Set change triggers: new kit, weather shift, adjacent trade change, design update; require a re-brief each time one is hit.
Pitfalls and fixes in execution
/> The biggest pitfall is drift: day one looks good, day three someone swaps the vac for whatever is in the van, or moves fencing “just for an hour.” Counter this by making verification visible. Supervisors should start shifts with a two-minute walk of the set-up against the RAMS, not a desk review. If the controls aren’t there—extraction, barriers, permits—work doesn’t start.
Link RAMS to permits and temporary works on purpose. If a slab opening has a TW check, write the method so it cannot progress to the next step without that sign-off. For isolation, name the lock-out point and tag, and require the lead to show it during the brief. For traffic management, include delivery timings and banksman positions so plant and pedestrians remain segregated; if a new delivery pattern appears, pause and re-sequence.
Keep the document lean and navigable. Crews need method steps, sketches, and responsibilities more than pages of generic hazards. One-page summaries with photos and a simple plan, backed by the full document for the file, often land better on busy sites.
Keeping RAMS live through the programme
/>
Actions for this week to bin generic RAMS
– Walk one active workface with the gang and redraw the exclusion zone on a sketch; stick it to the RAMS and re-brief on the spot.
– Compare the named kit in the document with the kit on the floor; swap out anything that doesn’t meet the spec and record the change.
– Pin down interfaces by talking to the two nearest trades; write in a sequence note that avoids overlap or sets a time window.
– Rewrite one high-risk step with a clear hold point and who authorises release; make sure supervisors know to pause there.
– Capture three photos of the correct set-up and add them to the briefing pack; use them in tomorrow’s toolbox for new starters.
Getting RAMS right is less about templates and more about accurate, everyday supervision wrapped around real controls. Expect more scrutiny on whether your paperwork matches the workface and whether you’re reacting when the plan changes. The bottom line: if someone can’t point to the control on the floor, it isn’t in place—fix that before you pick up a tool.
FAQ
/>
How specific do RAMS need to be to count as “site-specific”?
They should describe the exact location, sequence, plant, and interfaces for the work you’re doing, not a generic version. If someone unfamiliar with the job can stand at the workface and match the steps and controls to what they see, you’re in the right place.
# Who should draft and sign off RAMS on a typical UK site?
/> The subcontractor carrying out the work should draft them, with input from the supervisor who knows the task and routes. The principal contractor or site manager usually reviews and accepts them, and specialist elements may also need sign-off from permit issuers or temporary works coordinators.
# When do RAMS need updating during a job?
/> Update whenever something material changes: different plant, altered access, new adjacent trades, weather that affects controls, design tweaks, or permit conditions. Treat updates as new information—re-brief the crew at the workface and make sure the changed controls are in place before restarting.
# How do RAMS deal with interfaces between trades and permits?
/> Call out who is where and when, draw exclusion zones, and set sequences that avoid overlap. Link key steps to permits or inspections (hot works, isolations, temporary works checks) and name the person who authorises each release so there’s no ambiguity on stop/go moments.
# What’s a sensible way to brief RAMS without wasting time?
/> Keep it at the workface, short and focused on the top five controls, with photos or sketches. Get the responsible person to point out isolations, barriers, and access routes, and have the crew confirm they’ve got the right kit; signatures then record a meaningful conversation, not just a paper exercise.
