Another RAMS request at four o'clock
A facilities management client emails at four in the afternoon: the engineer booked for tomorrow's condenser replacement on their roof cannot attend without site-specific RAMS, a permit to work for roof access and a lifting plan for the crane. The service manager opens a RAMS from a similar job, changes the address, edits the access section, forgets to remove the reference to scaffold from the previous site, and sends it at seven. The client rejects it.
Documents copied, not built
Your safety management system has sound method statements and risk assessments, written and approved by your competent people. What makes each job's document slow is that it needs to be site-specific: the client, the access route, the working at height arrangements, the permits required, the emergency arrangements at that site. Copying the last similar document is the fastest way, and the most error-prone.
Air conditioning work also changes shape often. A service visit becomes a compressor change, a replacement needs a crane instead of a hoist, or the client's roof access rules change. Each change means another version of a document that was already written in a hurry.
- Each RAMS is edited from a previous one.
- Site details are retyped, and old details slip through.
- Client permit processes differ and are tracked by email.
- Signed versions are hard to find later.
- Engineers do not always have the approved version on site.
What the rewriting costs
Senior time every week on documents. Jobs delayed or refused at the gate because paperwork is late or wrong. Mistakes that undermine the credibility of your safety documentation with clients. And the risk that the document on site does not match the job being done.
The content of your RAMS is a safety matter for your competent persons. The problem this addresses is the administration: assembling, routing, tracking and storing.
The RAMS builder we set up
- Your approved method statement and risk assessment sections are loaded as a library, each owned and versioned by your competent person. We do not write safety content.
- Site records hold the site-specific details: access arrangements, roof and plant room notes, client contacts, known hazards and the client's permit requirements.
- For each job, the builder selects the sections that match the job type and site, fills in the site details, and highlights anything that needs a person's judgement.
- The draft is reviewed and approved by your nominated person before release. Nothing is sent unapproved.
- Permit requests to the client are prepared and tracked with status, so the scheduler knows whether the job can go ahead.
- The signed RAMS and permits are stored on the job and available to the engineer in their app on site.
| Step | Now | With the builder |
|---|---|---|
| Starting point | Last similar document | Approved library sections |
| Site details | Retyped | From the site record |
| Approval | Sometimes skipped | Required before release |
| Permits | Email chains | Tracked with status |
| On site | Maybe printed | In the engineer's app |
Paperwork that is ready before the van leaves
RAMS are produced quickly from approved content, reviewed by the right person and sent in time. Old site details do not creep in. Permits are tracked so jobs do not arrive at gates unprepared. Engineers have the right version on their phone. And when a client asks for the RAMS used on a past job, it is on the job.
Your competent person also gets control of the content back. Updating an approved section once changes every future document, instead of old wording surviving in copies of copies.
Is RAMS admin eating your week?
- RAMS are copied from previous jobs and edited.
- Clients have rejected RAMS with wrong site details.
- Permit requests are tracked in email.
- Engineers have been refused site access over paperwork.
- Finding the signed RAMS for a past job is hard.