Defect Management with Context: Linking, Not Searching
You document a defect on Monday. On Wednesday the subcontractor asks for the photos. On Friday someone’s looking for the notes from the meeting. Each piece of information exists somewhere. But nowhere together.
This isn’t an organization problem. It’s a structural one: photos, notes, tasks, and defects are stored as isolated data points, with no connection between them. The moment someone needs the full context of a defect, the search begins.
Defects and tasks in kontekst solve exactly that. Defects and tasks are available with version 1.7.0. → See full release notes
The Problem: Information Without Connection
During the site walk: You spot concrete damage, photograph it, log the defect. Three weeks later the subcontractor asks: “Which photos go with this? What was discussed in the meeting?” The search begins: through photo folders, notes, protocols. With some luck you end up with everything.
With the defect list: The defect list is complete, the photos are there, the comments from coordination meetings too. But they’re spread across three different places. Bringing them together takes longer than the actual work.
Years later: Property management reports a façade issue. During construction, everything was documented: structural details, material specs. But where exactly? The search through old project folders begins.
The core problem isn’t that information is missing. It’s there, just not connected.
Linking Instead of Attachments: What’s Different in kontekst
Often it works like this: you create a defect, attach a photo as a file, assign a person. When a photo only hangs off an entry as a file attachment, it exists only there. If you find the same photo later in your photo folder, you won’t know which defect it belonged to.
kontekst works differently. Every element (photo, note, task, defect) stays an independent, findable object. At the same time it can be linked to any number of other objects. From a photo to a defect. From a defect to a note. From a note to another photo. In every direction.
These links are the foundation of kontekst. Everything else builds on them.
A single photo can be linked to a defect, a task, and a note at the same time, without being copied. Every photo stays findable in your photo database. At the same time it’s connected to all relevant workflows.
Defects and Tasks: Where Everything Comes Together

A defect or task bundles exactly one process. Everything that belongs to it gets linked there: photos and notes. On the plan, the defect is pinned in place.
For example:
- A defect: “Concrete spalling, 3rd floor, column B12”
- A task: “Fix electrical wiring, room 3.12”
- A coordination task: “Clarify façade connection to building services”
- A point on the defect list for handover
From any element you move to the next, no searching required.
You also link defects and tasks to each other in the browser. That way you group the defects from a site walk, record which defect waits on another, record a recurring defect again, or mark a duplicate. In the app you see these links on the defect.
What This Looks Like in Practice
Document a defect and track it end to end
During a site walk you spot concrete damage on a column.
-
Create the defect: In the kontekst lens app you create the defect: “Concrete spalling, 3rd floor, column B12”.
-
Link the photo: You photograph the damage and link the photo to the defect. If you choose the defect before taking photos, new photos are linked to it automatically.
-
Add context: Later you add a note: “Checked with structural engineer on 15/01, reinforcement exposed, no load-bearing risk.” You link this note to both the photo and the defect.
-
Document the fix: After the repair you photograph the result. You link this photo to the same defect too.
The complete history of a defect in one place. Before photos, notes from coordination, after documentation. When someone asks, you open the defect instead of searching folders.
Create a task and link a site photo
During a site walk you document an incorrectly routed electrical installation.
-
Create the task: “Fix electrical wiring in room 3.12, route according to plan.”
-
Link the photo: Room 3.12, wiring not routed according to plan. You link the photo to the task.
-
Assign: You assign the task to the responsible electrician. The linked photo is attached right there, no lengthy explanations needed.
-
Document the progress: Notes and further photos after the correction. Everything linked to the same task.
The whole team sees the trail. From the first photo through notes to the final documentation. Every person involved has the full context immediately.

Beyond the Defect: Securing Building Knowledge
Defects and tasks work across the entire project lifecycle, not just during construction.
Suppose a facility manager takes over the building five years after construction is complete. A façade issue comes up. He filters by the tag “façade” and finds the photos from the construction phase, linked to defects and notes and pinned on the plan. Structural details are stored as documents in the same project.
Construction-phase information often gets lost over the years. When it is linked in the same project, it stays findable.
More Use Cases
Example scenario: water infiltration across multiple storeys
Suppose a refurbishment project has recurring water ingress across several storeys. The project manager creates a task “Water infiltration” and links all photos and notes from different inspections. They assign the defects on each storey to the task and see there how many are already done. When the planning team requests the documentation, everything is already connected: photos from several storeys, notes from several inspections, available to everyone on the team.
Instead of searching folders, you open the task.
Defect tracking through to handover
Every defect is logged on its own. During the owner walkthrough the site manager can show the history of each defect item: from identification through notes and photos of intermediate steps to the final resolution. That way he goes into handover well prepared.
Ready to rethink defect management?
The kontekst lens app works offline, kontekst is hosted in Germany, and it runs on iOS, Android, and in the browser. Document on site as you always have and link what belongs together.
Next steps: