1.5 Templates pack: NCR, CAPA, audit, calibration, incoming report

A good template is much more than a blank form to fill out; it is a carefully structured data collection instrument. When completely unconstrained free-text entries are allowed in quality records, it becomes incredibly difficult to generate a reliable Pareto chart, accurately trend supplier performance, or predict future failures.

This section outlines the minimum viable fields recommended for a robust Quality Management System. Whether Excel, Project management software, or dedicated enterprise QMS software is used, tracking these specific data points is highly recommended. They must be thought of as the “primary keys” that clearly link high-level quality data back to the everyday engineering reality on the floor.

Non-conformance report (NCR)

The NCR is the fundamental building block of failure data. To properly support the Material Review Board (MRB) process (covered in Chapter 9.1), the NCR needs to capture the “What” and the “How Many” with high precision.

Critical Data Architecture:

• Defect Code (Standardized): Vague, unhelpful descriptions like “Bad solder” must be avoided. Standard descriptive codes such as “IPC-610-Soldering-Bridge” must be used instead. Relying on free text makes automated defect analysis nearly impossible.
• Traceability ID: This should be a Date Code, Lot Number, or Serial Number. Without this identifier, the risk cannot be bounded, which often forces the entire day’s production run to be suspected.
• Quantities: The Qty Received, Qty Inspected, Qty Suspect, and Qty Rejected must always be clearly recorded.

Pro-Tip: When calculating the “Yield” metric, the math must be based on the actual Qty Inspected, rather than the total Qty Received at the dock.

Corrective and preventive action (CAPA)

A good CAPA template functions as a logical, guided workflow, rather than just a simple questionnaire. It is designed to help guide the investigation from observing the initial symptom all the way down to isolating the systemic root issue (refer to Chapter 9.2).

Helpful Logic Fields:

• Problem Statement (5W1H): Who, What, Where, When, Why, How.
  • Poor: “The unit failed.”
  • Good: “Unit SN123 failed the output voltage test at 45°C during the burn-in phase on Line 2.”
• Root Cause Category: The issue must be clearly classified as Design, Process, Component, or Software.
• Action Type:
  • Correction: This is the immediate containment step (e.g. “Screen the existing warehouse stock”).
  • Corrective Action: This is the actual root cause elimination (e.g. “Modify the physical molding tool”).
  • Validation Method: How the team will objectively prove the fix works (e.g. “Test 30 consecutive units from the next production run”).

Audit checklist

An internal audit that lacks objective evidence is often just an exchange of opinions. A strong audit template gently prompts specific facts to be recorded and clear references to be documented (refer to Chapter 8 for more on auditing).

Structure:

• Reference Standard: The specific standard being evaluated must be noted (e.g. ISO 9001:2015, Clause 8.5.1).
• Objective Evidence: The auditor should record the specific document number, serial number, or record ID that they actually viewed.
  • Example Entry: “Reviewed the training record for Operator A. Smith. Verified Record #TR-2024-05 is complete.”
• Finding Grade:
  • Major: This indicates a significant system breakdown or a direct risk to product quality.
  • Minor: This usually reflects a single, isolated lapse in compliance.
  • Observation: This is an Opportunity for Improvement (OFI).

Calibration record

The calibration record is the vital link between in-house measurement tools and recognized National Standards (like NIST or ISO). If this traceability link is broken, the engineering measurements taken by that specific tool are technically invalid (refer to Chapter 3.4).

The Traceability Chain:

• Asset ID: The unique internal identifier of the tool.
• Master Standard Used: The exact Asset ID of the “Gold Standard” equipment used by the lab to calibrate the tool.
• As-Found / As-Left Data:
  • As-Found: The tool’s reading before any adjustments are made. This is crucial! If the As-Found reading is out of tolerance, the quality team must thoughtfully review all products measured by this tool since its last good calibration.
  • As-Left: The tool’s correct reading after the physical adjustment.

Incoming quality control (IQC) report

The IQC report acts as the facility’s firewall log. It clearly justifies exactly why an incoming supplier lot was accepted into stock or placed into quarantine (refer to Chapter 4.3).

Inspection Logic:

• AQL Level: The agreed-upon level must be noted (e.g. Level II, 0.65).
• Sample Size: This quantity should be calculated from the applied AQL table.
• Defect Breakdown:
  • Critical: A safety issue, resulting in an automatic reject of the lot.
  • Major: A functional failure that prevents the part from working as intended.
  • Minor: A cosmetic imperfection that does not affect functionality.
• Decision: PASS, REJECT, or UAI (Use As Is) must be clearly stated. It must be noted that UAI requires a referenced, approved Deviation number.

Final Checkout: Templates pack: NCR, CAPA, audit, calibration, incoming report

Record Type	Critical Identification Field	Engineering Reason
NCR	Traceability ID	Without this, it is very difficult to isolate the exact “Blast Radius” of a specific defect.
CAPA	Validation Evidence	A CAPA is not officially closed until the fix is objectively proven effective by data.
Audit	Objective Evidence	Statements like “Process looks good” are opinions. Specific file names or IDs provide the required proof.
Calibration	”As-Found” Data	This data is required to determine if previous production runs are analytically suspect.
IQC Report	Sample Size	This must precisely match the required Lot Size via the Acceptable Quality Level (AQL). Inspecting random quantities invalidates the statistical math.