Security for Festivals: A 2026 Guide for London

You're three weeks from final sign-off, the site plan is still changing, and someone has just asked whether security can be “sorted later”. That's the moment most festival problems start. In London, security for festivals isn't a guard-order you place when the posters go up, it's a working system that starts months before gates open and keeps running through the last bin emptying, the final sweep, and the handover to the night team.

The right way to run it is boring in the best possible sense. Assess the footprint, map the risks, build the staffing model, lock the gate process, connect CCTV and radio cover, then document everything for licensing, the safety advisory group, and the post-event review. Treating it as one integrated FM contract, with reception, CCTV, cleaning, and event cover under one accountable lead, changes the whole shape of the operation. You get one chain of evidence, one reporting line, and one team that knows the site instead of a patchwork of contractors who only meet on show day.

Table of Contents

• Why Festival Security Needs a Head Start - Start with the footprint, not the guard count - Work backwards from the approvals pack

• Staffing Models and Role Allocation - Map the job to the ground - Keep the control measures human, not theoretical

• Access Control, Accreditation and Search Screening - Treat accreditation and screening as one system - What good looks like at the barrier

• Crowd Management and On-Site Operations - Design the route, then manage the behaviour - Use visible help, not just visible enforcement

• CCTV, Body-Worn Cameras and Real-Time Monitoring - Build the situational awareness stack - Ask for the reporting, not just the cameras

• Police Liaison, Licensing and Governance - Make the contract match the governance - Tie the technology to the evidence trail

• Post-Event Reporting and Continuous Improvement - Build a report that people can act on - Use the report to decide the next contract

Why Festival Security Needs a Head Start

The first mistake I see is the late realisation that the security plan should already have been in motion. A London festival doesn't give you the luxury of improvisation, because the site is tight, the neighbours are watching, the licence conditions are specific, and the police want to know who owns each part of the risk. If the plan only starts when the build begins, you're already behind on the things that usually fail, access control, crowd movement, emergency routes, and the chain of command.

Start with the footprint, not the guard count

London's A Practitioners Toolkit for Major Events in Cities points the process in the right direction, begin with a threat and vulnerability assessment, then build a layered protective security plan, then write the security operations plan that covers emergency response and crisis management London's Practitioners Toolkit for Major Events in Cities. That sequence matters because the physical footprint decides the plan, not the other way around. If you don't know where pinch points form, where the welfare tent sits, or which route the ambulance will use at peak density, the staffing number is just a guess.

The useful habit is to walk the site at different times of day, once in daylight, once at dusk, and once when the build is noisy and awkward. That's when you spot the weak links, the side gate that invites tailgating, the dead corner near a container stack, the queue line that blocks a fire path, or the entrance that looks fine on paper but collapses under a bag-search queue. I've seen more trouble caused by a badly placed barrier than by a lack of bodies.

Practical rule: if the route to welfare, medics, or the emergency exit isn't obvious to a stressed steward at 2 a.m., it isn't good enough.

Work backwards from the approvals pack

The organiser should be able to hand the safety advisory group a tidy pack before the event opens. At minimum that means the risk assessment, the layered security concept, the operations plan, evacuation and crisis procedures, the communication tree, and evidence that the personnel are trained and vetted. The point isn't paperwork for its own sake. It's to prove that someone has thought through how the festival will operate when the weather turns, the queue grows, or a refusal at the gate becomes a confrontation.

Festival organisers should also be preparing for Martyn’s Law. The Terrorism (Protection of Premises) Act 2025 is expected to come into force in spring 2027, and qualifying events can include public events where 800 or more people are expected at the same time and entry is subject to a condition such as a ticket or pass. Although the duties are not yet in force, the Home Office has published statutory guidance so organisers can prepare their public-protection procedures and security measures now.

The single accountable contract matters in an integrated FM model, where the same lead can manage security, reception, CCTV, cleaning, and incident logging across the site. That means one version of the truth, one escalation path, and one team who can tell the difference between a cleaning issue, a welfare issue, and a security issue without sending three different contractors to the same place.

The artefacts worth having ready before gates open are simple:

• Threat and vulnerability assessment for the event footprint.

• Security operations plan with emergency and crisis actions.

• Site map showing entrances, exits, welfare points, restricted areas, and emergency routes.

• Briefing schedule for supervisors, stewards, and control room staff.

• Communication tree covering police, medics, licensing, and venue management.

• Incident logging format for refusal, search, patrol, and welfare events.

For larger festivals, planning may need to begin many months in advance. The appropriate lead time will depend on the event's scale, licensing requirements, site complexity and the level of consultation required with the local authority, emergency services and Safety Advisory Group. Late decisions can create problems with access control, crowd flow and escalation procedures once the event is live.

Staffing Models and Role Allocation

There is no universal security guard-to-attendee ratio that works for every festival.

Staffing levels should be based on the size, layout, audience profile, activities and specific risks of the event.

A flat open field, a multi-stage site, and a dense urban venue each need different cover because the risk sits in different places. The core question is whether the layout lets staff do specific jobs without blurring into each other.

A gate marshal who is also expected to patrol the perimeter, support welfare, and watch the backstage line will miss things. That is how small issues turn into crowd pressure, unauthorised access, and slow response times.

Map the job to the ground

The best teams know exactly where they belong. Entrance screening is not roaming patrol, perimeter control is not welfare, and backstage cover is not a substitute for front-of-house visibility. When one team is asked to absorb every incident type, people stop spotting problems early and start reacting too late.

An illustrative role-allocation matrix might look like this; give each task a supervisor who reports into the event lead. If the site has multiple entrances, a baggage-check area, a backstage zone, and a welfare point, the headcount has to move with those pressure points rather than stay fixed on a spreadsheet. That is why a good supplier asks for the site plan before naming numbers.

Here is a simple staffing matrix that shows the principle.

Role	Headcount (Day)	Headcount (Evening)	Primary location	Reporting line
Gate screening	4	6	Main entrance and ticket lanes	Gate supervisor
Roaming patrol	2	3	Public areas and blind spots	Security manager
Perimeter control	2	2	Fence line and service access	Perimeter supervisor
Backstage cover	1	2	Production and restricted areas	Event security lead
Welfare support	1	2	Welfare tent and help point	Welfare liaison
Dispersal support	2	3	Exit routes and taxi rank	Late-shift supervisor
Control room cover	1	1	Security control point	Security manager

These figures are illustrative only and should not be treated as recommended staffing levels. Actual staffing must be determined by the event's risk assessment, site layout, capacity, activities and operating requirements.

Keep the control measures human, not theoretical

Control is discipline. Tabletop exercises, site walkthroughs, and pre- and post-shift briefings catch the failure points before the crowd does. That is the moment to confirm who handles refusal of entry, who calls the show-stop trigger, and who takes over if a supervisor is pulled into a welfare incident.

A lot of operators also miss the value of a consistent team. Solomon's Facilities Management is one London option that combines event security with other FM functions, so the same contract can cover guard deployment, access control, reception, CCTV, cleaning, and the support functions around it. That matters because event security companies like this can reduce the handoff problems that come from splitting security, front-of-house, and housekeeping across separate suppliers.

Operational truth: if the briefing is vague, the site plan is usually vague too.

For organisers, the quickest check is simple. Can every guard say where they start, who they report to, and what incident type they own? If the answer is no, the staffing model is not ready.

Access Control, Accreditation and Search Screening

The gate is the highest-risk chokepoint on the whole site. It's where ticketing, accreditation, baggage search, and visitor flow collide, and it's also where the longest queues create the easiest opportunities for frustration, tailgating, and low-level disorder. If the gate is messy, the rest of the event spends the day catching up.

Treat accreditation and screening as one system

A festival gate works best when ticket validation, wristband hierarchy, crew accreditation, and contractor induction all sit inside the same process. Staff and suppliers should know their clearance level before they get near the barrier. Lost-and-found handling should also be defined early, because vague hand-offs at the entrance create arguments and slow the whole line down.

Historical police data compiled by Aviva in 2011 illustrates how theft has long been a festival-security concern. Aviva's review of police-recorded crime across the top seven UK festivals found 945 reported theft incidents in one year, with a combined value of just under £190,000. Of those, 650 were thefts from tents and 295 were personal thefts such as pickpocketing, with Glastonbury alone recording 230 tent thefts and 22 personal thefts, and Reading recording 202 tent thefts and 128 personal thefts Aviva's review of police-recorded crime. That's why perimeter checks and visible patrols matter, they directly target the most common loss patterns, not some abstract notion of “more security”.

A good provider should be able to explain the gate sequence in plain English:

• Ticket validation before anything else.

• Wristband issue matched to access level.

• Search protocol based on intelligence and consistency.

• Refusal logging when the person doesn't meet entry criteria.

• Visitor flow design that keeps queues moving without creating gaps.

What good looks like at the barrier

The gate should feel firm, polite, and predictable. Search teams need clear rules on bags, wands, secondary checks, and escalation to a supervisor when someone refuses the process. The whole point is consistency, because inconsistent enforcement is what turns one queue into a crowd argument.

If you're comparing providers, ask how they connect the gate to the rest of the operation. An operator with proper access control systems should be able to show how accreditation, contractor movement, and incident logging all link together, not just how they scan tickets. Access control systems should support the event, not sit apart from it.

The strongest gate teams are also the calmest. They don't over-talk, they don't over-search, and they don't let one difficult refusal distract them from the rest of the line. That balance reduces friction without relaxing control.

Crowd Management and On-Site Operations

Once the gates open, the job changes. The issue is no longer just entry control, it's how people move, where they pause, who they ask for help, and how quickly the site can absorb pressure without building dangerous density. Crowd management is mostly about small decisions made early, before the site feels crowded.

Design the route, then manage the behaviour

Barrier layout and signage do more than direct people, they shape how people think the site works. If entrances, exits, food points, toilets, and welfare tents are placed without a clear logic, the crowd creates its own shortcuts. Those shortcuts are where clashes, bottlenecks, and confusion tend to start.

The practical fix is straightforward, keep sightlines open, keep queues separated, and make it obvious where people should go next. If a steward has to keep pointing three different ways, the layout is doing too much work. A clean route with obvious markers usually reduces pressure better than a louder command from the front line.

I'd also treat welfare as a security function, not a side service. Festivals need plans for accessibility, multilingual evacuation, and inclusive safety for women, disabled attendees, and families, alongside crowd flow and dispersal. That's not a niche add-on. It's part of making sure people can leave safely when conditions change - OAS festival-security guidance.

Use visible help, not just visible enforcement

The best front-line teams are easy to approach. That means visible help-seeking roles, trained stewards who can de-escalate, and staff who know how to deal with harassment, intoxication, lost people, and welfare concerns without escalating every contact into an enforcement moment. UK-facing guidance has also pushed body-worn cameras as an accountability and incident-capture measure, which makes sense when the issue is a high volume of small incidents rather than a single headline problem visible, helpful and de-escalatory approach.

That's where the integrated FM model helps on the ground. Security, reception and medical teams should operate within a coordinated communications and escalation plan, with clear routes for passing urgent information between teams.

https://www.youtube.com/embed/ra_Lq0DbkiM

Friendly doesn't mean soft. It means staff are briefed well enough to keep moving, make decisions, and call support before a small issue becomes a crowd problem.

CCTV, Body-Worn Cameras and Real-Time Monitoring

Technology only earns its place if it helps the supervisor make a faster, cleaner decision. At a festival, that means knowing what's happening at the gate, the perimeter, the service roads, and the crowd edges without waiting for someone to phone in a problem after it has already spread.

Build the situational awareness stack

A solid setup starts with fixed CCTV, then adds mobile patrols, then routes what they see into a central control room with real-time alerts and a clear dispatch process. Where body-worn video is used, organisers should also ensure its use is necessary and proportionate, complete an appropriate Data Protection Impact Assessment (DPIA), provide clear privacy information and have suitable retention and disposal procedures in place.

That matters because footage on its own isn't useful if no one can retrieve it quickly. A provider that can pull a clip within about two hours gives the organiser a real operational advantage during the event and immediately after it. Solomon's Facilities Management offers CCTV monitoring services with 24/7 remote operators, real-time alerts, and monthly monitoring reports, which is the sort of structure event teams should ask for rather than a vague promise of “camera cover”.

Ask for the reporting, not just the cameras

The monitoring room should do more than watch screens. It should log incidents, confirm who received the alert, and show how the response was closed out. If a fence line breach, a gate refusal, or a welfare escalation is observed, the chain from alert to dispatch to outcome needs to be visible.

A useful monthly monitoring report should show patterns, not just isolated clips. Repeated loitering at one perimeter point, a recurring queue issue at one gate, or a cluster of late-night incidents near a dark route tells you where the next adjustment should be made. That's the value of the technology layer, it helps the event team fix the site, not just record what went wrong.

CCTV is strongest when it supports the radio plan, not when it replaces it.

If you're buying from a supplier, ask three simple questions. Who is watching, how quickly can they escalate, and how fast can they extract the footage when the police want it? If they can't answer those cleanly, the system isn't mature enough for a live event.

Police Liaison, Licensing and Governance

The approval process is usually won or lost in the paperwork and the relationships around it. A London festival has to fit inside the local authority's licence conditions, the safety advisory group process, and the police event liaison structure, and the security plan has to read as if all three were considered from the start. If the documentation looks improvised, everyone notices.

Make the contract match the governance

A single accountable contract makes liaison easier because one person owns the evidence chain. The organiser isn't chasing one firm for the staffing list, another for CCTV, and a third for incident reports. The police, licensing officer, and event manager all know who to call, who can explain a decision, and who can produce the logs.

That also helps with the event's safety, security and licensing documentation. The documents usually need to show the risk assessment, the security operations plan, evacuation and welfare procedures, the communication tree, and evidence that the team is trained and vetted. These are not separate silos, they're the proof that the event has a live governance system and not just a set of hired bodies on the gate.

Tie the technology to the evidence trail

CCTV, body-worn cameras, radios, and escalation trees should sit together as a situational awareness stack. When an incident happens, control room staff should know which feed to check, which patrol to dispatch, and which log entry will support the post-event review. The practical value is less about spectacle and more about being able to explain, in plain terms, why a refusal happened or how a crowd issue was contained.

That is where an integrated FM provider can fit naturally. It already runs inside office, retail, or residential governance structures, so the discipline around reporting, shift handover, and incident ownership tends to be familiar. The festival version just has more people, more noise, and less margin for error.

If the SAG asks for a change, answer quickly and in writing. Slow responses create doubt, and doubt costs more time than the original change ever would have done.

Post-Event Reporting and Continuous Improvement

The event doesn't end when the headline act finishes. The test is the handover, the incident pack, and the review that tells you what to change before next year's licence meeting. A festival that learns properly gets calmer over time, and the security plan gets sharper because it's based on actual site behaviour, not assumptions.

Build a report that people can act on

A proper post-event report should pull together incident logs, refusal-of-entry counts, medical interventions, CCTV clips, witness statements, and a written comparison with the security operations plan. It should also note where the plan held up, where the radios were too quiet or too busy, and which gate or route needed more support than expected. That's the document that lets the organiser, the police, and the local authority see whether the controls were proportional and effective.

Get Licensed's 2026 UK Festival Safety Audit, which compiles published police data from major festivals, highlights how outcomes varied between events. It reported that Glastonbury 2025 recorded 31 arrests and 145 crimes at a 210,000-capacity event, while Creamfields rose to 43 arrests from 32 in 2024, a 34.4% increase year on year.

The same audit reported arrests falling at several other major festivals in 2025 compared with 2024, including TRNSMT down 53%, Boardmasters down 45%, Parklife down 25%, and Reading Festival down 26% UK Festival Safety Audit. The lesson is simple, security isn't generic, and the event's own operating model changes the outcome.

Use the report to decide the next contract

A good integrated FM and security supplier should be able to carry that learning into the next season. That's one reason organisers keep a multi-year relationship in place rather than re-tendering guards every summer. The value is in continuity, the same team, the same logs, the same control habits, and the same ability to spot recurring problems at the same gate or fence line.

The morning-after checklist is short:

• Close the incident log with all late entries.

• Archive the clips linked to refusals and incidents.

• Review the radio handovers for missed escalations.

• Note the repeated pinch points on the site map.

• Record the changes needed for the next version of the plan.

If you run the review properly, next year's event starts with better information than this year's one had. That's the point of continuous improvement, and it's why the organiser should treat festival security as part of the wider FM operation, not a stand-alone invoice.

---

If you're planning a festival in London and want security, CCTV, reception, and site support handled under one contract, talk to Solomon's Facilities Management about how its integrated model fits event operations. Visit Solomon's Facilities Management to see how their SIA-licensed team can support access control, monitoring, and on-site coordination before your next event date lands on the calendar.