Planned reconfiguration steps, gear, and signage.
Switch safely between everyday use and high-footfall events. Define triggers and layouts using the temporary modes framework (239, 327) and choose portable elements that complement fixed HVM bollards. Plan staffing, wayfinding, and barriers (545, 353) with clear overrides/EFO rules (354). Document changes and reversions (718, 716), test before go-live (631–636), and run a post-event review to refine KPIs and flows (542, 547). 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.
825.1 Triggers & authority
Define who declares event mode and when (239, 131). Authority prevents unsafe HVM bollard changes.
Set a named authorization hierarchy and a simple decision tree that identifies the trigger (ticket sales, VIP arrival, police alert) and the time-based response window. Only the accountable owner may change modes of operation for HVM arrays; this prevents ad-hoc bollard movements that might weaken the defend line. Cross-reference the 239 — Temporary / Event Modes policy and log all declarations in the site diary.
Publish “pre-event checks” (who verifies interlocks, signage, cones, radio channels). If your site is in Dubai, align the trigger/authority map with SIRA expectations and the venue’s incident command posture; list the escalation path up to blue-light services.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
825.2 Pre-approved layouts
Portable elements, cones, barriers (327). Layouts must retain crash rated bollard integrity (232).
Create 2–3 standard layouts that combine fixed crash-rated lines with an event chicane, cones and pedestrian barriers. The golden rule: never widen the clear-gap beyond the limits in 232 — Spacing rules for HVM & Crash-Rated Bollards. Show keepered openings, refuge pockets, and steward posts on the key plan. For removable/lift-out pieces, note the as-tested configuration and any allowable variants.
825.3 Staffing & stewarding
Briefing packs, radios, escalation (547). Human layer backs HVM bollard systems.
Use a written stewarding plan with positions, steward count, and relief breaks. Equip teams with radios, a channel plan, and laminated escalation cues tied to 547 — Emergency Modes & Incident Response. When automatic lanes are present, designate a stewarded gate and ensure operators understand fail-state philosophy and EFO initiators.
825.4 Wayfinding & comms
Temporary signs, VMS, PA scripts (353, 357). Comms reduce confusion.
Prepare a portable wayfinding kit: high-contrast arrows, queue markers, and a small wayfinding legend. Pair with variable message signs and pre-approved PA scripts that call out egress cones, holding pens and detours. All messages should match the safety signalling rules in 353 — Safety Signalling and 357 — Signage & markings to avoid contradictory cues near vehicle access control points.
825.5 Safety overrides
Document limited, timed overrides (354, 355). Overrides never bypass interlocks (352).
Any override must be time-boxed with a visible countdown and recorded in the audit trail. Never bypass safety relays or the 352 — Interlock matrix. Define EFO cooldown and reset hierarchy in line with 354 — EFO & overrides and 355 — Fail-safe/secure states.
825.6 Access windows
Vendor/service schedules (236, 325). Maintain HVM bollard gaps when open.
For deliveries and services, publish short access windows coordinated with queue and crowd peaks. Mark keepered access with cones and a marshal line so the clear-gap rule is maintained. For turning envelopes, cross-check 325 — Turning & Service Access and the site’s credentialed access list.
825.7 Reset-to-normal
Checklists, inspections, evidence (239.8, 716). Reset preserves crash rated bollard compliance.
Use a signed reset-to-normal checklist that confirms bollard positions, latched access states, and reinstated signage. Capture photos per 716 — Evidence Capture Standards and file variations in 718 — Change Log. If automatic lanes were altered, run the essential tests from 630 — Commissioning & safety tests before reopening.
825.8 KPI & crowd review
Measure flows and incidents (542). Lessons roll into 118.
Log throughput, Ops/hour, queue pressure, alarm floods, and incidents, then compare against alert thresholds set in 542 — KPI Set. Convene an After-Action Review (AAR) within 48 hours and feed deltas to 118 — Change Log and the stewarding plan.
825.9 Approval & records
Event plans filed under 717/938. Records sustain HVM bollard governance.
Store the signed event plan, witness diary, and evidence pack under 717 — Authority Submittals and 938 — Submission-Pack Guidance. Nominate a records custodian, retention period, and a one-page index for quick retrieval.
Related
External resources
- NPSA — Hostile Vehicle Mitigation guidance
- DHS/FEMA 426 — Reference Manual
- ASTM F2656 — Crash rating overview
825 Event Mode Reconfiguration — FAQ
What counts as a safe trigger to enter event mode?
Use objective criteria such as scheduled kick-off time minus X minutes, crowd density at defined marshal lines, or a police instruction. The accountable owner activates event mode within the published response window and records the declaration in the site diary and audit trail.
Can portable barriers replace crash-rated bollards?
No. Portable cones and pedestrian barriers are for wayfinding and queue control. They cannot replace the tested performance of crash-rated systems. Keep clear-gaps and defend lines exactly as specified in the pre-approved layouts.
How do we manage Emergency Fast Operation (EFO) during events?
Define who may trigger EFO, the EFO timing window, and the cooldown between activations. All actions must respect the interlock matrix and be logged via the audit trail. After an EFO, run a quick functional check before resuming normal cycles.
What proves we’ve fully reset to normal after the event?
A signed reset-to-normal checklist, photo evidence per the Evidence Capture Standards, reinstated signage, and, where applicable, a short re-test of automatic lanes (loops, safety edges, interlocks). File the pack under Authority Submittals/Submission guidance with a one-page index.