Plan and floor plan from one source Tasks per role, not per name Every version demonstrably approved

Custom evacuation plan software development

Appfront builds evacuation plan software for organisations with multiple buildings or a complex occupancy: the plan structured according to NEN 8112, the floor plans according to NEN 1414-1 generated from the same data, tasks recorded per emergency response (BHV) role with occupancy per part of the day, drills and evaluations as actions with an owner, and every change approved with a version, date and person responsible. So the version on the wall, the version at reception and the version in the BHV folder are all the same.

What is evacuation plan software?

Evacuation plan software turns the plan into a structured set of data instead of a text file: buildings, floors, sectors, escape routes, facilities, roles, tasks and drills are separate components that are linked to one another. The chapter structure according to NEN 8112 and the evacuation floor plans according to NEN 1414-1 come from the same source. If you move an emergency exit or a fire extinguisher, the system shows which floor plans and which procedure texts need to be approved again.

Without such a system, the plan sits in a Word file on a network drive, floor plans from three years ago hang on the wall, the names of departed employees are still in the running text and the evaluation of the last drill is in a mailbox. During an inspection or after an incident, nobody can demonstrate which version applied when and who approved it.

We build custom because the plan has to fit your buildings and your organisation: how your sectors are divided, which roles your emergency response (BHV) organisation has, where staffing data comes from (HR, rosters, access control), which drawing files you have and what makes a care location different from a distribution centre. A document management system has no concept of a sector, a role, or a floor plan that moves with the plan.

One source for text and drawing

The plan according to NEN 8112 and the floor plans according to NEN 1414-1 from the same data. A change to the building shows which texts and drawings need to be approved again.

Roles instead of names

Evacuation tasks per function: BHV coordinator, team leader, alarm notification point, assembly point coordinator. People are linked to the role; staff turnover affects the occupancy list, not the plan.

Demonstrability

Every change, approval and drill with date, person responsible and version number. During an inspection, you show in a single overview which version has applied since when and who approved it.

How we build your evacuation plan software

We start with the sector division, not with the screens: until it is settled how the building is divided and who sweeps which sector, you are building on sand.

1
Inventory with BHV and facilities

We go through the existing plans and take stock of buildings, sector and floor division, roles and sources: drawings in DWG or IFC, the detector list of the fire alarm system and the occupancy from HR or access control.

2
Data model and standards check

Building, floor, sector, escape route, facility, role, task and drill as separate components. We then check whether the mandatory elements of NEN 8112 and the drawing requirements of NEN 1414-1 each have a place.

3
Building in short iterations

First building data and floor plans, then the plan components and publication, finally the drill and revision module. After each iteration, a BHV team leader tests with real building data, not demo data.

4
Rollout, revision round and handover

We migrate your existing plans, run one full revision round per location and hand over with admin documentation and a configured authorisation structure.

What evacuation plan software actually does

Every organisation thinks its situation is unique. That's true of the content, not of the functionality: these six components almost always come up, only the details differ.

Plan structure

Chapters, procedures and tasks per role in a fixed layout, with standard text at organisation level and location-specific deviations beneath it.

Floor plan management

Base drawings from AutoCAD or BIM with escape routes, emergency exits, fire-fighting equipment, first aid equipment and assembly points as objects, using the NEN 7010 symbols as NEN 1414-1 requires.

Roles and staffing

Chief emergency response officer, team leaders, evacuation team, reporting point and assembly point coordinator, with staffing per part of the day and an alert when a sector is understaffed.

Drill module

Plan a drill, record the scenario, log times per sector and turn bottlenecks from the evaluation into actions with an owner and a deadline.

Revision and version control

Change proposals, approval by a designated authoriser, automatic version numbers and a list of floor plans that need to be reprinted and put back up.

Publication and offline use

Print-ready PDFs to scale for the wall, a concise card for the emergency response folder and a mobile view that also works when the network is down.

Who we build evacuation plan software for

The software is for organisations where a single template for all buildings isn't enough, because occupancy, self-reliance or ownership differs per location.

Healthcare organisations

People with limited self-reliance are usually moved horizontally to an adjacent fire compartment. The core is a current occupancy and mobility indication per room and the shelter capacity per compartment.

Education

Classrooms change occupancy every hour. The integration with the timetabling system makes the roll call at the assembly point workable: the teacher gets the class list for that moment.

Multi-tenant buildings

One building plan alongside separate emergency response organisations per tenant. What you need is central management of shared areas and shielding of tenant-specific parts.

Industry and logistics

Large sectors, hazardous substances and rotating shifts. The core is staffing per part of the day, the integration with access control and drills per shift.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page is about managing the plan and the floor plans. For inspections to the standard, see our page on a condition assessment inspection app NEN 2767, for the safety walk-round on the shop floor our page on a NEN 3140 inspection app, and for building management as a whole our page on maintenance software. You can read about our approach on building custom software.

Plan structure according to NEN 8112 Floor plans according to NEN 1414-1 Base drawings from DWG and IFC Symbols according to NEN 7010 Roles and staffing per part of the day Integration with HR and access control Integration with timetabling systems Fire alarm system detector list Version control with authorisation Mobile view without network

Why Appfront for your evacuation plan software?

An evacuation plan is only as good as the version hanging in the building. That's what we build on: one source, one authorisation, one overview during an inspection.

Text and drawing can't drift apart

Plan and floor plan come from the same data. A changed emergency exit flags which texts and drawings need to be re-authorised.

The plan survives staff turnover

Tasks belong to the role, people to the staffing. When someone leaves, they disappear from the list; the plan doesn't change.

Demonstrable at every inspection

Version, date, authoriser and the latest drill in one overview. Not reconstructed from mailboxes, but shown.

Security and privacy in evacuation plan software

The software works with building floor plans, staff occupancy data and, in some cases, mobility data on residents or patients. Access is set up per role and per location: the head of emergency response (BHV) manages the system, shift leaders see their own sectors, tenants in a multi-occupancy building see only their own section, and a supervisory authority gets a readable overview. Every change and approval is logged; for care providers, the setup is aligned with NEN 7510.

The software runs in a European data centre with encrypted storage and daily backups, and the mobile view keeps working if the network goes down. Integrations with HR, access control and scheduling systems use their own keys, which can be revoked per integration.

Frequently asked questions about evacuation plan software

Questions that heads of emergency response and facility managers ask before getting started.

It manages the evacuation plan as structured data: buildings, sectors, escape routes, facilities, roles and tasks in line with NEN 8112, floor plans in line with NEN 1414-1 from the same source, emergency response team staffing per part of the day, exercises with evaluations and actions, and version control with formal approval. Publication is available as print and as a mobile view that works without a network.

No. Existing plans are migrated to the system's structure: chapters, procedures and tasks per role. What is the same across the organisation becomes standard text; what differs per location is listed below it as a deviation. We then run one review round per location, so the first approved plan is correct straight away.

As a base layer from your drawing files in DWG or IFC, on which escape routes, emergency exits, extinguishing equipment and assembly points are placed as objects using the NEN 7010 symbols. If you move an object, the floor plan changes and you get a notification of which texts and prints need to be updated.

Through integrations: emergency response role staffing per part of the day from HR or the schedule, presence from access control, and in education the class list for that period from the scheduling system. A sector with no staffed role triggers an alert to the shift leader before the shift begins.

Yes. An exercise is planned with a scenario, times per sector are recorded, and the bottlenecks from the evaluation become actions with an owner and a deadline. At the next exercise, you can see which actions have been completed and whether the bottleneck has gone.

Yes. The mobile view of the plan and floor plans is stored locally on the emergency response team's devices and remains available without a network. Scaled print PDFs for the wall and the condensed card for the emergency response folder come from the same version.

Check that first. A document management system stores the plan as a file with versions, and that is enough for a single building with fixed staffing. Custom software makes sense when the plan and floor plan need to come from the same source, when tasks need to be assigned per role rather than per name, when occupancy needs to come from other systems, or when you need to show during an inspection which version applied when.

One plan, one floor plan and one version that demonstrably applies?

Tell us how many locations you have, where occupancy data comes from and when the plan was last approved. We'll show you what plan structure, floor plan management and version control look like.

Edit content