Free Nonconformance Tracker (NCR Log) Excel Template
Log every nonconformance — supplier, in-process, customer-returned. Track disposition, root cause, and corrective action linkage. Built for ISO 9001 traceability.
What you get
Working NCR log with disposition workflow (accept / reject / rework / scrap), root cause analysis fields, and CA linkage. The substrate of an ISO 9001 quality system.
Free 30-day trial · No credit card required · Used by manufacturers since 1991
Why manufacturers still use Excel for this
A nonconformance is any deviation from specification — a supplier shipped the wrong material, an in-process inspection failed, a customer returned a defective part. The NCR log is the central evidence that you noticed, decided what to do, and (sometimes) prevented recurrence.
Most quality systems fail not from lack of NCRs but from lack of follow-through. NCRs get logged, dispositioned, and forgotten. The same nonconformance recurs next month. The root-cause analysis column is what separates a useful NCR log from an event diary.
This template enforces that discipline: every NCR has a root-cause field (even "unknown" is a valid answer that flags the row for follow-up), and a corrective-action link column that ties the NCR to the CA workflow. Tracked over 90 days, the patterns drive the improvement project list.
What's inside the template
NCR event log
NCR number, date, source (supplier/in-process/customer), item, quantity, description, severity, disposition, root cause, CA linkage.
Disposition workflow
Accept / reject / rework / scrap / use-as-is — each with required signature fields and a return-to-supplier flag where applicable.
Root cause categorization
5M categories: Man, Machine, Material, Method, Measurement. Free-text root cause underneath the category.
CA linkage tracker
NCRs requiring corrective action are flagged with the CA number; rollup shows open CAs aging beyond target.
NCR Pareto by source
Where are NCRs coming from? Suppliers, in-process operations, customers. Drives the supplier development and process improvement priorities.
Monthly trend chart
NCR count by month, by source. Track whether quality is actually improving over time.
How to use this template
A practical walkthrough, from the sample data to a plan built on your own numbers.
- 1
Define what triggers an NCR
Not every defect needs an NCR — but every NCR-eligible event needs one. Define the threshold upfront (e.g., any failed final inspection, any customer return, any supplier reject batch).
- 2
Assign NCR numbers sequentially
A simple YYYY-NNNN format works. Auditors expect to see sequential numbering with no gaps — gaps suggest deletions and trigger questions.
- 3
Force a root cause within 5 business days
Open NCRs without a root cause are dead. Set a 5-day SLA. "Unknown — under investigation" is acceptable for week one; not after that.
- 4
Close the loop with CA verification
When a CA closes, the NCR rollup should show the recurrence trend for that root cause. If recurrence continues, the CA did not work.
When you outgrow this template
Excel is the right answer for early-stage planning, until it isn't. These are the warning signs that you need a real production scheduling tool.
If three or more of these apply, you have outgrown spreadsheet planning. EDGEBIC, the current generation of RMDB, is User Solutions' finite capacity scheduling and production planning software. It imports the same orders, routings, work centers and stock from Excel, CSV or your ERP, schedules them against real machine, labor and material limits, and shows the result on a drag-and-drop Gantt chart. It is a one-time license: EDGEBIC APS is $25,000, and EDGEBIC Complete, which adds MRP, inventory and purchasing, is $35,000.
See EDGEBICFrequently asked questions
What is the difference between an NCR and a defect?+
A defect is any deviation from spec. An NCR is a formal record opened when the defect warrants disposition and root-cause analysis. Most shops do not open an NCR for every defect — only for ones above a severity threshold or that affect customer-facing product.
How fast does a root cause need to be identified?+
ISO 9001 does not specify, but auditors will ask. A reasonable internal SLA is 5 business days for "preliminary root cause" and 30 days for "confirmed root cause with corrective action." NCRs older than 60 days without root cause raise audit flags.
Should I link every NCR to a corrective action?+
No — not every NCR requires a CA. Severity matters. A one-off supplier defect that was caught at incoming inspection might not need a CA. A recurring in-process defect with customer impact definitely does. The flag column makes the decision explicit.
How does this template support ISO 9001 / AS9100?+
It satisfies the "documented information of nonconformities" requirement in both standards. The disposition workflow, root cause field, and CA linkage create the traceability auditors expect. The template does not satisfy other clauses (management review, internal audit, etc.) — those are separate documents.
Start with the spreadsheet. Move to EDGEBIC when it breaks.
The template handles the math for a small plan. EDGEBIC is what manufacturers move to when orders, routings and capacity change faster than a spreadsheet can follow: published one-time pricing, and implementation measured in days.