RAMS that nobody reads are worse than useless. Too many projects churn out 20-page packs full of generic hazards, brand templates and recycled boilerplate, then expect supervisors to brief it at 07:30 while the delivery lorry is reversing. The aim isn’t to bin the detail; it’s to make a two-page, task-specific summary that crews can actually use on the day, with the full pack available for background and assurance.
TL;DR
/>
– Strip RAMS to the job at hand: task scope, key hazards, critical controls, permits, and stop/go triggers
– Use plain site language, photos or sketches, and a simple step-by-step method tied to controls
– Name who does what, where the exclusion zones are, and what prompts a pause-and-escalate
– Brief it at the workface, get sign-on, and keep the sheet with the supervisor for dynamic changes
What a two-page RAMS actually covers on a UK site
/> A two-page RAMS is the live, working version of your safe system of work. It covers the task scope in a sentence or two, the sequence of steps, the credible hazards for those steps, and the controls in plain English. It makes the non-negotiables obvious: exclusion zones, permit needs (hot works, live services, confined spaces as relevant), interface points with other trades, and the link to any temporary works controls.
It clarifies supervision: who is the point of contact, who checks plant and equipment, who stops the job if conditions change. It references the bigger pack only where needed, not by dumping paragraphs of legislation. Emergency arrangements are simple and site-specific: nearest muster, first-aider, how to isolate power or plant safely. PPE is there, but as the last line, not the headline.
How to build it: from scope to steps
/> Start with the scope and boundaries. “Core-drill four penetrations through slab in Stair B” is better than “Drilling works.” Note what is in and out, especially if there are adjacent live areas, sensitive finishes, or public interfaces.
Break the task into steps and put the main hazards next to each step. For example, set-up (manual handling, slips), drilling (silica dust, services strike, noise), clean-down (waste, sharp arisings). For each hazard, state the control that matters in practice: services scan confirmed and marked, dust suppression or M-class extraction, acoustic screens if close to occupied areas, water management to avoid slips, and a defined exclusion zone with barriers and signage.
Add permits and checkpoints at the right moment in the sequence, not as a separate page. If there’s a permit to dig or hot works, put “Permit authorised and displayed before Step 2.” Put names, not roles, where possible on the day. Use a small sketch or photo to show plant routes, access points, and where barriers go. Finish with “stop work if” triggers: unmarked cables found, dust control fails, MEWP can’t maintain clearances, or weather changes affect stability.
Scenario: ceiling install during a live retail fit-out
/> Night shift on a city-centre fit-out. The drylining subcontractor is fixing MF ceiling grid while M&E are running containment above. A MEWP shares the aisle with a pallet truck delivering boards. The sprinkler contractor has a permit to isolate a zone while heads are dropped. The original RAMS is 18 pages; the supervisor tries to brief it while half the crew are still signing in.
Instead, a two-page version is used. Page one shows the aisle layout, MEWP path, and a red-shaded exclusion zone for overhead works with designated a banksman. It lists the sequencing: containment complete and signed off before the grid install enters that bay; hot works permit held by M&E for any cutting; daily pre-use check on the MEWP; barrier positions; noise window times. Page two sets stop/go triggers: if pedestrian flow increases (late-night stock), banksman halts MEWP; if dust extraction fails, work pauses. The crew sign on after a five-minute talk at the aisle, the banksman’s name is written in, and the permit numbers are added at the top.
Where RAMS fall apart and how to fix them
/> Vague scopes bury risk. “General works” invites confusion; define location, interfaces and limits so supervisors can police the boundary. Tie the method to actual site constraints rather than a generic sequence.
Interfaces get forgotten. If your task depends on others finishing first or isolations being active, anchor those dependencies in the steps with a visible “do not proceed until” line. Make someone accountable for checking the preconditions.
Permits become paperwork, not controls. Put the permit point exactly where the risk turns on: before hot cutting starts, not when collecting keys. Show where the permit is kept and who holds it.
Changes mid-shift undo good planning. Build in simple dynamic risk prompts: weather check for external lifts, plant/pedestrian review at shift change, noise windows verified with the store. Empower the supervisor with stop authority and state when to escalate to the principal contractor.
Two-page RAMS essentials: briefings and behaviours
/> A short document only works if it’s briefed well. Do it at the workface, not in the canteen. Walk the work area, point to where barriers will go, show the exact access route, and confirm who’s controlling plant-to-pedestrian interfaces. Use the sketch to confirm temporary works boundaries, edge protection status, and any voids or openings that the job passes near. Keep it conversational: “What could hurt us here?” will surface more than a script.
Keep it live. If the sequence changes because deliveries arrive early or another trade overruns, mark the change on the sheet and pause to brief the team. If the control fails (extraction breaks, ground softens under outriggers, exclusion zone repeatedly breached), stop, make safe, and call the supervisor or site manager. Use permits as real-time controls: rebrief any permit condition changes and relocate signage.
# Seven-day push: make RAMS readable on live works
/> Pick one current task per trade and convert the RAMS to two pages, then trial it on a morning briefing. Stand with the supervisor and write down unclear steps or missing controls as crews ask questions. Add a photo or sketch for any area with tight clearances or temporary works nearby. Agree stop/go triggers with the principal contractor so supervisors know when to escalate. File the two-pager in the work area and keep the full pack in the site file for auditing.
Common mistakes when slimming RAMS
/>
Cutting the risk thinking along with the pages
Some teams delete content instead of distilling it. Keep the risk reasoning; just express it in fewer, clearer words tied to the steps.
# Leaving out interface controls
/> A neat two-pager that ignores shared access routes, live services, or temporary works can create new hazards. Always draw the interfaces.
# Generic PPE lists as the main control
/> Listing hard hat, gloves and goggles is not a method. Put engineering and procedural controls first and make PPE the backstop.
# No stop-work triggers
/> Without clear “if this, then stop” prompts, supervisors carry risk alone. State the red lines and who to call when they are met.
Two-page RAMS essentials: quick checklist
/>
– Define task scope with limits, location, and adjacent activities that matter
– Break into steps and put each main hazard with its practical control next to the step
– Mark exclusion zones, plant routes, access/egress, and temporary works boundaries on a simple sketch
– Embed permits and sign-offs at the right points in the sequence with holder names
– Name the supervisor, banksman/spotter, and who has authority to stop and escalate
– List 3–5 stop/go triggers linked to real site conditions (weather, services, crowding, equipment failure)
Short, specific and live beats long, generic and ignored. Expect more client and regulator focus on whether your briefings change behaviour at the coalface, not how glossy the PDF looks.
FAQ
/>
How do I keep the two-page RAMS aligned with the full pack?
Treat the two-pager as a précis of the full RAMS, not a separate document. Update both when methods or controls change, and keep the version date and author on the two-pager. Store the full pack in the site file and the two-pager with the supervisor at the workface.
# What if the task changes mid-shift?
/> Pause, make safe, and re-scope the job in simple terms before continuing. Amend the two-pager by hand if needed, brief the crew again, and note any new permits or interface controls. Escalate to the site manager if the change affects temporary works, live services, or plant routes.
# How do I handle permits within a short RAMS?
/> Place permit steps exactly where they affect the method and write who holds them. Include where the permit is displayed and any critical conditions the crew must follow. Reconfirm permits at shift handover and if the sequence slips.
# Can I use photos and sketches instead of text?
/> Yes, provided they are clear, recent, and annotated with the controls that matter. A simple plan marking exclusion zones, access, and hazards often communicates better than paragraphs. Keep images to the specific area and remove anything that confuses.
# What should supervisors focus on during the briefing?
/> Stand at the workface and point to the real hazards and controls: edges, services, plant paths, and interfaces with other trades. Confirm names for control roles, check permits are in force, and state the stop/go triggers. Get verbal feedback to test understanding, then sign on and start in sequence.
