Use case · Issues and snags
An issue reported today should still be tracked tomorrow.
Document the observation on site, with its photos and your explanations. The issue stays visible until it is dealt with, and everyone knows who needs to act.

The problem
An issue seen on site quickly gets lost in messages.
A photo sent in a hurry, an “I’ll handle it” on the phone. A few days later, nobody knows whether the fix was done.
On-site scene · fictitious example
Under a sink, a plumber notices a corroded stop valve that is dripping. He sends a message about it. Two weeks later, nobody knows whether it has been replaced.
The consequences
- Issues forgotten between two visits.
- Snags discovered at handover.
- Discussions with nothing to settle them.
The KWALTOR journey
From finding to sign-off, the issue stays tracked.
You show, KWALTOR prepares, you check, and what follows stays linked to its origin.
1Show
Film the issue and explain what you see, on site.
2KWALTOR prepares
An observation is prepared: what was found, where, and what still needs checking.
3Check
You correct and confirm; the issue becomes an item to track.
4Follow up
Kontrol shows what is still open, who needs to act and what has been resolved.
The result
Issues stay visible between two visits.
- Every issue keeps its photos and its context.
- What is still open is visible to everyone who needs to act.
- The sign-off is documented too.
The proof, in the app


Other use cases
Book a demo
A reported issue stays visible until it is resolved.
We show you how an issue is documented, tracked and resolved, on a situation from your trade.
- An issue documented, tracked and then resolved.
- Who needs to act, and what is still open.
- No commitment.
