RAMS stands for risk assessment and method statement. It is a site convention rather than a legal term, and it names two documents that travel together: the assessment, which lists the hazards, who could be harmed and the controls, and the method statement, which sets out how the job will actually be done with those controls inside the steps. When a principal contractor asks for your RAMS, they are asking to see both halves before you come on site.
Risk assessment: what could go wrong and what stops it
The hazards actually present on this job, who is at risk including the public, the controls you will use, and the residual risk once they are in place. Generic phrases such as take care are not controls, and a reviewer reading a page of them will read the whole pack as decoration.
Method statement: the order of work
The sequence somebody can follow, with the plant, access equipment, competence and permits named against the step that needs them. The two halves have to meet: every control named in the assessment should appear in a step, which is a five minute check and the most common reason a pack is returned.
Why the acronym matters more than it should
Sites ask for RAMS because it is one word for the evidence they need. Answer with both halves, specific to the job, dated and versioned, and the request is closed. Answer with a downloaded template carrying your logo and it usually comes back.
Questions people ask about rams meaning
Is RAMS a legal requirement?
The duties to assess risk and to plan and control construction work are legal; RAMS is the ordinary way of evidencing both. On almost any managed site it is also a contractual requirement.
Who writes the RAMS?
Somebody competent in the work, which on a small job is usually the person running it. It is then briefed to the crew, and the briefing record matters as much as the document.
How often should RAMS be updated?
Whenever the sequence, the plant, the crew or the site changes, and after any incident. The version in force should be the one the crew was briefed on, which is why it belongs on the job record rather than in an email thread.