RAMS & method statements
RAMS packs with nothing invented
Steps reference hazards in the bound risk-assessment versions instead of restating them, so the pack cannot drift from the assessment. Issue freezes a snapshot, briefings record against the exact version, and clients accept the exact thing you sent.
Included free — like the rest of the platform.
How it works
- 1
Write the method statement
Sequenced steps with PPE, plant, trades and hold points — eight starter templates carry the authoring load, and every statement gets its own MS reference.
- 2
Bind the assessments
A pack binds specific published risk-assessment and COSHH versions. Suggested bindings rank your own registers against the job — a deterministic rule, not a guess.
- 3
Pass the gate, issue the pack
The issue gate refuses a pack where a high-residual hazard is addressed by no step. Issuing freezes the full snapshot — a later revision to the risk assessment never alters what was issued.
- 4
Brief the workforce
Version-anchored briefings with signatures, captured for a whole gang at once — and queued offline with sync failures surfaced, never silently lost.
- 5
Send it out, take them in
Issue to a client on a share link and record their acceptance against the exact version. On the other side, review contractors’ incoming packs against a proper checklist.
What it does
Method-statement library
Reusable statements with starter templates, hold points and PPE vocabularies — written once, used across packs.
Binding by version
Packs bind RA and COSHH versions, not documents-in-general — so "which assessment was this built on" has an exact answer.
The issue gate
A pack with an unaddressed high-residual hazard does not issue. The headline rule, enforced structurally.
Append-only briefings
Briefing records are version-anchored and signed. Re-issuing warns that briefings need re-taking — it never quietly invalidates them.
Client issue & acceptance
Share links carry the pack to people without accounts; their acceptance decision is recorded against the exact version.
Contractor pack reviews
Incoming RAMS from contractors reviewed against a checklist, on the record, beside their other documents.
What was in force on the day
After an event, nobody cares what the pack says now. They ask what it said then, and who was briefed on it.
- Issued versions freeze the full snapshot — bound hazards included
- Re-issue writes version n+1 and leaves n readable, with its briefings intact
- The investigator’s question has a one-click answer
Guides for this module
Write a method statement
Sequenced steps with PPE, plant and hold points — built once in the library, reused across packs.
5 min read
Build and issue a RAMS pack
Bind real risk-assessment versions, reference their hazards from the steps, and pass the gate that refuses an incoherent pack.
7 min read
Brief the workforce and send the pack out
Version-anchored briefings with signatures — plus client issue by link, and the review queue for packs contractors send you.
6 min read
Works with
Risk assessments
The HSE five-step method as a working editor — signed, versioned, acknowledged by the people it protects.
Permits to work
Authorise high-risk work with the checks that must happen first — and a live board of what is open right now.
Contractors
Approve who comes on site: documents and insurance verified, RAMS reviewed, inductions done, sign-in at the gate.