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
- Audits and quality oversight
Audits and quality oversight
Follow audit findings and use inspection evidence to explain quality work.
OverviewMy Inspections×
Soil Testing Lab System · Audits and quality oversight
New
My Inspections
Inspections
| Inspection number | Subject reference | Inspection type | Scheduled at | Completed at | Assigned to | |
|---|---|---|---|---|---|---|
| INS-72399 | Planned ins-502 | Incoming | 27 Oct | |||
| INS-53509 | In progress ins-671 | In process | 12 Oct | |||
| INS-84293 | Review ins-435 | Final | 27 Oct | |||
| INS-21889 | Accepted ins-834 | Service | 08 Oct | |||
| INS-23703 | Rejected ins-989 | Incoming | 04 Oct |
6 of 6 records
Planned ins-502Inspections · INS-72399
IncomingScheduled at27 Oct
StatusPlanned
What you can do
Keep the audit question and follow-up together
Quality Auditor prepares an audit with a scope, planned date and named auditor. The audit state shows whether the work is planned, in progress, reporting or closed. Use the scope to explain which laboratory activity is being examined so the findings can be read in the context of the work that prompted them.
Each audit finding records a requirement, finding text and severity, with an owner and due date. The closure date provides another point for follow-up. Inspection outcomes and corrective action evidence help the team explain the laboratory’s response to quality issues, while controlled documents and acknowledgments provide context for the procedures staff were expected to use.
How the work is organized
- Audit scope. Quality Auditor identifies the activity under examination and the planned work. The named auditor and dates make responsibility visible during reporting.
- Owned finding. Record the requirement and finding with a severity, owner and due date. Give the owner enough detail to understand the follow-up without relying on the audit meeting alone.
- Quality evidence. Read relevant inspection checks, corrective work and method records when preparing the audit explanation. Keep each record’s actual relationship and context clear during the review.
What to agree during setup
Agree how audit scopes are named and how findings are assigned to people. Define what supports a recorded closure date and who checks that evidence before the audit is closed. A finding should retain a recognizable requirement even when the team later revises the procedure discussed during the audit.
Also agree how the auditor uses inspection outcomes in the review. Distinguish unresolved checks from failed checks and read the underlying observations before drawing a conclusion. Inspect corrective effectiveness outcomes in their parent nonconformance context. Decide how approved document versions and staff acknowledgments will be presented during an audit so the record links remain understandable when methods change.
Check the handoff on an actual case
Plan an audit of soil sample receipt and result attribution. Quality Auditor reviews sample S-1042, its inspection checks and the analyte entry linked to it. Use the approved receipt procedure and the relevant staff acknowledgment to explain the expected operating process.
Record a finding against a specific requirement and assign an owner with a due date. Ask the Quality Reviewer to read the finding and identify the supporting inspection or document evidence. Before recording closure, check the follow-up explanation and any related corrective work. Then close the audit under the agreed reporting procedure while retaining the original scope and owned findings for later reference.
What your team sees
- Audit Worklist — Follow audits in preparation, execution and reporting.
- Failed Checks — Inspect the observations and evidence behind failed inspection requirements.
- Inspection Lifecycle Board — Discuss the recorded inspection workload and disposition outcomes.
Follow the work through
Use methods, training and audits and corrective action verification when the review identifies follow-up work.
What it keeps track of
Data model- Audits
- Internal and supplier quality audits with scope, auditor and reporting status.
- Audit findings
- Findings raised from an audit against a specific requirement, with owner and due date.
- People
- Laboratory staff and quality personnel referenced by inspections, audits, corrective actions and result reviews.
- 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.
- 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.
- Controlled documents
- Versioned controlled documents such as SO ps and methods, with effective date and approval status.
- Training acknowledgments
- Acknowledgments recording that a person has read and accepted a controlled document version.
Who uses it
Permissions- Quality Auditor
- , Quality Reviewer, Inspector, Document Coordinator, Action Owner.
- Quality Auditor
- Maintains the audit and its findings; the other participants supply the relevant operating evidence.
Set up Soil Testing Lab System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.