The problem with project-by-project RAMS
RAMS written project-by-project look fresh on paper and decay fast in practice. Hazards drift. Wording diverges. Approvers default to rubber-stamp. The next audit exposes inconsistency that was always there but never visible at the page level.
The factory pattern
- Task library - the irreducible unit is the task, not the project. Each task carries its own hazards, control measures, PPE, training and evidence requirements.
- Method statements assemble from tasks - the project method statement composes tasks plus project-specific narrative, never freehand controls.
- Evidence attached at production - toolbox talks, training records, COSHH sheets and inspection records hang off the task they evidence.
- Approval gates - supervisor sign-off is one click, with the approver pinned to the version they approved.
What changes
Production time drops by a third or more - typically 40% in pilot data - because the assembly is template-driven. Audit response time drops further: instead of trawling SharePoint, you point at the task and its evidence index. And RAMS rewrites at re-tender stage become composition exercises, not blank-page work.