RAMS audit evidence checklist for UK construction sites
What evidence is needed for RAMS audits?
If you are asked to evidence your RAMS in an audit, the auditor is usually trying to answer one question: did you control risk in practice, or did you only generate paperwork.
That is why “the RAMS document” rarely passes on its own. You normally need the records that prove the RAMS was produced for the task, reviewed and approved, issued as a controlled version, briefed to the right people, and kept under change control when site conditions shifted.
This article sets out the evidence set that typically proves control, plus a usable audit checklist you can lift into your own process. It also aligns to an AI-assisted workflow where the audit trail matters as much as the final output, as covered in AI-generated Risk Assessments and Method Statements guide.
Quick Answer..
For most RAMS audits, you need evidence across four areas: planning inputs (why this RAMS matches this job), competence and approval (who reviewed it and what changed), communication (who was briefed on which version), and change control (how you handled site changes without losing control). The RAMS file is only one record in that chain.
What a “RAMS audit” is actually testing
Audits vary, but the core test is consistent: can you demonstrate that the method statement and risk assessment were applied, not just written.
In practice, auditors often probe three weaknesses because they indicate loss of control.
First is version uncertainty. If supervisors and operatives cannot clearly identify the current revision, the audit trail collapses and the site control looks informal.
Second is briefing ambiguity. If the briefing evidence does not tie back to a specific RAMS ID and revision, there is no proof that the right controls were communicated.
Third is unmanaged change. If the site changed (sequence, interface, plant, ground, access, permits) and the RAMS did not, then the controls may be out of date even if the document looks complete.
If you want a deeper view of governance, approval, and review on site, this companion post is relevant: How to review and approve RAMS.
The minimum evidence set, mapped to the RAMS lifecycle
Think of your evidence as a lifecycle bundle. Each stage should leave a record that proves control.
Most audit-ready sets include:
-
Task and scope record
A short job scope note that makes the RAMS site-specific. This is where you capture what is being done, where, when, and what interfaces exist. -
Inputs pack
Anything the RAMS was based on, such as drawings, constraints, sequencing, client rules, logistics plans, or temporary works assumptions. Auditors use this to check that the RAMS reflects reality. -
Draft and version history
A controlled revision trail that shows the RAMS did not “float around” as an uncontrolled file. This should include who edited it and why. -
Review comments and responses
A record of what was queried and how it was resolved. This is particularly important where high-risk controls, permits, or exclusion zones are involved. -
Approval record
A clear approval linked to the final issued revision. The approval should show the approver, date, and any conditions. -
Issue and distribution record
Evidence of what was issued, when, and to whom, so you can prove that teams were not working off a draft. -
Briefing record tied to the revision
Attendance and role list, date, supervisor sign-off, and a way to show that the briefing related to the issued revision. -
Work start evidence and control confirmation
This is where audits often move beyond paperwork. Photos of set-up, exclusion zones, permits displayed, and pre-start checks can matter if you have them as part of your system. -
Change request and change log
A record of what changed, what triggered it, and what controls were added or amended. -
Revised approval and re-brief evidence
If a revision was required, auditors tend to look for proof you did not skip re-approval and re-brief.
If your current RAMS process struggles with keeping these steps joined up, read this post on version control: How do you control versions of RAMS on site?.
Audit checklist: what to gather before the auditor arrives
This is a practical pre-audit checklist. The goal is speed and certainty, not a big folder of unrelated documents.
A) Version control and source of truth
-
RAMS has a unique ID and revision number
-
A version register exists and shows current revision
-
Superseded versions are clearly marked as superseded
-
You can point to one issued copy as the source of truth
-
The issue date and distribution are recorded
B) Review and approval evidence
-
The reviewer and approver are named and dated
-
Review comments exist for meaningful changes, not just a tick
-
Approval is linked to the issued revision, not a generic sign-off
-
Any conditions, hold points, or permit dependencies are recorded
C) Site briefing and communication evidence
-
Briefing record includes RAMS ID and revision
-
Attendees list includes roles, not just names
-
Supervisor sign-off is recorded
-
Understanding checks are evidenced (even short notes)
-
Where relevant, inductions or specific briefings cross-reference the RAMS
D) Permits, hold points, and interfaces
-
Required permits are recorded and linked to the task
-
Hold points are stated and can be evidenced (inspection sign-off, authorisation)
-
Interfaces with other trades or traffic management are captured
-
Changes in access, sequencing, or exclusion zones are reflected in records
E) Change control evidence
-
A clear change trigger was recorded when conditions changed
-
A change request exists with the reason and risk impact
-
RAMS was revised and the revision is identifiable
-
Re-approval happened where required
-
Re-brief record exists and references the new revision
For change control detail and the evidence trail, this is the most aligned spoke: RAMS change control on site.
Using ChatGPT for RAMS?
Draft Faster. Review Site Risks Properly.
Get access to our free RAMS generator now.
Common audit failures and how to close the gaps
Most failures happen because evidence is fragmented. The RAMS exists, but the supporting records are missing or cannot be tied to the specific revision.
Failure 1: Briefing signatures without version reference
A sheet of signatures proves attendance, not content. If the auditor asks “which version was briefed”, you need an answer that is backed by a record.
Fix: add RAMS ID and revision to the briefing record, and ensure the supervisor sign-off references that same revision.
Failure 2: Uncontrolled edits after approval
If the approved RAMS was edited directly, you have a broken audit trail. Even if the changes were sensible, the control process is not provable.
Fix: enforce a revise-approve-issue loop. If you want the workflow steps that make this repeatable, use RAMS governance and version control as the baseline.
Failure 3: No recorded trigger for change
Auditors often ask why a revision was raised, or why it was not raised. If nothing captures the trigger, your change control looks reactive rather than controlled.
Fix: record triggers as short factual notes, then link them to the revised RAMS and the re-brief record.
Failure 4: Evidence exists, but it is not connected
This is the biggest practical problem. You might have approvals, briefings, and permits, but they sit in separate places with no clear linkage.
Fix: use one consistent ID and revision reference across every record: approval, issue, briefing, permits, photos, change log, and close-out.
How to structure evidence for AI-assisted RAMS without increasing admin
If AI is involved in drafting RAMS content, the audit requirement does not go away. It shifts towards proving review, approval, and controlled issue, because the drafting step is faster.
The practical approach is to keep the evidence set small but structured. A short inputs pack, a revision history, a reviewer comments log, and a controlled briefing trail usually does more for audit readiness than a large number of disconnected screenshots.
You also need discipline around where “the current version” lives. If supervisors can access multiple copies, the audit risk increases because you cannot prove what was used on the day.
If you are building digital audit readiness into a broader compliance approach, this is a supporting read: Digital audit trails for construction compliance.
Frequently Asked Questions
What is the single most important piece of RAMS audit evidence?
A controlled RAMS version trail, because it anchors everything else. Without a clear current revision and proof of approval and issue, briefing and change control evidence cannot be trusted.
Do auditors need to see briefing signatures?
Often yes, but signatures alone are weak evidence. The briefing record should also state the RAMS ID and revision, attendee roles, supervisor sign-off, and any understanding check notes.
How do I evidence that a RAMS was site-specific?
Use a task scope record and inputs pack that captures site constraints and interfaces, then ensure the RAMS references those constraints in the method and controls.
When should a RAMS be revised for audit purposes?
When site conditions, sequencing, interfaces, plant, access, or control measures materially change. The trigger should be recorded, followed by a controlled revise-approve-issue and re-brief cycle.
What evidence helps most during a spot audit on site?
Evidence you can retrieve quickly: the current RAMS revision, approval record, briefing record tied to that revision, and the change log if revisions occurred.
Conclusion
RAMS audits are not just about whether you have a document. They are about whether you can prove control across the lifecycle: inputs, competence and approval, issue of a controlled version, briefing against that version, and change control when the job changes.
If you build your evidence set around a single RAMS ID and revision that flows through approvals, briefings, permits, and change logs, audits become faster and far less stressful. You stop relying on memory and you start relying on records that prove what happened.
If you want a structured way to control RAMS versions, approvals, briefings, and change records in one place, explore the RAMS feature here: RAMS.
Using ChatGPT for RAMS?
Draft Faster. Review Properly.
Get access to our free RAMS generator and speed up your first draft with site-specific review built in.
