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.
- Soil Testing Lab System
- Features
- Nonconformances and corrective actions
Nonconformances and corrective actions
Contain failed inspection scope and close corrective work only after independent verification.
OverviewEffectiveness Review Queue×
Soil Testing Lab System · Nonconformances and corrective actions
New
Effectiveness Review Queue
Close waits for the quality reviewer
| Nonconformance | Root cause | Action | Due date | Completed at | Owner | |
|---|---|---|---|---|---|---|
| NNC-2000 | RC-840 | ACT-337 | 17 Oct | |||
| NNC-9875 | RC-261 | ACT-566 | 08 Oct | |||
| NNC-4267 | RC-513 | ACT-337 | 23 Oct | |||
| NNC-2451 | RC-937 | ACT-104 | 26 Oct | |||
| NNC-6072 | RC-662 | ACT-113 | 22 Oct |
6 of 6 records
RC-840Corrective actions · CA-84606
Effectiveness reviewNonconformanceNNC-2000
ActionACT-337
Due date17 Oct
What you can do
Carry the failed requirement into owned work
A rejected inspection gives the team a concrete issue to investigate. The linked nonconformance retains the detected date, severity and description against that inspection. The Quality Reviewer coordinates containment and disposition, while Action Owner records the root cause, planned action and due date for the corrective work.
Corrective actions remain linked to their parent nonconformance. That relationship lets the reviewer inspect the full set of work before deciding whether the underlying issue is ready to close. An implemented action still needs effectiveness review; the owner supplies the evidence and an independent Quality Reviewer decides whether the outcome is acceptable.
How the work is organized
- Issue context. Read the inspection and failed-check evidence when describing the nonconformance. Keep the severity and description useful to the people who will contain and investigate the issue.
- Owned action. Action Owner records the root cause and action plan with a due date. My Corrective Actions helps that person follow the work assigned to them.
- Effectiveness decision. The independent Quality Reviewer examines the submitted outcome. Accepted work can close; failed verification returns the action to implementation with the earlier context retained.
What to agree during setup
Agree how the team uses containment, investigation and disposition states before asking for corrective implementation. Decide what a plan needs before it is approved and which evidence the owner must provide for effectiveness review. The reviewer should be able to explain what changed and why the evidence supports the outcome.
Configure the independence check against the action owner and rehearse it using different accounts. Define how failed verification returns work to the owner and what explanation accompanies that result. Review the parent nonconformance’s linked actions before closure: an accepted result on an individual action must not hide another action still awaiting an acceptable outcome.
Check the handoff on an actual case
Use a rejected incoming inspection where the sample identity check failed. The Quality Reviewer reads the observation and coordinates containment while the team investigates. Action Owner records the cause, a plan to address it and the due date, then follows the agreed approval and implementation procedure.
Submit the implementation evidence for independent effectiveness review. Rehearse a failed verification first and confirm that the action returns to implementation with its history available. Then submit a supported outcome and have the reviewer accept it. Include another linked action still awaiting verification and check that the parent nonconformance remains open until all linked actions have accepted outcomes.
What your team sees
- Open Nonconformances — Read issues moving through containment, investigation and disposition.
- My Corrective Actions — Follow owned action plans and due dates.
- Effectiveness Review Queue — Inspect implementation work awaiting the independent outcome decision.
Follow the work through
Use corrective action verification and inspect the wider quality context through methods, training and audits.
What it keeps track of
Data model- Nonconformances
- Nonconformances raised from failed inspection scope, with severity and disposition status.
- Corrective actions
- Corrective actions owned by a person, with root cause, action plan and effectiveness review.
- Inspections
- Quality inspections covering incoming, in-process, final and service checks for soil testing operations.
- Inspection checks
- Individual requirement checks captured against an inspection, with observation and evidence.
- People
- Laboratory staff and quality personnel referenced by inspections, audits, corrective actions and result reviews.
Who uses it
Permissions- Quality Reviewer
- , Action Owner, Inspector, Quality Auditor.
- The owner implements the action; the independent reviewer evaluates effectiveness.
Set up Soil Testing Lab System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.