The date is set, the line-up is locked, tickets are almost ready to go on sale — and then one thing stands between you and your event: the permit. For many organisers that is the tensest moment of the whole process, because the municipality can say no. And the document it hinges on is almost always the same: the safety plan.
The good news is that the municipality is not trying to trip you up. It wants to know one thing: have you thought about what can go wrong, and have you arranged for it? This is a practical guide through the sections that really matter — with special attention to the part where most plans are too thin: crowd monitoring.
First: notification or permit?
Not every event needs a full permit. A small neighbourhood fair can often be handled with a simple notification; a festival with ten thousand visitors certainly cannot. The municipality makes the distinction with a risk scan, and the result is usually a sorting into risk classes — commonly A (regular, low risk), B (attention event) and C (high risk). That class determines which advisers get involved and how much you have to supply.
The most important advice we give organisers: find out that class early. The lead time for a B or C event can easily be eight to twelve weeks, because the safety region, fire brigade, police and medical services all become involved. Anyone who knocks on the door three weeks ahead with a C event is too late.
What belongs in a safety plan
The structure varies by municipality and safety region, but under the hood every format revolves around the same national methodology: an audience profile (who is coming, how many, when), an organisation profile (who is responsible for what, which lines run where) and a block of risks and measures. In plain language, your plan answers four questions:
- How many people are allowed at most? Your capacity, substantiated — not a round number that sounds nice.
- How do you know you stay below that? Your monitoring. This is where most plans fall down.
- Who intervenes when things go wrong? Your escalation chain: who decides, who calls whom.
- How do you evacuate? Your evacuation plan, including emergency routes and assembly points.
Crowd monitoring — where it usually goes wrong
In nine out of ten plans, question two answers with some variant of "we keep an eye on the numbers". That is not a method, it is a promise. A safety region adviser sees straight through it, because the follow-up question is simple: how, and when do you intervene?
A strong monitoring section does two things. First, it describes a concrete measurement point. If you work with tickets, that is your biggest opportunity: every scan at the gate is a data point about a person, at a place, at a time. So you can count cumulatively how many visitors were admitted per entrance, and set that against your capacity — with thresholds at which you act.
Second, it is honest about what cannot be done. A "current attendance" figure cannot be measured as long as visitors do not check out when they leave. So do not include that number — a made-up figure is more dangerous during an incident than no figure. What you may claim is the cumulative admitted count: a hard upper bound on attendance, and precisely the number the permit is about. That accounting of your measurement method — this we count, this we don't, and why — is worth its weight in gold in an application. It shows you understand what you measure.
Escalation and evacuation: make it demonstrable
For the last two questions, concreteness always beats fine writing. Record your alert chain: at which threshold does an alert go to whom, and how does that person confirm they have seen it? A chain you can reconstruct afterwards — who confirmed what, and when — is exactly what a permit authority wants to see.
The same goes for the evacuation, plus one thing: rehearse it. A rehearsed evacuation with a log is not a plus at larger events but a requirement. Anyone who can demonstrate that the tent was empty in four minutes stands a couple of classes stronger than someone who has written a paragraph about evacuating. What exactly belongs in such a record — and why you let it build during the (drilled) evacuation instead of afterwards — is covered in the evacuation record as evidence.
How MijnEvent handles this for you
These exact sections — the monitoring, the alert chain, the evacuation and the model texts — we provide for free. The Safety & permit module turns your gate scans into a live dashboard with figures per entrance and alerts on unusual crowding, capacity and weather. The alert chain is recorded immutably, the evacuation button puts emergency routes on every steward phone with a drill mode, and afterwards you have an evaluation report with an accounting of the measurement method.
And before your application, the permit helper generates the monitoring, communication and evacuation paragraphs in the national profile methodology. You paste them into your municipality's format and keep your time for the things that really carry your signature.
What a tool does not do, we say honestly: it does not replace your safety plan, and at a genuinely large event it does not replace your security organisation or professional crowd management. But it turns the sections an application usually fails on — the monitoring and the evacuation — from a promise into a demonstrable process. And that is exactly what the municipality wants to read.
