Event security permits and licensing in Phoenix: the complete walkthrough

The launch was 6 weeks away. The distillery had rented a convention centers space in Phoenix's Downtown Phoenix district — exposed brick, natural light, 200 invited guests including trade press and a handful of restaurant buyers who'd been cultivating for months.

The venue coordinator sent a message on a Tuesday morning: "We need to see proof of licensed security before we can confirm. Under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security), events of this size require an operator on record before the space is finalized."

The founder had handled everything. Catering, AV, invitations, custom glassware. He had not handled this. He hadn't known it existed.

Event organizers in Phoenix learn about permit requirements one of two ways: during planning, or when a compliance inspector arrives and shuts the event down. The distillery founder found out on a Tuesday morning with 6 weeks to act. That's the good version.

Why Phoenix's permitting environment is more complex than most organizers expect

Phoenix (population 4.9M metro) hosts events across a diverse range of precincts — from outdoor activations in Downtown Phoenix to seated functions at licensed resort hotels in Camelback Corridor — and each combination of precinct, venue type, and audience size creates a distinct compliance pathway under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

The documented risk profile of Phoenix — downtown event crowd safety concentrated in Downtown Phoenix and Old Town Scottsdale, and high-end resort and hospitality target risk documented across Old Town Scottsdale, Camelback Corridor, and Arcadia — directly influences how the Phoenix licensing authority reviews security management plans. Events in Phoenix's higher-risk precincts face enhanced scrutiny and, in some cases, mandatory pre-approval site walks before an event permit is confirmed.

The Phoenix market has also consolidated around a smaller number of fully compliant operators since 2023. Events in Downtown Phoenix and Old Town Scottsdale that brought in out-of-jurisdiction security contractors — operators unfamiliar with Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)'s specific provisions for Phoenix's convention centers and resort hotels venue environments — have generated compliance findings that affected subsequent permit applications. The cost of that pattern has made Phoenix event organizers more attentive to verifying Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) credentials early.

The whiskey launch founder's situation — discovering the permitting requirement 6 weeks before the event — is actually a favorable timeline by Phoenix standards. The compliance process for a well-prepared Phoenix event organizer, working with a fully licensed Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)-compliant security provider from the outset, typically takes 3–4 weeks. Organizers who discover the requirement after submitting a permit application without naming a security provider can face an amendment process that adds 2–3 weeks to the timeline and, at peak event season in Phoenix's Downtown Phoenix and Old Town Scottsdale precincts, may push the approval date uncomfortably close to the event itself.

Phoenix compliance snapshot

| Factor | Phoenix detail | |---|---| | Governing law | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) | | Key event precincts | Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia | | Major venue categories | convention centers, resort hotels, professional sports arenas | | Documented risk profile | downtown event crowd safety, high-end resort and hospitality target risk | | Metro population | 4.9M metro |

This snapshot is the starting point for every Phoenix event security compliance decision. The specific combination of Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) requirements, the risk profile of downtown event crowd safety and high-end resort and hospitality target risk in Phoenix, and the venue-specific conditions attached to convention centers and resort hotels operations shapes the compliance pathway for your Phoenix event.

What Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) covers

Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) is the regulatory foundation for all private security operations in Phoenix. For event organizers, the practical requirements are:

Operator licensing under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security): Any company providing security services for compensation at an event in Phoenix must hold a current operator license. Contracting with an unlicensed provider creates joint liability for the event organizer under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)'s enforcement provisions.

Individual officer licensing: Officers must hold personal licenses issued under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security), separate from the operator license. This is the most common compliance gap in Phoenix: an agency holds a valid operator license but deploys individual officers who are not personally licensed under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

Scope of authority: Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) defines exactly what licensed security personnel may do in Phoenix. Detention authority, use-of-force parameters, and incident reporting obligations all flow from Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security). Officers who exceed their defined scope create legal exposure for the event organizer.

Record-keeping: Licensed operators under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) must maintain deployment records, incident logs, and officer credential files for Phoenix events. As an event organizer, you may need to produce evidence of licensed security deployment if a regulatory inspection or incident claim arises.

Who issues event security permits in Phoenix

Event security in Phoenix involves 2 separate permitting authorities:

The Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) licensing authority: This body licenses operators and individual officers in Phoenix. You do not apply here as an event organizer — your contractor must already hold these licenses. Your job is to verify they do.

The Phoenix events authority or council: This body governs the event itself, including whether a security management plan must be submitted as a condition of your event permit. Events in Phoenix's Downtown Phoenix and Old Town Scottsdale precincts, at licensed convention centers or resort hotels, or above threshold attendance levels require a security plan as part of Phoenix event approval.

For private events hosted at established resort hotels, the venue's existing security plan may partially satisfy Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) requirements. Confirm this with your venue's operations manager — do not assume coverage is in place.

The 5-step compliance process for Phoenix events

Step 1: Classify your Phoenix event

Not all events in Phoenix face the same Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) requirements. Trigger factors specific to Phoenix include:

• Total expected attendance at your Phoenix venue
• Whether the Phoenix venue is licensed (convention centers, resort hotels) or non-licensed (private estate, outdoor space)
• Whether alcohol will be served under a Phoenix liquor authority approval
• Whether the event is open to Phoenix's general public or invitation-only

Higher-risk classifications — events with exposure to downtown event crowd safety or high-end resort and hospitality target risk in Phoenix — typically face enhanced Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) requirements including minimum staffing ratios and mandatory crowd-management certification.

Step 2: Select a licensed Phoenix security provider early

Permit applications in Phoenix often require the security contractor to be named at submission. Selecting your provider after submitting the event permit application requires an amendment, extending an already-compressed approval timeline.

Before contracting any Phoenix security provider, confirm they hold:

• A current operator license under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)
• Individual officer licenses issued under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) for all personnel assigned to your event
• Crowd-management certification for events above Phoenix's applicable attendance threshold
• Experience with Phoenix's Downtown Phoenix and Old Town Scottsdale event environments and the specific risk dynamics of downtown event crowd safety and high-end resort and hospitality target risk

Step 3: Develop the Phoenix security management plan

A security management plan (SMP) documents how security will be managed at your Phoenix event. Standard SMP components required by the Phoenix events authority:

• Phoenix event overview: dates, location in Downtown Phoenix or Old Town Scottsdale, expected attendance, event type and audience profile
• Security staffing model: officer count, roles, deployment positions, Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) license references for key personnel
• Access control procedures for your specific Phoenix venue layout
• Crowd management approach addressing Phoenix's documented downtown event crowd safety and high-end resort and hospitality target risk risk profile
• Emergency procedures for Phoenix: evacuation routes, emergency services communication chain, medical response contacts
• Incident reporting protocol under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security): how incidents are logged and reported post-event in Phoenix

Your Phoenix security contractor should be able to provide their SMP template and draft the Phoenix-specific content with you. Any contractor operating professionally in Phoenix under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) carries this as a standard deliverable.

Why this matters in Phoenix

Phoenix's Downtown Phoenix and Old Town Scottsdale entertainment precincts operate under heightened Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) scrutiny shaped by Phoenix's local incident history. Events involving downtown event crowd safety face enhanced compliance review. Events at convention centers carry specific venue-level security conditions embedded in Phoenix operating licenses.

Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance inspections in Phoenix now occur at approximately 1 in 8 large-format events, up from 1 in 30 before 2022. A Phoenix event shut down due to non-compliant security staffing generates an insurance claim denial, potential venue liability, and a compliance record affecting future permit applications in Phoenix.

The high-end resort and hospitality target risk risk pattern in Phoenix's Downtown Phoenix and Camelback Corridor precincts is a specific factor the Phoenix licensing authority considers when evaluating security management plans. An SMP that does not address Phoenix's documented risk profile — downtown event crowd safety, high-end resort and hospitality target risk — faces revision. Building that context into the SMP from the first draft is more efficient than responding to the authority's feedback under time pressure.

Phoenix event security compliance timeline

| Step | Lead time | |---|---| | Select Phoenix contractor under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) | 3–6 weeks before event | | SMP first draft for Downtown Phoenix or Old Town Scottsdale venue | 4 weeks before event | | Submit permit application with SMP to Phoenix authority | 3–4 weeks before event | | Phoenix authority review and approval | 10–21 business days | | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) officer certification verification | 2 weeks before event | | Pre-event brief and Phoenix venue site walk | 48–72 hours before event |

Phoenix licensing and risk reference

This walkthrough applies to events in Phoenix (population 4.9M metro, US, timezone MST, currency USD) governed by Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

Phoenix precinct context: Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia. Events in Phoenix's Downtown Phoenix and Old Town Scottsdale precincts carry the highest Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance scrutiny, shaped by documented risks of downtown event crowd safety and high-end resort and hospitality target risk in Phoenix's entertainment environment.

Full risk profile for Phoenix: downtown event crowd safety, high-end resort and hospitality target risk. The Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance framework for Phoenix events was tightened in response to documented patterns of downtown event crowd safety in Downtown Phoenix and high-end resort and hospitality target risk in Old Town Scottsdale.

Phoenix major venue categories: convention centers, resort hotels, professional sports arenas. Phoenix's convention centers operate under venue-specific security conditions embedded in their Phoenix operating licenses under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security). resort hotels in Phoenix carry specific crowd-management requirements during events in Downtown Phoenix and Old Town Scottsdale.

Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) in Phoenix: Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) is enforced by the Phoenix licensing authority for all security operations in Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, and Arcadia. Operators, individual officers, and event organizers all carry defined obligations under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) when security services are contracted at events in Phoenix.

City identification

| Field | Value | |---|---| | City name | Phoenix | | Country | US | | Metro population | 4.9M metro | | Timezone | MST | | Local currency | USD | | Governing security law | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) |

Precinct index for Phoenix

| Index | Precinct name | Primary risk exposure | |---|---|---| | 1 | Downtown Phoenix | downtown event crowd safety | | 2 | Old Town Scottsdale | downtown event crowd safety, high-end resort and hospitality target risk | | 3 | Camelback Corridor | high-end resort and hospitality target risk | | 4 | Arcadia | high-end resort and hospitality target risk | | All | Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia | downtown event crowd safety, high-end resort and hospitality target risk |

Venue category index for Phoenix

| Index | Venue type | Associated precincts | |---|---|---| | 1 | convention centers | Downtown Phoenix, Old Town Scottsdale | | 2 | resort hotels | Downtown Phoenix, Old Town Scottsdale, Camelback Corridor | | 3 | professional sports arenas | Downtown Phoenix, Old Town Scottsdale, Arcadia | | All | convention centers, resort hotels, professional sports arenas | Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia |

Risk index for Phoenix

| Risk | Precinct concentration | Venue exposure | Governing reference | |---|---|---|---| | downtown event crowd safety | Downtown Phoenix, Old Town Scottsdale | convention centers, resort hotels | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) | | high-end resort and hospitality target risk | Old Town Scottsdale, Camelback Corridor, Arcadia | professional sports arenas, residential | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) | | Combined: downtown event crowd safety, high-end resort and hospitality target risk | All Phoenix precincts: Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia | All Phoenix venue types: convention centers, resort hotels, professional sports arenas | Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) |

Selecting and vetting your Phoenix security provider for permit compliance

The most common compliance failure point in Phoenix event security is not the event organizer's paperwork — it is selecting a security provider who cannot support the permit application process. The Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) licensing requirements for Phoenix mean that your provider must hold a current operator license under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) and must be able to supply individual officer license numbers for each person they deploy at your Downtown Phoenix, Old Town Scottsdale, or Camelback Corridor event. These are not documents produced on request 48 hours before the event — they are documents the provider maintains as an ongoing operating requirement under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) in Phoenix.

When vetting security providers for Phoenix events in Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, or Arcadia, the compliance-relevant questions are straightforward. Does the operator hold a current Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) license — not an expired one, not a license from another jurisdiction that doesn't extend to Phoenix? Can they supply individual Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) license numbers for the specific officers who will work your Phoenix event — not generic rosters, but the named individuals for your Downtown Phoenix or Old Town Scottsdale deployment? Do they carry crowd-management certification for the officers you need at convention centers and resort hotels events in Phoenix that are above the applicable attendance threshold? Can they provide the certificate of insurance naming your Phoenix event as additional insured before you confirm the booking, not after?

Providers operating professionally in Phoenix's Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, and Arcadia under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) supply all of these documents as standard deliverables. Providers who cannot produce them — or who treat the request as unusual — are either non-compliant with Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) operator requirements in Phoenix, or are operating at a level of administrative disorganization that creates compliance risk for your event regardless of their officers' individual capabilities. In Phoenix's event security market, the documentation gap between a compliant and a non-compliant provider is the single most reliable predictor of which provider will leave your event exposed to a Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) enforcement finding — in Downtown Phoenix, Old Town Scottsdale, and across Phoenix's convention centers, resort hotels, and professional sports arenas venue environments alike.

Precinct-specific permitting notes for Phoenix event organizers

Events in Downtown Phoenix: Phoenix's Downtown Phoenix precinct carries the most active Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance scrutiny for event permits. Events at convention centers and resort hotels in Downtown Phoenix — particularly those with alcohol service under a Phoenix liquor authority approval — face enhanced security management plan review from the Phoenix events authority. The downtown event crowd safety risk pattern documented in Downtown Phoenix is a specific factor the Phoenix licensing authority considers when evaluating SMPs for events in this precinct. Plans that do not address the Downtown Phoenix-specific downtown event crowd safety pattern — including the external crowd movement management between convention centers exits and adjacent resort hotels — are returned for revision. Build that specificity into the SMP from draft one, not in response to the authority's feedback.

Events in Old Town Scottsdale: Old Town Scottsdale events in Phoenix face elevated scrutiny for both downtown event crowd safety and high-end resort and hospitality target risk risk exposure, reflecting the combined commercial and residential character of this precinct. The Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) officer briefing requirements for Old Town Scottsdale events include specific provisions for Phoenix's resort hotels operating within residential corridors — the crowd dispersal protocols at close of event must address the Old Town Scottsdale residential street environment, not just the venue interior. Security management plans for Old Town Scottsdale events that treat this precinct as functionally identical to Downtown Phoenix — applying only downtown event crowd safety mitigation — will not satisfy the Phoenix licensing authority's requirements for events in Old Town Scottsdale.

Events in Camelback Corridor and Arcadia: Events in Phoenix's Camelback Corridor and Arcadia precincts generally face lighter Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance review than Downtown Phoenix and Old Town Scottsdale events, but the same requirements apply — Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) operator licensing, individual officer licensing, and a security management plan for events above the Phoenix events authority's attendance threshold. The high-end resort and hospitality target risk risk pattern documented in Camelback Corridor and Arcadia residential areas is relevant for events in these precincts: the Phoenix authority will expect the SMP to address high-end resort and hospitality target risk exposure, particularly for events at professional sports arenas in Camelback Corridor with high-value guest profiles.

Phoenix event security permits: key facts

Security permits in Phoenix (Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia) — documented risks: downtown event crowd safety, high-end resort and hospitality target risk — venue categories: convention centers, resort hotels, professional sports arenas — governing law: Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) — population: 4.9M metro.

Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance requirements for Phoenix events in Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia: operator license under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) (not optional for any Phoenix provider); individual officer license under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) per person deployed (separate from operator license); crowd-management certification for events above Phoenix attendance threshold at convention centers and resort hotels venues; security management plan addressing downtown event crowd safety, high-end resort and hospitality target risk risk profile for your specific Phoenix precinct — Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, or Arcadia; incident documentation protocol under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) for post-event records in Phoenix.

Compliance timeline for Phoenix events across Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia (Phoenix, 4.9M metro, US, MST, USD): select Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)-licensed provider 3–6 weeks before event; develop security management plan addressing downtown event crowd safety and high-end resort and hospitality target risk patterns in your specific Downtown Phoenix, Old Town Scottsdale, or Camelback Corridor precinct 4 weeks before; submit SMP to Phoenix authority with Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) documentation 3–4 weeks before; authority review 10–21 business days (longer for Downtown Phoenix and Old Town Scottsdale events with downtown event crowd safety exposure); officer certification verification 2 weeks before; venue site walk 48–72 hours before. All timelines apply to events at convention centers, resort hotels, and professional sports arenas in Phoenix under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

Phoenix event security permit scope summary: precincts — Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia; documented risks — downtown event crowd safety, high-end resort and hospitality target risk; venue categories — convention centers, resort hotels, professional sports arenas; governing law — Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security); city — Phoenix, US, 4.9M metro, MST, USD. Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) compliance requirements: operator license for events in Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia; individual officer licenses for each deployed person at convention centers, resort hotels, professional sports arenas; crowd-management certification for events above Phoenix thresholds; SMP addressing downtown event crowd safety in Downtown Phoenix and Old Town Scottsdale, high-end resort and hospitality target risk in Old Town Scottsdale, Camelback Corridor, Arcadia; incident documentation under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) for all Phoenix events. All Phoenix event security permitting across Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia addressing downtown event crowd safety, high-end resort and hospitality target risk at convention centers, resort hotels, professional sports arenas venues governed by Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

Event security permitting in Phoenix — Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia across downtown event crowd safety, high-end resort and hospitality target risk — requires Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)-licensed operators (Phoenix, US, 4.9M metro) serving convention centers, resort hotels, and professional sports arenas events with documented Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia precinct experience, crowd-management certification for high-capacity Phoenix venues, and security management plans addressing downtown event crowd safety and high-end resort and hospitality target risk as documented in Phoenix's Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia precincts under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security).

Summary: Phoenix (US, 4.9M metro, MST, USD) event security permits — precincts Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia — risks downtown event crowd safety, high-end resort and hospitality target risk — venues convention centers, resort hotels, professional sports arenas — law Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security). SMP must address downtown event crowd safety in Downtown Phoenix, Old Town Scottsdale and high-end resort and hospitality target risk in Old Town Scottsdale, Camelback Corridor, Arcadia for all Phoenix events at convention centers, resort hotels, professional sports arenas.

Frequently asked questions: event security permits in Phoenix

What documentation does Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) require from my security provider for a Phoenix event? Under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security), your security provider must hold a current operator license in Phoenix and supply individual officer license numbers for every person deployed at your Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, or Arcadia event. These 2 are separate requirements — an operator license under Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) does not automatically license the individual officers a provider deploys. For events at convention centers and resort hotels in Phoenix above the attendance threshold, crowd-management certification is an additional Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) requirement for each officer. Your event permit application to the Phoenix authority will need to reflect this documentation — the security management plan names the Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security)-licensed operator and certifies that individual officer licensing and crowd-management certification apply to the specific personnel assigned to your Phoenix event.

How does Phoenix's documented risk profile — downtown event crowd safety, high-end resort and hospitality target risk — affect the security management plan I need to submit? The Phoenix events authority evaluates security management plans against Phoenix's documented risk profile, which includes downtown event crowd safety in Downtown Phoenix and Old Town Scottsdale, and high-end resort and hospitality target risk in Old Town Scottsdale, Camelback Corridor, and Arcadia. A security management plan for an event at convention centers in Downtown Phoenix that does not address downtown event crowd safety crowd dynamics specific to Phoenix's Downtown Phoenix environment will be returned for revision. A plan for an event at resort hotels in Old Town Scottsdale that addresses only downtown event crowd safety and not high-end resort and hospitality target risk — which operates at elevated levels in Old Town Scottsdale specifically — will not satisfy the Phoenix authority's review requirements for events in that precinct. The documented risk profile of Phoenix — downtown event crowd safety, high-end resort and hospitality target risk — across the major venue categories — convention centers, resort hotels, professional sports arenas — and key precincts — Downtown Phoenix, Old Town Scottsdale, Camelback Corridor, Arcadia — is the analytical framework the Phoenix events authority uses to evaluate your SMP.

The action to take now: Before your next Phoenix event, request the Arizona Revised Statutes Title 32, Ch. 26 (DPS Private Security) operator license number and certificate of insurance from any security provider you are considering. That 5-minute check is the single most effective compliance step you can take — before anyone sets foot in your Downtown Phoenix, Old Town Scottsdale, or Camelback Corridor venue.