Event Security

Inside Our Playbook for Marathon-Day Crowd Control

Managing 30,000 spectators across multiple zones isn't improvised. Here's how our team prepares months before race day.

D

Dana Alvarez, Event Ops

Jul 28, 2026 · 7 min read

Get Access

Security Assessment Checklist

The Boston Marathon isn't a single event — it's dozens of micro-environments happening simultaneously across 26 miles. Each zone has its own crowd density, access requirements, and emergency egress considerations. A plan that works at mile 10 doesn't automatically work at the finish line.

Zoning before day one

Our planning starts in February. We walk the full course route, identify pinch points, map access roads for emergency vehicles, and define the communication chain for each zone lead. By the time race week arrives, every officer knows their zone, their supervisor, and their fallback point.

The crowd doesn't wait for you to figure out where you're supposed to stand. Your team has to already know.

Communication protocols under noise

Marathon day is loud. Radio communication degrades in dense crowds and near the finish line sound systems. We run a parallel text-based command channel for supervisors and pre-position officers at visual checkpoints so direction can be given without audio.

Zone leads check in every 20 minutes via text command channel

Visual confirmation protocols replace radio confirmation in high-noise areas

All officers carry laminated zone maps with egress routes marked

Medical handoff points are pre-coordinated with BAA and Boston EMS

What we've built over multiple marathon seasons is a system that degrades gracefully — if one communication channel fails, officers can still operate because the plan is embedded, not dependent on real-time instruction.

Event SecurityCrowd ControlBoston