One defect described as "fix plaster by the window" can mean three different locations, two contractors, and several hours of searching for information. That's exactly why the question how to keep a defect log is not just about a form or table. It's about the way your team establishes facts, assigns responsibility, and confirms that a defect has actually been removed.
A well-maintained defect log organizes the process from reporting, through repair, to confirmed closure. On a construction site, during apartment handover, safety audit or technical inspection, there is no room for guessing. Each entry should answer simple questions: what is non-compliant, where exactly is it located, who will carry out the correction, by when, and who will confirm its completion.
What is a defect log in practice?
A defect log is a register of defects, faults, deviations from design, specification, execution standard or safety requirements. It doesn't have to be limited to construction work only. You can register documentation gaps, equipment damage, installation irregularities or shortcomings found during safety inspections in the same way.
Its value doesn't lie in the number of entries alone. The log should enable action to be taken without additional phone calls and arrangements. The person receiving a report should immediately know what the problem concerns, in which apartment, room or part of the building it occurs, and what the expected result of the correction should be.
In practice, the log may be kept in an Excel spreadsheet, on paper protocols or in a defect management system. Any of these variants can work if the rules are consistent. The difference appears with a larger number of apartments, trades and contractors. Then separate photos, messages and successive versions of files quickly cease to form a reliable register.
How to keep a defect log step by step
The most effective model is simple: one report means one specific non-compliance. Don't combine several defects in one entry just because they occur in the same room. "Scratched window, missing sealant and uneven grout in the bathroom" are three different tasks, often for different people and with different completion deadlines.
1. Assign each defect a unique number
Each entry should have a unique identifier. This makes discussions at meetings, report exchange and subsequent work billing easier. Instead of saying "that defect on the third floor", you can indicate the report number, object and location.
Numbering can be automatic or set according to an adopted scheme, for example project-year-sequential number. What matters more than the format is that the number is not changed and not reissued after closing the previous entry.
2. Indicate the location so there is no doubt
The description "stairwell B" is rarely sufficient. Good location includes the building, floor, apartment or zone, room and the element the defect concerns. Example: "Building 2, stairwell B, floor 4, apartment 4.12, bathroom, wall by the installation riser".
For handovers and large investments, marking the point directly on the current floor plan is particularly useful. A photo shows the problem, but often doesn't allow you to recreate its location after several weeks. A point on the plan shortens the crew's route to the defect and limits disputes over the scope of work.
3. Describe the actual condition, not interpretation
The description should be brief, but technically useful. Instead of writing "poorly done", record what exactly was found: "visible crack in GK board above the frame, length approximately 40 cm" or "missing sealant at the junction of the shower tray and wall".
If you know the requirement, indicate it in the report: design documentation, apartment standard, technical specification, agreement with the investor or regulation. However, it's worth separating fact from decision. First you register the non-compliance, then you determine how to remove it or who should approve the method.
4. Add documentation that allows you to assess the problem
Photos are essential, but their quality matters. It's worth adding one wide-angle shot showing context and one or two close-ups of the defect. For damage, scratches and deviations, a measuring tape, spirit level or other reference point will be helpful.
Don't document everything with photos as backup. The material should confirm a specific entry. An excess of random photographs makes subsequent handover difficult, especially when an inspector or investor wants to quickly check the history of a given report.
5. Assign responsibility and deadline
A defect log without task ownership becomes a list of observations. Each entry should have an assigned contractor, crew or person coordinating the removal of the defect. In the case of multi-trade work, it's also worth indicating the person responsible for resolving the order of work.
The deadline should be realistic and result from the schedule and technological dependencies. Not every defect can be closed immediately. A missing vent can be removed quickly, but improving insulation after cladding is completed may require a design decision and additional scope of work. This should be noted in the log, rather than repeatedly postponing the deadline without explanation.
Establish statuses that reflect the actual process
The most common mistake is treating "closed" status as information that the contractor declares work completion. A declaration is not yet confirmation of quality. The log should separate correction completion from its verification.
In most projects, the following statuses are sufficient: new, assigned, in progress, submitted for inspection, accepted as closed, and rejected for re-work. You can add a "suspended" status if the defect requires a designer's decision, material delivery or arrangements with the investor.
Key is to establish who can change the status to final. Usually the contractor can mark the task as ready for inspection, while closure remains with the site manager, inspector, the person receiving the apartment or another authorized participant in the process. This separation protects both parties: the contractor has a record of the repair report, and the receiver maintains control over quality.
Keep a history of changes and decisions
On a construction site, disputes often don't concern the defect itself, but the question: who, when and on what basis made the decision. That's why it's worth registering the date of report, author, status changes, comments, new deadlines and documentation before and after repair with each entry.
The history matters also when a report is deemed unjustified or excluded from the scope of a specific contractor. Instead of deleting the entry, it's better to keep it with a clear justification of the decision. Removing data may "clean up" the list for a moment, but later makes it difficult to defend your position during billing or final handover.
Adapt the form of the log to the team, not the other way around
Full digital work is convenient when contractors update statuses in the app and immediately add photos after repair. Not every project works this way though. Some crews still prefer a readable PDF report, and management may need an Excel summary for a meeting or billing.
This is not a process flaw, as long as the data source remains one. The worst variant is keeping several independent lists in parallel: one by the inspector, another by the general contractor and a third by the subcontractor. Differences in numbers, statuses and deadlines appear almost immediately.
A system like FixControl allows you to keep a report in the field on a floor plan, attach photos and description, then pass information to the contractor in the app or as an organized report. This is practical where the level of digitalization of investment participants varies, but everyone needs the same, unambiguous data.
Monitor the log at meetings and before handover
The defect log should work together with the team, not be updated only before handover. At regular meetings, it's worth analyzing primarily overdue entries, tasks ready for verification, recurring non-compliances and points blocking subsequent work.
Before final handover, filtering by object, trade, contractor, status and date is useful. This allows you to quickly check if open items remain on the list and whether closed reports have documentation confirming problem removal. A low percentage of open defects alone is not enough if among them are defects critical to safety, usability or apartment handover.
A well-maintained defect log doesn't increase bureaucracy. It replaces ambiguous phone calls, photos without addresses and spreadsheets circulating among construction participants. When each report has a location, owner, deadline and confirmed history, the team can focus on removing defects, not establishing what the correction was actually about.