De-shutter a column on a Tuesday, find honeycombing at the beam junction, and watch what happens next. A photo lands in the WhatsApp group. Three people call each other. The subcontractor says the concrete was late; the pump operator blames the mix. By Friday nobody remembers who agreed to what — and the repair happens without an approved method statement.
Quality issues are not rare events on Indian sites. They are part of daily execution. What decides your profit and reputation is how quickly you detect, document, fix and prevent them.
That is exactly what an NCR — a Non-Conformance Report — is for. And it is why so many contractors now search for NCR management software construction teams can actually use from the field, not just from the head office.
What is an NCR in construction?#
An NCR (Non-Conformance Report) is a formal record raised when work, material or a process does not meet the approved drawing, specification, IS/CPWD requirement, method statement or agreed quality standard.
It is not extra paperwork. Done right, it is a control mechanism: a traceable record of what went wrong, a defined disposition (repair, rework, replace, or accept-as-is with approval), a named owner with a due date, evidence of closure, and a lesson fed back so the same issue does not repeat next month on the next floor.
Common NCR triggers on Indian sites#
- Concrete and reinforcement: honeycombing, cube failures, cover issues, bar spacing or lapping mismatch
- Formwork and alignment: column out of plumb, slab level mismatch, camber not maintained
- Waterproofing: ponding test failure, leakage at sunken slab, improper screed slopes
- Finishes: tile hollowness, plaster cracks, paint shade mismatch, undulations
- MEP and materials: wrong sleeve location, inadequate supports or earthing, unapproved make, missing MTC/TC
NCR vs snag list vs RFI#
| Item | What it is | When it's used | Typical owner/PMC expectation |
|---|---|---|---|
| NCR | Non-conformance (deviation from approved requirement) | When the work or material is not as per spec or drawing | Formal workflow plus evidence of corrective action |
| Snag/Punch | Finishing defects or incomplete items | Near handover or milestone completion | Faster close-out list, often less formal |
| RFI | Request for clarification | When drawings or specs are unclear or conflicting | Clear question plus documented response |
Why NCRs feel harder on Indian construction sites#
The difficulty is rarely the form. It is the terrain. Multiple subcontractors and thekedaar layers blur accountability — everyone did the work, nobody owns the defect. Drawings revise faster than prints reach site, especially in interiors and MEP. Procurement pressure forces availability-based substitutions. And approvals sit split across owner, PMC, architect, consultants and vendors, each expecting their own documentation for billing.
Handle NCRs informally — calls and chats — and two things follow, reliably. The same defect repeats, and closure proof vanishes right when you need it for an audit or a bill.
What to look for in NCR management software for construction#
If you are evaluating NCR management software construction teams can adopt quickly, judge it on field usability and traceability. Not dashboards.
1) Fast NCR capture from site#
A mobile form that works offline or on weak network. Photos with markups and clear location tagging. A reference to the right drawing revision or spec clause, right there on the form.
2) Clear ownership and due dates#
Assign to a person or role, set target dates, escalate ageing NCRs. Keep containment action separate from corrective action. Statuses should stay simple: Open, Actioned, Verified, Closed.
3) Evidence, approvals and CAPA#
Attach test reports and MIR/WIR records, generate a shareable NCR PDF, keep an audit trail. And capture root cause, corrective action and preventive action — the part that stops the repeat.
4) Insights and integration#
Ageing, repeat issues, defect hotspots, subcontractor scorecards. Links to checklists, inspections, tasks and drawings, so actions cannot quietly fall between tools.
A practical NCR workflow for Indian sites (7 steps)#
This works for residential towers, villas, warehouses and infrastructure packages alike. Keep it simple and repeatable.
Step 1: Detect and contain (same day)#
Stop the non-conformance from getting worse. Barricade or hold further work in that location, mark the area clearly — paint, tag, or a plain HOLD sign — and inform the supervisor, QA/QC and the subcontractor.
Step 2: Record the NCR (10 minutes if your form is right)#
Minimum fields:
- NCR number, date, raised by
- Project and location (tower/floor/flat or chainage)
- Trade (civil, finishes, MEP)
- Reference: drawing number and revision, or spec clause
- What is wrong, in plain words
- Photos, plus test report reference if any
Step 3: Classify and assign ownership#
Set severity — Minor or Major, defined once for your company, not re-argued per NCR. Name the owner: subcontractor, vendor, site engineer or QA. Set a due date for the initial response.
One tip that pays off: make the responsible party a role ("shuttering contractor supervisor") plus a named person. Accountability then survives staff changes.
Step 4: Decide disposition, with the required approvals#
The usual options: rework (redo as per spec), repair (correct without full redo, still meeting acceptance criteria), replace the material or component, accept-as-is with written consultant or PMC approval, or reject and remove. Accept-as-is without the written approval is not a disposition — it is a future dispute.
Step 5: Do a quick root cause analysis#
Even five minutes helps. Why did it happen here? Which control failed — the inspection, the checklist, the drawing revision, the material batch?
Step 6: Corrective and preventive actions#
Corrective action fixes this NCR. Preventive action changes something so it does not repeat: a new checklist point ("verify cover blocks before pour"), a hold point added to the ITP, a toolbox talk or method refresher for the crew on bar spacing, shutter joints or curing.
Step 7: Verify and close, with evidence#
Before closing, confirm the work now meets the acceptance criteria per spec and drawing, the after-photos and any re-test evidence are attached, and the approver — PMC or consultant where required — has signed off.
Practical examples from Indian construction sites#
Three scenarios where a proper NCR trail saves time and, more importantly, arguments.
Example 1: Honeycombing on a column after de-shuttering#
What happens: The column shows honeycombing near the beam-column junction.
Containment: Stop further finishing in that zone; assess structural impact.
The NCR record should include: the location (Tower B, 7th floor, grid B-4), photos with the honeycombed area marked, and references to the concrete spec, cover requirement and shuttering checklist.
Disposition: Typically repair — polymer mortar or micro-concrete — under a consultant-approved method statement.
Corrective action: Repair per the approved procedure, then curing and inspection.
Preventive action: Add "tighten shutter joints, eliminate leakage points" to the checklist; control vibration method and spacing during the pour; verify slump and segregation risk at delivery.
How software helps: The defect photos, repair method statement and consultant approval stay attached to the NCR forever. And if the same crew keeps producing repeats, the dashboard says so before your P&L does.
Example 2: Toilet waterproofing ponding test failure#
What happens: After waterproofing, the ponding test shows leakage to the slab below.
Containment: Stop tiling and all finishing until the source is fixed.
The NCR record should include: test start and end times, a water-depth photo, the leakage photo from below, and the waterproofing system details — product, batch, applicator crew.
Disposition: Rework. Remove the layers, redo the waterproofing, retest.
Corrective action: Redo with correct surface prep, corner treatment and curing.
Preventive action: Add hold points for surface moisture check and corner fillet inspection; train the crew on detailing at pipe penetrations and traps.
How software helps: The ponding evidence lives on the NCR, and you can enforce a hard rule — no tiling task can be marked done until this NCR is closed.
Example 3: Wrong sleeve location for an MEP shaft#
What happens: The sleeve is cast in the wrong position; later, someone requests core cutting.
Containment: Freeze further work and coordinate with the structural consultant.
The NCR record should include: a marked drawing snapshot showing the correct sleeve position, and a site photo with a measurement reference.
Disposition: Repair or accept-as-is, depending on structural impact. Core cutting is never the default; it needs approval.
Corrective action: Implement the approved rectification and update the as-built.
Preventive action: Put "MEP sleeves verified and signed by civil plus MEP" on the pre-pour checklist, and keep the latest drawing revision in one place so old prints stop circulating.
Best practices that make NCRs easier to close#
Write the NCR in plain language — what, where, how much deviation. Always reference the approved requirement: the drawing revision or spec clause, not "as per standard". Capture before and after photos; closure without evidence fails audits. Do not skip root cause, or you will keep paying the same rework bill under new NCR numbers. And review ageing weekly — a 15-minute quality meeting prevents 30-day NCRs.
Reports and metrics that actually improve quality#
Even a small contractor gets real value from five reports:
- NCR ageing: open NCRs bucketed by days
- Repeat NCR rate: how many issues recur, by trade and subcontractor
- Top defect types: waterproofing leakage, tile hollowness, cover issues
- Time to close: average closure days, and which stage delays — approval or rectification
- Location hotspots: the tower or floor where defects cluster, which is usually a crew story
These turn NCRs from documents into a quality improvement loop.
Implementation checklist for SMB builders and contractors#
Rolling out NCR management software construction teams will actually use is mostly change management, not configuration. A practical rollout:
- Start with one project and 1–2 trades — civil plus waterproofing is a good pairing
- Freeze a simple NCR template and resist the urge to overdesign it
- Define roles and approvals — who can close, who must approve Major NCRs
- Set basic SLAs: same-day raising, 48-hour initial response, weekly closure review
- Train on mobile with real examples — real NCRs beat long PPTs every time
- Link NCRs to tasks and checklists so actions cannot be missed, and review patterns monthly
Where SiteSetu fits (naturally)#
The practical advantage is not more software — it is fewer disconnected tools. When NCRs, checklists, drawings and task follow-ups live together, engineers spend less time chasing messages and more time closing issues correctly.
Final takeaway#
NCRs are unavoidable in construction. Unmanaged NCRs, though, quietly eat profit through rework, lost time and disputes. A simple, field-ready workflow — supported by NCR management software construction teams actually adopt — closes the loop: detect early, fix fast, prevent repeats.
2026 update: treat NCR management software as a controlled process#
The biggest improvement since this article was first published is not a new dashboard. It is a clearer standard for evidence. A reliable NCR management software process must show what was expected, what actually happened, who verified it, what exception arose and how that exception was closed. If the team cannot reconstruct that chain later, the record is incomplete — even when the screen shows green.
Three primary references now give Indian teams a clearer evidence standard. BIS describes the National Building Code of India 2016 as a model code and identifies Part 7 as covering construction management, practices and safety. The exact contractual standard still depends on approved drawings, specifications, applicable Indian Standards and local rules — so a checklist must name its governing document and revision instead of saying only "as per standard".
For Maharashtra real-estate projects, the revised MahaRERA Form 2A quality-assurance certificate asks whether inspection registers, the site order book and quality-control test registers are properly maintained and endorsed, and whether testing facilities are available. Nationally, RERA Section 14(3) keeps the familiar five-year defect-liability duty and the 30-day rectification window after an allottee gives notice. These provisions do not turn every observation into a statutory defect, but they make dated inspection and closure evidence far more valuable.
The 2026 lesson: separate observation, acceptance criterion, disposition and verified closure. A photograph proves how something looked at one moment. It does not by itself prove specification compliance, test acceptance or approval by the authorised person.
A field-ready workflow for NCR management software#
Run one workflow from the first site event to final review:
| Stage | What the team records | Control question |
|---|---|---|
| Define | Scope, project, location, governing requirement and responsible role | Is the current approved basis visible? |
| Capture | A numbered non-conformance record, with date and source evidence | Was it recorded where and when the event occurred? |
| Verify | Requirement, evidence, root cause, correction, corrective action and effectiveness check | Can a second person reproduce the decision? |
| Approve | Named approver, decision, comments and time | Did the authorised role approve, reject or return it? |
| Close | Corrective action, final evidence and closure acceptance | Is closure verified rather than merely reported? |
| Review | Trend and exception age; monitor NCR age, recurrence and reopen rate | Is management acting on recurring failure? |
The normal owner is the QA/QC lead, with authorised disposition approval. Configure a substitute and an escalation route before leave, shift change or package handover forces the issue. Shared passwords and retrospective signatures destroy accountability.
Data design before software configuration#
Decide the record structure before you touch the screens:
- Identity: unique number, project, zone, floor or chainage, package and responsible contractor
- Basis: drawing, specification, contract clause, rule, method statement or approved request — with revision
- Event: date and time, creator, quantity or status, source document and contemporaneous evidence
- Decision: reviewer, approval state, comment, due date and reason for rejection or change
- Closure: action taken, final evidence, verifier and closure time
- Audit: revision history, exported attachments, permission changes and any manual correction
Use controlled pick-lists for project, location, contractor and activity, but keep a comment field for genuine exceptions. Free-text spelling should never create five identities for the same floor, vendor or material. Equally, nobody should be forced into a wrong list value just to submit the form — route master-data corrections to a named owner.
Metrics that reveal process health#
Track a small, balanced set: completion on time, median approval cycle, missing-evidence rate, aged exceptions, reopen or reversal rate, and NCR age, recurrence and reopen rate. Compare rates using a fair denominator — inspections performed, worker-hours, equipment-hours, quantity installed or purchase value. Raw counts reward busy projects and can hide a weak smaller site.
The critical red flag for NCRs is closing one when repair is reported rather than when compliance is verified. Add a monthly sample audit comparing the digital record with the site condition and the original evidence. If dashboard and sample disagree, fix the process and master data before adding any more automation.
A 30-day implementation plan#
Week 1: define and sample#
Choose one project and one work package. Map the current process, identify the authoritative documents, agree the minimum fields, and collect ten recent examples — including two failures or disputes.
Week 2: configure and rehearse#
Configure roles, statuses, required evidence, due dates and escalation. Run the workflow on real historical examples, then simulate the awkward cases: a rejection, offline capture, a changed requirement, an incorrect entry, a reassignment.
Week 3: controlled live pilot#
Run the new process on one shift or package while keeping a named fallback. Review incomplete and returned records daily. Do not expand until field users can complete the record without a coordinator repairing it afterward.
Week 4: reconcile and decide#
Compare the system with physical conditions and source documents. Measure cycle time, exceptions and user corrections. Approve the next rollout only after owners have accepted the data-quality gaps and their corrective actions.
Connect the record to adjacent workflows#
Do not deploy this as an isolated register. Connect the quality control workflow with the quality module so the originating need and its approval stay visible. Then link snag-list closure to drawing revision control, so field evidence and the latest controlled information agree.
Governance gets easier when the material testing frequency guide uses the same project, location and responsibility codes as your inspection checklists. Use the site-engineer workflow for rollout aids — but give every downloaded format an owner and a revision, or the uncontrolled template becomes yet another conflicting record.
This connected design prevents a familiar failure: one module says an item is complete while the evidence, the commercial record or the downstream action says otherwise. The same identifiers should survive from request through verification and closure.
Questions for the monthly control review#
A useful monthly review is short enough to run and specific enough to change behaviour. Ask these against a sample of live records — not just a dashboard:
- Can the team trace a numbered non-conformance record from the originating event through approval and closure?
- Does the sampled record contain requirement, evidence, root cause, correction, corrective action and effectiveness check?
- Can the normal owner — QA/QC lead with authorised disposition approval — explain every manual correction and late approval in the sample?
- Are the current drawing, specification, rate, rule or method references visible at the point of work?
- Which location, subcontractor, material or work package contributes most to NCR age, recurrence and reopen rate?
- Were high-risk exceptions escalated before work, payment or handover proceeded?
- Do physical conditions and source documents agree with the system status?
- Are permissions limited to people who need to view, edit, approve or export the record?
- Has superseded or duplicate information been withdrawn from field use?
- Did last month's corrective action reduce recurrence — or merely close old entries?
Record the sample size, the exceptions and the actions. For NCR management software, the most dangerous assurance is a clean summary built on untested source records. The failure mode to challenge first is an NCR closed when repair was reported rather than when compliance was verified.
FAQs#
What is the minimum record needed for NCR management software?#
Start with a numbered non-conformance record. It should identify the project and location, state what happened, preserve requirement, evidence, root cause, correction, corrective action and effectiveness check, and show who created, checked and approved it. Add fields only when they support a decision, a compliance duty or recurring analysis.
Who should own NCR management software on a construction project?#
The normal model is a QA/QC lead as owner, with authorised disposition approval. A system administrator can configure permissions and reports, but cannot replace the person accountable for verifying site conditions or commercial facts.
Can Excel or WhatsApp be used for this process?#
For a small pilot, yes — provided there is one controlled version, named owners, protected approvals and a dependable archive. They turn risky when records get copied across groups, corrections overwrite history, or nobody can prove which version governed the work.
Which KPI should the team review first?#
Start with NCR age, recurrence and reopen rate. Review it by project, location and responsible package, and always inspect the source records behind an unusual result. A KPI is a signal for investigation, not proof of performance by itself.
How long should these construction records be retained?#
Use the longest applicable period across law, state rules, contract, warranty or defect-liability obligations, tax requirements and your organisation's approved retention schedule. Keep the record readable with its attachments and approvals — a database row whose evidence links have expired is not meaningful retention.
Does software make the process legally compliant?#
No. Software can make records timely, searchable and harder to alter silently, but compliance depends on the applicable rule, correct procedure, competent people and truthful evidence. Get project-specific legal, tax, labour or engineering advice wherever the interpretation affects rights or safety.
References and Further Reading
Primary and supporting sources cited in this article.
Tags: