Custom site app for product checks and sign-off on the building site
On-site verification is still needed to confirm that a delivered product matches the specification and that the conditions of use are met. That check has one good moment: while the product is still on the pallet. Once it has been processed, the question changes from checking to proving.
Why the moment on site matters
A KOMO certificate describes the performance in the application and includes the conditions of use and the processing guidelines. Those conditions are not an appendix but the condition under which the performance applies. If it is applied outside those conditions, the declaration no longer says anything about what is in place.
On site, little stands behind that. The declaration sits in a folder or an inbox, the product is outside, and the person who processes it is not the one who read the document. The misconception that a product with only a certificate may carry the KOMO mark belongs in that list too.
What is on site is the moment. At delivery you can still see which type has arrived, which batch is marked on it, and whether that matches what was ordered and what the declaration covers. A photo of the label at that moment is the evidence that cannot be recreated later.
The same applies to processing. A condition signed off at the moment of application, with a photo, is provable. The same question after handover is a reminder, and in the event of a defect, that is the difference.
How we build this
The core is delivery and processing: two moments when someone has the product in hand, and when recording costs less than reconstructing afterwards.
Type, batch and label against what was ordered and what the declaration covers, with a photo as evidence.
The application conditions from the certificate appear on screen as short checkpoints, rather than as a document.
Whoever applies the product signs off the checkpoints at the time itself, with location and timestamp recorded.
The sign-off reaches the application record in the project, where the accountability is built up.
What the app does in practice
The delivery check carries the whole process. What else you need depends on your role and on how many subcontractors are working on site.
Photographing label and batch
A photo on arrival is quicker than retyping and leaves evidence of what was delivered.
Seeing the declaration alongside
Which certificate or attest covers this product, directly on the device, without opening a folder that nobody has with them.
Conditions as short points
The application conditions are translated into points that someone wearing work gloves can sign off.
Works without signal
Basements, villages and remote locations rarely have coverage. The app works offline and synchronises as soon as there is a connection.
Escalating deviations straight away
A different type from what was ordered, or a condition that cannot be met, goes directly to the works planning team.
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 varies by project. Four situations.
Executors
They are present when the lorry arrives and are the only ones who can still see what has actually been delivered at that point.
Planning engineers
They know the order and the declaration, but are not at the place where it is unloaded.
Quality assessors
They need provability at the moment of application, not a reconstruction at handover.
Subcontractors
They apply the product and are the ones who have to meet the conditions in practice, often without having seen the certificate.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
Declarations are renewed, products get successors and conditions differ per certificate. Checkpoints, product types and fields should be configurable and not hard-coded into the app.
Why Appfront
The right moment is at the pallet
After that, checking is no longer possible and it becomes proving. We build the recording for that one moment.
Conditions must be readable on the scaffold
A certificate is a document; a checkpoint is an action. We translate the one into the other.
The photo settles the debate
Type and batch on photo, with time and location, is the only evidence that still holds up half a year later.
We do not judge your work
The judgement remains 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. With subcontractors that is sensitive: signing off means accountability. We set access by role and by project, show a subcontractor only their own work, and log inspection. What is stored locally on the device is encrypted and can be wiped remotely if a phone is lost.
On this topic, the reliability of the moment is the key point. A sign-off added after handover is no longer evidence in the event of a defect, but a problem in itself. We record sign-offs in an unalterable way, with time, place and person, even when synchronisation happens later, and any correction appears as a visible amendment alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about product inspection on the construction site
On-site verification is still needed to confirm that the delivered product matches the specification and that the conditions of application have been met. The declaration states what should be delivered, not what has actually been delivered.
The conditions under which the performance stated in the certificate applies. They are set out in the certificate itself, alongside the processing guidelines. Outside those conditions, the declaration says nothing further about what is stated.
Because the product is still visible at that stage. By handover it is hidden within the structure, and the question shifts from checking that it is correct to proving that it once was.
Yes. Basements, concrete cores and remote locations rarely have coverage. The app works locally and synchronises as soon as a connection is restored, keeping the original timestamp.
Yes, and that is usually the point. He only sees his own work and the items he needs to sign off. See our approach to getting an app built.
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?
Pick one facade from an ongoing project and ask for the type and batch of the product used, with the date. If no photo exists, the answer to a defect is a reminder. We build this as a standalone app and as part of a wider project to get an app built.