Non-Conformances

From issue to root cause,
with the trail to prove it.

AI-assisted intake, structured root cause analysis, and evidence-gated closure. NCRs and customer complaints in one workflow — the way investigations should run, not the way spreadsheets force them to.

app.qformance.io / ncrs / NCR-2026-0148
NCR-2026-0148High severityCustomer complaintOpened 18 Apr · 3d open

Customer-reported finish defect on shipped batch B-22041 (37 units)

Events
Conditions
Causes & Factors
18 Apr · 09:14
Defect reported
Customer call: 12 of 37 units show clouded finish
18 Apr · 14:30
Containment placed
Remaining stock of B-22041 quarantined; 240 units held
19 Apr · 11:00
Cause identified
Lacquer batch L-1109 humidity exposure during storage
19 Apr · 16:20
Corrective opened
Update WI-FIN-08 humidity threshold + storage SOP
20 Apr · 10:00
Customer credit
37-unit replacement scheduled, ETA 22 Apr
Closure blocked — 1 corrective action awaiting verification, RCA evidence missing for “lacquer batch QC”.

Open them faster.

The friction of opening an NCR is what kills your data quality. AI takes that friction away — and the rest of the form is built for the way investigations actually work.

AI draft assist

Type one sentence describing what happened. AI fills the title, description, source, severity, and suggested category — you review, adjust, and submit. The first ten minutes of every NCR, automated.

ECFC dual-lane timeline

Events, Conditions, and Causes & Factors recorded as a structured timeline — the investigation reads like a story, not a wall of free text. Built for quality engineers, not form-fillers.

Customer complaints, same flow

Customer complaints route through the same pipeline as internal NCRs — same RCA tooling, same evidence gating, same audit trail. One register, one source of truth.

New NCR · AI draft assist
What you typed
Customer called — 12 of 37 units in batch B-22041 showed clouded finish on the dashboard panels.
AI-filled fields
Title
Customer-reported finish defect on shipped batch B-22041 (37 units)
Source
Customer complaint
Severity
High
HIGH
Category
Cosmetic / Surface finish
Affected qty
37 units · batch B-22041

Root cause analysis that holds up.

Three structured RCA tools, native to the NCR workflow — pick the one that fits the failure mode. Every chain of reasoning is preserved, not summarized.

5-Why

Drill from symptom to root cause.

Five structured iterations. Each 'why' links to evidence and the resulting action — so the chain of reasoning is preserved, not lost in a meeting.

5-Why · NCR-2026-0148
1
Why was the finish clouded?
Lacquer cured under high humidity
2
Why was humidity high during cure?
Storage area RH exceeded 65% threshold
3
Why did RH exceed threshold?
Dehumidifier offline since 14 Apr
4
Why was the dehumidifier offline?
Filter alarm ignored — no escalation path
5
Why was the alarm ignored?
No assigned owner for storage-area equipment alarms
ROOT CAUSE
Fishbone (Ishikawa)

Categorize contributing factors.

Across the standard 6Ms — Man, Machine, Method, Material, Measurement, Environment — visually. Add custom categories, drag causes between branches, export the diagram for your CAPA report.

Fishbone · 6M categories
EFFECTManNo alarm ownerOp. unawareMethodNo escalationRH limit informalMachineDehumidifier offAlarm ignoredMaterialLacquer batch L-1109MeasurementRH not loggedEnvironmentRH > 65%
Fault Tree

Model how multiple failures combined.

When you need to model how multiple failures combined to produce the event, the Fault Tree gives you AND/OR logic, intermediate events, and basic causes — built in the editor, no external tooling.

Fault Tree · clouded finish
Clouded finishORHigh RH during cureBad lacquer batchANDDehum offNo alarmL-1109

Close with evidence, not promises.

An NCR doesn't close because someone clicked a button — it closes because the evidence is there. Configurable gating, structured action types, and a complete activity history.

Mandatory evidence gating

Configure which fields, attachments, and verification steps are required before an NCR can close. The system blocks closure until evidence is present — no more retroactive paperwork.

Money lost or time lost — both, attributed

Capture cost losses (labor, scrap, penalties, regulatory, reputation, environmental) and time losses (internal labor hours, external NPT) on the same record. Each line attributed to internal or external party so the register reports who carried the impact.

Three action types

Containment for the immediate problem, corrective for the root cause, preventive for related risks. Each with its own assignee, due date, and verification step.

Full activity log

Every status change, comment, attachment, and approval is timestamped and attributed. Auditors see the complete history of how the NCR was handled — not just the final state.

Closure panel · NCR-2026-0148
Evidence checklist
Photos of defective unitsOK
×Lacquer batch QC reportMISSING
Storage RH log (14–18 Apr)OK
Customer credit confirmationOK
Action verification
CONTAINMENTverified
Quarantine batch B-22041
L. Chen
CORRECTIVEpending
Update WI-FIN-08 humidity threshold
M. Patel
PREVENTIVEverified
Assign storage alarm owner
A. Okafor
🚫 Closure blocked · 1 action pending, 1 evidence missing

Wired into the rest of your QMS.

From audit findings

Auditors raise an NCR from any finding with one click — the question, evidence, and clause context all carry across.

Into the risk register

Recurring NCRs surface as risk candidates. Link an NCR to an existing risk or raise a new one without leaving the record.

Out to MOC

When the corrective action requires a process or document change, raise a Management of Change record directly from the NCR — the change inherits the cause context.

Document evidence, frozen

Reference a controlled document in your evidence and the link freezes to the approved version in force at the time. Audit reconstruction shows exactly what was used.

Connections · NCR-2026-0148
NCR-2026-0148
This investigation
Audit A-45 finding
Risk RR-022
MOC-074 raised
WI-FIN-08 v2.3 (frozen)
Actions & Verification

Every NCR action lands in one place.

Containment, corrective, and preventive actions don’t live siloed inside the NCR. They flow into the unified Actions view alongside every other action across the QMS — same verification flow, same overdue tracking, same My Actions queue.

Unified register

NCR actions appear alongside audit, MOC, meeting, and FMEA actions in one Mine / All view — no module-hopping to see what your team owes.

Verification, not paperwork

Each action is closed by a single verifier with notes — optionally linked to the meeting where effectiveness was confirmed. The verification record locks to that meeting once it closes, so the audit trail freezes with it.

Frozen closure evidence + recoverable delete

Closure evidence pins to a specific document version, file, or URL — permanent even if the underlying document changes. And an NCR sent to Trash is recoverable for 90 days with one-click restore, including cross-module links and the full History.

Make every NCR a record you'd trust under audit.

Start your 30-day free trial. Open your first NCR, run a real RCA, and see what an investigation trail should look like.