Safety Advisory Groups: what to expect and how to prepare

If your event is big enough, on public land, or just new to the area, you'll meet the Safety Advisory Group — the SAG. Organisers who understand what a SAG is (and isn't) find the process useful rather than frightening.

What a SAG is

A Safety Advisory Group is a panel convened by the local authority that brings together the people who'd deal with your event going wrong: council officers (events, licensing, environmental health, highways), police, fire and rescue, and ambulance service, sometimes with others — a stadium safety officer, the coastguard, a national park authority — depending on the event.

Its job is to review event plans and advise. The key word is advise: a SAG is not a licensing body and generally has no statutory power to approve or ban an event. What it has is influence over the people who do hold power — the council as landowner, the licensing authority, the police — and a paper trail. An organiser who ignores SAG advice and has an incident will meet that paper trail again in less friendly surroundings.

What a SAG asks for

The core pack is consistent across the country:

• An event management plan — the main document under review.
• A risk assessment, and a fire risk assessment.
• A site plan that matches the text.
• Proof of public liability insurance.
• Where relevant: a traffic management plan, medical and stewarding plans, licensing details, and — increasingly — your thinking on Martyn's Law and counter-terrorism basics.

Deadlines vary by council and by event scale — some SAGs ask for draft documents around three months before the event with final versions a few weeks out. Find your council's SAG or events page early and put its dates in your calendar first; everything else works backwards from them.

How the meeting actually goes

Usually: a table (or a video call), each service asking questions about their patch. Police want crowd numbers, alcohol and egress; fire want access routes, gas and structures; ambulance want your medical cover and rendezvous points; highways want the roads. It's direct but rarely hostile — these are people who would genuinely rather fix your plan in March than respond to it in July.

What lands well: knowing your own plan, answering plainly, and saying 'I don't know yet — I'll confirm by [date]' instead of improvising. What lands badly: paperwork clearly copied from another event, numbers that don't match between documents, and treating the questions as obstruction.

After the meeting: actions, versions and sign-off

A SAG review usually ends with actions: sections to expand, numbers to confirm, a revised site plan. Treat these like a builder treats a snag list — turn them around quickly, in writing, and version your documents visibly ('EMP v3, updated 14 May') so nobody reviews a stale copy. Half the friction in SAG processes is two agencies holding different versions of the same plan.

Keep the final pack — plan, risk assessments, correspondence — together after the event too. If anything did go wrong, that file is the difference between demonstrating diligence and reconstructing it.

If you're small enough to escape the SAG

Plenty of community events never see one — the council events team just reviews the paperwork by email, or (for private events on private land) nobody formally reviews it at all. The SAG pack is still the right target, at smaller scale: the plan, the risk assessment and the site map are what your insurer, your landowner and — in the worst case — an investigator would ask for. Build the habit at fete size and festival size looks after itself.

Common questions

Can a SAG stop my event?

Not directly, in most cases — it's advisory. But the council can refuse its land, the licensing authority can review a licence, and the police have their own powers. In practice, an event that dismisses serious SAG concerns tends to lose one of those permissions instead. Treat the advice as the warning system it is.

Do I have to attend a meeting?

For smaller events, often not — many SAGs review documents without calling the organiser in. If you are invited, go (or send the person who actually knows the plan). Declining the invitation is technically possible and practically unwise.

How early should I contact the council about my event?

As soon as the date and venue are pencilled in. Early contact costs one email and buys you the real deadlines, the right forms, and a named officer — the three things organisers most often lack in the final month.