Observation vs NCR vs Snag vs Defect in Construction
Quick definitions (one sentence each)
- Observation: A documented concern or deviation noted during inspections that should be corrected quickly, often before it becomes a formal nonconpliance.
- Site Observation Report (SOR): A structured “observation” record (often with photos and a due date) used to track minor or early-stage issues without immediately triggering the NCR system.
- NCR (Non-Conformance Report): A formal QA/QC record used when non-compliance is confirmed against the contract/specs/drawings/ITP requirements.
- Snag / Punch List: A closeout list used to complete and polish the works (finishes, missing items, minor defects) before handover.
- Defect (DLP): A defect managed after taking-over during the Defects Liability Period (or defects correction period) under the contract’s defects regime.
At-a-glance comparison
The simple decision rule (text-based)
Use an NCR only when non-compliance is confirmed and needs formal containment/verification.
Use an Observation (SOR) when the issue is minor, early, or needs clarification—and can be corrected quickly with evidence.
Use a Snag list for closeout completion items.
Use a Defect (DLP) record when the issue is managed after taking-over under the defects regime.
1) When to use an Observation (and why SOR matters)
An observation is your best tool for preventing “paper escalation.” It keeps the team aligned on early corrections without turning every issue into a contractual fight. However, observations only work if they are tracked and closed properly.
Site Observation Report (SOR)
A Site Observation Report (SOR) is simply a disciplined version of an observation: it is documented, assigned a due date, and closed with evidence. Without a log, SORs decay into “ignored comments” and later reappear as NCRs.
SOR log (why contractors should take it seriously)
- Problem: Contractors sometimes ignore SORs because they don’t immediately impact payment.
- Reality: Ignored SORs often become NCRs once the issue is repeated, concealed, or starts affecting compliance and commissioning.
- Control: Maintain a simple SOR log and review it weekly (open/overdue/escalate).
Minimum SOR log fields: SOR ID, date, location, photo ref, observation text, due date, status, closure evidence ref, escalated to NCR? (Y/N).
2) When to use an NCR (confirmed non-compliance)
Use an NCR when compliance is no longer “a discussion.” Typical triggers include:
- Failed tests (e.g., pressure test, NDT, concrete strength).
- Rejected inspections (work not per drawings/spec, tolerances exceeded).
- Missing mandatory records (inspection hold point missed; work covered).
- Unauthorized deviations (unapproved material/subcontractor, unapproved method change).
If you need the full NCR workflow and definition, see NCR Meaning in Construction. If you need the actual form and tracker, see NCR Form Template and NCR Log Template.
3) When to use a Snag / Punch List
Snags are typically used for closeout and handover readiness: incomplete items, cosmetic fixes, minor damage, missing labels, touch-ups, adjustments, and finishing alignment issues. They are essential, but they are not a replacement for NCRs.
Related reading and tools:
- What Is a Snag List?
- Snag List Excel Format Sample
- How to Create Your First Snag
- Snaghere: Snag List Software
4) When to use a Defect record (DLP context)
Defects are issues managed after taking-over under the defects regime (DLP/defects correction period). They often appear during operation or once the building is in use. While some open NCRs can be carried into handover as “outstanding items,” this must be controlled carefully.
5) Advice for Contractors: How to prevent an NCR and keep it an Observation
- Act immediately on verbal cues: Train foremen to fix issues the moment an engineer points at something, before the camera comes out.
- Communicate intent proactively: If a minor deviation is necessary due to site conditions, request a field change before proceeding—don’t ask for forgiveness later.
- Self-correct and document: If an observation is issued, close it out with a photo and a quick note to the engineer within 24 hours. A closed observation is an NCR that never happened.
- Manage the cash flow risk: It is usually cheaper to spend 2 labor hours fixing an observation immediately than to suffer a long payment delay on a holdback for an open NCR.
6) A note for Engineers and Consultants: the commercial reality of NCRs
- Project interest vs paper compliance: Creating a cash flow crisis over minor, non-safety-critical issues often leads to delays and claims—rarely in the Employer’s best interest.
- The “hammer” vs the “nudge”: Use NCRs for safety, structural integrity, statutory compliance, repeated failures, or concealment risk. Use a strongly worded observation/SOR for first-time minor issues and cosmetic deviations.
- Preserving the relationship: Over-issuing NCRs creates an adversarial environment that reduces communication and early problem-solving.
7) How issues escalate (and how to stop it)
Most escalation happens because of two things: lack of closure evidence and missed timelines. A clean escalation ladder is:
- Observation (quick fix + photo)
- SOR (logged + due date + closure evidence)
- NCR (confirmed non-compliance + containment + verification)
- Contractual notice (when ignored or repeated) — see Timely Notices in Construction
8) Examples (short and practical)
- Observation/SOR: Cosmetic sealant gap, small paint defect, missing label, minor alignment issue. Close with photo and short note.
- NCR: Pressure test failure, unapproved pipe material installed, inspection rejected at hold point, missing mandatory inspection record.
- Snag: Touch-up paint, chipped tile, missing door stopper, incomplete silicone at handover.
- Defect (DLP): Post-handover leak, settlement crack that develops over time, operational defect discovered during use.
If you need a real remediation workflow example, see the checklist: Remediate Pile Defects Checklist (Grout or Core Repair).
Common mistakes (and how to avoid them)
- Using NCRs for everything: It inflates paperwork, damages trust, and slows closure.
- Using snags for compliance issues: A snag list does not replace containment, verification, and evidence-based closure.
- No SOR log: Untracked observations become repeat findings and then NCRs.
- Closing without evidence: No photo/test ref = weak closeout and future disputes.
- Missing ITP/Hold points: Many “surprise NCRs” start with skipped inspections. See Inspection & Test Plan (ITP) in Construction.
Related reading (optional)
Tip: If you want fewer NCRs on your project, invest in two simple habits: (1) a strict SOR log with weekly closure, and (2) fast photo-based closure evidence for minor issues. That is how “observations” stay observations.
