Hazard ID, likelihood, consequence, and residual risk.

Translate hazards into practical controls before foundations, ducts, or panels are touched. Identify risks from excavation, lifting, electrical/hydraulic work, and public interfaces (351, 613, 615, 347). Use a simple matrix to set controls and residual risk. Link RAMS directly to the Method Statement (721), define review triggers (design changes, utilities found 617), communicate on site (723), and retain records for SAT/authority reviews (638, 717). Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.

Important: This is a general guide. For live projects we develop a tailored Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.

722.1 Hazard identification

List task hazards: excavation, lifting, electrical, groundwater (613–614). Hazards around HVM bollard work are explicit.

Start with a site walk and a structured list that follows the work sequence: surveys and underground detection, excavation & shoring, dewatering, formwork/pours, lifting/positioning, cabling/energization, commissioning, and handover. Note hazards that affect the rating-critical dependencies so controls preserve the bollard’s tested performance.

Use multiple sources: drawings, utility searches (241–243), site constraints (216), and the hazard analysis for HVM bollard sites. Capture materials/plant hazards (724), electrical panels and supply & protection, and hydraulic oil handling (512). Where public access exists, pre-tag “public interface” hazards for separate treatment.

For clarity, group hazards by task and environment (e.g., hot climate, confined trenches, traffic proximity). One line per hazard is enough if you include credible cause, consequence, people at risk, and link to the planned control in section 722.3/722.4.

AspectWhat mattersWhere to verify
PerformanceTested system (bollard + footing)Global crash ratings
OperationsDuty, fail-state, safety devices & measuresInstallation Guide

722.2 Risk evaluation

Rate likelihood/severity and residual risk. Evaluation defends crash rated bollard decisions.

Adopt a simple 5×5 risk matrix with clear banding and an ALARP statement. Score each hazard for inherent (pre-control) risk, list controls, then re-score for residual risk. Use consistent scales (e.g., “likely” vs “possible”) and define consequences that reflect H&S, environmental, service disruption, and security impacts on foundations & installation dependencies.

Where evaluation affects security intent (e.g., barrier left down during works), reference the alarm philosophy and modes of operation. If approvals are in scope, note any conditions set by authorities and link to authority submittals and SIRA Bollards (UAE).

722.3 Control hierarchy

Eliminate, substitute, engineer, admin, PPE. Controls keep HVM bollard sites safe (351).

Apply the hierarchy in order: eliminate the hazard (e.g., re-route to avoid a utility conflict), substitute methods/plant, engineer out exposure (edge protection, trench boxes), implement administrative controls (permits, training, PTW & toolbox talks), then specify PPE. Record each chosen control with a brief rationale showing why higher-order options were selected or not practicable.

Link controls to acceptance checks (ITP 714) and to pre-commission prerequisites so safety and quality are evidenced together.

722.4 Specific method controls

Tie controls to steps in 721.3. Specifics prevent crash rated bollard nonconformities.

Mirror your Method Statement format step-by-step: (a) set-out & mark-ups, (b) excavation/shoring, (c) dewatering, (d) rebar/forms/pours, (e) lifts/positioning, (f) cabling/terminations, (g) energization/LOTO, (h) commissioning/SAT. For each step, list “do this / check this / evidence here,” referencing evidence capture standards and the relevant ITP line.

Examples: mandrel tests for ducts (246), sump covers and pumps with sump sizing, lifting plans with certified slings/points, electrical power-failure modes rehearsed in a controlled setting, and interlock matrix verification prior to live traffic.

722.5 Environmental risks

Dust, noise, silt, spills (546, 245). Environmental controls protect HVM bollard reputation.

Plan for hot, sandy, and coastal contexts: dust suppression, spill kits, waste segregation, and silt control on dewatering discharge (drainage strategy). For noise, apply enclosure treatments and acceptable acoustic limits. Track environmental incidents in the same log as H&S to simplify governance and lessons learned.

722.6 Public interface risks

Segregation, signage, escorts (357). Public safety sustains crash rated bollard approvals.

Design exclusion zones, barriers, and stewarding where works touch public desire lines. Use clear signage & markings, night conspicuity, and escorts as needed. Sequence works to avoid queue spillback and maintain emergency access. Where approvals or sensitive sites apply, align arrangements with authority submittals and any SIRA comments (SIRA Bollards (UAE)).

722.7 Residual risk sign-off

Accept/mitigate with named owners. Sign-off clarifies HVM bollard accountability.

Present a concise register showing the final (post-control) risk per task, who owns it (RACI in spec/ITP), and any hold points before proceeding. Where residual risk remains above tolerance, escalate to the third-party/witness path or revise scope/methods to reduce it. Capture sign-off with names, roles, and date.

722.8 Review & updates

Revise after incidents or changes (718, 727). Reviews keep crash rated bollard RAMS current.

Set triggers for re-issue: design changes, utilities discovered, method changes, incidents/near-misses, or authority comments. Keep change control consistent with variations & change log, bump the version, and re-brief the team (723). Record what changed and why, and keep superseded versions accessible (911).

722.9 Records & distribution

File under 911; brief teams daily. Records make HVM bollard compliance auditable.

File the RAMS, permits, sign-offs, and photo/video evidence per the file index & naming rules (911) and evidence capture standards (716). Before energization or SAT, confirm the latest RAMS is in the SAT / witness pack. Use a daily briefing with a short toolbox talk so controls remain visible to the crew.

Related

External resources

722 Risk Assessment — FAQ

What is the difference between RAMS and a Method Statement?
RAMS combines the risk assessment (hazards, likelihood/severity, residual risk) with the method statement (how the work will be done). The Method Statement sets the sequence and responsibilities; RAMS explains why each control is needed and how risk is reduced to ALARP.
Which hazards matter most on HVM bollard sites?
Top recurring risks include utility strikes during excavation/ducting, unstable trenches, lifting/positioning injuries, hydraulic oil spills, electrical energization errors, and public interface risks (segregation and night conspicuity). Treat anything that could undermine rating-critical dependencies as high priority.
How often should we review and re-issue our RAMS?
Review at each phase change and whenever there is an incident, design/method change, authority comment, or discovery on site (e.g., uncharted utilities). Use version control and re-brief via toolbox talks.
Do UAE projects require anything special for approvals?
Projects that fall under security approvals may require aligned RAMS content and evidence packs. Where in scope, cross-reference your submission to the authority’s requirements and SIRA expectations, and include the RAMS in the SAT/witness pack.