Construction Defects: Identification, Responsibilities and Contractual Remedies

Construction defects are noncompliant or deficient work, materials or performance found during construction, testing or handover. Contractors ordinarily control their own work and that of their subcontractors, while Engineers or consultants inspect under their appointed roles. Findings should be recorded, linked to the correct observation, NCR, snag or contractual notice, corrected under an authorized process and verified before closure.

1. What Is a Construction Defect?

A construction defect is a departure from the requirements governing the work. It may concern a component's materials, dimensions, workmanship, installation, compliance testing or performance. The relevant comparison is with the signed contract, issued-for-construction and approved drawings, approved submissions, specifications, inspection and test plans (ITPs), accepted samples and applicable legal requirements. The precise document hierarchy is contract-specific.

A visible crack, staining or poor alignment is a finding; it is not necessarily proof of a particular cause, failure mechanism, or structural danger. The inspector must document observations and distinguish them from engineering conclusions. Technical assessment, design changes and acceptance of departures require properly authorized specialists.

Typical categories of construction defects

Discipline	Example finding	What determines noncompliance?
Concrete and structural	Honeycombing, exposed reinforcement, suspect cracks, reinforcement out of position.	Structural drawings, specifications, tests and engineer assessment.
Architectural finishes	Debonded tiles, poor finish, misalignment, incomplete fixtures.	Approved samples, tolerances, finish schedules and scope.
Waterproofing / roofing	Open laps, defective drain termination, water ingress.	System approvals, details, test criteria and recorded tests.
Mechanical and plumbing	Leaking joint, unsupported pipe, defective slope, failed pressure test.	Approved shop drawings, ITP, product instructions and witnessed testing.
Façade / doors / windows	Sealant gaps, installation damage or a failed performance test.	Approved façade details, product requirements and acceptance tests.
Fire and life safety	Incomplete firestopping or a failed required system test.	Applicable fire design, approvals and authority requirements.

Important: Suspected structural instability, life-safety defects or hazards demand immediate control under the site safety procedure and referral to competent professionals. A defect register or general article cannot establish whether work is safe to load, occupy or conceal.

2. Who Identifies Defects and Who Must Rectify Them?

Contractor quality control

The Contractor is typically responsible for delivering conforming work and managing its own trades and Subcontractors. Internal inspections, tests and quality surveillance identify deficiencies early, before the Engineer or consultant discovers them. The Contractor may record a defect against a Subcontractor and require correction under the subcontract, while remaining accountable to the Employer under the main contract, subject to the agreed scope and allocations.

Engineer, consultant and supervision team

The Engineer or designated consultant inspects work and communicates concerns or documented defects to the Contractor within the authority given by the appointment and contract. Depending on the contract, inspection may result in a defect notification, observation, NCR or an instruction issued through the formal communication procedure. The Engineer's approval, rejection and remedy powers are defined by the actual conditions and delegated roles; they must not be presumed identical in FIDIC, NEC, AIA, JCT or bespoke contracts.

Independent inspectors, authorities and Employer representatives

Specialist testing companies, third-party inspectors and authorities may identify deficiencies through defined inspections and regulatory checks. Their reports can provide evidence, but contractual instructions and obligations should be communicated through the authorized channels established for the project.

Practical principle: Finding a defect, deciding who pays to correct it and formally certifying the result are distinct decisions. The issue should not be closed merely because the responsible party reports that it has been rectified.

3. Construction Defect vs Observation, NCR, Snag and Contractual Notice

Not every inspection finding warrants the same document. The correct record depends on the evidence, project procedures, work stage, type of failure and governing contract.

Record	Normal purpose	What it does not automatically do
Defect entry	Track a finding requiring assessment or rectification.	Issue an NCR or establish liability.
Observation / SOR	Record a concern or discrepancy needing action, clarification or inspection.	Prove confirmed nonconformance or approve a change.
NCR	Control a confirmed departure from specified requirements with a corrective and verification process.	Create a contractual backcharge, default or termination right by itself.
Snag / punch list	Record incomplete or defective finishing and closeout work.	Certify practical completion or handover automatically.
Notice to Correct	Require correction of contractual nonperformance through an available contractual remedy.	Automatically authorize payment deduction, replacement by others or termination.
Backcharge / deduction	Track a proposed or assessed recovery of costs when the contract permits it.	Prove entitlement or costs without notices and supporting assessment.

4. From Defect Discovery to Closure: A Practical Workflow

1. Identify: inspect work, record exact location, trade, observed condition, relevant requirement and evidence.
2. Control immediate risk: stop or protect affected work where the approved safety or quality procedure requires; do not conceal a potentially nonconforming element before required review.
3. Log: add one finding to the issuer's Construction Defects Register and identify the party responsible for responding.
4. Issue appropriate record: observation, NCR, snag or other document according to the actual project quality and contract procedure.
5. Respond: the Contractor or Subcontractor submits correction evidence, proposal, technical clarification or reasoned objection. A Work Inspection Request (WIR) may be used for reinspection where applicable.
6. Review disposition: the competent reviewer determines whether correction, repair, replacement, further testing or a permissible concession is required. A deviation or variation request does not, by submission alone, authorize nonconforming work.
7. Verify: undertake required reinspection or tests and document the findings, signed response, supporting records and decision.
8. Close or escalate: close on authorized verification. If contractual obligations remain unfulfilled, assess the separate notice and remedy procedures rather than treating an open NCR as an automatic backcharge.

5. Defect Registers: Issuer vs Respondent

Issuer-side construction defects register

The Construction Defects Log is intended for whoever identifies defects for another party to rectify: the Engineer in relation to the Contractor, or the Contractor in relation to its Subcontractors. A compact working log generally needs a Defect ID, date, location, division, short defect name, factual description, responsible party, issued document reference and status.

Contractor or Subcontractor response registers

The separate Construction Observations Log tracks the original observation number, received date, location, description and how the respondent replied (for example WIR, authorized objection, technical query or variation request), including submission reference, date and the status determined by the reviewer. The existing NCR Log separately tracks formal NCRs. These response registers should not duplicate the inspector's entire findings record.

Keeping the working logs concise helps them fit in an A4 landscape printout. Detailed photographs, drawings, root causes, repair methods, tests and cost breakdowns belong in the individual documents or their attachments, not dozens of register columns.

6. When Is a Notice to Correct Appropriate?

A Notice to Correct concerns a failure to perform a contractual obligation. It is not simply the next box automatically ticked whenever an observation or NCR passes a target date. The power to issue a notice, the recipient, required content, remedy period and consequences depend on the conditions of contract and particular amendments.

FIDIC example: Under the FIDIC Red Book framework, the Engineer may have a contractual mechanism to require a Contractor to make good failures within a specified appropriate period. Verify the adopted edition and particular conditions. The notice should identify the obligation and failure and comply with contractual communication rules; an earlier observation deadline does not in every contract replace these requirements.

NEC4 example: NEC4 ECC distinguishes the Supervisor's role in defect notification and review from Project Manager functions concerning correction, acceptance and assessment of uncorrected defects. It is incorrect to treat an Engineer or consultant as the universally authorized issuer or assessor under all forms. The contract's own vocabulary and role allocation govern.

See Notice to Correct: Meaning, Cure Period and Template and record formal notices in the Construction Notices Log.

7. When May a Backcharge or Deduction Follow?

In some contracts, the Employer or Contractor may arrange correction by others and seek cost recovery or deductions after following the required contractual steps. In others, specific valuation or payment mechanisms apply. Important considerations include an established failure or obligation, authorized notice, reasonable opportunity to remedy where required, actual and properly assessed costs, evidence of work by others and the applicable payment or claim procedure.

Do not assume: (a) that every NCR permits backcharging, (b) that a Notice to Correct is itself a backcharge notice, (c) that a cost entered in a register is an approved deduction or (d) that a payment withholding or termination power exists without checking the agreement.

The existing Backcharge Log already handles financial tracking. The Notices Log should retain the formal correspondence and cure deadlines. Technical and financial records must remain linked by references, without losing their separate purposes.

8. Worked Example: Defective Waterproofing at a Roof Drain

Finding: the site engineer observes that a roof waterproofing membrane does not terminate correctly at a roof drain. A photograph shows the condition, but determining the approved detail and functional adequacy requires reference to the approved waterproofing system and relevant test or inspection requirements.

Initial control: the affected area is kept accessible and protected as required. The issuer enters the finding in the defect register. A contractor or consultant raises an observation or NCR if the evidence and procedure warrant it.

Response: the waterproofing Subcontractor proposes correction in accordance with the approved system. The Contractor records its reply and submits the appropriate WIR or quality evidence; if there is a legitimate disagreement about the approved detail, the issue is formally clarified rather than ignored.

Verification: the designated reviewer checks the corrected detail and any specified test result. Only then does the register show verified closure. If the responsible party fails to meet a contractual obligation, the contract administrator separately assesses whether a Notice to Correct or another remedy is available.

9. What Happens at Taking-Over or During the Defects Correction Period?

Incomplete items, outstanding NCRs and defects identified after completion may be subject to different procedures and consequences. The governing contract determines when work can be taken over, which deficiencies prevent completion, the time for correction, and any remaining rights. Do not assume every 'Defects Liability Period' has the same definition or consequences; NEC4, for example, uses specific terms including defects date and defect correction period.

Read Defects Liability Period: Handover and Rectification and Open NCRs at Taking-Over for the separate handover questions.

10. Common Errors in Construction Defect Management

• Recording vague phrases such as 'poor workmanship' without location, specification or measured finding.
• Treating every observation as a confirmed NCR, or every NCR as contractual default.
• Asking the Contractor to correct work without documenting the contractual or quality procedure and approving any required engineered repair.
• Treating a WIR submission or Contractor's claim of correction as final acceptance.
• Combining observation, NCR, formal notice and backcharge into a single register with no separate document history.
• Failing to preserve formal notice delivery evidence and the contract-dependent deadlines.
• Escalating to a deduction or termination merely because an internal target date expired.

Key Resources in the Construction Defects Cluster

Construction Defects Log (Excel) · Construction Observations Log (Excel) · NCR Log (Excel/PDF) · Construction Notices Log (Excel) · Backcharge Log (Excel/PDF). These are complementary resources, not a fixed universal contractual sequence.

References

NEC Contracts — What NEC4 ECC supervisors do, and need to know

NEC Contracts — Dictionary of defined terms, including Defect

FIDIC — Construction Contract 2017 Red Book, reprinted 2022 with amendments