For a Bonfire Night event, security planning should start with a shared operational picture: the event profile, site, arrival and departure patterns, communications, welfare arrangements and decision-makers. Give any security provider a clear brief early, test how the plan will work if conditions change, and leave time to record incidents and learn from the event.
Published: 4 November 2026 | Reviewed: 4 November 2026
Start with the event profile, not a generic deployment
The useful first question is not “how many people do we need?”, but “what is this event asking the venue and its partners to manage?” HSE advises organisers to identify the event’s scale, type, audience, location, duration and time of year, then translate that into an appropriate plan.
Use one working brief for the format, programme, expected attendance, entry arrangements, venue, operating times, organisations and named decision-makers. Include the period before the public arrives and close-down afterwards: HSE notes that build-up and break-down also need management and co-ordination.
Make the site information usable under pressure
A site plan should be useful to the people who have to act on it. Give the agreed team a current version showing the address and reference points, arrival and departure routes, public and working areas, access points, delivery arrangements, welfare and medical locations, key contacts, and agreed emergency information. Confirm who owns updates when the layout or programme changes.
Security providers need enough site-specific information to understand their agreed role. NPSA advises time for temporary-event teams to familiarise themselves with the venue, reference points, equipment and communications. Issue the final brief early, arrange a walk-through where useful, and avoid relying on verbal changes passed through several people.
Plan arrival and departure as managed phases
Arrival and departure deserve their own plan. Decide what guests, performers, suppliers and neighbours need to know: when to arrive, which entrance or transport point to use, how to find facilities and what to do if arrangements change. Align information with the venue, organiser and partners so messages do not conflict.
Keep a simple picture of changes from the brief: delayed programming, altered access, transport issues or site conditions may affect the agreed approach. For departure, agree the close trigger, communication sequence, responsible contacts and how late changes will be shared. This supports continuity; it does not promise the original timetable.
Give every team a clear communications and welfare picture
Before opening, identify the event lead, venue contact, security lead and escalation route. Agree the communication methods, their fallback, the owner of public-update wording and records to be kept. HSE recommends testing communications equipment and briefing people on relevant site risks and emergency arrangements. Use a short, site-specific briefing and a clear handover process.
Record agreed locations and contacts for facilities, first aid or medical support, accessible assistance and weather-related arrangements. Make sure the people likely to be asked for help know how to direct an enquiry. The detail should reflect the event and venue, including personnel and volunteer welfare through handovers and breaks.
| Before the event | Decision-led check |
|---|---|
| Event profile | Have we recorded the audience, programme, operating periods, venue and named leads? |
| Site information | Is there one current, usable plan with reference points, contacts and agreed operational information? |
| Arrival and departure | Do guest, supplier and venue messages match, including for changes to the programme? |
| Communications | Have roles, escalation routes, fallback methods and public-message ownership been briefed and tested? |
| Welfare | Can the team direct people to the agreed support points and escalate concerns appropriately? |
| Contingencies | Are the decision-makers, consultation points and communication steps clear if conditions change? |
| Close-down | Who records issues, leads the handover and convenes the debrief? |
Agree how contingency decisions will be made
A contingency plan is valuable when it explains the decision process, not when it predicts every scenario. HSE says emergency plans should be proportionate to event risk and consider contingencies such as severe weather, a cancelled act or unavailable key staff. Work through material changes—weather, a site issue, lost communications, programme disruption or changed attendance—and agree the information required, consultation points, decision-maker and communication route.
A tabletop discussion can test those questions before the day. Government event-security guidance similarly recommends risk assessment and tabletop exercises from site preparation to conclusion. Keep a decision log: what changed, who assessed it, what was decided, who was informed and what needs later review.
Make incident reporting factual, timely and reviewable
Agree a simple reporting route before the event. A useful record distinguishes observed facts from assumptions and captures the time, location, people involved or affected, actions taken, notifications and follow-up. The immediate response should follow the event’s agreed arrangements and involve appropriate services or venue contacts when required. Staff should know who receives a report and where it is logged.
At close-down, reconcile open matters, record changes to the site or operating picture, confirm handovers and arrange a focused debrief. HSE describes post-event debriefing as good practice, particularly after a significant incident or emergency. Retain what worked, identify the gap, assign an owner and record the next action.
What to prepare before speaking to a security provider
Bring the event brief, current site plan, programme, expected attendance, constraints, venue contacts and agreed emergency or welfare information. Explain the roles to be supported, the operational information personnel need, communications, reporting expectations and event-day decision-makers. Ask how the provider will evidence licence status appropriate to each supplied role, site instructions, records and proposed subcontracting. SIA guidance makes clear that licensing can depend on the activity and circumstances, not simply a job title; use official guidance and obtain advice appropriate to your situation where uncertain.
Plan the operational record with SSS Official
SSS Official’s event security service can discuss a London event around its venue, format, guest experience, agreed access arrangements, communication routes and escalation procedures. SSS deploys personnel holding the SIA licence appropriate to their role and is ISO 9001:2015 certified. Where included in the agreed client configuration, the SSS Application can support attendance, site instructions, foot and mobile patrol logs, lone-worker processes and incident reports. Clients can be given access to agreed rotas, vetting and licence details, and incident records. These tools support documentation; they do not replace organiser decisions or certify legal compliance.
To discuss the planning information for a Bonfire Night event or venue, contact SSS Official.
Sources and further reading
- HSE: Getting started with event safety
- HSE: Managing an event
- HSE: Planning for incidents and emergencies
- UK Government / SIA: Events guidance for buyers of security
- UK Government / SIA: Check if you need an SIA licence to work at an event
- NPSA: Security contractor guidance for events
This article provides general operational information for organisers and venues. It is not legal advice, fire-safety advice, or a substitute for event-specific assessment, official guidance or advice from suitably competent professionals.