Skip to main content
← Fix the Laws

Event Security Standards

Overview​

This page sketches a policy concept that recurs throughout the research corpus: a framework for public-event security standards applicable to political speakers, candidates, and other high-profile public figures whose schedules expose them to elevated risk. It is not legal advice, and it does not assume that any specific organization, venue, or contractor acted improperly at the Charlie Kirk event at Utah Valley University or at any other event. It summarizes ideas from commentators who believe that consistent, published standards would both improve safety and enable after-action accountability.

The basic goal is to explore how a standards framework might:

  • Define baseline security expectations for covered events.
  • Require transparent contracting and vetting of security personnel and subcontractors.
  • Create clear after-action review procedures so that lessons from any incident can be learned and applied.

Problems this proposal is trying to address (as described)​

Commentators in the research corpus argue that public-event security is currently uneven and opaque:

  • No published baseline — Event organizers, venues, and contractors operate under varied internal standards, making it difficult for the public or researchers to evaluate whether a given event's security was adequate.
  • Opaque contracting — Layered subcontracting can make it hard to determine who was actually on post, under whose supervision, and with what training.
  • Inconsistent coordination with local law enforcement — Coordination practices vary widely across jurisdictions, and the handoff between private security and local police is a recurring point of concern.
  • Limited after-action transparency — When something goes wrong, the relevant reviews are often internal to the contracting organization, with no public component.
  • Drone and electronic threats — Commentators note that the threat picture has expanded to include small drones and electronic disruption, and that standards have not kept pace.

These themes are presented here as concerns and claims, not as adjudicated findings about any specific event or contractor.

Core ideas for an event-security standards framework​

Commentators sketch various possible reforms, which can be grouped into themes:

1. Published baseline standards​

A statute or regulation could establish tiered baseline standards for covered events, with the tier determined by factors such as:

  • Expected attendance.
  • Public profile of the principal speaker.
  • Known or foreseeable threat information.
  • Venue characteristics (indoor, outdoor, open perimeter).

Each tier could specify minimum expectations for venue assessment, perimeter protection, access control, sightline management, and coordination with local law enforcement. Organizers could be free to exceed these expectations; they would simply be required to meet them.

2. Transparent contracting​

To make after-action review meaningful, the framework could require:

  • A written chain-of-command document identifying every security entity involved, from the prime contractor through every subcontractor, along with the employees assigned to each post.
  • Standardized credentialing so that personnel roles are identifiable during and after an event.
  • Public registration of the prime security contractor for covered events, so that researchers and journalists can connect events to their security providers.

3. Personnel vetting and training standards​

A statute could establish baseline vetting expectations for personnel at covered events:

  • Criminal-background checks within a defined lookback period.
  • Documentation of relevant training (executive protection, de-escalation, medical).
  • Disclosure of any prior adverse employment actions in security roles.
  • Restrictions on assigning personnel with recent, unresolved ethics or criminal matters to principal-protection posts.

Subcontractor personnel could be subject to the same standards, with the prime contractor responsible for verification.

4. Coordination with local law enforcement​

Pre-event coordination with local law enforcement could be formalized by requiring:

  • A written operations plan shared in advance with the senior responsible law-enforcement official for the venue.
  • Designated liaison roles on each side, with clear communication procedures.
  • Standardized handoff protocols for incidents escalating from private security response to law-enforcement response.
  • Post-event debrief between the two organizations to identify coordination gaps.

5. Counter-drone and counter-electronic planning​

Given the expanding threat surface, the framework could require covered events above a threshold tier to have:

  • A drone-detection capability or explicit coordination with a local partner that has one.
  • Documented procedures for responding to detected drone activity, including rules on when to alert the principal's protection detail.
  • A radio-frequency (RF) environment assessment for outdoor events in jurisdictions where this is feasible.
  • Awareness of any ongoing local counter-UAS testing or exercises that could affect the event.

6. Medical response standards​

Commentators note that medical response time is often decisive in shooting incidents. The framework could specify:

  • Minimum on-site medical personnel based on event size.
  • Pre-identified transport routes and receiving facilities.
  • Communication protocols with EMS, including call codes and pre-arranged escalation.
  • Requirements for trauma kits at defined staffing ratios.

7. Digital-evidence preservation and handling​

In the event of an incident, the standards could require:

  • Immediate preservation of all security-camera footage, access-control logs, and radio traffic recordings.
  • Prohibition on destruction or overwriting during a defined post-incident window.
  • A documented chain of custody for digital evidence transferred to law enforcement.
  • Prompt notification to local and, where applicable, federal authorities in response to covered incidents.

See Digital Evidence Preservation for a fuller discussion.

8. After-action review​

Any covered incident involving death or serious injury could trigger a required after-action review with three components:

  • An internal review by the organizing entity and its prime security contractor.
  • An external review commissioned from a qualified, independent professional.
  • A public summary, with sensitive operational details redacted, covering what worked, what failed, and what should change.

The statute should protect good-faith participants in these reviews from retaliation.

9. Reporting and data collection​

A statutory reporting requirement could create a public dataset of covered incidents, with standardized fields, enabling researchers and journalists to study trends. Sensitive personal details would be redacted, but the aggregate record of incidents, responses, and outcomes would be accessible.

10. Insurance and liability clarity​

Commentators note that liability exposure drives many operational choices. A statutory framework could clarify expectations around insurance coverage, liability limitations for compliant actors, and exposure for non-compliant actors, so that responsible providers are not disadvantaged.

Safeguards and limits​

Several safeguards are central to any event-security standards approach:

  • Proportionality — Smaller community events should not be burdened with the same standards as major venues hosting national figures.
  • Speech protection — Security standards should not function as a tool to discourage controversial speakers from appearing; they should set safety baselines, not content-based burdens.
  • Cost and access — Standards should be achievable so that smaller organizations can host speakers without requiring a disproportionate financial investment.
  • Privacy of attendees — Credentialing and access-control requirements should respect attendees' privacy to the extent consistent with safety.
  • Avoidance of liability traps — Standards should be defined clearly enough that good-faith compliance is achievable, and after-action review should distinguish between bad outcomes and negligent conduct.

These safeguards are at least as important as the standards themselves.

How this connects to other pages​

This plan ties into other reform-oriented topics:

  • Law 1 and Law 2 — disclosure regimes that would make post-incident records reviewable.
  • Digital Evidence Preservation — standards for handling event footage and logs.
  • TSUSA — complementary organizational governance reforms.
  • Fix Overview — broader summaries of reform themes from the research corpus.

As with all pages in this section, the purpose here is to organize ideas and claims that have been raised — not to assert that any named individual, agency, or organization acted unlawfully.