Event security plan: what to agree before doors open

An event security plan should say who is responsible for security, what each team is expected to do, how access and incidents will be managed, and who can make decisions when conditions change. Build it with your venue and a suitably qualified security provider, then test the handoffs before you let ticket holders in.

A quote for "security staff" doesn't settle those questions. Neither does a venue saying it has security covered. You need to know whether that includes the queue outside, an entry dispute, a contractor arriving late, support for someone reporting harassment, and the period after the performance finishes.

This guide helps you turn those conversations into a written brief and opening-day agreement. The staffing and procedures must fit your event, venue and local requirements. The practical goal is simple: when something happens, the people on shift know their job and who to contact.

Start with the event you're actually running

Give your venue and security provider an accurate event brief before asking them to recommend coverage. Include the event format, audience, operating hours, expected arrival pattern, alcohol service, public and restricted areas, and any activities that change how people move around.

Include setup and pack-down as well as the advertised show. Contractors may be working before ticket staff arrive, and equipment may remain after the audience leaves. Say which periods are within the security provider's contract and who takes responsibility when that contract ends.

Start from the current site plan and event risk assessment. The assessment identifies hazards and the controls you need. Your security plan turns the relevant controls into assigned duties, working arrangements and decisions. It shouldn't become a second document with a different description of the same venue.

Ask the provider what information is missing. If the recommendation depends on assumptions about capacity, entrances or the event format, write those assumptions down. Changing the layout or adding an after-party should trigger a review of the arrangements that depended on the original brief.

In Great Britain, HSE's guidance on event safety responsibilities makes clear that allocating crowd-safety work to contractors does not remove the organiser's overall responsibility. Treat the contract as an agreement about delivery, with named people coordinating the work.

Name the people who can make decisions

The plan needs actual names, shift coverage and deputies. A box labelled "management" isn't much use when three organisations are on site and each thinks someone else is in charge.

Agree the event lead, venue duty manager and security supervisor. Add the medical lead and other specialist leads relevant to your operation. Define how they work together and what decisions sit with each role. Medical decisions, for example, should reach the appropriate medical professional rather than become a debate at the ticket desk.

Record who can authorise a pause in admissions, a change to a public route, a show stop and a restart. Match that authority to the venue's established procedures and any applicable conditions. Identify who speaks with emergency services and how responsibility passes to them when required.

Make the deputy arrangement real. If the event lead is unavailable, everyone should know who takes the call. That person needs the information and authority to act, not just a place on the contact list.

For urgent danger, your reporting arrangements must not make staff wait for internal permission to call emergency services. Brief them on immediate actions within their training and the local emergency contact process. Internal coordination should support a response, never become a queue of approvals.

Write the security provider's brief around duties

Ask for a plan explaining what the proposed team will do throughout the event. A headcount without duties leaves you unable to judge whether the quote covers the work.

Your brief should ask the provider to confirm:

• The duties covered, including entry, audience areas, restricted access and departure where relevant.

• The supervision structure and the person who will brief the team.

• The qualifications, experience and licences required for the assigned work.

• The shifts, breaks and relief arrangements that keep agreed duties covered.

• Equipment supplied by the provider and equipment expected from you or the venue.

• How absences, late replacements and changes to the event will be handled.

• The incident records and end-of-shift handover you will receive.

Don't choose staffing by copying a ratio from another event. Ask the provider to explain the recommendation against your site, duties, audience, programme and risk assessment. The useful question is whether the agreed functions can be delivered throughout the operating period, including breaks and simultaneous demands.

In the UK, the SIA's event-staff licensing guidance distinguishes ticket checking and wayfinding from licensable security activities. The duties, premises and employment arrangement affect the requirement. Don't assume calling someone a steward makes every task you give them unlicensed work. Check the actual role with the provider and verify required licences through the appropriate authority.

Give entry staff a clear boundary. They can resolve a booking question within their role; they shouldn't be left to improvise a security intervention. The security supervisor should know where those referrals come from and who continues serving the rest of the queue.

Turn a vague duty into a usable instruction

Take the phrase "cover the entrance". It leaves too much unsaid. A useful duty record names the role, operating period, task, reporting line and limits. Complete it with your provider rather than handing over wording that hasn't been agreed.

For example, a hypothetical ticket-support record could say: "The ticketing lead handles booking enquiries during the public admission period, using the event's approved ticketing process. Security concerns go to the security supervisor. The venue duty manager receives reports about the effect on queue conditions. The named relief person takes over during breaks. The lead records unresolved booking issues before handing over."

That's a ticketing responsibility, not a security deployment recommendation. The provider writes the corresponding instructions for its team, including the duties they are trained and authorised to perform. Read the two together. If both records say the other team is responsible for the same problem, resolve it before signing off the brief.

Agree access zones and who may use them

Use the same zone names on the plan, staff briefing and signs. "Backstage" can mean something different to a performer, a caterer and a venue manager. If the wording changes between teams, access decisions become arguments.

Describe the areas people may enter and the approval needed. Public areas, production workspaces, performer facilities and supplier areas may need different arrangements. Define the distinction without circulating sensitive operational detail more widely than necessary.

For each restricted area, record the responsible team, who grants access, how authorisation is checked and where a person goes if their permission is unclear. Include temporary access for deliveries or a replacement worker. A familiar face shouldn't force a junior staff member to choose between politeness and the agreed process.

Keep emergency escape separate from normal access restrictions. Access controls must be reviewed with the venue and relevant safety specialists so they don't obstruct emergency use. A rule about who may enter a workspace is not a reason to compromise an escape route.

The staff version of the plan can contain the operational detail people need for their duties. The public version should contain clear arrival information, entry conditions and help points. Your customer-facing event page doesn't need your staffing positions, internal contact list or response arrangements.

Connect ticket checking with the entry plan

Entry involves several jobs. Checking a ticket, resolving a booking problem, applying an entry policy and managing the queue need to work together, even when different teams do them.

Agree where the ticketing team handles exceptions so a missing confirmation or disputed booking doesn't stop every arriving buyer. Tell staff who can look up an order, who can correct a ticketing mistake and who receives a security-related concern. Keep personal booking information away from unnecessary public discussion.

Loopyah's ticketing and check-in tools let door staff scan QR tickets from their phones with check-in access. Use those permissions for the job they support. A ticket scan doesn't assess crowd conditions or replace the venue's agreed occupancy and emergency procedures.

Confirm how the venue and event team will monitor the number of people present, including the effect of staff, contractors, re-entry and departures. A total of tickets sold is not a live occupancy count. Ask who supplies the operational count, who reviews it and what happens if the information becomes unreliable.

HSE's crowd-control guidance, written for Great Britain, covers arrival, movement inside the venue and departure. It specifically warns that security searches must not create an overcrowding risk. Review the entry process as a whole with the venue and provider, rather than judging each desk or check in isolation.

Publish relevant entry conditions before people travel. Make sure ticket support and security use the same current policy, including the route for access-related exceptions. An attendee shouldn't get one answer by email and a contradictory answer at the door.

Make communication usable during the event

Agree how staff contact the right person in normal operation and during an incident. List the communication method for each role, the backup method and the person responsible for maintaining the contact sheet.

Use plain location names that match the site plan. "Something's happening over there" forces the recipient to ask questions before they can send help. Practise a short report that gives the location, what has been observed, whether anyone needs urgent assistance and who is reporting it.

Test communication equipment where staff will use it, under realistic conditions where possible. Confirm that the security supervisor can reach the venue duty manager and that relevant instructions reach staff working away from the main event area. Agree the fallback for a failed device or unavailable network.

Decide who can make public announcements and how they get authorised information. Prepare wording for foreseeable operational situations with the venue, then confirm how it will be delivered. Staff should know the approved message, not try to interpret competing rumours from several group chats.

Keep sensitive personal details out of general channels unless the response requires them. An incident log, medical record and casual team message serve different purposes. Agree who records information and who is allowed to receive it.

Plan escalation without making everyone a responder

Write down the route for routine issues, urgent concerns and emergencies. The distinction should help staff find the right support quickly, while the actual response follows the venue's procedures and the relevant specialists' training.

A ticketing complaint might go to the ticketing lead. A harassment report needs the agreed welfare or security route. A person requiring urgent medical help needs medical assistance and, where necessary, emergency services. Don't make the first staff member decide everything before they are allowed to ask for help.

Give staff simple reporting responsibilities: recognise that help is needed, communicate what they've observed, take immediate actions within their training and follow instructions from the appropriate lead. They should not investigate a threat or undertake a physical intervention they are neither trained nor authorised to perform.

HSE's incident and emergency planning guidance addresses emergency roles, coordination with responders and show-stop arrangements. For events in Great Britain, use it alongside the venue's plans and appropriate local consultation. Agree who can initiate a show stop, how production receives the instruction and who must be consulted before restarting.

After an incident, record the time, location, observed facts, action taken and person receiving the handover. Keep opinions distinct from observations. Restrict access to the record and agree the applicable retention and reporting arrangements with the responsible organisation. The purpose is to support response and follow-up, not to create a story for the team chat.

Include accessible help and emergency communication

Someone who cannot hear an announcement or use the planned route still needs usable information and assistance. Review those arrangements with the venue before deciding the security plan is complete.

Discuss how people ask for help, how staff identify the appropriate support and how accessible routes remain usable during the event. Don't assume an attendee will have a companion who can interpret instructions or provide physical assistance. Ask about the support they need and involve staff trained for the agreed task.

In the United States, the Department of Justice's ADA effective communication guidance explains the obligations of covered public bodies and public-facing businesses. The appropriate aid or service depends on the communication and the person's needs. Build those arrangements into your briefing rather than leaving them to whoever happens to answer the question.

Our event accessibility checklist covers the wider attendee journey. For the security brief, concentrate on the handoffs: who receives an access request, who checks the venue arrangement and who communicates a confirmed answer. Private information should reach the people who need it to deliver support.

Treat opening, shift changes and closing as decisions

Before doors open, bring the relevant leads together and confirm that the agreed arrangements are in place. Record unresolved issues, the person fixing each one and whether the issue prevents opening. A start time printed on a ticket doesn't remove the need to resolve a critical gap.

Your opening review should cover the venue's readiness checks, the agreed staff and equipment, communication tests, access and entry arrangements, and the availability of the specialist support included in the plan. Ask each lead to confirm their part rather than accepting a general "all good" from someone who hasn't checked it.

For a shift handover, use a short written record alongside the conversation:

• Outgoing and incoming supervisor names and handover time.

• Current operating conditions and any change to the original plan.

• Unresolved incidents, support requests and actions still assigned.

• Coverage, equipment or communication issues needing attention.

• The next scheduled activity likely to affect duties.

• Confirmation that the incoming person has accepted the handover.

Don't end coverage simply because the stage programme has finished. Agree the responsibilities for audience departure, remaining guests, supplier access and the transfer back to venue management. Define the condition for standing the team down and who gives that instruction.

Put the agreement into a document people can use

Keep a current working version with an owner, issue date and revision number. Changes should reach everyone affected. A beautifully formatted plan is useless if the security supervisor is working from yesterday's entrance layout.

Use this document structure as the agenda for your final planning meeting:

1. Event and scope. The operating periods, areas, activities and assumptions covered by this plan.

2. Responsibilities. The named leads, deputies, decision authority and contact arrangements.

3. Provider duties. The agreed services, staff competence, supervision, coverage and equipment.

4. Access and entry. The zone permissions, public entry process, ticketing handoffs and occupancy responsibilities.

5. Communication and escalation. The reporting routes, backup methods and connection to the venue's emergency procedures.

6. Readiness and handover. The opening review, shift transfers, close-down decision and records required.

Keep detailed site-specific emergency procedures and sensitive material in controlled attachments where appropriate. Give staff the parts they need to carry out their role. They should know where the full current plan is held and whom to ask if their instructions conflict.

Ask the provider to confirm the final deliverables in writing: the agreed duty schedule, named supervisor, evidence of required credentials, briefing arrangements, equipment responsibilities and handover records. Agree how changes affect cost before the event. This lets you compare quotes on the service being supplied and avoids discovering a necessary duty was excluded.

Walk through a realistic handoff before event day

Use a short discussion exercise with the venue, security supervisor, ticketing lead and other relevant staff. Pick an ordinary problem that crosses team boundaries, then follow it until responsibility is clear.

For example, imagine a hypothetical paid evening show where the ticket support device stops working as arrivals increase. Ask who identifies the problem, who takes responsibility for the booking enquiries, who monitors the effect on the queue and who can decide to pause admission if conditions require it. Don't invent a technical workaround on the spot. Confirm the supported contingency and the limits within which it may be used.

Then ask what happens if the usual lead is unavailable or the next shift arrives halfway through the problem. The incoming supervisor should receive the facts, decisions already made and outstanding actions. If the answer depends on "someone will tell them", improve the handover before the event.

Record the gap, give it an owner and confirm the fix. Repeat the affected part of the exercise when the fix changes how another team works. A rehearsal that produces an action nobody completes hasn't resolved the problem.

Review delivery before you repeat the booking

After the event, compare what you agreed with what happened. Ask the venue and security supervisor about staffing changes, handover problems, unclear instructions and duties that took more time than expected. Include the ticketing team's experience of referrals and entry support.

Separate a change to the plan from a failure to deliver it. Extra work requested during the evening should have a clear record of who authorised it. Missing agreed coverage needs an explanation and a corrective action. Looking only at the final invoice won't tell you which occurred.

Choose specific improvements for the next event. If ticket staff didn't know where to refer an incident, update the briefing and test that handoff. If a late programme change extended the operating period, put the revised hours into the next brief and quote. Don't carry an exception forward as an unspoken expectation.

Keep the approved plan and relevant delivery records through the retention process agreed by the responsible organisations. Restrict personal information to those who need it. Then start the next event from the lessons learned, while checking the new venue, audience and programme afresh.

Your event security plan is ready when the venue, provider and event team agree on the duties, decision authority and handoffs, and the people on shift can use them. Get that agreement before doors open, keep it current as conditions change, and review what actually happened before you book the next event.