Structured audits, evidence, and closeout.
Audits keep projects honest. This page standardizes site audit types (safety, quality, technical), who leads them, and the evidence you must capture to prove compliance. You’ll map audits to ITP hold points, rate findings by risk, and track corrective actions to closure. Templates and filing rules ensure HVM bollard and crash-rated records withstand authority review and future incidents. 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.
728.1 Audit plan & cadence
Weekly internal; monthly cross-audits. Cadence keeps HVM bollard standards high.
Start with a written audit plan that names the audit leader, scope boundaries, and timing. Weekly internal audits verify day-to-day control of Method Statements and Risk Assessment (RAMS) actions in the field. A monthly cross-audit by someone outside the delivery team provides independent challenge and protects the integrity of crash-rated intent through installation and commissioning.
Map audit windows to ITP hold and witness points so checks occur before concealment or irreversible steps. This keeps critical evidence, such as rebar cage layout or levelling and grout beds, verifiable. Document skipped or shortened audits with rationale and a recovery plan to avoid blind spots later.
| Aspect | What matters | Where to verify |
|---|---|---|
| Timing | Before concealment & ITP hold points | ITP — Hold/Witness |
| Independence | Monthly cross-audits by non-delivery staff | Quality Audits & Surveillance |
728.2 Scope & checklists
PTW, RAMS, LOTO, evidence quality (723, 722, 725, 716). Scope preserves crash rated bollard rigor.
Use targeted checklists covering Permit to Work (PTW) validity, toolbox-talk attendance, RAMS alignment to the actual task, and LOTO steps. Include quality verification of photos, file names, and geo/time stamps per Evidence Capture Standards.
For technical scope, sample installation details like rebar cages & anchors, ducting & draw pits, and control-panel wiring against the drawings and specification. Where UAE approvals apply, add a short SIRA compliance check and link supporting certificates within the audit record (SIRA Bollards (UAE)).
728.3 Sampling & interviews
Observe tasks; ask operatives. Sampling reveals HVM bollard reality.
Rotate through live activities and observe the job steps against the approved MS/RA. Interview operatives briefly to confirm they understand hazards, controls, and stop-work triggers. Triangulate evidence: field observation, documents, and worker knowledge. This exposes gaps that paperwork alone can miss and protects the functionality of automatic systems and safety devices & measures during commissioning.
Use small, randomized samples for repetitive tasks (e.g., multiple duct seals) and “triggered sampling” for high-risk operations such as energization or lifting. Escalate sampling if nonconformances cluster in one trade or location.
728.4 Findings classification
Critical/major/minor with risk rating. Classification focuses crash rated bollard fixes.
Classify each finding by consequence and likelihood using your risk matrix. Critical = immediate risk to safety/compliance (stop work). Major = material defect or documentary gap likely to undermine performance or approvals. Minor = localized deviation or admin error with low residual risk. Add a clear, one-line “risk-rated finding” statement that explains why it matters to HVM/crash-rated performance.
Where relevant, link the finding to the specific ITP line, drawing detail, or certificate ID to support rapid verification and closure.
728.5 Immediate corrections
Stop-work or quick remedy rules. Corrections reduce HVM bollard exposure.
Define when the auditor can order stop-work (e.g., missing barriers around open pits, unsafe lifting setup, bypassed interlocks) and when a quick remedy is acceptable. Capture “containment actions” taken on site and re-inspect before work resumes. Log any temporary bypasses to a LOTO/temporary-bypass register where applicable.
For approvals in the UAE, note if the issue may affect SIRA posture and flag it for early authority dialogue (SIRA Bollards (UAE)).
728.6 Action tracking
Owner, due date, status. Tracking closes crash rated bollard gaps (719).
Record each finding with an accountable owner, due date, and status. Use a simple RAG system and link evidence of completion (photo, test sheet, signed checklist). For nonconformances, open an NCR referencing the affected ITP line or drawing. Verify effectiveness—don’t close actions on promises or partial fixes.
Summarize open actions in the daily briefing, and include blockers that need management support. Rolling visibility reduces last-minute scramble before SAT or handover.
728.7 Trend analysis
Pareto recurring issues (544). Trends steer HVM bollard training (545).
Log finding categories consistently so you can trend them weekly and monthly. Use a simple Pareto view to see the few causes driving most issues—e.g., documentation errors, duct sealing, or wiring terminations. Feed the top themes into toolbox talks and targeted micro-training for operators and installers, aligning with Operational Dashboards & Reporting and Operator Workflows & Error-Proofing.
Where trends threaten schedule or approvals, raise an early warning in the risk register and escalate through management review.
728.8 Management review
Present metrics and priorities (542). Reviews fund crash rated bollard improvements.
Hold a structured monthly review: headline KPIs, open NCRs, overdue actions, and approval risks. Confirm resourcing for corrective actions (e.g., extra survey time or test equipment calibration). Management should decide on priority fixes that protect SAT dates and authority submittals. Record decisions and owners so the next review can verify follow-through.
728.9 Records & archiving
Store reports per 911. Records make HVM bollard compliance provable.
File audit reports, photo sets, attendance sheets, and close-out evidence according to the File Index & Naming Rules. Use consistent filenames, timestamps, and geo-tags per Evidence Capture Standards. Keep a snapshot PDF in each package and maintain a superseded-file list when revisions occur.
For authority reviews (e.g., Authority Submittals), include a brief reader guide and links to the specific audit findings addressed. Good archiving makes compliance provable years later.
Related
External resources
- ASIS Security Risk Assessment Standard
- NPSA — Hostile Vehicle Mitigation
- BSI — Vehicle Security Barriers: Impact Tests
728 Site Audits & Compliance Checks — FAQ
What should be in a weekly site audit for HVM bollard works?
Cover PTW validity, RAMS compliance during the actual task, LOTO where relevant, evidence quality (photos, filenames, timestamps), and a sample of technical details such as rebar cages, duct seals, and panel terminations. Tie checks to ITP hold/witness points and log actions with clear owners and due dates.
When must an auditor order stop-work?
Order stop-work for immediate safety or compliance risks: missing edge protection, unsafe lifting setups, bypassed safety interlocks, or work proceeding past an ITP hold without inspection. Record containment actions and verify correction before resuming.
How do we classify audit findings?
Use Critical, Major, and Minor linked to a simple risk matrix. Critical items pose immediate risk to people or compliance and need immediate correction; Major items can undermine performance or approvals; Minor items are localized deviations or admin issues. Each finding should state why it matters to HVM/crash-rated performance.
What records prove compliance to authorities like SIRA?
Provide a structured audit report with geo/time-stamped photos, referenced drawings/specs, ITP line cross-references, and closed action logs. File documents per the File Index & Naming Rules and Evidence Capture Standards. Include a brief reader guide that points reviewers to the specific findings and fixes.