Risk Assessment and Method Statement (RAMS): A Practical Guide to Safer Work

Every job has risks. However, teams can control many of those risks when they plan the work before they start. A Risk Assessment and Method Statement (RAMS) brings two important safety tools together. First, the risk assessment identifies hazards and evaluates the risks. Then, the method statement explains how the team will complete the work safely. Together, they give workers a clear plan.

Moreover, RAMS can improve communication between project managers, supervisors, contractors, and workers. They can also help teams check that planned controls remain in place while work continues.

eAuditor Audits & Inspections helps teams digitize this process. Its construction resources support risk assessments, method statements, site checks, evidence capture, corrective actions, and reporting. For example, eAuditor’s Construction Site Risk Assessment Checklist checks whether the risk assessment is site-specific, whether it covers hazards, and whether controls are in place and effective.

What Is a Risk Assessment and Method Statement (RAMS)?

A Risk Assessment and Method Statement, or RAMS, is a set of documents used to plan work, identify hazards, define controls, and explain how workers should complete a task safely.

The two parts have different jobs.

A risk assessment asks:

• What can cause harm?
• Who could get hurt?
• How serious could the harm be?
• How likely is it to happen?
• What controls can reduce the risk?
• What level of risk remains?

A method statement then explains:

• What work will take place?
• Who will do the work?
• What equipment will they use?
• What steps will they follow?
• What controls must they use?
• What should they do if conditions change?
• What should they do during an emergency?

Therefore, RAMS connects risk planning with practical work instructions.

Why RAMS Matters

Good planning can prevent many avoidable problems.

For example, a construction team may plan to lift a heavy component. The risk assessment can identify crushing, falling-object, lifting, and vehicle hazards. Then, the method statement can explain the lifting sequence, equipment, exclusion zone, competent personnel, communication method, and emergency steps.

As a result, workers know what the job involves before they start.

A strong RAMS process can help organizations:

• Identify hazards early.
• Control workplace risks.
• Improve worker awareness.
• Standardize work methods.
• Clarify responsibilities.
• Improve contractor coordination.
• Support site inspections.
• Reduce avoidable incidents.
• Strengthen safety records.
• Improve project planning.

Furthermore, eAuditor’s construction method statement guidance identifies risk controls, responsibilities, work sequences, emergency procedures, inspections, and monitoring as key parts of a method statement.

Risk Assessment and Method Statement: Key Difference

The two documents work together, but they are not the same.

Risk Assessment

The risk assessment focuses on risk.

It identifies hazards, evaluates risk, and defines controls.

For example:

Hazard: Working at height.

Risk: A worker could fall.

Control: Use suitable edge protection and approved access equipment.

Method Statement

The method statement focuses on how the work will happen.

For example:

1. Inspect the work area.
2. Set up approved access equipment.
3. Install required edge protection.
4. Check equipment before use.
5. Complete the task.
6. Remove equipment safely.
7. Inspect the area after completion.

Therefore, the risk assessment answers “What can go wrong?”, while the method statement answers “How will we do the work safely?”

What Should a RAMS Document Include?

A RAMS document should match the work. However, most useful RAMS documents contain several common sections.

Project Information

Start with basic project details.

Include:

• Project name
• Site location
• Client
• Contractor
• Subcontractor
• Task name
• RAMS reference number
• Revision number
• Date
• Prepared by
• Reviewed by
• Approved by

This information helps workers identify the correct document.

Scope of Work

Next, explain what the RAMS covers.

Describe:

• Work activity
• Work area
• Start point
• End point
• Work boundaries
• Main deliverables
• Activities included
• Activities excluded

Keep the scope clear.

If the scope changes, review the RAMS before the team continues.

Roles and Responsibilities

Every RAMS should make responsibilities clear.

Identify:

• Project manager
• Site manager
• Supervisor
• Safety professional
• Competent workers
• Equipment operators
• Contractors
• Subcontractors
• First aider
• Emergency coordinator

Therefore, people know who manages each part of the work.

Risk Assessment Section

The risk assessment forms the safety foundation of RAMS.

Hazard Identification

First, identify the hazards linked to the task.

Common hazards include:

• Falls from height
• Moving vehicles
• Moving machinery
• Falling objects
• Electrical energy
• Fire
• Hot work
• Chemicals
• Dust
• Noise
• Vibration
• Manual handling
• Confined spaces
• Excavation
• Slips and trips
• Poor weather
• Environmental conditions

However, do not copy a generic hazard list and stop there.

Walk through the actual task.

Ask what could happen at each stage.

Who Could Be Harmed?

Next, identify people who may face the risk.

They may include:

• Employees
• Contractors
• Visitors
• Members of the public
• Drivers
• Equipment operators
• Maintenance workers
• Emergency responders

Also consider people who may need additional support.

Risk Evaluation

Then, assess each risk using your organization’s approved scoring method.

A common approach considers:

Likelihood × Severity = Risk Rating

However, organizations should use their approved risk matrix rather than applying a generic score without context.

eAuditor’s risk management guidance describes configuring likelihood and severity parameters and using structured risk scoring to support consistent assessments.

Control Measures

Next, define controls.

Use the strongest practical controls first.

Examples include:

• Remove the hazard.
• Change the work method.
• Use physical safeguards.
• Isolate energy sources.
• Use barriers.
• Improve ventilation.
• Use safe access systems.
• Provide training.
• Use suitable PPE.

The goal is to reduce risk at the source whenever possible.

Method Statement Section

Once the risks and controls are clear, explain how the work will happen.

Work Sequence

Break the job into simple steps.

For example:

1. Prepare the work area.
2. Inspect equipment.
3. Confirm permits and controls.
4. Establish exclusion zones.
5. Complete the work.
6. Monitor conditions.
7. Remove equipment.
8. Inspect the area.
9. Close the task.

This format helps workers follow the planned method.

eAuditor’s Construction Method Statement Template describes the work sequence as a core part of the method statement and includes site preparation, equipment setup, work sequence, inspection points, and completion activities.

Equipment and Materials

List the equipment needed.

This may include:

• Tools
• Plant
• Machinery
• Vehicles
• Lifting equipment
• Access equipment
• Materials
• Barriers
• Safety equipment
• PPE

Also, identify any inspection or certification requirements that apply.

Personal Protective Equipment

List PPE based on the assessed risks.

Depending on the task, this may include:

• Safety helmet
• Safety footwear
• Gloves
• Eye protection
• Hearing protection
• Respiratory protection
• High-visibility clothing
• Fall protection equipment

However, PPE should support stronger controls. It should not replace effective risk reduction where other controls are reasonably practicable.

Permits and Supporting Documents

Some work requires additional documents.

Depending on the task, RAMS may link to:

• Permit to work
• Hot work permit
• Confined space permit
• Isolation procedure
• Lifting plan
• Traffic management plan
• Emergency plan
• COSHH information
• Inspection certificates
• Equipment records
• Competency records

eAuditor’s Point of Work Risk Assessment template checks whether workers have the right documentation, including risk assessments, permits, and method statements. (eAuditor)

Emergency Procedures

Every RAMS should explain what happens when something goes wrong.

Include suitable arrangements for:

• Fire
• Injury
• Equipment failure
• Spill
• Evacuation
• Severe weather
• Utility strike
• Structural failure
• Loss of control
• Other foreseeable emergencies

Also, identify emergency contacts, first aid arrangements, evacuation routes, and assembly points where relevant.

eAuditor’s Construction Method Statement Template includes emergency contacts, first aid, evacuation procedures, fire response, and incident reporting within the method statement structure. (eAuditor)

Worker Consultation and Briefing

RAMS should not sit in an office.

Workers need to understand the document before they start.

Therefore:

• Explain the task.
• Review the hazards.
• Explain the controls.
• Discuss the work sequence.
• Confirm required PPE.
• Explain emergency arrangements.
• Allow workers to ask questions.
• Record attendance or acknowledgment where required.

Moreover, workers often know practical risks that may not appear in a generic assessment. Therefore, their input can improve the RAMS.

RAMS Approval

Before work starts, the right people should review and approve the RAMS.

The review should confirm:

• The scope is correct.
• Hazards are identified.
• Controls are suitable.
• The work method is clear.
• Required equipment is available.
• Competent workers are assigned.
• Emergency arrangements are suitable.
• Supporting documents are available.

eAuditor’s method statement guidance describes a review and approval process involving document preparation, safety review, client review, supervisor approval, and workforce communication. (eAuditor)

RAMS Review and Revision

RAMS should change when the work changes.

Review the document when:

• The work method changes.
• Site conditions change.
• New hazards appear.
• Equipment changes.
• Personnel change.
• An incident occurs.
• A near miss occurs.
• The control measures prove ineffective.
• The project enters a new phase.

For example, a method that works during early construction may not work once other contractors, vehicles, or services enter the same area.

Therefore, treat RAMS as a live safety document.

RAMS Site Inspection

A RAMS document is useful only when workers follow it.

Supervisors should check the work against the approved RAMS.

Inspect:

• Work method
• PPE
• Access
• Equipment
• Exclusion zones
• Control measures
• Permit conditions
• Site conditions
• Worker understanding

eAuditor’s Construction Site Risk Assessment Checklist asks whether nominated controls are in place and whether those controls remain effective. (eAuditor)

RAMS Non-Conformance and Corrective Actions

Site inspections may reveal gaps.

For example:

Finding: Workers are not using the required exclusion zone.

Risk: People could enter the lifting area.

Action: Stop the activity, establish the zone, brief the team, and verify compliance.

A digital workflow can connect the finding to an assigned corrective action.

Therefore, teams can track:

• Finding
• Responsible person
• Due date
• Action
• Evidence
• Completion
• Verification

How eAuditor Audits & Inspections Handles RAMS

eAuditor Audits & Inspections helps organizations move RAMS from static paperwork to a digital safety workflow.

Its construction method statement resources describe standardized templates, mobile access, collaboration, evidence capture, automated reporting, corrective action tracking, and centralized document management. (eAuditor)

Digital RAMS Templates

Teams can create structured templates for different tasks.

For example, they can build separate RAMS workflows for:

• Excavation
• Roofing
• Demolition
• Electrical work
• Lifting
• Scaffolding
• Hot work
• Concrete work
• Maintenance
• Work at height

As a result, teams can standardize the information required for each activity.

Mobile Access

Site teams can access digital safety information on mobile devices.

Therefore, supervisors and workers can review the current information where the work takes place.

eAuditor’s construction method statement guidance highlights mobile access, instant site access, reduced paperwork, and improved document control. (eAuditor)

Risk Assessment Checks

eAuditor can support structured risk assessments that cover hazards, risk ratings, and controls.

Its risk management guidance recommends configuring risk scoring and mandatory evidence fields, then recording hazards, locations, observations, and photographic evidence during assessments. (eAuditor)

Method Statement Management

Teams can document:

• Scope
• Work sequence
• Equipment
• Responsibilities
• Controls
• PPE
• Emergency procedures
• Environmental controls
• Inspection points

Therefore, workers receive a clearer picture of how the job should run.

Evidence Capture

Sometimes, a written note is not enough.

Teams can capture:

• Site photos
• Hazard photos
• Inspection evidence
• Comments
• Supporting documents
• Corrective action evidence

This creates a stronger record of what happened on site.

Corrective Action Tracking

When an inspection finds a problem, eAuditor can support corrective action management.

Teams can assign actions, set deadlines, monitor progress, and verify completion. eAuditor’s method statement guidance specifically describes assigning corrective actions, setting deadlines, monitoring status, and verifying corrective measures. (eAuditor)

Reporting and Document Control

Digital records can make reporting easier.

eAuditor’s construction method statement resources describe automated reports containing method statement details, inspection findings, corrective actions, and compliance records. They also describe centralized cloud storage and version control. (eAuditor)

As a result, managers can find the right record faster.

Linking RAMS With Site Inspections

RAMS should not operate alone.

Teams can connect the planned controls with actual site checks.

For example:

RAMS: Workers must use suitable fall protection.

Site inspection: Is fall protection in place and used correctly?

Finding: Control missing.

Corrective action: Stop the task and restore the control.

Verification: Supervisor confirms compliance.

This creates a useful link between planning and execution.

Common RAMS Mistakes

Even good teams can make simple mistakes.

Using Generic RAMS

A generic RAMS may miss site-specific hazards.

Instead, assess the actual task and conditions.

Writing Too Much

Long documents can become difficult to use.

Keep the language clear. Break complex work into simple steps.

Missing Control Measures

Listing a hazard without explaining the control does not give workers enough direction.

Therefore, connect each significant hazard to practical controls.

Ignoring Workers

Workers perform the task every day.

Their experience can reveal hazards that managers may miss.

Failing to Update RAMS

A RAMS document can become outdated quickly.

Review it when the task, environment, equipment, or controls change.

Treating Approval as the End

Approval only confirms that the document is suitable at that point.

Supervisors must still check that workers follow it.

RAMS Quick Checklist

Use this list as a starting point. Adapt it to the work and your organization’s requirements.

Project and Document Control

• Project details are correct.
• Site location is recorded.
• Scope is clear.
• Document reference is recorded.
• Revision number is current.
• Review date is recorded.
• Required approvals are complete.

Risk Assessment

• Hazards are identified.
• People at risk are identified.
• Existing controls are recorded.
• Risk ratings follow the approved method.
• Additional controls are defined.
• Residual risk is acceptable.
• Site-specific conditions are included.

Method Statement

• Work steps are clear.
• Responsibilities are defined.
• Equipment is listed.
• Materials are listed.
• PPE is identified.
• Permits are identified.
• Emergency arrangements are included.
• Environmental controls are included.

Worker Briefing

• Workers received the RAMS briefing.
• Workers understood the controls.
• Questions were addressed.
• Required competency was confirmed.
• Attendance or acknowledgment was recorded where required.

Site Verification

• RAMS is available on site.
• Workers follow the approved method.
• Controls are in place.
• Controls remain effective.
• Equipment remains suitable.
• Site conditions remain consistent with the RAMS.

Review

• Changes are recorded.
• Findings are documented.
• Corrective actions are assigned.
• Actions are closed.
• RAMS is reviewed after significant changes.

RAMS Benefits for Different Teams

RAMS can help different people in different ways.

For Project Managers

RAMS provides a structured way to plan work, assign responsibilities, and monitor safety requirements.

For Site Supervisors

It gives supervisors a clear reference for checking work methods and controls.

For Workers

It explains what they need to do and which controls they need to follow.

For Contractors

It helps align contractor activities with site requirements.

For Safety Teams

It provides a basis for risk review, inspection, monitoring, and corrective action.

For Clients

It provides evidence that the project team planned the work and established safety controls.

Related Verified eAuditor Resources

The following resources come from eAuditor’s own website or template library. They relate directly to RAMS, risk assessment, method statements, and construction safety.

eAuditor Template Library

Construction Site Risk Assessment Checklist — includes daily risk assessment and Safe Work Method Statement checks, including site-specific hazards, controls, training, plant, and environmental considerations.

Construction Site Risk Assessment Checklist — SWMS Version — checks whether the SWMS is available, site-specific, covers tasks and hazards, identifies supporting documents, and has workforce sign-off.

Point of Work Risk Assessment Guide and Checklist — checks risk assessments, permits, method statements, PPE, access, tools, work at height, chemicals, and other task hazards.

Safety File Audit Checklist — includes checks for method statements, site-specific risk assessments, safe work procedures, monitoring plans, emergency plans, and related safety documentation.

Axis Site Inspection Checklist — includes checks for method statements, risk assessments, worker competency, PPE, work at height, tools, hot work, and site activities.

Verified eAuditor Blog Articles

Construction Method Statement Template — covers project information, scope, responsibilities, equipment, work sequence, risk controls, emergency procedures, approvals, and digital method statement management.

Construction Safe Work Method Statement (SWMS) — explains digital SWMS templates, mobile access, real-time compliance checks, evidence capture, and corrective action tracking.

Risk Management Checklist — covers risk assessment template design, risk identification, scoring, evidence capture, and risk evaluation.

Contractor Management Checklist — includes contractor checks for RAMS, induction, competence, and site safety requirements.

Construction Site Risk Assessment Checklist — a related eAuditor resource for construction risk assessment and site safety management.

Frequently Asked Questions

1. What does RAMS stand for?

RAMS stands for Risk Assessment and Method Statement. It combines risk assessment with a practical method statement for completing work safely.

2. What is the purpose of RAMS?

RAMS helps teams identify hazards, assess risks, define controls, and explain how workers should complete the task safely.

3. What is the difference between a risk assessment and a method statement?

A risk assessment identifies hazards and evaluates risks. In contrast, a method statement explains the safe sequence and controls for completing the work.

4. Who should prepare RAMS?

A competent person with suitable knowledge of the work should prepare the RAMS. Depending on the project, this may involve a project manager, site manager, engineer, supervisor, safety professional, or contractor.

5. When should RAMS be completed?

RAMS should be prepared and reviewed before the relevant work starts. Teams should also review it when conditions, methods, equipment, or risks change.

6. Do workers need to read the RAMS?

Yes. Workers who perform the task need to understand the hazards, controls, work method, and emergency arrangements that apply to them.

7. Can RAMS be used for every type of work?

RAMS can support many types of work. However, the content must match the actual task, hazards, site conditions, and applicable requirements.

8. Can eAuditor manage RAMS digitally?

Yes. eAuditor supports digital method statement and risk assessment workflows, including templates, mobile access, evidence capture, corrective actions, reporting, and document management.

9. Can eAuditor track RAMS corrective actions?

Yes. Teams can assign corrective actions, set deadlines, monitor progress, and verify completion.

10. How often should RAMS be reviewed?

Review RAMS whenever the work changes, new hazards appear, controls change, an incident or near miss occurs, or site conditions make the existing document unsuitable. Regular review also helps keep the document useful throughout the project.

Final Thoughts

A Risk Assessment and Method Statement does more than satisfy a paperwork requirement.

It helps teams think before they act.

First, the risk assessment identifies what could cause harm. Then, the method statement explains how the team will control those risks while completing the work. After that, site inspections can check whether workers actually follow the agreed method.

That connection matters.

With eAuditor Audits & Inspections, organizations can bring risk assessments, method statements, site checks, evidence, corrective actions, and reports into a digital workflow. Therefore, teams can move from static documents to a more active safety process.

Most importantly, RAMS should remain practical. Workers should understand it. Supervisors should use it. Managers should review it. And when conditions change, the document should change too.

When teams follow that approach, RAMS becomes more than a document. It becomes part of how safer work gets done.