Digital RAMS vs paper: choosing a workflow that works on site

Digital RAMS can make the current risk assessment and method statement easier to distribute, revise and find; paper can be easier to read when devices, signal or power fail. Neither format makes the work safe by itself. The test is whether the right workers can understand the current, site-specific controls before and during the task, and whether supervisors can see that those controls are being used. A PDF on a phone, a signed paper sheet and a purpose-built workflow can all fail if the underlying assessment is generic or changes are not communicated.

In Great Britain, a risk assessment is about the hazards, who could be harmed and the controls to take. HSE's risk-assessment guidance explains the process; HSE's construction method-statement guidance explains how a method statement can turn those controls into a safe sequence and communicate it to the workforce. For demolition or dismantling, the CDM 2015 written-arrangements duty applies before work begins. The legal and safety question is not whether the document lives in an app or a ring binder; it is whether the duties and work controls are met. Do not mistake the format for an HSE approval stamp.

What counts as “digital RAMS”?

The term covers very different systems. At one end, a company writes a Word document, emails a PDF and saves it in a folder. At the other, a system may support controlled versions, named reviewers, worker briefings, acknowledgements, offline access or subcontractor submissions. Do not assume every digital RAMS product has all of those features. A vendor demonstration should show exactly how the proposed system handles a real job from draft to site revision, not just how quickly it creates a document.

Paper RAMS is also more than a printed PDF. A good paper process has an approved master, issue date, clear revision number, a controlled site copy, a briefing record, a route for changes and a way to recall superseded pages. The comparison is between workflows, not screens and sheets. Some teams use a hybrid: digital master and distribution, with a controlled paper site copy for low-connectivity work.

Side-by-side comparison

Digital is not automatically cheaper, faster or safer. The answer depends on team size, project turnover, subcontractor interfaces, quality of existing controls and whether the software actually solves a bottleneck. The most valuable improvement is often a controlled current version, not a flashy generation feature. Conversely, a high-risk operation may still need drawings and a face-to-face briefing that a small phone screen cannot replace.

Five questions to ask before switching

1. Is the RAMS itself specific enough?

Before comparing formats, inspect a recent job. Does the assessment describe actual site hazards, people affected, plant, sequence, interfaces and emergency actions? Can an operative explain what changes between stages? HSE says a method statement should set out the work in a logical sequence with the control measures. A generic template electronically signed by everyone remains generic. Software may make duplication easier if users accept the first draft without checking site reality.

2. Who controls release and revisions?

Name the author, competent reviewer, approver and person who may issue a new version. A meaningful change—new access route, unexpected service, changed plant, altered structural sequence—should trigger reassessment before work continues. The current version must have a clear identifier. Workers and subcontractors need to know when the old version is no longer valid. Ask whether the platform can preserve a read-only history and whether paper copies can be clearly recalled. If not, build that control outside the tool.

3. Can workers use it where the work happens?

Test the real environment. Does the site have reception? Are phones allowed? Are workers wearing gloves? Will drawings be legible? Can a subcontractor without a company login read the method? Does the workflow support workers with different languages, literacy needs or disabilities? “Sent by email” is not the same as briefed and understood. HSE's method-statement guidance emphasises clarity and communication to the people carrying out the work. A short, illustrated workface extract may help, provided it stays aligned with the approved full method.

4. What evidence is worth keeping?

Record who approved the method, which version was issued, when the team was briefed, questions raised, and what changed. A digital timestamp can help but is only evidence of the event the system actually captured; a tap on “acknowledge” is not proof of safe practice. A paper signature has the same limitation. Supervisors still need to observe work, address deviations and stop unsafe methods. Design records for the decisions you may need to explain, rather than collecting clicks for their own sake.

5. What happens when the system fails?

Decide what workers do if a server, mobile connection or device is unavailable. Does a controlled offline copy exist? How will a late revision reach a worker with an old local PDF? A paper fallback should be marked with the current version and reconciled when service returns. If no trustworthy method is available at the workface, the work should pause until the team can confirm the approved controls. The continuity plan belongs in the operational process, not only in an IT document.

A practical migration plan

Start with one repeatable but real task. Pick a job with a competent reviewer, a supervisor willing to test the workflow, and enough change or distribution activity to reveal the pain points. Do not use a uniquely high-risk demolition sequence as a software pilot before the approval and offline controls are proven.

1. Map the existing path. Identify who drafts, reviews, issues, briefs, changes and archives RAMS today. Note recurring failures: stale copies, late subcontractor submissions, missing drawings, unreadable forms or review delays.
2. Set a document standard. Agree mandatory fields, version naming, reviewer sign-off, site-specific content and linked plans. Apply the standard to paper and digital alike.
3. Test the candidate system with a real job. Create a draft, reject a defect, approve a revision, distribute it, brief workers and retrieve the version history. Include a subcontractor and a worker with limited signal.
4. Run a controlled hybrid period. Name one authoritative master. If a paper site copy is used, print the released version and mark earlier copies void. Compare the methods in actual use at the workface.
5. Train supervisors on change control. They should know which changes need a new assessment and who can approve it. Test an unexpected condition scenario and confirm that work stops while the method is revised.
6. Review outcomes. Measure factual errors, revision lag, briefing coverage, accessibility and time to find an approved document. Do not declare success solely because more PDFs were produced.

For some small firms, disciplined paper plus a shared folder may be sufficient. For a contractor running many changing sites, a controlled digital workflow may reduce the chance of the wrong version circulating. The choice should reflect the risk and coordination problem the business actually has.

Example: a changed access route

A roofing team has been briefed on RAMS that uses a particular access tower. On arrival, the tower location is blocked by another trade. With paper, the supervisor marks the existing copy as not applicable, pauses access work and seeks an assessed alternative; the approved revision is printed and rebriefed. With a digital system, the same safety decision is needed. A quick edit to the PDF is not enough unless the competent person reviews the changed access, the new version is released, and workers receive the update. The software can accelerate distribution; it cannot decide whether the alternative access is safe.

Common claims to challenge

“Digital RAMS are legally required.” No general UK rule requires an app. The duties concern suitable assessment, planning, written arrangements where required, and communicating/implementing controls. Some clients impose contract requirements for a submission format; that is a separate issue.

“A signature proves the work is safe.” It helps show an acknowledgement or briefing took place, but does not prove the assessment was suitable, the worker understood it or site conditions matched it.

“AI-generated means approved.” Any generated draft needs a competent, site-specific check. HSE does not certify a document because a tool wrote it. High-risk methods need the appropriate engineering or specialist review.

“Paper is obsolete.” Paper can be useful for a clear, controlled workface copy and as a resilience measure. Its weakness is often revision distribution, not the material itself.

“Everyone sees the latest version in the app.” Test this with offline devices, exported PDFs, shared accounts and subcontractors. A central master does not automatically remove old copies.

Where Complys fits

The live Complys RAMS template and risk assessment software page are potential next steps only after current route, whole-page wording and implementation are verified. Complys's live blog and guides make broad claims about generation, sign-off and document handling; those should not be repeated as proven features without checking the current product. A defensible CTA is: compare your current paper workflow with a verified Complys demonstration, ask to see version control, site briefing and offline/contingency handling, and decide whether it improves your actual RAMS process. Do not imply that a platform, digital acknowledgement or AI draft gives legal approval.

Source, claim, owner, product, links and writer-side QA

Terminal writer-side disposition: READY.