What Is an NCR in Construction?

The test for whether something deserves an NCR is whether a requirement exists and was not met. Quality standards use the same definition: a nonconformity is the non-fulfilment of a requirement. If nobody can point to the drawing note, specification paragraph or inspection step that was missed, the observation belongs somewhere else, such as an RFI asking what the requirement is.

That is also why a well-written NCR cites its requirement. "Concrete cover looks thin" is an opinion. "Cover to the bottom mat measured 1.25 in. at gridline C/4; detail 3/S-501 requires 2 in. minimum" is a nonconformance, and it is the version that survives a dispute.

Most templates carry the same fields: a unique NCR number and date, the location, who raised it, the requirement and the document it comes from, a description of what was found with photographs or test results, and a classification of severity. The response half adds the proposed disposition, the root cause, the corrective action, any action to prevent recurrence, and the verification sign-off with a closing date.

The two fields that decide whether the report is useful later are the requirement reference and the root cause. The first makes the finding checkable. The second is what lets a team see that the same cause is behind a cluster of reports.

Rework removes the defect and builds the item again to the original requirement. Repair brings the item to an acceptable condition without fully meeting the original requirement, and usually needs the engineer of record to approve the method. Reject and replace applies to material or equipment that cannot be fixed on site.

Accept as is, sometimes called use as is, means the item stays as built. It is a decision for the designer and the owner, not the contractor, because the project is accepting something short of the contract requirement. Under AIA A201-2017 the owner may accept nonconforming work in place of requiring its removal and correction, with an equitable reduction in the contract sum (section 12.3). That adjustment is the reason an accept-as-is NCR should reach the cost and contract record rather than simply being marked closed.

Quality vocabulary separates two things that field teams often run together. A correction fixes the nonconformity you found: the rebar is moved, the wall is rebuilt. A corrective action removes the cause so it does not recur: the placement drawing is clarified, the crew is retrained, the hold point is moved earlier in the Inspection and Test Plan.

An NCR that records only the correction closes the instance and leaves the cause in place. The corrective action field is where a quality program shows whether it learns anything from its own reports.

The NCR itself is not an AIA or ConsensusDocs form. The obligation behind it is in the general conditions: A201-2017 Article 12, Uncovering and Correction of Work, requires the contractor to correct work that does not conform to the contract documents. The mechanics of raising, numbering and closing NCRs are usually written into the project quality requirements, commonly in Division 01, or into an owner’s quality specification.

Because of that split, two projects can use the word NCR for slightly different things. One treats it as any recorded deviation, another reserves it for items that need a formal disposition and sends minor defects to a punch or deficiency list. Reading the quality section of the specification is the way to know which applies.

A punch list item is a minor incomplete or defective item recorded near completion and closed by working down the list. An NCR is a formal record with a disposition and a verification step, raised whenever the deviation is found. A deviation that is small and fixed on the spot may never need an NCR; one that affects structure, fire resistance or a hold point nearly always does.

An RFI asks what the documents require. An NCR says the documents were not followed. A change order changes the requirement itself. An NCR never changes the requirement; if the owner decides to live with the deviation, that decision is a separate contractual step.

A single NCR is an event. Twenty of them are data. Grouping the log by trade, specification section and root cause shows whether the problem is one crew, one detail that is hard to build, or one requirement that is easy to miss in the documents. A cluster against a detail usually means the detail needs to be redrawn or clarified for the next project.

Closure time matters as well. An NCR that blocks a hold point holds up the next trade, so the age of open reports on the critical path is worth tracking separately from the total.