Custom quality assurance file and assurance plan software
Under the Building Quality Assurance Act (Wkb), for buildings in consequence class 1 an independent quality assurer checks whether construction follows the rules. Before the start they draw up a risk assessment and an assurance plan, during construction they carry out the plan, and the completion notification comes with a file. Appfront builds software for quality assurers that records all of this per project: from risk assessment to declaration.
What is software for the quality assurance file and assurance plan?
The Building Quality Assurance Act applies to buildings in consequence class 1, mainly homes and simple commercial buildings. Here it is not the municipality that checks the construction work, but a private quality assurer. Before the start, they draw up a risk assessment of the specific building and an assurance plan: how they will handle those risks and when they will check what. The client sends both to the municipality with the building notification.
During construction, the quality assurer carries out the assurance plan: they review drawings and calculations, inspect on site, and collect evidence from the contractor. The completion notification comes with a file for the competent authority, including data on structural safety and fire safety, and the quality assurer's declaration. At many firms, this sits in separate documents, spreadsheets and emails per project.
We build custom software because firms differ in working methods, instruments and projects. The software records the risk assessment and assurance plan per project, schedules the assurance checkpoints, lets the inspector record on site what has been checked, and compiles the file from what happened during construction. We take the requirements of your approved instrument into account in the first step.
Plan per project
Risk assessment and assurance plan recorded.
Assurance on site
Inspections with photo and finding.
File at completion notification
Compiled from what happened.
How we build your software for the quality assurance file and assurance plan
We start with a completed project: how the risk assessment and assurance plan were drawn up, how the assurance checkpoints were planned and carried out, what evidence came from the contractor, and how the file was compiled. Then we define what your instrument looks like: which risks, which assurance checkpoints per type of building, and what is recorded at each checkpoint. We often start with the assurance plan and recording on site, because that is where most of the scattered work sits. Collecting evidence from the contractor and compiling the file follow after that. Afterwards, we keep the software up to date as rules or your instrument change.
Plan, assurance, evidence and file.
Risks and assurance checkpoints.
Plan, inspection and file.
Go-live, integrations and maintenance.
What software for the quality assurance file and assurance plan does in practice
The components below appear in almost all software for quality assurers. Which ones you need depends on your instrument and projects.
Risk assessment
Per building.
Assurance plan
With assurance checkpoints.
Inspections
On site.
Deviations
Through to resolution.
Proof
From the contractor.
Dossier
With declaration.
Who we build software for the quality assurance file and assurance plan for
The software is intended for organisations that work as quality assurers under the Wkb. The more projects and inspectors you have, the more it delivers.
Quality assurers
Many projects. One working method matters.
Agencies
Multiple inspectors. Overview matters.
Construction companies
Own assurance. Separation of roles matters.
Consultancies
Assurance alongside advisory work. The file matters.
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 covers the quality assurer's side. For the contractor recording evidence, see our page on the Wkb integration; for collecting information from subcontractors, our page on the as-built file; and for the electrical installation, our page on the NEN 1010 handover inspection file. You can read about our way of working on building software.
Why Appfront for your quality assurance file and assurance plan software?
An assurance plan in a separate document, and evidence arriving by email, cost a quality assurer hours on every project and leave the file vulnerable at completion notification. That is what we build on: one plan per project, assurance on the building site, and a file that takes shape during construction.
One way of working
The same for every project.
Evidence in one place
Not in the inbox.
File ready
At completion notification.
Security and privacy for quality assurance file and assurance plan software
The software processes data about projects, clients, contractors and inspectors, and documents such as drawings and calculations. Access is set up per project and role, a contractor only sees their own projects, and every finding and change is recorded with who made it and when.
The software runs in a European data centre, with encrypted storage and daily backups. Data you are required to retain remains available. We record the processing in a data processing agreement.
Frequently asked questions about quality assurance file and assurance plan software
Questions quality assurers ask before they get started.
For buildings in consequence class 1, a private quality assurer checks whether building is done in line with the technical building regulations. Before the start, they draw up a risk assessment and an assurance plan, carry out the assurance during construction, and issue a statement at completion notification if the building meets the regulations.
How the quality assurer deals with the risks from the risk assessment: which components they assess, when they carry out checks, and what evidence they expect from the contractor. The plan must be ready before the start, because the client sends it to the municipality with the building notification.
That page covers the contractor's side: recording evidence at the moment itself and using the assurance plan as a checklist. This page covers the quality assurer's side: risk assessment, assurance plan, inspections and statement. The two fit together.
Yes, if you want that. For each project, the contractor gets access to the assurance moments that require evidence and submits photos, documents and measurements. The quality assurer assesses them and records whether they are sufficient.
Yes, that is the intention. A quality assurer works with an approved instrument that sets requirements for working method and recording. The software follows your instrument, and in the first step we establish what it requires.
What the regulations and your instrument require, such as information on structural safety and fire safety, the assurance carried out, and the quality assurer's statement. The software compiles it from what was recorded during construction. The municipality checks the file for completeness.
Yes, if needed. The inspector can record on a tablet or phone without a connection, and the data goes to the project as soon as there is signal again.
From risk assessment to statement in one file?
Tell us how you currently draw up assurance plans, how inspections are recorded, and how the file comes together at completion notification. We will show you what the software looks like.