Somewhere on every contractor’s computer there is a folder with a name like “RAMS
MASTER FINAL v3”. Inside it are the templates: the risk assessment from a job in 2019,
the method statement borrowed from a mate, the one a consultant wrote years ago that
still does the rounds with the consultant’s initials in the footer.
The construction industry is not short of templates. You can download hundreds of them
free in an afternoon. Yet the same paperwork problems keep happening on the same
sites: documents that describe a different job, hazards missed because they were not on
last time’s list, and operatives signing sheets they have never read.
After more than thirty years in construction and engineering, I have come to a firm
conclusion. The industry’s paperwork problem was never a shortage of templates. It is
the absence of systems. And the difference between the two is worth understanding,
because it is the difference between paperwork that protects people and paperwork that
just exists.
Table of Contents
The template trap
A template is a starting point pretending to be a finished job.
That is not how it gets used, though, and everyone in the industry knows it. The real
workflow, on thousands of jobs every week, is this: open the RAMS from the last job,
change the site address, swap the client’s name, skim it once, send it off. The document
exists. The box is ticked. And the paperwork now describes a site that is not this one.
I have seen method statements with the wrong site name surviving on page six, three
jobs after it was first written. Nobody caught it, which tells you exactly how many people
read page six. I have seen a risk assessment for first-floor joinery submitted for a
groundworks package. It was accepted.
None of this happens because contractors are careless about safety. Most of the trades
people I have worked with take real pride in doing the job right. It happens because the
template approach makes the wrong thing easy and the right thing slow. Rewriting a
document properly for every job takes hours the business does not have, usually at night,
usually unpaid. Changing the names takes five minutes. The incentive does all the work
from there.
What the paperwork is actually for
Better Compliance Systems, Not More Templates Page 2 of 3
It is worth going back to first principles, because the industry has drifted a long way from
them.
A risk assessment and method statement has one real job: to make sure the specific risks
of a specific job have been thought about by someone competent, and that the
conclusions reach the people doing the work. It is a record of thinking. The clue is in
what the document is supposed to contain: this site, this task, this week, these people,
this kit.
A recycled template inverts that. The document gets produced without the thinking
having happened. It will pass a quick check, because it looks like every other RAMS the
reviewer has seen, and it protects nobody, because it describes nothing real. The worst of
it is what recycled paperwork teaches people on site: that the documents are a formality,
produced for the file, safe to sign unread. Once a workforce has learned that lesson, even
the good documents stop working.
What a system looks like
When I say construction businesses need systems, I do not primarily mean software. I
mean a repeatable way of working with a few non-negotiable properties. You could run
one on paper if you were disciplined enough. The properties are what matter.
Job-specific by default.
The starting point for any document is this job: its location,
its tasks, its actual hazards. Generic content should have to justify its way in, not be the
base that specifics are occasionally added to.
Reviewed by someone competent.
A document nobody senior has read is a guess.
The review is where experience catches the thing the writer missed, and it needs to be a
real step, not a signature applied on the way past.
Versioned.
Jobs change. Programmes move, methods change, new trades arrive. A
system knows which version of a document was current on which date, and what
changed between them. A folder of files called FINAL, FINAL2 and FINAL-use-this-one
does not.
Distributed to the people doing the work.
A method statement in the site office protects the site office. It has to reach the people on the tools, in a form they will actually engage with, and a briefing that answers questions rather than collecting signatures.
Signed off meaningfully.
A signature should record that a named person confirmed a specific thing on a specific date. If the sign-off sheet cannot tell you what was actually confirmed, it is decoration. Read that list again, and notice that a template delivers none of it. A template is a piece of content. A system is what ensures the content is true, current, reviewed and communicated. That is the whole distinction. Better Compliance Systems, Not More Templates Page 3 of 3
Where software fits, and where it does not
I build software in this space through RAMS AI, so let me be straight about what it can and cannot do. Good software makes the right way the easy way. It can hold the job details so documents start from the real site rather than a blank page or an old file. It can track versions honestly, chase the review step, get documents to phones on site and record who confirmed what and when. It collapses the hours that make people reach for their last job’s paperwork, and that matters, because the shortcuts are a symptom of time pressure, not laziness.
Here is what no software does: it does not think for you, and it does not make you compliant. Compliance is a property of what actually happens on site, not of any document or tool. A business with poor practices and excellent software has poor practices. Anyone who tells you their product guarantees compliance is selling something the law does not allow them to deliver, and you should hold your wallet a little tighter when you hear it. The judgement stays human. The system’s job is to make sure the judgement happens, gets recorded and gets communicated, every time, without heroics.
Raising the standard
If you run a construction business, here is a test worth ten minutes of your time. Take
the last RAMS you sent out and read it as if you were an operative seeing it cold. Does it
describe the job you are actually doing this week? Would the person on the tools learn
anything from it that keeps them safer? Could you say, with a straight face, when it was
last properly reviewed and by whom?
If the answers are uncomfortable, the fix is not another template. You have plenty. The
fix is deciding how documents get produced, checked, updated and communicated in
your business, and then making that process easier to follow than the shortcut.
The industry has spent decades treating paperwork as a tax on real work. The result is a
paper mountain that protects no one. The businesses getting this right have stopped
asking “have we got a document for that?” and started asking “has anyone actually
thought about this job?” That is the question the whole system exists to answer.
Everything else is filing.
AUTHOR BIO:
Carl Barrie has spent more than thirty years in construction and engineering. He is the
founder of RAMS AI (ramsai.co.uk), which helps UK construction businesses produce
job-specific risk assessments and method statements in minutes instead of evenings.
