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 · Last reviewed 18 August 2026
Start the pack
- 1
Open RAMS and start a new pack for the job — it gets its own RAMS reference.
- 2
Bind the risk assessments and COSHH assessments that govern the work. Binding is by published version, and suggested bindings rank your own registers against the job — a deterministic rule, not a guess.
Build the method against the hazards
- 1
Open the pack builder and bring in method-statement steps from the library, or write steps for this pack.
- 2
Where a step controls a hazard, reference the hazard from the bound assessment version — the step points at the real hazard rather than restating it in different words.
Note: This referencing model is what keeps a pack coherent: the method cannot quietly drift away from the assessment it claims to implement.
Pass the gate and issue
- 1
Issue the pack. The gate checks it first — its headline rule refuses a pack where a high-residual hazard in a bound assessment is addressed by no step.
- 2
Fix what the gate names, then issue. Issuing freezes the full snapshot — statements, steps, bound hazards — and records the author’s attestation.
- 3
Download the pack PDF for the job file; it renders from the frozen version.
Tip: When a bound risk assessment is later revised, the issued pack does not change — re-issue deliberately, as version two, when the job should pick up the new assessment.