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.
- Quality Management
- Features
- Nonconformances
Nonconformances
Keep rejected inspection scope tied to its issue, containment and disposition.
OverviewMy inspections×
Quality Management · Nonconformances
New
My inspections
Inspections
| Inspection number | Subject reference | Scheduled at | Status | Assigned to | |
|---|---|---|---|---|---|
| INS-27754 | Planned ins-571 | 19 Oct | Planned | ||
| INS-27165 | In progress ins-606 | 06 Oct | In progress | ||
| INS-85409 | Review ins-347 | 27 Oct | Review | ||
| INS-39187 | Accepted ins-840 | 10 Oct | Accepted | ||
| INS-44388 | Rejected ins-506 | 03 Oct | Planned |
6 of 6 records
Planned ins-571Inspections · INS-27754
PlannedScheduled at19 Oct
What you can do
Follow the issue back to its source
A rejected inspection can raise a linked nonconformance for the failed scope. The record carries its detected date, severity and description, and points to the inspection that produced it. That link matters when several checks were recorded on the same subject: a corrective owner can return to the observation and evidence instead of working from a short issue title alone.
Quality Manager uses the nonconformance to keep the issue visible as it moves from Open through Containment, Investigation and Disposition to Closed. The record does not stand in for a full corrective action. corrective actions link back to the issue and carry their own owner, root cause, action, due date and status. Closure depends on all linked actions being closed after effectiveness review.
How the work is organized
- Detect. Quality Approver rejects failed inspection scope after reviewing required check results and raises the linked issue.
- Contain. Quality Manager records the problem and follows the issue through containment and investigation.
- Resolve. Corrective owners complete approved actions; the issue closes only after linked actions close.
Severity is selected as Minor, Major or Critical. Decide what each means for the team’s response and who needs to see the issue at each stage. The description should identify the failed condition in terms a person investigating it can verify. A status change alone should never erase the inspection context.
What to agree during setup
Agree how rejected scope is described when one inspection has both passing and failing checks. Use the inspection link to retain the complete check history, then describe the specific failed condition on the nonconformance. Assign responsibility for containment and for starting linked corrective action work. Decide who records the Disposition decision and what evidence the reviewer needs before the issue is eligible to close.
People assigned to actions must be connected to Users so each owner can find their work. A nonconformance has no separate owner reference; its corrective actions carry owners. Quality Manager should therefore review both the issue and its linked actions when asking who must act next.
Check the handoff on an actual case
A Final inspection for Q-104 finds a surface defect. The Quality Approver rejects the failed scope after seeing the Inspector’s check result, observation and attachment. The linked nonconformance is recorded with a Major severity and a description of the defect. Quality Manager follows containment and investigation, then the team records a corrective action for the root cause.
If two corrective actions are linked to that issue, closing one is not enough. The correction workflow requires every linked action to be Closed before the nonconformance reaches Closed. During rehearsal, leave one action in effectiveness review and confirm the issue stays open. This distinguishes completed work from verified resolution and gives the reviewer a clear reason to withhold closure.
A failed check without usable evidence should be handled before the inspection leaves the Inspector’s queue. It should not become a vague issue that the corrective owner has to reconstruct. Keep the observation and attachment at the source, then use the nonconformance description to explain the scope of the failure.
What your team sees
- Open nonconformances — Issues still in containment, investigation or disposition, with severity and source inspection.
- Actions for effectiveness review — Linked corrective work awaiting the independent check needed for closure.
Follow the work through
What it keeps track of
Data model- Nonconformances
- Nonconformances records for Quality Management.
- Inspections
- Inspections records for Quality Management.
- Inspection checks
- Inspection Checks records for Quality Management.
- Corrective actions
- Corrective Actions records for Quality Management.
Who uses it
Permissions- Quality Approver
- Decides failed inspection scope.
- Quality Manager
- Follows the issue.
- Inspector
- Supplies the original check evidence.
- Assigned corrective owners resolve linked actions.
Set up Quality Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.