RAMS (Risk Assessments & Method Statement) Online: Everything You Need to Know
Published 30/10/2026

Loose safety documentation has a habit of letting people down. Word documents and spreadsheets get saved in a dozen different places, versions drift apart, and proving compliance after the fact can feel like guesswork.
This is part of why so many teams are moving away from scattered files and into a proper RAMS Online system, one that keeps Risk Assessments and Method Statements in a single, trackable place rather than spread across inboxes and shared drives. This guide walks through what RAMS is, who tends to rely on it, how to put one together properly, and why a platform like Online Induction is worth considering for managing it day to day.
View templates, forms and examples
See how RAMS sign-off works inside an online induction.
What Is RAMS?
RAMS stands for Risk Assessment and Method Statement, and it's genuinely two documents working together rather than one.
Risk assessment
Looks at the hazards involved in a task and how likely each one is to cause harm.
Method statement
Walks through, step by step, how the work should actually be carried out safely, including who's responsible for what along the way.
RAMS tends to be reserved for higher-risk or specialised work rather than everyday tasks, things like working at height, operating heavy machinery, or handling hazardous materials. The job is broken into stages, the risks at each stage are named honestly, and the controls needed to manage them are spelled out clearly enough that anyone on the team can follow along without second-guessing.
It's worth being upfront that RAMS isn't itself a single legally mandated document. It's the pairing of a risk assessment, which is a legal requirement in most places, with a method statement, which isn't always compulsory but has become the accepted, sensible way to plan and manage higher-risk work. Together, they give a fuller, more honest picture of what could go wrong and exactly what to do about it.
Is RAMS the Same as a Method Statement?
Not quite, though it's an easy mix-up. A method statement is one half of RAMS, not the whole thing. RAMS is the combination of a risk assessment, which identifies hazards and how likely they are to cause harm, and a method statement, which sets out the step-by-step process for carrying out the task safely.
People often use "RAMS" and "method statement" interchangeably in everyday conversation, but a method statement on its own doesn't include the formal hazard and risk analysis that makes up the "RA" half of RAMS. A complete RAMS document genuinely needs both parts to be useful, and to hold up under scrutiny.
Who Uses RAMS?

RAMS is most closely tied to construction, though it isn't limited to it. Any business working with higher-risk tasks, including manufacturing, engineering, logistics, utilities, and facilities management, can reasonably use RAMS to plan safely.
Within construction, RAMS tends to show up at a few different levels:
Principal and main contractors
Use RAMS to show that site activities have been thought through properly and that safe systems of work are genuinely in place before anything starts.
Subcontractors and specialist trades
Are usually asked to submit RAMS before beginning on site, and it's often requested during tendering as evidence that a contractor takes safety seriously.
Site managers and safety officers
Review and approve RAMS, then use it to brief workers before higher-risk tasks begin.
Clients and public sector project owners
Frequently look over subcontractors' RAMS as part of their own due diligence before granting site access.
In short, wherever a main contractor or client needs reassurance that risk has genuinely been considered in advance, RAMS is the document that provides it, and it's often checked across every subcontractor and supplier on a project rather than just once at the start.
How to Set Up RAMS
A well-built RAMS document tends to follow a fairly consistent structure, whether it's drafted in a Word document or built directly in a proper system.

At minimum, it should include:
- Project and task detailsIncluding the start date, expected duration, and the date the risk assessment was carried out.
- Document control informationSuch as the author's name and a revision number, so any changes can be tracked honestly over time.
- Key personnelListing the managers, supervisors, workers, and subcontractors involved in the task.
- Regulatory contextReferencing any relevant laws, industry standards, or best-practice guidance that applies to the work.
- Hazard identificationSummarising the hazards drawn from the underlying risk assessment.
- Step-by-step methodLaying out a clear sequence of how the task will actually be carried out, with the relevant control measure noted at each step.
- Sign-off and acknowledgementConfirming that every worker involved has genuinely read, understood, and agreed to follow the RAMS before starting.
Once drafted, a RAMS document should be reviewed and approved by a competent person, such as a site manager or health and safety advisor, then shared with everyone involved and signed off before work begins.
It's also worth building in a routine review. RAMS should be revisited whenever the scope of work, site conditions, or personnel change, since a document that's fallen out of date can't really protect anyone.
Can RAMS Be Generic, or Does It Need to Be Site-Specific?
Generic RAMS templates certainly have their place. They're a sensible starting point and can save time on tasks that are genuinely standard and repeatable. But a RAMS document is only as useful as its relevance to the actual conditions on site, and a purely generic document is unlikely to hold up well to scrutiny.
Site-specific factors, such as access arrangements, ground conditions, weather exposure, nearby workers or public areas, the equipment being used, and the sequence of other trades on site, can all genuinely change the level of risk and the controls needed.
Good practice is to start from a template where one exists, then honestly adapt it to reflect the real task, site, and conditions before it's approved and signed off. Main contractors and clients reviewing RAMS will often send back documents that look copy-pasted and don't reference the specific job at hand.
How Long Do You Need to Keep RAMS on File?
There isn't one universal answer here, since retention requirements vary by country, industry, and the nature of the work involved. As a general guide, RAMS should be kept for the duration of the project and for a reasonable period afterward, in case of a claim, dispute, or investigation.
Many businesses keep records for several years as standard practice, and longer where the work involves higher risks, such as asbestos or structural work, or where local regulations set a specific minimum. It's worth checking the retention rules that apply in your own jurisdiction and industry rather than assuming, and building that into your document management process from the start rather than treating it as an afterthought.
This is one area where a proper RAMS management system genuinely helps: records are stored centrally and are far less likely to be misplaced than a file buried in someone's inbox or an old spreadsheet.
What Happens if RAMS Isn't Followed on Site?
Ignoring or deviating from an approved RAMS undermines the entire reason it exists, which is to prevent harm on tasks that carry real risk. In practice, failing to follow RAMS can lead to a few different outcomes:
The task is stopped
A supervisor or site manager may stop the task on the spot.
Disciplinary action
The worker or contractor involved may face disciplinary action.
Reporting and investigation
Depending on severity, the incident may need to be reported and investigated.
Legal and insurance implications
If an accident happens and it later comes out that the RAMS wasn't followed, it may point to a wider failure to properly manage and enforce safety procedures.
This is why sign-off, supervision, and clear records of who has acknowledged a RAMS matter just as much as writing the document well in the first place.
Why Online Induction Is a Strong Fit for RAMS Management
RAMS managed through spreadsheets, email threads, and untracked shared documents tends to run into the same problems again and again. Files get duplicated or fall out of date, sign-offs are hard to verify, and there's rarely a reliable way to prove, during an audit or after an incident, who actually read and acknowledged a RAMS before starting work. Managing RAMS through an online induction and contractor management platform addresses these issues directly, rather than treating RAMS as a separate, disconnected task bolted onto everything else.
Online Induction brings contractor management, employee and site inductions, visitor sign-in, and contractor prequalification together into one connected system. That matters for RAMS management in a few practical, grounded ways:
RAMS review built into the induction process
Because inductions, contractor management, and RAMS can sit in the same workflow, a worker simply can't complete their induction, and therefore can't get on site, without first engaging with the relevant RAMS.
Digital sign-off and a clear audit trail
Instead of chasing replies over email or checking who's ticked a box on a shared spreadsheet, acknowledgement happens within the system itself and is timestamped, giving management an honest, retrievable record of who signed off on which RAMS and when.
Centralised, current documents
RAMS live in one place rather than being scattered across emails, shared drives, and spreadsheets, so everyone is signing off on the current version rather than something outdated.
Scales across contractors and multiple sites
The platform is built to work for small teams and large enterprises alike, which suits organisations trying to keep RAMS processes consistent across a whole supply chain.
Customisable rather than one-size-fits-all
Setup can be shaped around different trades, sites, or risk levels, so RAMS requirements don't need to be rebuilt from scratch for every new contractor or project.
Bring RAMS into your induction process
For any organisation that already requires induction before granting site access, folding RAMS management into that same digital process is a fairly natural next step. It closes the gap between the RAMS being written and every worker on site genuinely having read, understood, and agreed to it, which is really the whole point of having RAMS in the first place.
View templates, forms, checklists and courses