# The evacuation record: why the day after your event matters for the next permit — MijnEvent [Home](https://mijnevent.nl/en) / [Blog for event organizers](https://mijnevent.nl/en/blog) / The evacuation record: why the day after your event matters for the next permit safety permit evacuation event organising # The evacuation record: why the day after your event matters for the next permit An evacuation — real or drilled — is only finished once it is on paper. What belongs in an evacuation record, why the municipality asks for it, and how to make the record write itself instead of reconstructing it afterwards? MijnEvent · 27 July 2026 · 5 min read ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/ontruimingsverslag-evenement-bewijsstuk.webp) Photo: [Bernard Hermant](https://unsplash.com/@bernardhermant?utm_source=MijnEvent&utm_medium=referral) / [Unsplash](https://unsplash.com/?utm_source=MijnEvent&utm_medium=referral) In short - An evacuation record answers three questions: when was the decision made, who made it, and how did the execution go? The timeline matters more than the prose. - Reconstructing afterwards is the weakest form of record-keeping: memories diverge and timestamps become estimates. Capture decision moments as they happen. - A drill deserves a record too — in fact, for higher-risk events a demonstrably practised evacuation is often a requirement, not a bonus. - Acknowledgements count. That an alert was sent says little; that every steward confirmed it, with a timestamp, is the proof that your alerting chain works. - MijnEvent automatically and immutably logs the start, acknowledgements, emergency communication and the all-clear — the evacuation record rolls out of the log instead of out of everyone's memory. An evacuation takes fifteen minutes. The conversation about it takes months — with the municipality, the safety region, sometimes an insurer or a lawyer. And in all those conversations only one document counts: the evacuation record. Not what everyone remembers, but what was captured. This article is about that document: what belongs in it, why it is worth writing even after a drill, and how to make it write itself while you deal with more important things — like the evacuation itself. # The three questions a record answers Whoever reads an evacuation record after an incident — a permit officer, an adviser from the safety region — is looking for the answer to three questions: **When was the decision made?** The decision moment is the pivot of every evaluation. Not "around half past eight", but a timestamp. If there was a build-up before that moment (an alert, a weather warning, a blocked exit), the reader wants to see it in the timeline, including when it became known. **Who decided?** Evacuating is a human decision, not an automatism. The record names who pressed the button — literally or figuratively — and in which role. That is not about blame: it shows your escalation chain did what it exists for, with an authorised decision-maker in the right place. **How did the execution go?** From decision to "site clear": which communication went out, who received and acknowledged it, and when was the evacuation declared over? The acknowledgements are what makes the difference. That an emergency alert was sent says little; that every steward confirmed it within a minute is the proof that your alerting chain works. # Why reconstruction does not work Most evacuation records are written days later, from the memory of three people who were too busy to watch the clock. The result is predictable: timestamps become estimates, the order of events becomes a debate, and contradictions between your record and the observations of emergency services undermine precisely the trust you are trying to build. The lesson is simple and uncomfortable: **record-keeping that starts after the fact has started too late.** The alternative is capturing in the moment — every decision, every alert, every acknowledgement, timestamped as it happens. Not because you must, but because a reconstruction never carries the weight of a log that ran along. # The drill is your dress rehearsal — and your evidence For higher-risk events, the safety region's adviser looks past your evacuation paragraph to the question behind it: *has this ever been practised?* An evacuation plan that has never been walked through is a hypothesis. A drilled evacuation with a record is a fact. That is why the drill deserves a full record of its own: same timeline, same acknowledgements, clearly labelled as a drill. It buys you two things. Practically: you see where it creaks — the steward who confirmed after five minutes, the assembly point nobody could find — while nothing is at stake. And formally: in your next permit application you no longer write "we will practise", but "we practised on this date; the record is attached". That is a different application. # What concretely belongs in it A usable evacuation record is not a novel. A tight list will do: - **The build-up** — what was happening before the decision, with timestamps of the first signals. - **The decision** — timestamp, decision-maker, and whether it was a real evacuation or a drill. - **The communication** — which alerts went to stewards and visitors, when, and who acknowledged them. - **The course of events** — anything notable during execution: blocked routes, visitors needing help, contact with emergency services. - **The all-clear** — who gave it, when, and on what basis. - **The improvement points** — written down honestly. This is the paragraph that makes your next safety plan stronger. # How MijnEvent handles this for you MijnEvent's safety module is built on one principle: a human decides, the system records. The moment someone starts evacuation mode — real or as a drill — everything goes into the log automatically: the decision with timestamp and name, the alert to every steward including their acknowledgements, and the ending with the all-clear. In a real evacuation the emergency communication to visitors is added: by mail and as a notice on their wallet pass. During a drill that is deliberately left out — a drill involves only your organisation and the stewards, never your visitors. That log is immutable — nothing can be added or polished away afterwards, and precisely that makes it credible as evidence. Afterwards the evacuation record rolls out of the system as part of the evaluation report, ready to share with the municipality. Drill mode uses exactly the same path, clearly labelled as a drill. Want to know how the full safety dashboard works, from gate monitoring to the municipality view? Read [Safety & permit: live view of your inflow](/en/blog/safety-permit-module-gate-monitoring). And for the broader story about the permit application there is [the safety plan for your event](/en/blog/event-safety-plan-crowd-monitoring). Frequently asked questions ## Frequently asked questions ## Is an evacuation record mandatory? After a real evacuation the municipality or safety region will almost always ask for one, and for higher-risk events it is part of the standard evaluation file. Even without an obligation it is wise: this edition's record is the substantiation of your next application. ## How does it differ from the evaluation report? The evaluation report describes the whole event: inflow, peaks, no-show, incidents. The evacuation record zooms in on one occurrence — the (drilled) evacuation — with a timeline from decision to all-clear. In MijnEvent the evacuation record is part of the evaluation report. ## Should I write a record of a drill as well? Yes — especially of a drill. The point of drilling is demonstrating that you can do it, and without a record nothing has been demonstrated. A logged drill with timestamps and acknowledgements is worth a lot in your next edition's permit application. ## What if the evacuation was chaotic? Write it down as it went. An honest record with improvement points is more credible — and legally safer — than a polished story that contradicts what emergency services saw on site. This year's improvement points are the strongest paragraph of your next safety plan. [ Back to blog ](https://mijnevent.nl/en/blog) MijnEvent ## Read more [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/automatic-membership-renewal-dutch-law.webp) memberships Jasper Koers · 27 July 2026 · 6 min read ## Automatic membership renewal: collecting fees within Dutch renewal law Automatic renewal saves your club a pile of chasing work, but the law has rules about cancelling. Here is how renewal works in MijnEvent, and how to keep it clean. ](https://mijnevent.nl/en/blog/automatic-membership-renewal-dutch-law) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/knmi-weeralerts-veiligheidsplan.webp) safety MijnEvent · 27 July 2026 · 3 min read ## Weather monitoring in your safety plan: how KNMI warnings land in your alerts and logbook automatically Almost every safety-plan format has a 'weather monitoring' section — and almost nobody fills it in concretely. The Safety & Permit module pulls the KNMI warning code for your event location every hour and turns it into a demonstrable process. ](https://mijnevent.nl/en/blog/knmi-weather-alerts-event-safety-plan) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/rental-calendar-blocking-and-phone-bookings.webp) modules Jasper Koers · 27 July 2026 · 6 min read ## The rental calendar: seeing occupancy, blocking days and booking by phone The daily work in the rentals module: one monthly view of what is taken, a day closed off for maintenance, and the customer who calls put down straight away. ](https://mijnevent.nl/en/blog/rental-calendar-blocking-and-phone-bookings) MijnEvent ## Ready to get started? Create a free account and sell your first tickets today. [Start free](https://mijnevent.nl/registreer) [Pricing](https://mijnevent.nl/en/pricing)