These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Automotive QMS
- Features
- Nonconformances
Nonconformances
Link a rejected inspection to severity, containment and the issue that corrective action must resolve.
OverviewCritical severity×
Automotive QMS · Nonconformances
New
Critical severity
Nonconformances
| Inspection | Detected at | Severity | Description | Status | |
|---|---|---|---|---|---|
| INS-65769 | 18 Oct | Critical | Open nnc-674 | Open | |
| INS-48967 | 21 Oct | Critical | Containment nnc-216 | Containment | |
| INS-75389 | 13 Oct | Critical | Investigation nnc-299 | Investigation | |
| INS-77464 | 13 Oct | Critical | Disposition nnc-280 | Disposition | |
| INS-46546 | 06 Oct | Critical | Closed nnc-458 | Closed |
6 of 6 records
Open nnc-674Nonconformances · NNC-13086
CriticalInspectionINS-65769
Detected at18 Oct
StatusOpen
What you can do
Open a case from the failed inspection
A failed inspection decision needs a durable issue record. Quality Reviewer links a Nonconformance to the rejected Inspections case, records when it was detected, writes the description and chooses the severity. Minor, Major and Critical are the available values. That link lets the team return to the original checks and evidence while it decides containment and disposition.
The issue moves through Open, Containment, Investigation and Disposition before Closed. These states help the team separate immediate handling from the cause analysis and final close. A critical label is a severity decision; the status says where the follow-up stands. Both matter in the working queue.
How the work is organized
- Source first. A nonconformance names its inspection so a reviewer can revisit the exact check results.
- Severity with context. The description explains the affected scope and the selected severity, rather than asking another person to infer it from the label.
- Action link. Corrective actions point back to the nonconformance, keeping cause and effectiveness review with the original issue.
What to agree during setup
Agree what the team means by Minor, Major and Critical for its product and customer work. Choose who can make the containment decision after an inspection is rejected and how that decision is described in the record. Have the Quality Reviewer hand the issue to a named Corrective Action Owner and keep that responsibility visible on the linked action.
Define when the team advances from Containment to Investigation and Disposition. These status changes should reflect an actual decision or retained evidence. The issue should not be closed simply because an action was entered. Effectiveness review must assess the action before both records close.
Check the handoff on an actual case
Start with a reviewed incoming inspection that has a failed check and attachment. Quality Reviewer rejects it, opens a nonconformance and chooses Major for a known affected scope. Confirm the source inspection is linked and the description makes the scope clear. Move the issue into Containment and ask Corrective Action Owner to open an action linked to it. The owner records a cause and the intended action.
Now review the issue from the nonconformance page. The original inspection and its failed requirement should be reachable. The corrective action should point to the same issue. After the action is implemented, a separate Quality Reviewer checks effectiveness before the issue closes. If the reviewer finds the correction ineffective, keep the issue active for another cycle rather than treating the closed label as the evidence.
What your team sees
- Open nonconformances — Issues in active states with detection date and severity.
- Critical severity — The highest severity cases across their current states.
- Due for effectiveness review — Linked actions waiting for a separate reviewer.
Follow the work through
Follow inspection to disposition for failure intake and corrective action for cause and effectiveness review.
What it keeps track of
Data model- Nonconformances
- Nonconformances records for Quality & Compliance (Source).
- Inspections
- Inspections records for Quality & Compliance (Source).
- Inspection checks
- Inspection Checks records for Quality & Compliance (Source).
- Corrective actions
- Corrective Actions records for Quality & Compliance (Source).
- People
- People records for Quality & Compliance (Source).
Who uses it
Permissions- Quality Reviewer
- Makes the inspection decision and records the linked issue.
- Corrective Action Owner
- Investigates and completes assigned work.
- Admin
- Maintains access for the people taking those actions.
Set up Automotive QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.