← Inside PlanOps

The standard

The PlanOps RAMS Review Standard

The PlanOps team12 min read
The PlanOps RAMS Review Standard: twenty tests, four parts, one score where every point lost is traceable to a named criterion - shown as the weights of the twenty tests grouped into the four parts of the review

Version 1.2.1. First effective 30 July 2026 as v1.0.0. Published by PlanOps. Licensed under CC BY 4.0: use it, print it, adapt it, with attribution. The argument for the standard is in What a competent RAMS review actually tests.


What this is

A published, versioned standard for reviewing a subcontractor's risk assessment and method statement (RAMS) against the requirement the principal contractor issued for the activity. It defines twenty tests in four parts, the weight of each, the legal or project basis each one supports, and an arithmetic method that turns the reviewer's verdicts into a 0 to 100 score where every point lost is traceable to a named criterion.

It is written so that a health and safety manager can adopt it on paper without any software. It is also the standard PlanOps runs automatically on every RAMS submitted through the platform.

It is not a British Standard and it is not a legal opinion. Passing a test here is evidence towards managing a duty or requirement, not proof that the duty has been discharged.

The statutory references in this edition are mainly for construction work in Great Britain. References to Building Regulations Part 2A apply to building work in England. Different legislation applies in Northern Ireland.

How to use it on paper

The whole standard fits on two sides of A4: download the two-page checklist (PDF), print it, and put it next to the submission.

  1. Have the requirement you issued for the activity to hand: the risk category, the legislation you cited, any permit, any temporary works reference, the activity description, the risk level, and your organisation's own rules if any.
  2. For each of the twenty criteria, record a verdict: met, partially met, not met, or does not apply. "Does not apply" covers two situations: a criterion the activity does not engage at all (for example criterion 20 when no organisation rules were issued), and a criterion whose comparison material you do not have (see "The document-only subset" below). Every criterion must carry a verdict.
  3. For each criterion that is partially met or not met, record a severity: critical, major or minor. Critical means work under this RAMS could kill or seriously injure someone (no rescue plan, no temporary works design). Major means a material gap that must be closed before work starts. Minor means a limited deficiency that would not, on its own, materially affect safe execution.
  4. Score it using the method below, or simply apply the caps: any critical not met, serious gaps, send it back; any critical partially met, significant gaps; any major finding, at best gaps to close.
  5. Return the verdicts to the subcontractor with the review. The list of what was tested is the review.

The four parts and twenty criteria

Weights sum to 100. The "evidence basis" column is a guide to why the criterion matters. It may name a direct legal duty, recognised guidance or good practice, or a project or contract requirement. It should not be read as saying the law requires that exact RAMS heading or wording. Abbreviations: MHSWR is the Management of Health and Safety at Work Regulations 1999; CDM is the Construction (Design and Management) Regulations 2015; HSWA is the Health and Safety at Work etc. Act 1974; Part 2A is Part 2A of the Building Regulations 2010 (England, competence, from 1 October 2023).

Part 1: Is the risk assessment real? (18 points)

#CriterionThe testWeightEvidence basis
1Method statement supported by risk assessmentEvery safety-significant method statement step rests on an assessed risk, and the risk assessment and method statement clearly connect to each other rather than sit side by side.9MHSWR reg 3; CDM reg 15(2); HSE guidance on using method statements to put risk assessments into practice
2Foreseeable hazards and controls for this trade, this activity and this siteThe risk assessment covers the hazards this activity actually presents on this site, with controls that follow the hierarchy of control.9MHSWR regs 3 and 4 and Schedule 1; CDM regs 13 and 15 where applicable

Part 2: Does the method statement say enough? (56 points)

Each criterion asks the same shape of question: is this section present, specific and adequate?

#CriterionThe testWeightEvidence basis
3Scope of works stated and specificThe method statement states its scope (locations, boundaries, exclusions, interfaces) specifically enough for the remaining criteria to be audited against it. Tests presence and specificity only; whether the scope matches the activity you asked for is criterion 18.5Supports CDM reg 15(2) planning and management: the work has to be clear before it can be planned
4ProgrammeDuration, sequence and working hours are stated well enough to judge the controls against them.3CDM reg 13(2) sequencing and time allowed; CDM reg 12 construction phase plan; CDM reg 15(4) where there is only one contractor
5Resources, competence and equipmentPeople, plant and equipment are named, with competence requirements and supporting evidence (cards, tickets, certificates) where applicable.5CDM regs 8 and 15(7); PUWER regs 4 and 9 where work equipment is used; Part 2A regs 11E and 11F where building work in England is in scope
6Hazard identificationHazards are task-specific rather than generic, with competent input where needed and review or authorisation under the contractor's own arrangements.7MHSWR regs 3, 5 and 7
7Control measuresSupervision, permits, inspection regimes, briefings and PPE are specified and workable.8MHSWR reg 5; CDM regs 15(2) and 15(8); Personal Protective Equipment at Work Regulations 1992 as amended
8Emergency arrangementsRescue, first aid, welfare and raising-the-alarm arrangements are specific to this activity and location.7CDM regs 30 and 31; MHSWR reg 8; Health and Safety (First-Aid) Regulations 1981; CDM Schedule 2 welfare; activity-specific rescue duties where applicable
9Temporary worksTemporary works coordination, design, checks and lifting responsibilities are addressed where the activity involves them.6CDM reg 19; BS 5975-1:2024 as recognised temporary works management practice; BS 5975-2:2024 where falsework is relevant; LOLER 1998 where lifting
10Interface with others and the publicSegregation, signage, security, dust and noise controls address who else is affected.5CDM regs 13(1) and 13(3) coordination; CDM regs 17 and 18; HSWA s3; COSHH, noise and environmental duties where those risks are present
11Training and informationInduction, task briefing, specialist training and card requirements are stated where applicable.4CDM regs 13(4), 15(8) and 15(9); MHSWR reg 13; Part 2A reg 11F for building work in England; site or scheme card rules where applicable
12Environmental issuesWaste, pollution prevention, noise, permits and monitoring are addressed where the activity or project requires them.3Project and environmental requirements; Environmental Protection Act 1990 s34 for waste; Control of Pollution Act 1974 ss60-61 where construction-noise controls or consents apply; environmental permits and site consents where applicable
13Monitoring and reviewChecking, enforcement, change management and briefing records are described.3CDM reg 15(2) "monitor"; MHSWR reg 3(3) review of assessment; briefing records as evidence of management

Part 3: Does it answer the requirement you issued? (22 points)

Each criterion compares the submission against the requirement for this activity.

#CriterionThe testWeightEvidence basis
14Addresses the risk category on your requirementThe submission engages the specific hazard category your requirement identifies.4Supports the principal contractor's CDM reg 13 planning and coordination duties; this standard uses the issued risk category as the comparison point
15Addresses the legislation cited on your requirementFor each piece of legislation or guidance named on the requirement, the relevant requirements are addressed in the method and controls.4Applicable duties under the legislation or guidance identified on the requirement, for example LOLER 1998, Work at Height Regs 2005, CAR 2012, COSHH 2002 or Electricity at Work Regs 1989
16References the permit process you requireWhere the requirement calls for a permit, the submission references raising and closing it.3CDM regs 12 and 15(3) where the permit forms part of the construction phase plan, site rules or a principal contractor or principal designer direction; otherwise a project or site requirement
17Addresses the temporary works you referencedWhere the requirement references temporary works, their design, inspection and coordination are addressed.3CDM reg 19; BS 5975-1:2024 as recognised temporary works management practice; BS 5975-2:2024 where falsework is relevant
18Scope matches the activity on your requirementThe submitted scope neither falls short of nor overruns the activity the requirement describes. Tests conformity only; whether a scope is stated specifically enough to audit at all is criterion 3.4Supports CDM reg 13 coordination by checking that this is the right RAMS for the right work
19Controls proportionate to the riskControls are proportionate to the actual foreseeable risk, taking account of the risk level recorded on the requirement.4MHSWR reg 3 suitable and sufficient assessment; CDM reg 15(2) planning and management; the requirement's risk level is used as review evidence, not as a substitute for the contractor's own assessment

Part 4: Does it meet your own rules? (4 points)

#CriterionThe testWeightEvidence basis
20Organisation requirementsGaps against your organisation's own requirements (client standards, framework conditions, site rules beyond the regulations). Does not apply when none were issued.4CDM regs 13(3) and 15(3) where the requirement is in the construction phase plan, site rules or a principal contractor or principal designer direction; other client, framework or company rules are project or contract requirements

Two conduct rules apply to Part 4 and are not scored: cite each organisation requirement by its exact reference when it is used as a test; and where no organisation requirements were issued, do not invent any, mark criterion 20 as does not apply.

The document-only subset

The twenty criteria divide by what they need in front of the reviewer, and any review claiming this standard must say which set it ran.

Criteria 1 to 13 are document-only. They can be assessed from the RAMS itself: whether the risk assessment is real and whether the method statement says enough. Together they carry 74 of the 100 weight.

Criteria 14 to 20 are comparison criteria. Every one tests the submission against something the reviewer must hold: the requirement issued for the activity (its risk category, cited legislation, permit, temporary works references, activity description and risk level) for 14 to 19, and the organisation's own rules for 20. Without that material there is nothing to compare against, and the standard's own rule applies: a criterion whose comparison material is absent is recorded as does not apply and leaves the denominator. It is never guessed from the document, and its absence is never scored as a failure.

A review run without the requirement is therefore a document-only review: thirteen criteria over an applicable weight of 74 (less anything else that does not apply), and stated as such. It is a legitimate first pass and an incomplete review, and the result must say which it was. This is exactly how the free review at planops.ai/rams-review runs: it reads one document with no sight of any project, so it assesses the thirteen document-only criteria and reports criteria 14 to 20 as not applicable. Inside a project, where the requirement and the organisation rules exist, all twenty run.

Any result from a document-only review should carry the subset on its face, not in a footnote: "Document-only review: 13 of 20 tests assessed, applicable weight 74", ahead of the score. A document-only 92 and a full-review 92 are not the same level of scrutiny, and the result is the place to say so.

Scoring method

The score is arithmetic over the verdicts. The reviewer is never asked for a number.

Verdict factors.

VerdictFactor
Met0
Partially met0.5
Not met1.0
Does not applyremoved from denominator

Severity factors.

SeverityFactor
Critical1.0
Major0.6
Minor0.25
None0

Formula.

applicable_weight = sum of weights of criteria that apply
deduction(i)      = weight(i) x verdict_factor(i) x severity_factor(i)
score_before_caps = 100 x (applicable_weight - sum of deductions) / applicable_weight
score             = round( min(score_before_caps, cap) )

where cap = 100 when no cap condition below applies

Because no deduction can exceed its own weight, the score is inside 0 to 100 by construction.

Caps. Applied after the arithmetic, lowest cap wins.

WhenMaximum scoreWhy
Any criterion not met at critical severity49A single critical failure (no rescue plan, no temporary works design) puts the RAMS in the bottom band regardless of how much else it does well. Weighted deduction alone would leave such a submission in the nineties.
Any criterion partially met at critical severity69A partially addressed critical risk cannot sit above the significant-gaps band.
Any criterion not met or partially met at major severity89The top band is defined as "no material gaps; any findings are minor". A major finding contradicts that definition, so it must put the score below 90 however small the criterion's weight. Without this cap two major findings on low-weight criteria scored 96.

Coverage rule. Every criterion must carry a verdict. A score derived from a partial assessment is not a score: when any criterion is unassessed, report the score as unavailable and name the criteria that were missed.

Unavailable rule. When the review could not be read or completed, the score is null with a stated reason. Zero is never used to mean "could not assess". Zero is a real score, reserved for a submission that fails every applicable criterion at critical severity.

Bands

Band names describe the RAMS overall; they are not descriptions of the severity of individual findings. A single major finding places the whole document in the gaps-to-close band, because the top band is defined by the absence of material gaps.

ScoreBandMeaning
90 to 100No material gapsNothing was flagged against the twenty criteria that would hold this document up at review; any findings are minor and do not, on their own, affect safe execution.
70 to 89Gaps to closeThe substance is there, but at least one material gap remains. Work should not start until the points listed are closed.
50 to 69Significant gapsSeveral criteria are only partly addressed, or the shortfalls are wide. Expect it to come back for revision rather than be accepted as issued.
0 to 49Serious gapsThe submission has serious deficiencies, or at least one critical test has not been addressed. Send it back for rework before it goes any further.
No scoreNot scoredNot every criterion could be assessed, so no overall result is issued. The individual findings still stand.

Worked examples

1. Everything met, no organisation rules issued. Criteria 1 to 19 met; criterion 20 does not apply. Applicable weight 96, deductions 0. Score 100. No material gaps.

2. One major gap only. Everything met except emergency arrangements (criterion 8, weight 7), not met at major severity. No organisation requirements were issued, so criterion 20 does not apply. Deduction 7 x 1.0 x 0.6 = 4.2 of 96 applicable, which is 95.6 before caps. The major-finding cap brings it to 89. Gaps to close. A major gap cannot sit in the top band.

3. The steel-frame erection RAMS. A synthetic example used to design and test the method (the subcontractor and site are fictional). Twelve-storey steel frame, requirement titled "Tower crane operations, steel frame erection", citing LOLER 1998, CDM 2015 and BS 7121-1 and BS 7121-5, requiring a lifting permit and referencing the crane foundation temporary works, adjacent to an occupied office building with a noise restriction.

#VerdictSeverityDeductionPoints lost (of 100)
1MetNone00
2Partially metMajor2.702.81
3MetNone00
4Not metMajor1.801.87
5Partially metMajor1.501.56
6Not metCritical7.007.29
7Partially metMajor2.402.50
8Not metCritical7.007.29
9Not metCritical6.006.25
10Not metMajor3.003.12
11MetNone00
12Not metMajor1.801.87
13Partially metMinor0.380.39
14Not metCritical4.004.17
15Not metCritical4.004.17
16Not metMajor1.801.87
17Partially metMajor0.900.94
18Partially metMinor0.500.52
19Not metMajor2.402.50
20Does not apply

Applicable weight 96. Deductions 47.2. Score before caps 50.9. Five criteria not met at critical severity (6, 8, 9, 14, 15), so the cap applies: 49. Serious gaps.

The two scope criteria

Criteria 3 and 18 both concern scope and deliberately test different things. Criterion 3 sits in Part 2 and asks what every criterion in that part asks: is the section present, specific and adequate. Criterion 18 sits in Part 3 and does what every criterion in that part does: compares the submission with the requirement. The failures are different and so are the remedies. A vague scope means rewrite the method statement; a mismatched scope means this is the wrong RAMS for the activity. Up to v1.0.0 the two were worded so similarly that a scope mismatch was double-counted in practice; v1.1.0 corrected the wording rather than merging the criteria, so no ids, weights or scores changed.

Changelog

VersionDateChange
1.2.125 August 2026Clarified the legal and project basis in the "evidence basis" column, including jurisdiction, temporary works references, organisation requirements, environmental requirements, competent review, permits and proportionality to risk. Corrected two scoring-text examples: zero applies when every applicable criterion fails at critical severity, and example 2 now states why criterion 20 is not applicable. No ids, weights, factors, caps or band thresholds changed.
1.2.021 August 2026External review changes: corrected the 0 to 49 band description (a score below 50 can arise from accumulated major findings with no critical failure); renamed the 70 to 89 band from Minor gaps to Gaps to close and stated that band names describe the document, not individual findings; redefined minor severity as not materially affecting safe execution on its own; stated cap = 100 when no cap condition applies; reworded criteria 1 (safety-significant steps), 5 (competence evidence where applicable) and 15 (requirements addressed in method and controls); corrected the steel-frame example description from three to five critical failures. No ids, weights, factors, caps or band thresholds changed.
1.1.09 August 2026Reworded criteria 3 and 18 so the scope test each performs is distinct. No criterion ids, weights, verdict or severity factors, caps or bands changed; every score recorded under 1.0.0 remains comparable.
1.0.030 July 2026First published standard. The review score is derived from criterion verdicts rather than asked of the reviewer.

Criticism and adoption

If a weight, a test or a duty reference is wrong, tell us. Changes that alter the meaning of a stored score (renumbering, reweighting, new criteria) are published as a new major version with the old one kept readable. Clarifications are minor versions. Contributors are credited in the changelog.

RAMSHealth and safetyStandardsCDM 2015

Tell your project what you need.

Start free with 50 IU. No credit card, no training, no waiting.

Start free