Custom software for KOMO certificates and attestations applied in projects
A KOMO attest describes the performance of a building product in its application, and it does so under conditions. That is where the work lies: not in whether a product has a declaration, but in whether what happens with it in this project falls within the conditions under which that performance was established.
What a declaration does and doesn't tell you
A KOMO product certificate declares that the product conforms to the technical specification in the certificate and meets the stated requirements. A KOMO attest goes a step further and describes the performance of a building product, building element or building system in its application. There are also the attest-with-product-certificate and the process certificate. Quality declaration is the umbrella term for all of these documents.
An attest contains the technical specification, the building parts in which the product can be used, the performance requirements, the performance in the application, the conditions of application and the processing guidelines. The assessment is a one-off type assessment that is repeated at least every five years. Products with only an attest may not carry the KOMO mark.
Two things follow directly from this for the building site. Verification on site remains necessary to confirm that the delivered product matches the specification and that the conditions of application have been met. A declaration in a folder does not replace that check.
The underlying regulations are also changing. Certification bodies issue attests on the basis of the Besluit bouwwerken leefomgeving (Building and Living Environment Decree) from its entry into force, and for attests-with-product-certificate and process certificates, converting to it is mandatory. A declaration from an older series therefore does not automatically say what you think it says.
How we build this
The core is the application. Not the product and not the certificate, but the combination: this product, in this building part, in this project, on this date.
Certificate, attest or both, with the number, the body and the validity period as they appear on the document.
Where the product has been used and in which building part. That determines whether the attest covers the situation.
The conditions of application and processing guidelines from the attest are set as checkpoints for that application.
Not whether a declaration is valid now, but whether it was valid at the moment of application. That is the question that comes back later.
What the software actually does
The link between application and declaration holds everything together. What else you need depends on your role and on the number of projects running at the same time.
Declaration per applied product
Which document covers this product here, with its number and issuing body. Not one folder per project but one line per application.
Distinguishing between types
A product certificate says something different from an attestation. The system shows which type you hold and what it does and does not cover.
Application conditions as checkpoints
The conditions in the attestation become points that someone signs off, instead of text that nobody opens.
Validity on the application date
Expired certificates are rarely the problem. Certificates that had already expired on the construction date are.
Tracking reassessments
An attestation is reassessed at least every five years. The system shows which certificate is due for that.
A file per project
What was applied, under which certificate and with which sign-off, in the form in which a client or regulator asks for it.
Who we build for
Who asks for this differs per project. Four situations.
Contractors
They apply the product and have to show afterwards on what basis. Usually with suppliers who change themselves, too.
Clients
They want to know whether what was delivered matches what was agreed, without having to dig through the documents themselves.
Quality assurers
For them the question is not whether a certificate exists, but whether the application falls within its conditions.
Building control
They assess the file and benefit from an overview that shows the route from product to certificate.
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
Certificates are renewed, regulations shift and products are replaced by successors. Document types, conditions and checkpoints should be configurable rather than hard-coded.
Why Appfront
Holding a certificate is not the same as complying with it
The attestation applies under conditions. We turn those conditions into points that someone signs off.
The date of application counts
Not whether a certificate is valid today, but whether it was valid when the product went into the façade.
On-site verification is still needed
A document does not replace the check on site. We build that check into the process rather than alongside it.
We do not assess your building
The judgement stays with your quality assurer and the competent authority. We make sure the file underneath it is correct.
Security and privacy
A project file contains supplier details, prices in appendices and the names of the people who signed off. Not all of that should reach everyone. We set up access per role and per project, give a client insight into the accountability without your full procurement file, and log who has viewed what. Integrations run through secure connections to your existing software.
For this subject, the reliability of the moment is the point. A sign-off added after completion is no longer evidence when a defect arises. We record sign-offs immutably with time and person, and make a correction a visible correction alongside the original line. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about KOMO certificates in projects
A product certificate declares that the product conforms to the technical specification and meets the stated requirements. An attestation describes the performance of the product, element or system in its application, under the application conditions set for it.
The technical specification, the building elements in which the product can be used, the performance requirements, the performance in application, the application conditions and the installation guidelines.
The assessment is a one-off type assessment that is repeated at least every five years. In addition, certificates have been converted to the Besluit bouwwerken leefomgeving (Dutch Building Decree), so an old certificate does not necessarily say the same thing.
No. Products for which only an attestation has been issued may not carry the KOMO mark or logo. This is a common misunderstanding on construction sites.
On-site verification is still needed to confirm that the delivered product matches the specification and that the conditions of use have been met. We describe that check on our page about the KOMO app for the construction site.
No. This is about application and accountability. We describe the production file under your own assessment guideline on our page about certificate management and BRL files.
Was the declaration valid on the day you applied the product?
Take one product from a project last year and find its declaration, with the validity on the day of application and the conditions that came with it. If that takes half a day, a defect will cost you more. We build this as a standalone application and as part of a broader software development project.