RAMS is not a legal term. It is what the industry calls the pack a contractor hands over before starting: the risk assessment saying what could go wrong and what controls it, and the method statement saying how the job is done in sequence so those controls actually happen. What makes it legally significant is that a principal contractor has to plan, manage and monitor the construction phase and coordinate the contractors, and this pack is the document they do it with.
What a RAMS report contains, section by section
A cover page with the project, the client, the site address, the dates and a VERSION number. The scope, written narrowly enough that everybody knows what is excluded. The sequence of operations, in order, in the present tense, naming the plant and the access equipment actually being used. The risk assessments, with the residual risk after the controls rather than before. Substances, with the data sheets and the assessments for anything hazardous. Access and egress, including the working at height arrangements and anything over or near a public route. Permits, where hot works, confined space, roof access or isolation apply. Competence, meaning who is trained and certificated for what. Supervision, meaning who is in charge and who stops the job. Emergency arrangements, which is the section most often missing: first aid, rescue from height, spill, fire and the route an ambulance takes. And a briefing sheet for the people who will sign to say they were told.
Who reads it, and what they are looking for
Four readers, and they want different things. The principal contractor reads for INTERFACES: whether your sequence collides with another trade's, whether your isolation takes their power out, whether your scaffold alteration is somebody else's access. The client's adviser reads for competence and for whether the pack is specific to this site or generic. The site supervisor reads it to brief the gang, which is the only reading that changes what happens on the day. And an investigator reads it afterwards, comparing what it said with what was done, which is why an accurate pack that was followed is a defence and an aspirational one is evidence. The practical test before submitting is to read your own sequence as if you were the supervisor: if it cannot be briefed in five minutes, it will not be.
Version control, and the pack that was approved for a different job
The commonest failure is not a bad pack, it is a good pack from somewhere else. A pack carries a version and a date, it is approved for THIS site and this sequence, and it is reissued and re briefed when the sequence changes, when new plant arrives, when the access changes or when anybody new joins. Two habits keep it honest. Keep the site name and the date in the header of every page, because a photocopied section from another job is then visible at a glance. And record the briefing with names and the date, because an approved pack nobody was briefed on is the same as no pack at the point where it matters. Where a client asks for a pack before the sequence is settled, send it marked as a draft and reissue it, rather than letting a draft become the approved document by default.
Questions people ask about rams for work
Who has to produce RAMS?
Every contractor for their own work. The risk assessment duty is the employer's and cannot be handed up or down, and the method statement is how the contractor shows the principal contractor that the work can be managed alongside everybody else's. On a single contractor project the same contractor draws up the construction phase plan, and the RAMS pack usually sits inside it.
Does a one day job need a full pack?
It needs a risk assessment and a sequence, and both can be short. What a short job does not get to skip is the part that is specific: the access, the isolation, the permits and the emergency arrangements, because those are about the site rather than the duration. A two page pack that answers those beats a thirty page template that answers none of them, and most principal contractors will say so if asked.
Can a client reject a pack?
A principal contractor can and routinely does, usually for three reasons: it is generic and describes somebody else's site, the sequence conflicts with other trades or with the construction phase plan, or the emergency and rescue arrangements are missing or unworkable. Rejection is not a judgement on competence; it is the coordination duty being done. The fastest route through it is to ask what specifically has to change and to reissue with a new version number rather than editing the approved copy.