Start here
Effective event security begins before the first guest arrives. The organizer, venue, security provider, medical team, vendors, and public-safety partners need a shared understanding of the event, its risks, each person’s role, and the actions expected when conditions change. There is no responsible universal formula such as “one guard for every 100 attendees. ” Attendance matters, but so do venue design, entrance count, alcohol, audience profile, weather, transportation, cash or valuable assets, publicity, performers, restricted areas, prior incidents, and local public-safety requirements.
Key takeaways
- Assign one accountable event-security lead and identify the decision-makers for the organizer, venue, security team, medical support, and public safety.
- Build staffing from posts, duties, operating periods, relief, supervision, and credible risks—not attendance alone.
- Treat queues, parking, rideshare, loading areas, and the period after the program as part of the event.
- Separate crowd management from emergency response. Good flow, information, and queue design can reduce preventable friction.
- Decide in advance who may screen, deny entry, address intoxication, remove a credential, request that someone leave, or call 911.
- Plan for Arizona heat, dust, monsoon wind and rain, lightning, and potential loss of power or communications.
Who owns the security plan?
The event organizer remains responsible for integrating security into the larger event plan. Hiring guards does not transfer every safety, regulatory, or management duty to the security company.
Name these roles before planning begins:
| Role | Core responsibility to define |
|---|---|
| Event executive/organizer | Final operational decisions, budget, postponement/cancellation authority, and coordination across vendors |
| Venue representative | Building rules, occupancy, access, keys, utilities, fire/life-safety systems, and venue emergency procedures |
| Security lead | Security posts, briefings, supervision, reporting, communications, and escalation under the approved scope |
| Medical lead | First-aid/EMS resources, medical communication, patient access, and documentation |
| Public-information lead | Guest, staff, media, and family communications under normal and emergency conditions |
| Vendor/production lead | Staging, deliveries, performers, contractors, credentials, and production hazards |
| Public-safety liaison | Approved coordination with police, fire, EMS, emergency management, or other authorities |
One person may hold more than one role at a small event, but no critical responsibility should be assumed or left unnamed.
Start with an event risk profile
Collect facts before deciding headcount or posts.
Event characteristics
- date, public hours, setup, rehearsal, vendor access, and teardown;
- expected and maximum attendance;
- ticketed, invited, employee-only, or open-public entry;
- seated, standing, moving, competitive, religious, political, commercial, or entertainment format;
- age range and accessibility needs;
- alcohol, cash sales, merchandise, controlled items, or valuable equipment;
- public figures, performers, VIPs, contentious subject matter, or significant publicity;
- prior incidents, threats, disputes, protests, counter-events, or recurring problems; and
- indoor, outdoor, or mixed spaces.
Venue characteristics
- property boundaries and neighboring uses;
- public entrances, staff/vendor entrances, exits, gates, stairs, elevators, loading docks, and emergency access;
- expected queue locations and maximum queue space;
- parking, rideshare, transit, pedestrian routes, and road crossings;
- lighting, fencing, doors, locks, cameras, alarms, public-address systems, radios, and backup power;
- first-aid location, shelter areas, evacuation routes, and assembly or reunification areas;
- temporary stages, tents, fencing, generators, cooking, or pyrotechnic activities; and
- cellular/radio limitations and accessibility considerations.
Operating environment
Review weather and heat, nearby events, construction, transit changes, road closures, holidays, community concerns, and public-safety availability. CISA’s current Venue Guide recommends a site-specific physical-security assessment and protective measures tailored to the venue, supported by response and recovery planning.[2]
Build staffing from posts and duties—not a ratio
Start by listing every post that must operate at the same time. Then calculate the personnel needed to cover those posts, supervision, breaks, movement, and contingencies. Examples include:
- public entrances and exits;
- staff, vendor, loading, or performer access;
- ticket or credential support;
- bag or prohibited-item screening, if authorized and designed;
- queue and pedestrian-flow observation;
- parking, rideshare, or shuttle areas;
- backstage, cash, equipment, or other restricted zones;
- interior or perimeter patrol;
- control-room or communications support;
- alcohol-service observation or organizer liaison;
- a roving response or supervisor function; and
- setup, overnight, and teardown coverage.
Do not assign one officer to incompatible simultaneous duties. An entrance officer cannot continuously screen guests and patrol a remote parking lot. A supervisor responsible for the entire operation may not be available as a fixed post.
A practical planning calculation
Use this as a worksheet, not an industry standard:
- Count the posts required during each operating period.
- Add supervision appropriate to the complexity and span of control.
- Add relief so required posts remain covered during breaks.
- Add roving capacity when the plan requires response away from fixed posts.
- Recalculate for arrival, peak program, intermission, closing, and teardown; needs may change by phase.
- Reconcile the plan with venue rules, permits, insurers, and public-safety requirements.
If budget does not support every proposed post, reassess the event design—reduce entrances, change hours, improve barriers or credentials, relocate valuable activities, or modify attendance—rather than silently leaving a critical task uncovered.
Entrances, screening, and credentials
An effective entrance should move authorized guests through a clear process while preserving emergency egress.
Define:
- which entrances are public, staff-only, vendor-only, emergency-only, or closed;
- who supplies and verifies tickets or credentials;
- which bags or items are permitted under the organizer’s written policy;
- whether screening is visual, ticket-based, bag-related, technology-supported, or another approved method;
- who may make an exception or deny entry;
- what happens when a guest refuses a policy or has an accessibility need;
- where prohibited but lawful property may be returned or handled, if applicable;
- how waiting lines are formed without blocking exits, roads, or neighboring property; and
- how capacity information moves between ticketing, venue, and security leads.
CISA provides public-venue resources addressing screening, bag-search procedures, and credentialing.[3] Any search or screening program should be approved by the venue, organizer, counsel, insurer, and qualified security leadership. Officers should not improvise search authority or introduce unapproved physical contact.
Crowd management before crowd control
Crowd management uses space, timing, barriers, staffing, communication, and information to support orderly movement. It is broader than responding after behavior becomes disorderly.
Good planning addresses:
- clear signs and advance guest instructions;
- adequate entrance processing so queues do not become dangerous or frustrated;
- separation of incoming and outgoing flows where practical;
- accessible routes and accommodations;
- monitoring of density and chokepoints;
- open emergency routes;
- information for delays, schedule changes, sheltering, evacuation, or cancellation;
- safe movement at intermission and closing; and
- a lost-person and reunification process that protects personal information.
When a disturbance occurs, the plan should define who speaks with the person, who notifies the organizer, when alcohol service or entry may be stopped under approved authority, when police are called, and what officers may do under Arizona law and post orders. Private guards do not gain police powers through their employment.[4]
Alcohol changes the plan
Alcohol service can affect guest behavior, decision-making, medical needs, lines, disputes, and closing. Security does not replace the licensed alcohol provider or its legal responsibilities.
The plan should identify:
- the license holder and alcohol-service decision-maker;
- service locations and hours;
- credentialing or age-verification responsibility;
- entrances/exits to the licensed area;
- how staff communicate concerns about apparent intoxication or unsafe conduct;
- who may stop service, refuse entry, or ask someone to leave;
- transportation and safe-exit considerations;
- medical and police escalation; and
- documentation after an incident.
Arizona’s special-event liquor-license application specifically asks applicants to describe security and control measures and list police/security personnel and fencing or barriers when applicable.[5] That form is not a staffing calculator. The organizer and license holder should verify the current Arizona Department of Liquor Licenses and Control requirements, local approvals, and venue conditions for the actual event.
Parking, rideshare, and the perimeter
Security concerns often begin before guests reach the entrance and continue after the program ends. Map:
- vehicle entrances and exits;
- pedestrian crossings and accessible routes;
- rideshare, taxi, shuttle, bicycle, and transit areas;
- vendor and emergency-vehicle access;
- tailgating or gathering areas;
- lighting gaps and isolated paths;
- vehicle queues and potential road backups;
- cash or equipment movement; and
- the final employee/vendor departure.
Traffic direction on public roads may require authorized personnel or a public agency. Private security should not assume powers or duties that have not been legally and operationally approved. The plan should also preserve fire lanes and responder access throughout setup, public hours, and teardown.
Emergency action and communications
Security is one part of the emergency plan. Ready.gov emphasizes that the first minutes matter and that prompt warnings and accurate calls for public emergency services can save time.[6]
Build plain-language procedures for relevant hazards, which may include:
- medical emergency;
- fire or smoke;
- severe weather, heat illness, lightning, dust, wind, or flooding;
- missing child or vulnerable person;
- lost communications or power;
- suspicious item or threat;
- escalating fight or disorder;
- active violence;
- structural or production hazard; and
- evacuation, shelter, lockdown, cancellation, or reunification.
For each procedure, define who identifies the condition, who has decision authority, how staff and guests are warned, which communications channel is primary and backup, who calls 911, who meets responders, how emergency access is maintained, how people with disabilities or access and functional needs are supported, and how staff accountability is achieved.
Do not publish sensitive tactical details on the public event page. Keep full maps, radio channels, keys, vulnerabilities, and command information in controlled operational documents.
Arizona heat and monsoon planning
Arizona heat is a material event risk. The Arizona Department of Health Services describes increasingly long periods of extreme heat and provides current heat-preparedness resources.[7] Outdoor plans should address water, shade or cooling, work/rest arrangements, medical support, guest messaging, and thresholds for modifying or pausing activity. Security posts exposed to sun need the same protection as other workers.
The National Weather Service’s Phoenix office identifies dust storms, downbursts, flash floods, heat, and lightning among monsoon hazards and recommends checking forecasts and postponing outdoor activity when a severe thunderstorm warning is issued.[8] Establish who monitors official weather information and who can delay, shelter, evacuate, or cancel.
Armed or unarmed event security?
Do not answer this by event type alone. Consider the documented threat assessment, venue policy, organizer policy, insurer requirements, expected duties, police presence, response time, crowd density, alcohol, children, public figures, prior threats, and the consequences of introducing firearms into a crowded setting.
Unarmed officers can provide visible presence, entrance observation, credential support, patrol, communication, de-escalation, documentation, and emergency coordination. Armed coverage may be appropriate when a qualified assessment supports it, but it also requires additional licensing, firearms training, use-of-force policy, supervision, identification, and coordination. Arizona armed guards must satisfy DPS requirements.[9]
The decision should be written, reviewed, and integrated with the overall plan. Armed status does not create police authority, and it should never substitute for entrance design, communications, emergency planning, medical readiness, or public-safety coordination.
Information needed for an event-security proposal
Provide this information early:
| Planning field | Event answer |
|---|---|
| Event name, date, venue, and address | [ ] |
| Setup, staff/vendor arrival, public hours, and teardown | [ ] |
| Expected and maximum attendance | [ ] |
| Event format and audience | [ ] |
| Site map with entrances, exits, stage, vendors, parking, and emergency routes | [ ] |
| Ticketing, invitation, or public-entry model | [ ] |
| Alcohol, cash, merchandise, VIPs, performers, or restricted zones | [ ] |
| Known threats, prior incidents, protests, or community concerns | [ ] |
| Venue rules, permits, insurance, and required staffing | [ ] |
| Screening, bag, credential, reentry, and removal policies | [ ] |
| Police, fire, EMS, medical, and emergency-management contacts | [ ] |
| Radios, PA, alerts, and backup communications | [ ] |
| Heat, weather, shelter, evacuation, and cancellation plan | [ ] |
| Accessibility and reunification needs | [ ] |
| Requested officer duties and armed/unarmed status | [ ] |
| Reporting and post-event review expectations | [ ] |
Day-of operational checklist
- The final site map and event schedule match current conditions.
- All security personnel have signed in, are properly assigned, and received event-specific post orders.
- Organizer, venue, security, medical, production, and public-safety contacts are confirmed.
- Entrances, exits, emergency access, fire lanes, queues, restricted zones, and barriers are checked.
- Tickets, credentials, prohibited-item policy, exception authority, and reentry rules are understood.
- Radios and backup communication methods have been tested.
- Weather and heat monitoring responsibility and decision thresholds are active.
- Medical resources and the 911 meeting point are confirmed.
- Emergency messages and decision authority are confirmed.
- Break and relief coverage is scheduled.
- Reports, incident numbers, evidence/footage procedures, and end-of-shift briefing are ready.
After-action review
Within an agreed period after the event, review:
- entry and queue performance;
- crowd movement and accessibility;
- staffing, supervision, relief, and communications;
- medical, security, guest-service, weather, and operational incidents;
- calls, response, decisions, and handoffs;
- equipment or coverage failures;
- complaints, near misses, and unplanned workarounds;
- report completeness and footage preservation; and
- changes required before the next event.
Assign each corrective action an owner and due date. Keep the operational plan current rather than filing the review away.
Frequently asked questions
How many security guards does an event need?
There is no universal guards-per-attendee ratio. Staffing should follow simultaneous posts, duties, venue characteristics, alcohol, entrances, parking, restricted areas, threat information, event phases, required supervision, relief, and venue or public-authority requirements.
What can event security officers do?
Officers can perform lawful, contracted duties in the written plan, such as entrance observation, approved credential support, patrol, maintaining clear emergency routes, protecting assigned areas, documenting incidents, and communicating with event leadership or responders. Exact screening, search, removal, enforcement, and physical-intervention duties require explicit policy, training, and legal review.
How far in advance should event security be booked?
As soon as the venue, date, attendance range, and format are known. Complex or high-demand events need time for a site walk, risk review, staffing, public-safety coordination, post orders, and briefing. Ask the provider to confirm current lead times, minimums, and availability for the specific event.
Can Arrow cover a one-day or temporary event?
Arrow’s current service page lists special events and short-term assignments. Availability, geography, minimum hours, duties, pricing, equipment, and lead time must still be confirmed for the specific date and event.
Should event officers be armed?
Only after a documented risk assessment and review of venue, organizer, insurer, legal, and public-safety requirements. There is no safe universal answer based only on attendance or alcohol.
