How this estimate is built
This calculator is an educational estimate based on published industry guidance. Tectus is a marketplace that connects you with independent, licensed security companies; Tectus does not provide security services, staffing, or consulting, and using this tool does not create any professional or advisory relationship. Nothing on this page is legal advice.
The published band
Security-industry guidance for event staffing is commonly published as a band of roughly 1 officer per 50 guests (high-energy events) to 1 per 100 guests (low-risk, controlled events), and some cities, counties, and regulators publish or mandate ratios of their own. This calculator works only inside that published band: it never invents a tighter or looser ratio, and it never adds staffing increments of its own authorship. Where you see a range rather than a single number, that is deliberate — the published guidance is a band, not a number, and the final figure is always set between you, your licensed provider, and your local authorities.
How your inputs are used
Event type selects a base position in the band: invite-only and credentialed events start at the 1-per-100 end, while general-admission, concert, nightlife, and “not sure” events start at the conservative 1-per-50 end — uncertainty never loosens coverage. Alcohol moves any event to the 1-per-50 end; it is the best-documented adjustment in the published sources. Risk context you report — multiple separated areas, an open or hard-to-control perimeter, overnight hours, cash or high-value items — moves the estimate toward the conservative end of the same published band and widens the displayed range. Published guidance identifies these as risk factors but does not quantify them, so this calculator does not either: instead of inventing numbers, it gives you specific questions to raise with the licensed companies you get proposals from.
Every division rounds up. The low end of the range is never below two officers, because a lone officer cannot watch an entry and respond to an incident at the same time. Events serving alcohol at 150+ attendance never show fewer than three, mirroring a published municipal minimum pattern.
What this tool will not do
It will not produce a number for events of 5,000 or more; for events of 2,500 or more that are high-energy, serve alcohol, or lack a controlled perimeter; or for open-perimeter events of 1,000 or more that are high-energy or serve alcohol. Those profiles need a professional security plan built from a site-specific risk assessment. It will not produce a number when you report threats, prior violence, expected protests, weapons concerns, protection of a specific person, or a K-12/minor-dominated event — those situations are outside what any ratio can address, and the tool routes you to police coordination, professional threat assessment, protective-services providers, or your school district instead. If there is ever an immediate threat to anyone’s safety, contact local police or call 911.
Crowd managers are a different role
Many fire codes (through state and local adoption of model codes such as the International Fire Code and NFPA standards) require venues to designate trained crowd managers above certain occupancy thresholds. Crowd managers are a fire-code and occupancy-safety role. They are not licensed security officers, this calculator does not count them, and neither role substitutes for the other. Your venue and your local fire marshal determine whether crowd managers are required and how many. No security-staffing source cited below is a crowd-manager source, and no fire-code crowd-manager provision is a security-staffing source.
Sources
Verified as of August 2026; re-verified quarterly. These citations illustrate how the estimate is derived. They are not representations that any output satisfies any jurisdiction’s current requirements, and they are not compliance guidance — laws and local requirements change, so verify current rules with the issuing authority, your city, and your licensed provider.
- Security-industry guidance publishing the ~1:50–1:100 event staffing band, tightening to ~1:50–1:75 when alcohol is served — this tool uses the conservative 1:50 end for alcohol.
- City of St. Louis: published general rule of 1 security person per 50 attendees for special events, adjusted for alcohol, time, and location — the basis for placing general-admission public events at the 1:50 end.
- City of Minneapolis: ordinance mandating security personnel at ratios that tighten when intoxicating beverages are served — cited solely as corroboration that alcohol tightens security staffing (a security-personnel ordinance, not a crowd-manager source).
- New Mexico Alcoholic Beverage Control: guidance to special-event permit applicants that roughly 1 security person per 100 attendees is typical, with authority to require more.
- Calhoun County, SC: recreation-facility policy combining a per-100 ratio with an absolute 3-officer minimum when alcohol is served — the published pattern the 3-officer floor mirrors.
- Event Safety Alliance / ANSI ES1.9: event-security risk-assessment framework identifying event type and entry points as risk factors — cited for direction only; it does not quantify staffing increments, and neither does this tool.
- Model fire codes (IFC/NFPA as adopted locally): trained crowd-manager requirements above occupancy thresholds — cited only to distinguish the crowd-manager role from licensed security.
The two-officer floor, the application of the three-officer alcohol floor beyond its source jurisdiction, the width of the displayed range, and the decision to position risk-context events at the conservative end of the band are Tectus’s conservative editorial policy in presenting the published guidance. They are disclosed here as policy, not as published ratios — and they only ever make the estimate more cautious, never less.