How to Write a RAMS Document for a Small Contractor

What is a RAMS document and when do you need one?

RAMS stands for Risk Assessment and Method Statement. It combines two documents into one: the risk assessment identifies what could go wrong and how likely it is, while the method statement explains step by step how the work will be carried out safely.

As a small contractor, you'll typically need a RAMS before starting work on any site where a principal contractor is in charge, for any task with significant risk (working at height, confined spaces, lifting operations), and often as a condition of your insurance or contract. If a client or main contractor asks for your RAMS and you don't have one ready, you don't start work — it's that simple.

The good news is that writing a RAMS doesn't require a safety consultant or specialist software. You just need to understand the structure and fill it in honestly for the actual job you're doing.

The basic structure of a RAMS document

A RAMS document for a small contractor typically runs to two to five pages. Anything longer than that for a straightforward task is usually padding. Here's what every RAMS needs to include:

• Project details — site name, address, client, principal contractor, your company name, date, and document reference number.
• Description of works — a clear paragraph explaining what you're doing, where on site, and with what equipment or materials.
• Operatives involved — names or roles of workers carrying out the task, including any subcontractors.
• Risk assessment section — a table listing each hazard, who is at risk, the likelihood and severity (before and after controls), and the control measures in place.
• Method statement section — a numbered sequence of the work steps, written so that someone unfamiliar with the job could follow it safely.
• Signatures — the document should be signed by the person who prepared it, reviewed by a supervisor, and ideally signed by the operatives who have read it.

Writing the risk assessment part

The most common mistake small contractors make is copying a risk assessment from a previous job or downloading a generic template and submitting it unchanged. A principal contractor reviewing your RAMS will spot this immediately — especially if it mentions hazards that have nothing to do with your scope of work, or misses ones that obviously apply.

Start by thinking through the task from start to finish and asking: what could hurt someone here? Common hazards to consider include:

• Falls from height (ladders, scaffolding, edges, voids)
• Manual handling (lifting, carrying, repetitive movements)
• Struck by objects (falling tools, moving plant, reversing vehicles)
• Electrical hazards (buried cables, overhead lines, temporary supplies)
• Dust and fumes (cutting concrete, welding, chemical exposure)
• Noise and vibration (power tools, compactors)
• Working in proximity to the public or other trades

For each hazard, record who is at risk (your workers, other trades, members of the public), then write your control measures. Controls should follow the hierarchy of control: eliminate the hazard if possible, substitute with something safer, use engineering controls (barriers, extraction), then administrative controls (training, permits), and finally PPE as a last layer — not a first resort.

After listing your controls, score the residual risk. Most RAMS templates use a simple 1–5 scale for likelihood and severity, multiplied together to give a risk rating. Anything above 12 on a 25-point scale should prompt you to add further controls before the work goes ahead.

Writing the method statement part

The method statement is the "how we're going to do it" section. It should read like a clear sequence of steps — not a list of bullet points about what PPE to wear.

A good method statement for, say, installing a new roof light might look like this:

1. Attend site induction and sign in. Confirm work area boundaries with the site manager.
2. Erect mobile scaffold tower to access roof level. Check all components before assembly.
3. Mark out the roof light opening and confirm structural drawings are on site.
4. Cut opening using diamond disc cutter. Operatives to wear dust masks (FFP3), eye protection and ear defenders. Exclusion zone set below.
5. Remove cut section and dispose of materials via chute to skip below.
6. Fit roof light frame as per manufacturer instructions. Check alignment and seal all edges.
7. Inspect completed installation and clear all waste from roof level before descending.
8. Report completion to site manager and sign out.

Notice how each step tells the reader what happens, how, and what precautions apply at that specific step. That's the standard to aim for.

Getting the operatives to actually read it

A RAMS that sits in a site folder unsigned is just a piece of paper. Before work starts, you must brief the operatives on the contents — this is often called a "RAMS briefing" or task talk. Keep it short and practical: walk them through the main hazards, the controls, and the sequence of work. Then get them to sign to confirm they've understood it.

If the scope of work changes significantly during the job — new hazards appear, the method changes, additional operatives join — you should review and reissue the RAMS. A quick amendment with a new date and revised signatures is enough; you don't need to start from scratch.

Common reasons RAMS get rejected

• Generic hazards that don't match the actual task or location
• No reference to specific site conditions (the principal contractor wants to see you've thought about their site)
• Unsigned or undated
• Controls listed as "wear PPE" without specifying what PPE or why
• Method statement written in vague language ("work will be done safely") rather than actual steps
• Risk ratings that show high residual risk with no explanation of further action

A faster way to get it done on site

If you're managing multiple jobs and writing RAMS from a blank page every time is eating into your day, Safety Parrot lets you take photos of the work area and generate a structured risk assessment and method statement in seconds — which you can then review and tailor before submitting. It's pay-as-you-go with no subscription, so it works well for smaller contractors who need a professional document quickly without carrying the overhead of a safety consultant.

That said, whether you use a tool or write it by hand, the principles above are what make a RAMS actually useful rather than just a box-ticking exercise. Get the structure right, make it specific to the job, brief your team, and keep it on site. That's what good looks like.