Last updated: 25 August 2026

Security RAMS Template: The Complete UK Guide for 2026

A security RAMS template is a structured document combining a risk assessment and a method statement that sets out the hazards on a site and the safe working procedures security officers must follow. UK employers with five or more staff must record significant risk findings by law, and a well-built template turns that legal duty into a repeatable, auditable process across every site.

Key Takeaways

• A security RAMS template combines a risk assessment (hazard identification and control measures) with a method statement (the step-by-step safe system of work) into a single document used before deployment.
• Employers with five or more employees must record the significant findings of their risk assessments and any groups of employees especially at risk, according to Kingsley Napley LLP (2026).
• Penalties for non-compliance with risk assessment duties include unlimited fines and, in serious cases, imprisonment for responsible persons, per Kingsley Napley LLP (2026).
• HSE carried out over 13,200 workplace inspections in 2026/25, an increase of 47%, reports Arinite (2026), meaning security contractors are far more likely to be asked for evidence of live RAMS documentation than in previous years.
• Construction site security specifically carries heavy financial stakes, since construction site theft is estimated to cost the UK industry between £800 million and over £1 billion annually, according to Veritech Security (2026), which is why RAMS for site guarding must go beyond generic templates.

What is a security RAMS template?

A security RAMS template is a pre-built document structure that guides a security company through identifying site-specific hazards and defining a safe method of work before officers are deployed. RAMS stands for Risk Assessment and Method Statement — two documents traditionally produced separately but now almost always combined into one working paper. The risk assessment half identifies hazards (lone working, hostile visitors, vehicle movements, working at height on a gatehouse, forced entry) and rates their likelihood and severity. The method statement half then converts those findings into a written procedure: patrol routes, checkpoint frequency, escalation triggers, PPE, and communication protocols.

For security-specific work, a generic construction RAMS template borrowed from a trades contractor is rarely sufficient. Security guarding carries distinct hazards — conflict management, lone-working exposure during night shifts, and the handling of confidential access or keyholding responsibilities — that a joinery or scaffolding RAMS was never designed to capture.

Why RAMS matters more for security contracts than most trades

Security officers frequently work alone, often at night, often as the only person on a client site. That single fact changes what a RAMS needs to cover compared with a five-person bricklaying gang working daytime hours together. A security RAMS must explicitly address lone-worker risk, welfare check frequency, and SOS escalation — points a generic template will skip entirely.

What should a security RAMS template include?

A complete security RAMS template must contain, at minimum, a site description, a hazard register, control measures for each hazard, a documented method statement, emergency procedures, and a sign-off record naming the responsible manager and the date of review. Each section exists because a regulator, client auditor, or insurer will ask for it specifically — not because it looks thorough on paper.

The following sections are the baseline any UK security operator should expect in a usable template:

• Site and client details — site address, client name, contract reference, and site-specific access arrangements.
• Scope of works — exactly what the officer or team is contracted to do: static guarding, mobile patrol, keyholding, alarm response, door supervision, or event stewarding.
• Hazard identification — a structured list covering physical hazards (traffic, height, confined spaces), people-related hazards (aggression, forced entry, trespass), and environmental hazards (lone working after dark, weather exposure on external patrols).
• Risk rating — likelihood multiplied by severity, usually on a 1–5 scale, producing a residual risk score after controls are applied.
• Control measures — the specific mitigation for each hazard: two-person patrols in high-risk zones, radio check-ins every 30 minutes, body-worn cameras, or restricted key issue.
• Method statement — the step-by-step sequence officers must follow: arrival and handover procedure, patrol route and checkpoint order, incident escalation chain, and end-of-shift reporting.
• PPE and equipment requirements — hi-vis, torches, body armour where applicable, communication devices, and vehicle checks for mobile patrol staff.
• Emergency and welfare procedures — lone-worker check-in schedule, SOS protocol, nearest hospital or police contact point, and fire evacuation role if the officer holds one.
• Training and competency confirmation — SIA licence number and expiry, any site-specific induction completed, first aid certification where relevant.
• Review and sign-off — the name of the manager approving the RAMS, the date it takes effect, and the scheduled review date.

How a security RAMS differs from a construction RAMS

A construction RAMS focuses on trade-specific physical hazards — working at height, manual handling, excavation collapse, and plant machinery. A security RAMS instead centres on people-risk: conflict de-escalation, lone working, access control failure, and the security of client assets and information. Where a construction RAMS sits under the Construction (Design and Management) Regulations 2015 (CDM 2015), a security guarding RAMS more often sits under the general duties of the Health and Safety at Work etc. Act 1974 and the Management of Health and Safety at Work Regulations 1999, alongside British Standards written specifically for the security sector.

What legal duties apply to security RAMS in the UK?

UK employers have a statutory duty under the Management of Health and Safety at Work Regulations 1999 to carry out a "suitable and sufficient" risk assessment of the work their employees undertake. Employers with five or more employees must record the significant findings of their risk assessments and any groups of employees especially at risk, states Kingsley Napley LLP (2026). For a security company running a workforce across multiple client sites, that means a RAMS per site or per contract type — not one generic document covering the whole business.

Enforcement is not theoretical. HSE carried out over 13,200 workplace inspections in 2026/25, an increase of 47%, according to Arinite (2026). That sharp rise means a security contractor asked to produce a RAMS on the spot during a site visit or an HSE inspection is a realistic scenario, not a hypothetical one.

The consequences for getting it wrong are severe. Penalties for non-compliance with risk assessment duties include unlimited fines and, in serious cases, imprisonment for responsible persons, according to Kingsley Napley LLP (2026). As regulatory expert Andrew Sanderson of Kingsley Napley LLP puts it: "We are increasingly seeing the HSE taking a more assertive approach to enforcement, especially where there is a pattern of neglect or where vulnerable groups are affected." He adds: "The courts have also shown little leniency for businesses that fail in their risk assessment duties."

Which British Standards apply to security RAMS

Security guarding in the UK is shaped by several British Standards that a compliant RAMS template should reference directly:

• BS 7499:2020 — Provision of Static Guarding Security Services, Code of Practice, published by BSI. The 2020 revision placed greater emphasis on site-specific risk assessment as a precondition of static guarding contracts.
• BS 7960 — Code of practice for door supervisors, relevant where a RAMS covers licensed door supervision at licensed premises or events.
• BS 8593 — Code of practice for the process of conflict management, directly relevant to the hazard and control-measure sections of any RAMS involving public-facing security roles.
• The Private Security Industry Act 2001, which established the Security Industry Authority (SIA) and the licensing regime that every RAMS should cross-reference when confirming officer competency.
• CDM 2015, where a security RAMS forms part of a wider Construction Phase Plan on a construction site being guarded by a subcontracted security provider.

Security RAMS template vs generic construction RAMS template: which should you use?

Choosing between a generic construction RAMS template and one built specifically for security operations comes down to what hazards the document actually needs to capture. A construction template assumes a team working together in daylight on physical tasks. A security template assumes lone working, people-risk, and 24-hour coverage. Using the wrong one leaves genuine gaps that only surface during an incident investigation or an HSE inspection — exactly when the gap matters most.

In-house drafting vs a ready-built template: the trade-off

Drafting a RAMS from scratch for every new site gives full control over site-specific detail but is slow, inconsistent across officers, and hard to audit at scale. A ready-built security RAMS template — one already structured around BS 7499, lone-worker provisions, and SIA competency fields — gets a compliant document in front of a client faster and ensures every site manager is filling in the same fields in the same order. The trade-off is customisation time: a template still needs the site-specific hazards populated by someone who has actually walked the site, not copied from a similar contract. For growing security companies managing dozens of sites, a shared digital template with mandatory fields reduces the risk of a hurried, incomplete document being the one that gets audited.

How often should a security RAMS be reviewed?

A security RAMS should be reviewed whenever the scope of work changes, whenever an incident occurs on site, and at a minimum on contract renewal — never left static for the life of a multi-year contract. Static RAMS documents are one of the most common findings in HSE inspections and client compliance audits, because a site's risk profile rarely stays fixed. A shopping centre gaining a new tenant, a construction site moving from groundworks to fit-out, or a client site experiencing a spate of attempted break-ins are all legitimate triggers for an immediate RAMS review, regardless of when the last scheduled review took place.

Best practice for UK security operators is to build review triggers into the RAMS document itself:

• Scheduled review — at minimum every 12 months, or per contract renewal if shorter.
• Incident-triggered review — any reportable incident, near-miss, or client complaint relating to a hazard already listed in the RAMS.
• Scope-change review — new access points, new equipment, changed shift patterns, or a change from static to mobile coverage.
• Regulatory-change review — updates to relevant British Standards or legislation, such as a future revision of BS 7499.

Who signs off a security RAMS

Sign-off responsibility should sit with a named manager — typically an operations manager or contracts manager — who has either visited the site or reviewed a site survey completed by someone who has. A RAMS signed off without site-specific knowledge is a common weak point flagged in audits, because it suggests the document was copied rather than assessed. The signatory's name, role, and the date of approval should appear on the document itself, not just in an internal management system.

Your security RAMS template checklist

• Confirm the RAMS names the specific site, client, and contract reference — never a generic "all sites" document.
• List every hazard specific to that site's operating hours, including lone-working exposure on night shifts.
• Cross-reference officer competency: SIA licence number, expiry date, and BS 7858 vetting status where the contract requires it.
• Build in a welfare check and SOS escalation procedure for any lone-worker deployment.
• Reference the relevant British Standard for the service type — BS 7499 for static guarding, BS 7960 for door supervision, BS 8593 for conflict management.
• Record the sign-off name, role, and date, and set a scheduled review date no more than 12 months out.
• Trigger an immediate review after any incident, scope change, or client complaint tied to a listed hazard.
• Store the completed RAMS somewhere every officer on that site can access it before starting a shift, not buried in a head office filing system.

FAQ

What is a security RAMS template?

A security RAMS template is a structured document combining a risk assessment and a method statement, used to identify site-specific hazards facing security officers and set out the safe procedures they must follow before deployment. It typically covers hazard identification, control measures, PPE, emergency procedures, and sign-off by a named manager.

Is a RAMS legally required for security guarding services?

Yes, in effect. UK employers with five or more staff have a legal duty under the Management of Health and Safety at Work Regulations 1999 to record the significant findings of their risk assessments, and a RAMS is the standard way that duty is documented for security contracts. Kingsley Napley LLP (2026) confirms this recording duty applies specifically to businesses of that size.

How does a security RAMS differ from a standard construction RAMS?

A security RAMS focuses on people-risk hazards such as lone working, conflict management, and access control, while a construction RAMS focuses on physical hazards like working at height and manual handling. Security RAMS documents typically reference BS 7499, BS 7960, and BS 8593, whereas construction RAMS sit under CDM 2015 and trade-specific HSE guidance.

What is the difference between a risk assessment and a method statement?

A risk assessment identifies hazards and rates their likelihood and severity, while a method statement sets out the step-by-step safe procedure for carrying out the work once those risks have been controlled. A RAMS document combines both into a single paper so that hazard identification and safe working practice are read together.

What British Standards apply to security guarding RAMS?

BS 7499:2020 covers static guarding security services, BS 7960 covers door supervision, and BS 8593 covers conflict management — all published by BSI. A security RAMS should reference whichever standard matches the specific service being delivered on that contract.

How often should a security RAMS be reviewed or updated?

A security RAMS should be reviewed at least every 12 months, and immediately after any incident, scope change, or change in site conditions. Leaving a RAMS unreviewed for the life of a multi-year contract is a common finding in compliance audits and HSE inspections.

Can I use a free RAMS template for SIA-regulated security work?

A free generic RAMS template can be a starting point, but it must be adapted to reference the Security Industry Authority (SIA) licensing requirements, BS 7499 or BS 7960 as appropriate, and lone-worker provisions specific to security operations. A template built for trades work will typically miss these sector-specific fields entirely.

Who is responsible for approving and signing off a RAMS on site?

Sign-off responsibility typically sits with an operations manager or contracts manager who has either visited the site or reviewed a site survey. Their name, role, and the approval date should appear on the RAMS document itself, alongside a scheduled review date.

Building compliant RAMS across every site with Pulse Operations

Chasing down which version of a RAMS template is live at which site is one of the most common compliance gaps Pulse Operations sees among UK security operators managing multiple contracts. A paper or spreadsheet-based RAMS gets copied, edited locally, and quickly falls out of sync with what officers are actually being told at handover — exactly the pattern that shows up badly in an HSE inspection or a client compliance audit.

Pulse Operations was built by operators running a working London security and FM business, and its compliance runway sits alongside the same platform used for SIA licence tracking, BS 7858 vetting status, DBS checks, right-to-work records, training records, and Martyn's Law assessments — so a RAMS review sits next to the officer competency data it depends on, rather than in a separate filing system nobody checks before a shift starts.

If your business is still managing RAMS documents as static files scattered across sites and site managers, it's worth talking to Pulse Operations about how a single compliance runway can keep every site's documentation current, reviewed, and ready to produce the moment a client or an inspector asks for it.

Related Reading

• Guardhouse Alternative 2026: Best UK Options Compared
• SmartTask Alternative 2026: Best Options Compared
• TrackTik Pricing 2026: UK Cost Guide & Alternatives