RAMS · PDF packs
● RAMSfiredoorapp.co.uk
RAMS delivery
Risk and method on the job record.
When to create RAMS against live work, what belongs in RA and MS, versioning when scope moves, and issuing client-ready PDF packs from the same data.
When
Content
Versions
PDF pack
RAMS should read like the same job the inspection and quote already describe — not a generic template.
When to create
TriggerAfter quote scope agreed · before high-risk work
LinkRAMS sits on same job ID as inspection
Site fitAccess route · hot works · lifts realistic
EvidenceReference photos already on door record
ClientApproval captured before high-risk steps
HoldWeather / access gate logged on job
RAMS should not float in email attachments outside the job file.
If the job ID on RAMS does not match the quote, stop — that is how wrong doors get worked.
What to include
✓Hazards named with proportionate controls
✓Method steps in order · tools and stops clear
✓PPE matches what you actually enforce on site
✓Preset baseline + site tweaks — not one-off chaos per door
✓Competent person named where policy requires
✓Rescue / fire arrangements match site rules
Presets keep field teams fast; revisions track client changes.
Site-specific paragraphs belong in the MS — not only in the site manager’s notebook.
Issuing PDFs
GenerateFrom live RAMS + quote data
BundleMethod + risk + scope reference
RevisionRev letter bumps when scope edits
PortalClient sees same revision as PDF
EmailOptional copy · link still authoritative
ArchivePack hash stored on job for audit
Hand off from the record the client already trusts. Full walkthrough below.
Guide below
Platform builder →
When scope changes, bump revision before the crew returns — old RAMS should not cover new work.