Crowd surges, event modes, and temporary arrays.

Event venues swing from empty to packed in minutes. Use crowd and queue design (231, 239) to set safe, efficient flows and adopt temporary/event modes with portable elements (327, 825). Where threats warrant, deploy HVM bollards at pinch points (324) with proven interlocks and signalling (342–353). Plan rapid resets, drills, and post-event reviews (547), and keep evidence organized for authorities (938). 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.

817.1 Crowd pulses & modes

Ingress/egress peaks require pre-sets (239, 525). HVM bollard arrays avoid pinch points (321.5).

Match venue “pulses” (pre-gate surges, halftime exits, end-of-show waves) to pre-agreed modes of operation. For everyday use, keep pedestrian desire lines open; for event mode, bring in portable barriers or switch lane logic to protect the pinch point. Use live counts, steward observations, and ticket timings to trigger transitions safely.

Where vehicle threat exists, choose HVM systems sized for realistic run-ups (see Vehicle Dynamics Assessment). Avoid overspecifying: protect only the credible approach vectors and ensure pedestrian capacity from People Flow & Egress Widths (231) is preserved in each mode.

Coordinate the timing of mode changes via operations radio and a simple “ready-check” between stewards and the bollard operator. Document in the mode plan (525) how to reverse quickly if conditions change.

AspectWhat mattersWhere to verify
PerformanceTested system (bollard + foundation)Crash standards overview (411)
OperationsDuty cycles, fail state, signageModes of Operation (525) · Signage & Markings (357)
PeopleEgress width, queue safetyPeople Flow (231)

817.2 Perimeter rings

Layered protection with chicanes and islands (321–324). Protect temporary merchandise zones.

Create two or three “rings”: (a) outer traffic calming and event chicanes; (b) mid-ring to protect queues and merchandise kiosks; (c) inner ring at gates. Use Array Patterns (321) and Corners, Islands & Pinch Points (324) to form safe pedestrian corridors without creating handlebar traps.

For temporary retail, include a small exclusion zone behind any frontage barrier. Position card readers and counters outside the defend line so that crowding doesn’t spill into vehicle lanes; see Spacing Rules (232).

817.3 Service/coach access

Keepered openings and timed windows (325). Interlocks enforce safety (352).

Use keepered openings sized for team coaches and emergency vehicles. Grant access in short “windows” before or after peak pulses. An interlock matrix should prevent lowering automatic bollards when crowds are within the egress cone, and enforce PA/visual warnings before movement.

Consider EFO only where doctrine requires it, and prove safe behavior with test scripts (see 634 and 637).

817.4 Temporary streets

Portable elements and marshal plans (327). Restore normal after events (239.8).

On match days and festivals, convert streets to pedestrian-first corridors using temporary/event reconfiguration (327). Deploy lightweight surface units only for low-speed contexts; where credible vehicle threat exists, use certified portable systems and respect setback/run-up rules.

Write a marshal plan that shows steward posts, stewarded gates, and reset-to-normal checklists. After the event, remove temporary islands fully and confirm that permanent lanes and induction loops are unobstructed (see 239 and 825).

817.5 Signage & stewarding

High-clarity cues and PA alignment (353, 357). Prevent wrong-way vehicle entries.

Combine high-contrast ground markings with overhead boards and clear public-address scripts so voice, signs, and steward gestures never conflict. Use conspicuity cues around bollard lanes and provide a distinct hold line so drivers stop before the danger zone. A “wrong-way” prevention routine (lights, audible), tied into the Safety Signalling (353), should latch until cleared by the operator.

817.6 Emergency egress

EFO, overrides, and safe states (354–355). Drills prove behavior (547).

Emergency flows take priority over vehicles. Configure overrides & EFO (354), then verify fail-safe/secure states (355) with realistic drills from Emergency Modes & Incident Response (547). Keep pedestrians in the egress cone clear of moving equipment via interlocks and steward lines.

817.7 Surface & drainage

High-litter and spill loads (334, 245). Keep heads visible post-cleaning (365).

Events produce litter and spills that can block drainage and obscure bollard heads. Design for drainage (334) with silt baskets and accessible sumps; plan cleaning so water doesn’t flood control enclosures (see 245). After cleanup, confirm conspicuity and that any photo-eyes are clean and aligned; build this into the Preventive Maintenance Plan (734).

817.8 Noise & neighbors

Night limits and barriers (546). Scheduling respects residents.

Night matches and concerts require acoustic planning: select quiet enclosures and apply noise limits (546) to HPUs, with night mode to slow operations. Position acoustic screens to shield residential façades and schedule deliveries and coach departures away from curfew windows. Keep complaint hotlines and mitigation notes in the site’s service levels & availability pack.

817.9 Acceptance & evidence

Worked spacing examples, videos (232.9, 716). Pack streamlines approvals (717).

Authorities often request clear spacing diagrams, unedited test footage, and a coherent submission index. Use the Evidence Capture Standards (716) and the Submission-Pack Guidance (938) to build a single, traceable pack. In the UAE, align early with SIRA requirements and include a succinct Operational Requirements Document.

Prove the system on site: complete SAT/Witness Procedure (638), show fail-safe/fail-secure logic, and attach a tidy Handover Pack Index (736) for operations.

Related

External resources

817 Stadiums, Venues & Events — FAQ

What HVM bollard setup works best for stadium peak crowds?
Use layered rings: an outer chicane for traffic calming, a mid-ring that protects queues and merchandise, and an inner gate line sized to egress width rules (231). Tie lane behavior to named modes of operation with clear steward hand-signals and PA scripts.
How do we manage team coach access without compromising crowd safety?
Provide a keepered opening and schedule timed access windows outside the main pulses. Enforce an interlock matrix so bollards cannot lower while pedestrians occupy the egress cone.
Are temporary, surface-mounted barriers enough for big events?
They’re suitable for low-speed crowd separation. If there’s a credible vehicle threat, use certified HVM systems with proper setback and proven run-up control. See 327 and 825.
What documents help with authority approvals (e.g., SIRA in the UAE)?
Provide spacing drawings, crash test evidence, and an indexed submission pack built from Evidence Capture Standards (716) and Submission-Pack Guidance (938). For UAE projects, add a concise SIRA note and link to SIRA Bollards (UAE).