Every attachment on the checklist Ready for the Omgevingsloket Status per application for the client

Custom app for building permit application files

Appfront builds apps for architects, construction companies and consultancies that apply for environmental permits on behalf of their clients: a file per project with the checklist of attachments the Omgevingsloket (the Dutch environmental permitting portal) requires for that activity, the drawings and calculations in the correct version, the client's authorisation, and the status after submission with the municipality's questions alongside. So an application is never dismissed because a single attachment was missing.

What is an app for the application file of an environmental permit?

An application file for an environmental permit is everything the competent authority needs to decide on an activity: the application itself, the drawings, the calculations, the reports and the client's authorisation. Since the Omgevingswet (Environment and Planning Act), applications go through the Omgevingsloket, and each activity has submission requirements that determine which attachments must be included. An app for the application file turns that into a checklist per project, stores the documents in the right version and tracks the application after submission, including the questions the municipality asks.

Without such an app, the application sits in the portal, the drawings are on the network drive in three versions, the structural calculation is in an email from the structural engineer and the authorisation is in a scan. The municipality asks for additional information, the deadline is running, and the project manager is working out which version of the façade elevation was submitted. The client calls to ask how things stand, and the answer is a guess.

We build custom because the file has to fit your projects and your way of working: which activities you usually apply for, which attachments you supply as standard, which consultants contribute, how your drawings are managed and what the client is allowed to see. A generic project management package knows nothing about submission requirements or competent authorities.

Checklist per activity

Per project, the activities being applied for and, per activity, the attachments that belong with it, with the status per attachment: requested, received, checked, submitted.

Versioned documents

Drawings, calculations and reports in versions, with the submitted version marked. An update becomes a new version, not an overwritten file.

Status after submission

The submission date, the deadline, the requests for additional information and your response, visible to the team and, in plain language, to the client.

How we build your app for the application file of an environmental permit

We start with an application that ran into delays: which attachment was missing, who should have supplied it and where the file was. The app follows from that.

1
Mapping your applications

Which activities you apply for, which attachments recur per activity, which consultants contribute, how drawings are managed now and how the client is currently informed.

2
File and checklist

Per project, the activities and the checklist of attachments, with who supplies what and when. Linked to the project in your project administration.

3
Documents and submission

Versioned documents, the check before submission, submission via the Omgevingsloket and a record of exactly what was submitted.

4
Status, portal and handover to maintenance

Requests for additional information and deadlines in the file, the client portal, and then ongoing maintenance and extension to notifications and pre-application consultation.

What an app for a permit application file actually does

The components below appear at almost every firm that applies for permits. Which ones you need depends on the type of projects you handle and on your advisers.

Project file

For each project: the client, the location, the activities and the competent authority, with the client's authorisation as the first document.

Attachments checklist

For each activity, the attachments the permit desk asks for, plus what you routinely supply yourself, with the status of each attachment and who provides it.

Version control

Every drawing and report in versions, with the submitted version locked and the change visible when you supplement an application.

Advisers submit their documents

The structural engineer, the building services adviser and the building physics consultant upload their document to the file, against the attachment it belongs to, without email.

Deadlines and supplements

The submission date, the decision period and requests for supplements with their deadline, with an alert before every deadline.

Client portal

The client sees the status of their application, the submitted documents and what is being asked of them, without having to call.

Who we build an app for a permit application file for

The app is intended for firms and companies that regularly apply on behalf of others and where a missing attachment currently costs weeks.

Architecture firms

Applications for new builds and renovations, with drawings from your own firm and calculations from advisers. The checklist and adviser submissions are the core.

Construction companies and contractors

Applications as part of a building contract, often under time pressure. The deadlines and the integration with the project planning matter most.

Building consultancies

Applications as a service, for many clients at once. A portal per client and reporting on current applications are what you need.

Developers with multiple projects

Applications per project with different firms. An overview of all files and the status per competent authority is the core.

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 the application file. For managing the drawings themselves, in revisions, see our page on drawing revision management for architects, for the firm as a whole our page on architectural firm software, and for the permitting authority's side our page on permit software. You can read about our approach at building software.

If your organisation handles many applications across many locations at once, take a look at our software for environmental permit application files.

If the risk matrix results in a construction safety plan, there is our construction safety plan app.

If you want to track the BENG calculation from application through to completion, take a look at our software for the BENG calculation file.

If you want to see the rules from the environmental plan per location in your own system, there is our page on an IMOW integration.

Project file with activities and competent authority Attachments checklist per activity Version control of drawings and reports Adviser submissions in the file Client authorisation Deadlines and requests for supplements Client portal Integration with project administration Integration with drawing management Reporting on current applications

Why Appfront for your app for a permit application file?

A permit application is only as good as whether everything is included. That is what we build on: one checklist, one version, one status.

The checklist is per activity

What the permit desk asks for is in the file before the first drawing is made. A missing attachment is spotted during preparation, not when the request for supplements arrives.

Submitted means locked

The version that went to the permit desk stays the submitted version. A supplement is a new version with the change attached, not an overwritten file.

The client knows where things stand

Status, documents and what is being asked of them are in their portal. The project manager answers questions, not the same question every week.

Security and privacy in an app for a permit application file

The file contains drawings and reports owned by your practice or by consultants, as well as client and site data. Access is set up per role and per project: the project manager sees their own projects, a consultant sees only the attachment they supply, and the client sees only their own application. Every upload, change and submission is logged with name and time, and the submitted version can no longer be changed.

The app runs in a European data centre, with encrypted storage and daily backups. Integrations with your project administration and drawing management use their own keys, which can be revoked per integration.

Frequently asked questions about an app for the environmental permit application file

Questions that architects and construction companies ask before getting started.

It creates a file per project with the activities being applied for and, for each activity, a checklist of attachments. It stores drawings and reports in versions, lets consultants supply their documents directly in the file, records what has been submitted, and tracks deadlines and requests for additional information. The client sees the status in a portal.

Submission is done in the Omgevingsloket itself, by the authorised representative. The app prepares the file, checks the checklist and records which versions were submitted and when. Whether an integration with the portal is possible and worthwhile for your situation is something we look at in the first step.

From the submission requirements per activity, supplemented with what you routinely supply yourself and what a municipality asks for on top. You manage those lists in the app, so a change in the rules or in a municipality's practice is recorded once and then carries over into every new file.

The request appears in the file with its deadline, the requested documents become attachments with the status requested, the consultant who has to supply them receives a notification, and the addition becomes a new version. What was added and when is shown alongside what was originally submitted.

For buildings that require a quality assurer, the quality assurer is listed as a party in the file, along with the documents they supply or receive. The app keeps track of which documents are needed for the construction notification and the completion notification; the substantive assurance remains with the quality assurer.

Yes. The project and client come from your project administration, drawings can be linked from your drawing management in the current version, and the status of the application is passed back to the project planning. We connect to what you already use; the file doesn't become a second list of projects.

Check that first. A folder works as long as one person has the overview and the municipality never asks for anything. Custom software makes sense when several consultants contribute, when versions get mixed up, when deadlines are missed, or when clients phone to ask how things stand.

Every application submitted complete, and the status visible to everyone?

Tell us how many applications you submit per year, which consultants contribute and how often a request for additional information has moved the deadline in recent months. We'll show you what the file, the checklist and the portal look like.

Edit content