A mobile engineer can have the same RAMS in an inbox, a WhatsApp conversation, a downloads folder, a job app, and a printed customer pack. When the document is revised, only one of those copies may change.
The engineer is not necessarily careless when the wrong version opens. On a busy day across several customer sites, they will often use the route that worked last time, particularly if the file name looks familiar and the revision is buried inside the document.
The practical solution is to stop treating sent files as the controlled source. Give engineers one dependable route to the live RAMS, make the current revision obvious, and use downloaded or printed copies only within a defined offline process.
Understand where copies escape control
Map every route through which engineers currently receive RAMS. Include email attachments, shared drives, customer portals, job-management apps, personal downloads, messaging platforms, and paper packs.
Then ask what happens to each route after a revision. Can the old copy be removed? Does the link always open the current record? Will the engineer receive a clear alert, and can the supervisor see who still has not acknowledged the update?
This exercise usually shows that the business has a master document but several uncontrolled distribution points. Updating the master does not withdraw attachments already saved on a phone.
Use links to controlled records where possible
A notification can tell the engineer that RAMS have been issued, while the link takes them to the current approved record. This reduces the number of permanent attachments circulating between jobs and customers.
QR codes can help at the point of work, provided the code resolves to the live controlled record rather than a fixed PDF. Evalu-8 EHS supports mobile and QR access to RAMS while keeping approvals, versions and digital acknowledgement connected.
The route must remain simple. If the engineer needs several logins, searches, and filters to find the right job, they may return to the attachment saved yesterday because it feels more dependable.
Make offline access a controlled exception
Some plantrooms, rooftops and customer sites have poor connectivity, so a blanket ban on downloads may be unrealistic. Define how offline copies are prepared, how long they remain valid, and how the engineer confirms they have the latest version before work starts.
A synced mobile application can support offline use, but the team still needs to understand when the record was last updated and what happens if a revision is issued while the device is disconnected. Test this during software evaluation rather than accepting “works offline” as a complete answer.
For planned work, the supervisor can confirm synchronisation and revision during the pre-start check. For reactive work, the engineer may need to pause until the current safe method is available if there is uncertainty.
Make revision alerts meaningful
“RAMS updated” does not tell an engineer whether the change affects their work. A useful alert identifies the job, new revision, and practical difference, such as a changed isolation point, roof-access route or hot-work restriction.
Require fresh acknowledgement where the change affects the safe method. Earlier signatures should remain as history but should not be carried forward as if the engineer had accepted information they had not seen.
The supervisor should have a clear view of outstanding acknowledgement before the affected work begins. Chasing after the job only proves that the distribution process failed.
Remove old versions from normal view
Previous RAMS may need to be retained for audit or investigation, but they should sit in history rather than beside the live document. Use a clear superseded status and prevent old records from appearing in the engineer’s ordinary current-job list.
Where paper is required by a customer, mark the revision visibly and replace the site copy after a material change. Do not rely on somebody noticing that the footer says version four rather than version three.
One current route: a clear revision and a controlled offline process will do more than repeated reminders to “check you have the latest RAMS”. The system should make the safe choice the easiest choice for an engineer moving between customer sites.
