# Event Management and Crowd Safety # Large Event Communications with Mesh Networks ## Large Event Communications with Mesh Networks Managing communications across a sprawling outdoor event - a music festival, marathon, county fair, or major sporting event - has traditionally meant either expensive commercial radio rental packages or reliance on cellular networks that buckle under crowd-generated load. LoRa mesh networking offers event organisers a self-contained, scalable communications infrastructure that can be deployed, operated, and torn down entirely by in-house staff. ### The Scale Problem Events covering 15 to 50 acres typically require coordinated communications between dozens of staff roles: stage managers, security personnel, medical teams, parking attendants, vendor coordinators, and the central operations tent. Commercial event radio packages typically cost $500 or more per radio per day for rental, programming, and frequency coordination - a significant line item for events running on tight margins. A comparable mesh deployment covering the same venue can be built for $1,500-3,000 in hardware that the event organisation owns outright, amortised across many events. ### Typical Deployment Architecture A 15-node mesh for a 5,000-person outdoor event might be laid out as follows: - **Infrastructure nodes (5-6 nodes):** Mounted on light poles, temporary scaffold masts, or the roof of the main stage structure. These nodes provide the backbone coverage layer and are configured with higher transmit power and external antennas (3-6 dBi gain omnidirectional). Each is powered from AC mains via a weatherproof enclosure with a battery backup to survive generator cycling. - **Operations tent node (1 node):** Connected to a laptop running the Meshtastic web client or a dedicated display showing the network map and recent messages. This serves as the command-and-control hub. - **Mobile nodes (8-9 nodes):** Carried by key staff (security supervisor, medical team lead, stage manager, parking coordinator, etc.). Standard handheld Meshtastic devices with the default 2.5 dBi antenna perform well within the mesh coverage footprint. ### Position Tracking for Staff and Security GPS-enabled Meshtastic nodes broadcast position reports at configurable intervals (typically every 30-120 seconds for a moving staff member). The operations tent display shows a live map of all staff positions, enabling rapid resource dispatch. If a medical situation occurs in the southeast corner of the venue, the operations coordinator can see at a glance which medical team member is nearest and direct them via text message over the mesh - without needing to shout over a congested radio channel. ### Integration with Venue Maps Meshtastic map view can be loaded with custom venue base maps (exported from tools like QGIS or even hand-drawn site plans converted to georeferenced images) so that staff positions are displayed against the actual venue layout rather than generic satellite imagery. This is particularly useful for events held in venues with complex layouts - multi-stage festival grounds, fairgrounds with dozens of vendor areas, or racecourses with non-obvious access paths. ### Deployment Logistics A well-organised team of two people can deploy a 15-node infrastructure mesh in 3-4 hours on the morning before an event. Key logistics considerations include: - **Pre-event configuration:** All nodes should be pre-configured and tested in the shop before arrival on-site. Channel settings, node names, and firmware versions should all be verified. A checklist for each node prevents configuration errors under time pressure. - **Repeater placement:** Infrastructure nodes should be sited with line-of-sight to as much of the venue as possible. Walking the venue with a test node and recording RSSI values at key locations before finalising mast positions will prevent coverage surprises. - **Power planning:** All infrastructure nodes need power. AC runs or portable battery packs (20,000 mAh capacity provides 24+ hours of operation for a single node) should be planned before event day. - **Teardown:** Label every node and cable clearly. Post-event teardown should follow a documented node-by-node checklist to ensure all equipment is recovered. GPS tracking on infrastructure nodes provides a recovery safety net. ### Case Study: 5,000-Person Outdoor Event A regional music festival deployed a 15-node Meshtastic mesh across a 22-acre venue for a two-day event. Infrastructure nodes were mounted on four light poles and one temporary 8-metre mast at the main stage. Over the two-day event, the mesh carried over 1,200 text messages between staff with zero network outages. The total hardware cost was $1,800; equivalent commercial radio rental for the same staff complement would have run approximately $4,500 per day. # Crowd Monitoring and Safety Applications ## Crowd Monitoring and Safety Applications Beyond staff communications, LoRa mesh infrastructure deployed at events can serve an active crowd safety function - providing real-time or near-real-time situational awareness about crowd density, movement, and emerging incidents. These capabilities are particularly relevant for large events where crowd crush is a genuine risk, or for venues where incident command needs rapid visibility into conditions across a large area. ### Crowd Density Monitoring via Proxy Sensors Direct counting of individual people is both technically complex and raises significant privacy concerns. A practical and privacy-preserving alternative is to use passive WiFi and Bluetooth probe request counting as a proxy for crowd density. Modern smartphones continuously broadcast probe requests as they search for known WiFi networks; these requests are detectable by any WiFi-capable device in passive monitoring mode. A sensor node - typically a small single-board computer like a Raspberry Pi Zero 2W paired with a LoRa radio module - can count probe requests in a defined time window and transmit the count (not any identifying information) over the mesh to the operations centre. Correlating these counts with known venue capacity for each zone gives event safety staff a real-time density heatmap without collecting any individual-level data. Important caveats: probe request counting provides relative density rather than absolute headcounts, and iOS and Android devices vary in probe request behaviour due to MAC randomisation policies. Calibrating the system during setup by counting known groups provides a correction factor. ### Evacuation Coordination In an emergency requiring full or partial venue evacuation, the mesh provides a communications channel that is explicitly independent of cellular and WiFi infrastructure - both of which will be saturated by thousands of people simultaneously trying to call, text, and post to social media. Incident command can broadcast evacuation instructions to all staff simultaneously as a text message, confirm receipt from zone leaders, and monitor staff GPS positions to verify that all areas are being cleared. Pre-event planning should include documented mesh-based evacuation protocols: which node operators are responsible for which zones, what messages signal different alert levels (shelter-in-place vs. full evacuation), and how to confirm all-clear. These protocols should be practised at least once before the event in a tabletop exercise. ### Lost Child and Patron Location Assistance GPS-enabled nodes worn or carried by children (or vulnerable patrons in need of escort services) can transmit their position over the mesh to a family reunification station. At a practical level, this is most useful as a check-in/check-out system at large family events: a wristband node given to a child at entry can be tracked to the family reunification tent if the child becomes separated. This is a straightforward application that requires minimal infrastructure beyond the existing mesh backbone. ### Medical Team Dispatch Medical teams at large events benefit from mesh communications in several ways beyond simple voice replacement. A text-based dispatch system over mesh allows the medical coordinator to send structured information (location grid reference, nature of complaint, resources needed) to the responding team - information that is easy to mishear over radio in a noisy festival environment. The GPS position of the medical team can be monitored by dispatch to confirm arrival and to direct the nearest available team to new incidents. ### Privacy Considerations Event organisers deploying crowd monitoring systems should address privacy proactively: - **Aggregate data only:** Density counts by zone, not individual tracking, should be the operational norm. Log files should contain zone counts, not device identifiers. - **Disclosure:** If probe request counting is used, this should be disclosed in event terms and conditions and on signage at venue entrances. Many events already disclose security camera use; WiFi monitoring disclosure belongs in the same category. - **Data retention:** Density logs should be deleted after the event unless there is a specific safety or legal reason to retain them. Establish a data retention policy before deployment. - **Staff GPS tracking:** Staff should be informed that their GPS position is visible to operations centre staff during the event. This is typically disclosed in staff onboarding materials. ### Integration with Incident Command Structure For permitted events with a formal incident command structure (required by many jurisdictions for events above a certain attendance threshold), the mesh communications system should be integrated into the ICS organisation chart. The communications unit leader should understand the mesh system capabilities and limitations, and the operations section should include mesh-based status reporting in its protocols. Pre-event coordination with local fire, EMS, and law enforcement should identify whether those agencies want read-only access to the mesh map or whether they prefer to operate on their own networks with liaison officer communications.