A defect is quickly noted; what comes next is the hard part. It has to be assigned to the right party, given a deadline and tracked through to completion. If one step is lost, the evidence is missing in the end. Good defect management is therefore less a question of individual forms than of a continuous thread from the finding to acceptance.
The finding: specific, not blanket
It starts with a precise finding. What matters is specificity: where is the defect (location, component, trade), and what is the deviation from the target state, whether from the contract or from the accepted rules of technology? A blanket notice is usually not enough. A photo, a measured value and a clear location make the finding robust.
Notice and deadline
Anyone asserting a defect against the contractor requests rectification and sets a reasonable deadline. Under a VOB/B contract, the deadlines and forms of the VOB/B apply; otherwise the works-contract law of the BGB. The notice of defects should name the defect specifically, include the request and state the deadline, together with a reservation of further rights. Which basis applies in the individual case, and how to phrase it, belongs with a lawyer when in doubt; the following points are professional orientation, not legal advice.
Tracking: the status must stay visible
Between the notice and completion, it is decided whether defect management holds. Three things must be visible at all times:
- Status: open, in progress, done.
- Ownership: whose turn it is.
- Deadline: when it expires, and what happens if it is missed.
Plan-based location helps keep the overview; automatic deadline monitoring makes sure no date passes unnoticed. It is important that every finding stays linked to its origin, the site inspection report it came from.
Acceptance: the point with the biggest consequences
At acceptance, the threads come together. Defects noted are documented with a deadline for rectification, open items are named, and any reservation, for example of a contractual penalty, must be declared here. With acceptance the warranty period starts, the burden of proof reverses, and payment falls due. A clean acceptance protocol is therefore not a formality but a document with significant legal consequences.
The common thread pays off
The value does not arise in a single document but in the connection: finding, task, deadline, evidence, acceptance. Those who do not let this thread break not only save time in the end but also stand there with reliable evidence when in doubt. That is exactly what structured, continuous construction documentation is for, and why it is worth setting up defect management cleanly from the very first finding.