LEARN:

A non-conformance report (NCR) is the document that records work on a construction project that doesn't meet specification, the contract, the relevant Australian Standards, the National Construction Code, or the project's ITP. It's one of the most important documents in a construction QA program, and one of the most misused.

This article walks through what an NCR is, what should be in one, the typical workflow, and the common ways NCRs go wrong on real projects.

What an NCR actually is

An NCR is a written record that identifies:

• What's non-conforming. A specific item of work, described precisely, located precisely, photographed.
• What it doesn't conform to. The specific contract clause, Australian Standard, NCC clause, or ITP requirement that's been missed.
• Who's responsible. The trade or sub-contractor that did the work.
• What close-out looks like. The remediation required to bring the work into conformance.
• A status. Open, awaiting action, in progress, verified, closed.

The NCR is the QA program's exception-handling mechanism. Conformance gets recorded in the ITP inspection log; non-conformance triggers an NCR.

What should be in an NCR

A defensible NCR contains:

• NCR number and date. Sequenced for tracking; date for the audit trail.
• Project identifier. Project name, contract, address.
• Trade and sub-contractor. Who did the work.
• Location. Specific enough that anyone can find the non-conforming work (level 3, apartment 304, west balcony, north corner).
• Description of non-conformance. Clear language. Photograph mandatory. Measurements where they apply.
• Reference standard. The specific clause that's been missed. "Doesn't comply with AS 3740:2021 section 2.4.1" beats "waterproofing not done properly".
• Recommended close-out. What the trade has to do to bring the work into conformance.
• Assigned owner. Who's responsible for ensuring close-out.
• Status and history. Open, in progress, verified, closed. Each change logged.
• Close-out evidence. When the NCR is closed, the evidence of remediation (photograph, test result, inspection record).

A well-structured NCR is a complete record that another inspector could pick up and verify months later.

The NCR workflow

The standard workflow:

1. Issue. An inspection identifies non-conformance. NCR raised with full detail.
2. Notification. Issued to the trade and to the head contractor's QA lead.
3. Trade response. The trade acknowledges, plans the remediation, communicates the planned close-out date.
4. Remediation. Work done.
5. Verification. Independent inspection confirms the remediation meets specification. Photograph or test result captured.
6. Closure. NCR status updated to closed; evidence filed in the QA record.

Where the trade disputes the NCR, the matter usually resolves through technical discussion. Where it doesn't, the head contractor decides whether to escalate (formal direction, withhold payment, dispute escalation).

Why NCRs matter beyond the project

Three external audiences eventually scrutinise the NCR record:

• Insurers. Home-warranty and PI insurers test how a builder handles non-conformance. A clean NCR record (well-issued, well-managed, well-closed) is a positive signal. A messy record is a red flag.
• Tribunals and courts. When a defect matter escalates, the NCR history is one of the most-read sections of the QA file. A builder who issued the NCR, managed it, and verified close-out has a strong position. A builder where the NCR appears in the file but wasn't closed is in trouble.
• Clients. Sophisticated clients (large developers, government, institutional) audit NCR management as part of their builder vetting.

The audit trail of NCR management is one of the higher-value things a QA program produces.

Common ways NCRs go wrong

Three patterns that cause NCRs to fail:

• Verbal-only. The site team identifies a non-conformance and tells the trade to fix it. No written NCR. The work might get fixed but there's no record of either the issue or the fix. If the work fails later, the absence of an NCR is hard to explain.
• Issued but not closed. NCRs raised at audit but never closed out. The QA file shows open NCRs months after the relevant work was buried. At handover (or in a dispute) those open NCRs are a liability.
• Vague description and reference. "Tiling is wrong, fix it" doesn't reference the contract or the standard. The trade disputes the NCR on the basis that the requirement was never specified.

Each is fixable. The fix is structural: a workflow that requires written NCRs, automatic chase-ups for open NCRs, and reference-grade descriptions.

How NCRs feed back into ITP and risk management

A working QA program treats the NCR log as a feedback signal:

• Patterns inform ITP tightening. A trade that keeps generating NCRs against the same hold-point indicates the ITP isn't sharp enough.
• Patterns inform risk ratings. A sub-contractor with frequent NCRs gets a higher rating in the risk register.
• Patterns inform sub-contractor management. Repeat NCR-generators get pre-qualified more carefully on the next project.

A QA program without that feedback loop produces NCRs but doesn't get better. A program with the feedback loop continuously improves.

Where QBFS fits

QBFS designs QA programs (including the NCR workflow), runs sub-contractor audits that generate NCRs, and provides QC inspection that issues NCRs at hold-points.

Call Paul on 0407 146 737.

Start With a Call

Best way to start is a phone call. Tell Paul the project, the issue, where you sit in the build cycle. The next step gets sorted on the call: site visit, desktop review, or a referral if QBFS isn't the right fit.