QUALITY INTL CERTIFICATIONSRAMS Explained — Risk Assessment + Method Statement
RAMS stands for Risk Assessment and Method Statement — two documents bound into one. The risk assessment half lists the hazards, who is at risk and the controls; the method statement half sets out the step-by-step safe sequence of work with the resources, competencies and permits each step needs. Every step must trace back to a control.
How a risk assessment and method statement pair into one safe system of work.
What RAMS Means on UAE Projects
RAMS is the UK-born contractor term that travelled to the Gulf and stuck. On UAE projects — a tower fit-out in Dubai, a substation in Abu Dhabi, a pipeline tie-in in Sharjah — the client or main contractor asks for "the RAMS" before work starts, and what they expect is a single approved pack describing both what the risks are and exactly how the work will be done.
The pairing is the point. A risk assessment without a method statement says what could go wrong but not who does what, in what order, with which equipment. A method statement without a risk assessment describes a beautiful sequence nobody has checked against harm. Approving engineers read the two halves against each other, and the fastest way to a rejection is a method step with no matching control.
The Two Halves of a RAMS Document
The risk assessment half is analytical. It walks the activity, lists the hazards — falls, electrical, lifting, chemical, whatever the work generates — and for each one records who might be harmed and how, then the controls that reduce the risk. It answers the question "what could hurt people here, and what are we doing about it?"
The method statement half is operational. It sequences the work into steps from mobilisation to completion, and for each step states the resources, the competencies of the people doing it, and any permit required before it starts. It answers "who does what, in what order, with what, under which permission?"
| Element | Risk assessment half | Method statement half |
|---|---|---|
| Core question | What could harm people? | How will the work be done? |
| Content | Hazards, people at risk, controls | Step sequence, resources, competencies, permits |
| Style | Analytical | Procedural |
| Typical failure | Generic hazards not tied to this job | Steps with no traced controls |
How the Halves Pair: Traceability
The join between the two halves is traceability. Every step in the method statement must point back to the controls in the risk assessment that make it safe. When the method says "erect edge protection before opening the slab edge", the risk assessment must show falls from openings as a hazard with edge protection as a named control — and a trained crew listed among the competencies.
Reviewers check this first because it is where copied documents fall apart. A RAMS assembled from an old project keeps its internal links intact; one assembled fresh by pasting sections together usually has orphan steps, controls that serve nothing, and permits that appear from nowhere. Traceability is also what makes the document usable on site: the supervisor briefs the steps, and the controls arrive with them.
Beyond the two halves, strong RAMS share a frame. Roles and responsibilities are named — who supervises, who inspects, who holds authority to stop. Equipment is listed with its inspection status. Emergency arrangements spell out first aid, alarm routes and muster points for that specific location, not a generic site. Monitoring defines who checks compliance during the work and how. Without those four elements, a RAMS describes a plan nobody owns.
Worked Skeleton: A Concrete Pour
Take a ground-floor concrete pour on a UAE project. The skeleton below shows how steps and controls interlock in practice.
| Step | What happens | Traced controls |
|---|---|---|
| 1 Access and set-up | Delivery route, pump position, exclusion zone marked | Plant and pedestrian separation, permit posted |
| 2 Formwork and steel | Final checks on shutters, rebar, edge protection | Manual handling controls, edge protection on open sides |
| 3 Pump and deliveries | Pump unfolds on level ground, trucks cycle in | Competent banksman, vehicle routing, pumping zone exclusion |
| 4 Pour | Concrete placed and vibrated in sequence | PPE, noise controls, trained vibrator operators |
| 5 Finish and cure | Levelled, covered, curing regime started | Housekeeping of tools and hoses, access kept clear |
Each step names its competencies — pump operator, banksman, vibrator crew — and its permits where the site requires them. The emergency arrangements cover the pour's real risks: a truck striking a person in the exclusion zone, a pump hose whipping. That specificity is what an approving engineer looks for under the generic headings.
Why RAMS Get Rejected in UAE Approvals
Most rejections are avoidable and repetitive. Generic text copied from another project with the wrong site name still in it. Steps with no traced controls, or controls listed with no step to carry them. Missing competencies — the method names a crane crew the contractor has not evidenced. No emergency arrangements for the actual location. No permits referenced where the client's system demands them. No monitoring regime, so nobody checks compliance during the work.
Approval is a conversation, and the reviewer is testing whether the contractor has imagined the work. QIC (Quality International Certifications), a UAE training and inspection company since 1998, reviews contractor documentation across these projects, and the documents that pass first time are always the ones written from the work backwards — real steps, real controls — rather than assembled from templates.
Checklist
Before you submit a RAMS pack, check:
- Every method step traces to a named control in the risk assessment.
- Every control traces to a step that carries it.
- Roles, competencies and training evidence are named, not implied.
- Equipment is listed with current inspection status.
- Emergency arrangements match the actual work location.
- Permits required by the client's system are referenced.
- Monitoring during the work is assigned to a role.
- Site names, dates and references match this project, not the template.
Frequently Asked Questions
What does RAMS stand for in safety?
Risk Assessment and Method Statement — the combined document contractors submit for approval before work starts. The risk assessment half handles hazards, people at risk and controls; the method statement half handles the safe step-by-step sequence with resources, competencies and permits. In UAE usage it is a single pack, which is why the plural-looking acronym is treated as one document.
What is the difference between a risk assessment and a method statement?
The risk assessment analyses: it lists what could harm people and the controls that reduce the risk. The method statement prescribes: it sequences the work step by step, naming who does each step, with what equipment and under which permit. The two are bound together because every step needs its controls, and every control needs a step to live in.
Who writes and approves RAMS on UAE projects?
The contractor's competent person — usually a project engineer, HSE officer or supervisor who understands the work — writes the RAMS, with input from the crew doing the job. The client's or main contractor's approving engineer then reviews and signs it. Writing is delegation-friendly; approval belongs to someone with authority to challenge the sequence and the controls.
How detailed should a method statement be?
Detailed enough that a competent crew who never met the writer could do the work in the intended order with the intended controls. Real step sequences, real equipment, real competencies — not "carry out work safely". Too much detail fails too: a 60-step narrative nobody reads is a rejection risk, because the reviewer cannot see the sequence through the fog.
Can one RAMS cover multiple activities?
Only when the activities genuinely share steps, hazards and controls — like a series of similar concrete pours in one building. Distinct activities need distinct RAMS, or at minimum clearly separated sections with their own step sequences and traced controls. When the work changes character — different trades, locations, plant — one document cannot hold the traceability that approval depends on.