DIRECT ANSWER
A non-conformance report is closed when the corrective action has been completed, verified against the requirement and recorded with photographic evidence and a sign-off. The reason defects go missing is rarely that nobody fixed them. It is that closure is the only stage of the process that produces a record, and it is the stage most often skipped. A year later, an open NCR and one closed without evidence look exactly the same: an unanswered question about the structure.
Raising a defect is easy — anyone with a phone can photograph a problem. Fixing it usually happens. What fails, systematically, is proving the fix happened to the thing that was broken.
What Is an NCR in Construction?
DEFINITION
A non-conformance report (NCR) records work that does not meet the approved drawings, the project specification, the inspection and test plan or the applicable standards. It identifies the element and location, describes the non-conformance, carries evidence of the condition found, states the corrective action taken, and is closed only when that action has been verified and recorded. A construction defect log is the running record of all such reports — open, in progress and closed — against a project. The NCR documents the deviation; it does not decide the remedy, which is an engineering judgement.
Why Defects Reported on WhatsApp Disappear
A CHAT THREAD HAS NO CLOSED STATE
A photograph sent to a site group can be seen, replied to and acted on. What it cannot do is close. There is no moment at which the thread records that the work was corrected, by whom, verified against what, with the proof attached. So defects raised informally are rarely refused — they are buried by the next two hundred messages, and three months later nobody can say whether that column was ever attended to.
Notice which stage this exposes. Raising a defect produces a problem. Fixing it produces a repair. Only closure produces an asset — a record that the repair happened to that element. That record is what a client, an auditor or a buyer asks for, and it is the one output that informal reporting structurally cannot generate. A defect log that counts closures without requiring evidence is measuring activity, not resolution.
The NCR Lifecycle
- Detection. The non-conformance is identified, during a planned inspection or in the course of work, and compared against the requirement it fails.
- NCR creation. The report is raised against a specific element and location, with photographs of the condition as found and a description of what does not conform.
- Corrective action. The remedy is assessed and approved by qualified professionals, then carried out and documented. Root cause is recorded so the same defect can be prevented rather than merely repeated and repaired.
- Verification. The completed work is checked against the requirement by someone competent to judge it — not by the person who carried it out.
- Closure. Photographic evidence of the completed fix is attached to the same NCR and signed off. Until that exists, the NCR stays open regardless of what was done on site. What Fields Does an NCR Need? Copy this structure into your own defect log. The fields are deliberately plain — what makes a log usable is that every entry has all of them, not that any one field is clever. Field What goes in it Why it matters later Defect ID Unique reference Lets the record be found and cited Date raised Date of detection Establishes the timeline Project Project name or code Separates records across sites Location Grid, level, zone Says where, unambiguously Construction element Column C4, Slab L2, Beam B7 Ties the defect to a thing, not a photo Defect description What does not conform, and to what Names the requirement that was missed Before photographs Condition as found The evidence that cannot be recreated Root cause Why it happened The only field that prevents recurrence Corrective action What was approved and done Shows the remedy was decided, not improvised Verification evidence After photographs of the same element Proves the fix reached the defect Sign-off Who verified, and when Makes the closure attributable Closure status Open / in progress / closed The field people forget to update
The two highlighted rows are the ones most often left blank. Without root cause you repair the same defect repeatedly; without verification evidence you have a closure nobody can check.
Manual NCRs vs Automatic NCRs
A manual NCR depends on someone deciding the defect is worth writing up — which means marginal items, and items found under time pressure, are the ones that go unrecorded. An automatic NCR is raised by the system when a quality check is failed, so the record exists the moment the fail is entered. The difference is not speed. It is that the decision to create a record is no longer a judgement made by the person who is busiest.
Three Ways Teams Track Defects
The case for construction defect tracking software is not that it reports faster — a photograph sent on a phone is already instant. It is that the record is created whether or not anyone decides to create it, that it attaches to an element rather than to a conversation, and that it cannot be marked closed without the evidence. Those three properties are what separate a defect log you can rely on from a list of things people remember.
Informal (chat, calls)
Manual NCR register
Software-supported
Record created
Only if someone writes it up
If someone fills the form
Automatically when a check fails
Tied to element
No — tied to a message
By text description
To the element and location
Before evidence
In the chat, undated in practice
Printed or filed separately
Attached to the NCR
Closure proof
Usually absent
Often a signature only
Photographic evidence required
Open items visible
By scrolling and asking
By reading the register
Live defect log
Finds recurrence
Almost never
Only if someone reviews it
Comparable entries make patterns visible
Worked Example: Honeycombing on a Concrete Column
Honeycombing — voids where coarse aggregate has not been fully surrounded by mortar — is found on a column after de-shuttering. Here is the record it should generate.
Defect ID / date
NCR-014, raised on the day of detection
Element & location
Column C4, ground floor, grid B-3
Description
Honeycombing observed on the north face after de-shuttering; extent and depth recorded
Before photographs
Close and contextual images showing the affected area and its position on the column
Assessment
Referred to the structural engineer to determine severity and whether the defect is surface or structural
Corrective action
Remedy specified and approved by the qualified professional, carried out as directed and documented
Root cause
Recorded — for example a compaction, formwork or mix-related cause identified by the team
Verification
Checked against the approved remedy by someone other than the person who carried it out
Closure evidence
After photographs of the same column face, attached to NCR-014, with sign-off
Status
Closed — with both before and after images held against the element
NO UNIVERSAL REPAIR METHOD
This article deliberately does not prescribe how to repair honeycombing. The appropriate remedy depends on the extent and depth of the defect, whether reinforcement is exposed, the structural role of the member and the project specification. A shallow surface blemish and a void reaching the reinforcement are different problems with different consequences. The assessment and the method must be made and approved by a qualified structural engineer against the approved drawings, specification and applicable standards. The NCR records what was found, what was approved and what was done — it does not decide the remedy.
Monitoring Open NCRs and Spotting Patterns
Review open items by age rather than by count. Twenty NCRs raised this week is ordinary; one raised eleven weeks ago and still open is a problem, and a long list hides it. Set a cadence, look at the oldest items first, and ask what is blocking each one.
Recurrence is the second reason a log earns its keep. The value of a defect log is rarely the first occurrence — it is the second. Three honeycombing NCRs on three different columns in a chat thread look like three conversations. In a structured log, recorded against elements in a comparable way, they look like what they probably are: a pattern in the pour or compaction process that will keep producing defects until the cause is addressed. That is what the root cause field is for, and it is the field most often left blank.
Where defects are held against a model rather than a list — the approach behind digital twin construction — that pattern is easier still to see, because open items appear on the part of the building they belong to instead of in a register that has to be read line by line.
How a Defect Workflow Works in Practice
In construction quality management software such as BuildiyoQC, defects are raised with photographs and location details, and an NCR can be raised automatically when a quality check fails — so the record begins at the moment of the fail rather than when someone finds time to write it up. Closure requires photographic evidence of the completed fix together with sign-off, which is the control that stops an NCR being marked done without proof. A live defect log supports tracking across the project. The published listing for the Buildiyo QC mobile app download also describes photographs stamped with location and time, and work continuing without signal with syncing on reconnect. Confirm any behaviour you intend to rely on against your own workflow, and remember the software governs the record rather than the engineering. To talk through how your inspection and test plan would map onto this, Contact Buildiyo.
WHAT THE SOFTWARE DOES NOT DO
It does not assess a defect, decide a remedy, or certify that a repair is adequate. Those are engineering judgements made by qualified people against the approved drawings, specification and standards. What the workflow changes is whether the decision and its evidence survive — and in a dispute, surviving evidence is the whole argument.
Frequently Asked Questions
What does NCR mean in construction?
NCR stands for non-conformance report. It records work that does not meet the approved drawings, specification, inspection and test plan or applicable standards, and tracks it through corrective action, verification and formal closure.
What are common construction defects raised as NCRs?
Typically honeycombing and surface voids in concrete, reinforcement placement or cover not matching the drawing, misalignment or out-of-plumb work, cracking, water ingress and waterproofing failures, and services installed outside the approved layout. What makes any of them an NCR is the deviation from a stated requirement, not the appearance of the defect.
What fields should a non-conformance report contain?
Defect ID, date raised, project, location, construction element, defect description, before photographs, root cause, corrective action, verification evidence, sign-off and closure status. A log is only usable when every entry carries all of them.
Can an NCR be raised automatically?
Yes, in a system configured for it. In BuildiyoQC an NCR can be raised automatically when a quality check fails, so the record exists from the moment of the fail rather than depending on someone finding time to write it up afterwards.
Why are photographs required to close an NCR?
Because a signature records an opinion while a photograph records a condition. Closure needs an image of the completed fix on the same element as the before image, so that anyone reviewing the file later can see what was found and what it became without taking anyone’s word for it.
Who should verify a corrective action?
Someone competent to judge it against the requirement, and not the person who carried out the work. Self-verification is the most common weakness in defect tracking and the hardest to defend afterwards.
How do I close an NCR?
Complete the approved corrective action, have it verified against the requirement by a competent person, attach photographic evidence of the completed fix to the same NCR, record the sign-off, and only then mark it closed. If the evidence is missing, the NCR is not closed — it is merely untracked.
How do I identify recurring defects?
Record defects against elements in a consistent structure and complete the root cause field. Patterns only become visible when entries are comparable — three similar defects in a chat thread read as three incidents, while three similar entries in a structured log read as a process problem.
Closure Is the Deliverable
Construction defect tracking is often treated as a reporting exercise, which is why so much of it stops at the photograph of the problem. The useful output is at the other end: a closed record showing what was found, what a qualified professional approved, what was done, who verified it and what it looked like afterwards. That record is the only part of the process anyone will ask for in a year, and it is the only part a chat thread cannot produce. Give every defect an ID and an element, insist on the root cause and the after photograph, review open items by age, and treat an NCR without closure evidence as what it is — still open.
Top comments (0)