Skip to content

NCR Form Template: How to Write a Non-Conformance Report (with Free Template)

What the NCR Form Needs to Contain

A non-conformance report (NCR) form is the structured record you create when a product, component, process, or service fails to meet a specified requirement. Whether the failure is discovered at goods-inwards, during in-process inspection, at final release, or after a customer complaint, the NCR form captures the same core information in the same structure.

ISO 9001:2015 does not prescribe a specific NCR form format. Clauses 8.7 (control of nonconforming outputs) and 10.2 (nonconformity and corrective action) define what information the system must retain, not how it must be laid out. That flexibility is intentional — it means a two-page Word template works just as well as dedicated software, provided it captures everything a UKAS-accredited certification body auditor needs to trace the non-conformance from detection to verified closure.

This page provides a free NCR form template structure, with worked examples for each field, along with the ISO clause context that makes each field mandatory.

The NCR Form Template — Field by Field

Section 1: Identification

NCR number Sequential, unique reference. Simple format: NCR-[YEAR]-[SEQUENCE] (e.g. NCR-2026-047). Sequential numbering makes the NCR log easy to sort and audit trail easy to follow.

Date raised The date the non-conformance was detected and the NCR was opened. Not the date the investigation started.

Raised by Name and job title of the person raising the NCR. Not a department — a named individual. Auditors trace accountability to people.

NCR type Classify at the point of raising: Internal (found by your team) or External (customer complaint, supplier return, external audit finding). Type determines the response urgency and customer notification requirements.

Section 2: Description of the Non-Conformance

What is non-conforming Describe precisely: product reference, batch number, drawing number, process name, or document reference. "Batch A123" is useful. "Some parts" is not.

The requirement not met State the specific requirement that was breached: customer drawing dimension, internal specification number, ISO 9001 clause, or procedure reference. This is the "requirement" the NCR is raising against. It must be a documented requirement — NCRs cannot be raised against undocumented expectations.

What was found The actual condition observed. Include measurements, dimensions, quantities, or observations. "Surface roughness measured at Ra 3.8μm against Ra 1.6μm maximum on drawing DWG-001 Rev C" is audit-ready. "Rough surface" is not.

Quantity affected Number of parts, batch size, or extent of the non-conformance. This determines the containment scope.

Location Where the non-conforming product or material is: work-in-progress, finished goods quarantine, customer site, or supplier.

Section 3: Immediate Containment

Containment action taken What was done immediately to prevent the non-conforming product from progressing further: quarantined, labelled hold, customer notification, line stopped. Record the action and the date taken.

Disposition decision One of four options: use-as-is (requires customer or engineering concession), rework (to meet specification), return to supplier (for supplier-caused non-conformances), or scrap. Disposition must be authorised — not just decided by the inspector who found it.

Authorised by Name and role of the person who authorised the disposition. Clause 8.7 requires that the organisation ensure that nonconforming outputs are identified and controlled — that control includes documented authorisation.

Disposition date When the disposition was decided and executed.

Section 4: Root Cause Analysis

Root cause analysis required? Yes or No, with rationale. A one-off minor non-conformance from an isolated cause may need only correction and monitoring. Recurring issues, customer-reported issues, significant scrap, or issues with systemic risk require root cause analysis. Record the decision, not just the outcome.

Root cause analysis method State which method is being used: 5 Whys, fishbone diagram, 8D, or other. Match the method to the complexity of the problem. Our root cause analysis guide explains when each method is appropriate.

Root cause identified The underlying cause — not the symptom. "Operator error" is never a complete root cause. The root cause is why the error was possible: inadequate work instruction, tooling not maintained, inspection step missing, incoming material not checked.

Root cause confirmed on Date the root cause was verified (not just asserted). This is often a separate review step from the initial investigation.

Section 5: Corrective Action

Corrective action(s) defined One or more specific actions that address the root cause. Procedure changes, training updates, process controls, engineering change requests, supplier development actions. Corrective actions must target causes, not symptoms.

For each corrective action:

  • Owner — named individual responsible, not a department
  • Due date — specific date, not "ASAP" or "next month"
  • Status — Open / In Progress / Completed

Corrective action implementation date When the corrective action was implemented in practice, not when it was decided.

Section 6: Effectiveness Verification

Verification method How you will confirm the corrective action worked: re-inspection of next batch, review of KPI trend data, follow-up audit, customer confirmation. The method must produce objective evidence — a signature confirming "we believe it's fixed" does not count.

Verification result The actual outcome of the verification: pass/fail with evidence reference.

Verification date When verification was completed.

NCR closed by Named individual who closed the NCR. Typically a quality manager or quality engineer.

Closed date When the NCR was formally closed. An NCR cannot be closed before effectiveness verification is complete.

Worked Example

To illustrate how the template fills in practice, here is a complete worked example for a goods-inwards rejection:

Field Example Entry
NCR number NCR-2026-031
Date raised 12 July 2026
Raised by J. Patel, Goods Inwards Inspector
NCR type Internal (supplier-caused)
What is non-conforming Batch of 200 M8 hex head bolts, Supplier PO-2026-089
Requirement not met Grade 8.8 property class per drawing DWG-045 Rev B. Received bolts are Grade 4.6 per certificates.
What was found Material certificates show property class 4.6. Hardness testing confirms: Vickers HV range 130-145 (Grade 8.8 minimum: 250 HV per ISO 898-1:2013).
Quantity affected 200 pieces, entire batch. Lot number AB-2026-0612.
Location Quarantine cage, Goods Inwards Bay 3
Containment action Entire batch quarantined immediately. Red HOLD labels applied. Production scheduling notified — no release to floor.
Disposition decision Return to supplier
Authorised by S. Kumar, Quality Manager
Disposition date 12 July 2026
Root cause required? Yes — supplier provided incorrect grade. Second incident in 6 months.
RCA method 5 Whys
Root cause Supplier purchasing team ordered to correct PO number but pulled wrong stock from shelf. Shelf labelling at supplier is by part number only, not property class. Visual confirmation not possible without destructive testing.
Root cause confirmed 15 July 2026 (confirmed via supplier visit report)
Corrective action 1 Raise SCAR (Supplier Corrective Action Request) requiring supplier to implement segregated storage for M8 bolts by property class, with colour-coded bin labels. Owner: S. Kumar. Due: 31 July 2026.
Corrective action 2 Update incoming inspection procedure to include Vickers hardness spot-check for all fastener batches from this supplier until 3 consecutive clean lots. Owner: J. Patel. Due: 19 July 2026.
Verification method Review next two batches' incoming inspection records. Confirm supplier SCAR closed with evidence of new storage system.
Verification result Pending
NCR closed by
Closed date

Common NCR Form Mistakes

Corrective action = re-training "Retrain the operator" is one of the most common entries in SME corrective action records — and it almost never is the actual root cause. Retraining treats the person, not the system. If the work instruction was unclear, the fix is the instruction. If inspection procedures missed the defect, the fix is the inspection step. Auditors encounter "retrain operator" routinely across surveillance visits — it flags a QMS that is not identifying systemic causes.

Missing effectiveness verification The NCR is closed with a "completed" checkbox next to corrective actions, but no evidence that the actions actually worked. A UKAS certification body auditor will open previously-closed NCRs at random during surveillance visits specifically to check effectiveness verification records. If they are not there, the NCR was not properly closed.

Disposition without authority The inspector who found the defect decides and records the disposition without a separate authoriser. Clause 8.7 requires controlled handling of nonconforming outputs — "controlled" means authorised. The authoriser should be a different person from the inspector.

NCR raised after production continued Non-conforming material continued through production before containment. This is the most damaging finding — it suggests the NCR process is not integrated into production, only used retrospectively.

Connecting the NCR to Your Quality System

The NCR form does not exist in isolation. It connects to three other ISO 9001:2015 requirements:

  • CAPA process — for significant non-conformances, the NCR triggers a formal corrective action process with root cause analysis, action ownership, and effectiveness verification
  • Management review — NCR trends (type, frequency, source, repeat issues) are a required input to management review (clause 9.3.2)
  • Engineering change management — when root cause analysis identifies a design or process change as necessary, the corrective action generates an engineering change request (ECR), documented through the change control procedure
  • Internal audits — an internal audit of the NCR process checks whether NCRs are being raised consistently, closed properly, and whether corrective actions are effective

A well-documented NCR that connects to root cause, corrective action, and — where applicable — an engineering change gives a UKAS auditor a complete, traceable quality chain. That is the output the NCR form exists to produce.


This guide describes ISO 9001:2015 clauses 8.7 and 10.2 as published by the International Organization for Standardization. The full standard text is available from ISO. This guide is a practical reference — verify requirements with the standard and your UKAS-accredited certification body.


Sources


ChangeRoute is a quality management tool for ISO 9001-certified UK manufacturing SMEs. Join the waitlist to be notified when it launches.

Ready to automate your change management workflow?

ChangeRoute replaces paper ECRs with a structured digital workflow. Join the waitlist for early access.

No spam. Unsubscribe any time. Privacy policy.