Custom software for the as-built file at completion notification
When a building is handed over, information about how it was actually built goes with it: as-built drawings, products used, installation details and maintenance instructions. That information sits with dozens of subcontractors and installers, and it must be complete for each building number before the completion notification goes to the municipality and the file goes to the buyer. Appfront builds software in which subcontractors submit their as-built information themselves and the main contractor sees per building number what is still missing.
What is software for the as-built file at completion notification?
An as-built file records how a structure was actually built, not how it was designed. It contains revised drawings, details of the products and installations used, warranty certificates and maintenance instructions. Under the Wet kwaliteitsborging (Building Quality Assurance Act), a file for the competent authority must accompany the completion notification, and the client receives a consumer file. Much of that information is as-built information.
That information is not held by the main contractor, but by the subcontractors and installers who did the work. For each unit number, drawings, product sheets and instructions have to be requested, chased up and checked. In practice this is done with email and shared folders, and shortly before handover it turns out that, for some of the homes, the installation drawings or the heat pump's maintenance instructions are missing.
We build custom software because projects differ: the type of structures, the number of unit numbers, the subcontractors involved, and the quality assurance and document systems you already have. Which information must go into which file is something you determine with your quality assurer and the regulations; the software makes sure it is there for each unit number.
Per unit number
Which information is needed, and what you already have.
Subcontractors submit
Via a portal, without email and folders.
Complete for handover
The file ready for the completion notification and the buyer.
How we build your software for the as-built file for the completion notification
We start with your projects: which as-built information is needed for each type of structure, which subcontractors supply what, how this is handled now, and where things are missing at handover. We often start with the list of required information per unit number, because it immediately shows what is outstanding. The subcontractor portal, the checks and the compilation of the files follow. Integrations with your quality assurance or document system come once the foundation is in place.
Information, subcontractors and files.
What is needed, who supplies it.
Submitting and reviewing.
Ready for handover.
What software for the as-built file for the completion notification actually does
The components below appear in almost every piece of as-built file software. Which ones you need depends on your projects.
Request
Per unit number and party.
Portal
For subcontractors.
Drawings
Revisions per unit number.
Products
Details and instructions.
Completeness
What is still missing.
Cases
For the municipality and the buyer.
Who we build software for the as-built file for the completion notification for
The software is intended for anyone who has to collect as-built information from many parties. The more unit numbers and subcontractors, the greater the benefit.
Main contractors
Many subcontractors. Requesting information matters most.
Property developers
Many homes. Working per unit number is key.
Installation companies
Installations and drawings. Submission matters.
Property managers
After handover. A complete 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 is about collecting as-built information. For the integration with the file for the competent authority, see our page on the Wkb integration, for handover in finishing work our page on the handover checklist app, and for installations our page on the as-built file for electrical engineering. You can read about our approach at building software.
Why Appfront for your software for the as-built file for the completion notification?
An installation drawing that is missing at handover, or a subcontractor who only submits after three reminders, holds up a completion notification and leaves a buyer without a manual. That is what we build on: information per unit number, subcontractors who submit it themselves, and a file that is complete before handover.
No chasing
Subcontractors submit it themselves.
Per unit number
Missing items are visible.
Complete on time
Before the completion notification.
Security and privacy in software for the as-built file at completion notification
The software holds project data, drawings and documents from multiple parties, and for homes, buyers' details. Access is set up per role and per project, a subcontractor only sees its own request, and every submission is logged with a time and a name.
The software runs in a European data centre, with encrypted storage and daily backups. We document the processing in a data processing agreement.
Frequently asked questions about software for the as-built file at completion notification
Questions that contractors and developers ask before getting started.
An as-built file records how a building was actually built: revised drawings, the products and installations used, warranties and maintenance instructions. It differs from the design, because things always change during construction.
Under the Dutch Building Quality Assurance Act (Wet kwaliteitsborging), the completion notification must be accompanied by a file for the competent authority, and the client receives a consumer file. Much of the information in it is as-built information from subcontractors. Which information is mandatory is something you determine together with your quality assurer.
Via a portal. Each subcontractor sees what is requested per project and unit number, submits drawings and documents, and sees what is still outstanding. Reminders go out automatically, so nobody has to chase.
For each unit number, it shows which information is needed and what has already been submitted and approved. An overview shows which unit numbers are complete and where something is still missing, well before handover.
Yes. The complete file can be sent to the system you use with your quality assurer and the competent authority, or to your document management system. We will look at which integrations exist in the first step.
Yes. For each unit number, the software compiles the file with the information the buyer or manager needs, such as maintenance instructions and warranties, and delivers it digitally.
Check that first. A document management system stores documents, but usually doesn't know what is needed per unit number or who has to supply it. Custom software makes sense if requesting and checking currently runs through email and folders.
Want the as-built file complete before handover?
Tell us which projects you build, which subcontractors submit information and where things go wrong at handover. We will show you what the software looks like.