Custom site app for product checks and sign-off on the building site
On-site verification remains necessary to confirm that a delivered product matches the specification and that the conditions of application are met. That check has one good moment: while the product is still on the pallet. After that it gets installed, and the question changes from checking to proving.
Why the moment on site matters
A KOMO certificate describes the performance in application and includes the conditions of application and the installation guidelines. Those conditions are not an appendix but the condition under which the performance applies. If the product is applied outside those conditions, the certificate no longer says anything about what is there.
On site there is little to back that up. The certificate sits in a folder or a mailbox, the product is outside, and the person installing it is not the person who read the document. The misconception that a product with only an attestation may carry the KOMO mark belongs in the same category.
What is available on site is the moment itself. On delivery you can still see which type has arrived, which batch is on it and whether that matches what was ordered and what the certificate covers. A photo of the label at that moment is evidence that can't be created later.
The same goes for installation. A condition signed off during application, with images, is something you can demonstrate. The same question after completion is a recollection, and when there is a defect, that makes all the difference.
How we build this
The core is delivery and installation. Two moments when someone is holding the product, and when recording costs less than reconstructing afterwards.
Type, batch and label against what was ordered and what the certificate covers, with a photo as evidence.
The conditions of application from the certificate appear as short checkpoints rather than as a document.
Whoever installs it signs off the points at the time, with location and timestamp.
The sign-off lands with the application in the project, where the accountability is built up.
What the app actually does
The check on delivery carries the whole thing. What else you need depends on your role and on how many subcontractors work on site.
Photograph the label and batch
A photo on arrival is quicker than retyping, and it stays on record as proof of what was delivered.
See the declaration alongside
Which certificate or approval covers this product, right on the device, without opening a folder that nobody has with them.
Conditions as short points
The application conditions are turned into points that someone wearing work gloves can sign off.
Works without signal
Basements, building cores and remote locations rarely have coverage. The app works locally and syncs as soon as there is a connection.
Escalate a deviation straight away
A different type from the one ordered, or a condition that cannot be met, goes straight to work preparation.
Location in the building
Where it was applied, so that a later question about a specific façade or floor has an answer.
Who we build for
Who carries out the check differs from project to project. Four situations.
Contractors
They are there when the lorry arrives and are the only ones who can still see what was actually delivered.
Work planners
They know the order and the declaration, but are not at the spot where the delivery is unloaded.
Quality assurers
They need traceability at the moment of application, not a reconstruction at handover.
Subcontractors
They do the installation and are the ones who have to meet the conditions in practice, often without having seen the approval.
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
Declarations are renewed, products get successors and conditions differ per approval. Checkpoints, product types and fields should be configurable rather than hard-coded in the app.
Why Appfront
The right moment is at the pallet
After that, checking is no longer possible and it becomes a matter of proving. We build the recording for that one moment.
Conditions must be readable on the scaffolding
An approval is a document; a checkpoint is an action. We translate one into the other.
The photo settles the argument
Type and batch on camera, with time and location, is the only evidence that still stands up six months later.
We do not inspect your work
The judgement stays with your quality assurer and the competent authority. We make sure that what has been established is also recorded.
Security and privacy
What is recorded on site contains supplier details and the names of the people who signed off. For subcontractors that is sensitive: signing off means taking responsibility. We set access per role and per project, show a subcontractor only their own work, and log who has viewed what. Data stored locally on the device is encrypted and can be wiped remotely if a phone is lost.
For this topic, the reliability of the moment is the whole point. A sign-off added after handover is no longer evidence when a defect turns up, but an extra problem. We record sign-offs immutably with time, location and person, even when synchronisation happens later, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.
Frequently asked questions about product checks on site
On-site verification is still needed to confirm that the delivered product matches the specification and that the application conditions have been met. The declaration says what should have arrived, not what did arrive.
The conditions under which the performance stated in the approval applies. They are set out in the approval itself, alongside the processing guidelines, and outside those conditions the declaration says nothing about what is stated there.
Because the product is still visible then. By handover it is built into the structure, and the question shifts from checking to proving that it was right at the time.
Yes. Basements, concrete cores and remote locations rarely have coverage. The app works locally and syncs as soon as there is a connection again, preserving the original timestamp.
Yes, and that is usually the intention. They see only their own work and the items they need to sign off. See our approach to building an app.
In the project file, under the application it belongs to. We describe that file on our page about KOMO software for projects.
Can you show which batch is in this façade?
Take one façade from a current project and ask for the type and batch of the product applied, with the date. If no photo turns up, then in the event of a defect the answer is a recollection. We build this as a standalone app and as part of a broader app development project.