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
- Inspections and checks
Inspections and checks
Resolve the requirements and evidence before accepting or rejecting inspection scope.
OverviewInspection Review Queue×
Soil Testing Lab System · Inspections and checks
New
Inspection Review Queue
Approval conditions
| Inspection number | Subject reference | Inspection type | Scheduled at | Assigned to | Status | |
|---|---|---|---|---|---|---|
| INS-58356 | Review ins-784 | Incoming | 12 Oct | Review | ||
| INS-33595 | Review ins-629 | In process | 13 Oct | Review | ||
| INS-97516 | Review ins-138 | Final | 25 Oct | Review | ||
| INS-14085 | Review ins-297 | Service | 17 Oct | Review | ||
| INS-63062 | Review ins-386 | Incoming | 21 Oct | Review |
6 of 6 records
Review ins-784Inspections · INS-58356
IncomingScheduled at12 Oct
StatusReview
What you can do
Put the requirement beside the observation
An inspection identifies the subject being checked, its inspection type and the person assigned to conduct it. Each linked check records a requirement, observation and result, with supporting evidence where needed. The Inspector uses that structure to explain the work performed before the Quality Reviewer makes the disposition decision.
The Inspections page brings a status board together with a chronological record list and selected-record detail. From that working context, the team can inspect linked checks and nonconformances. Keep the observation specific enough that the reviewer can understand why the Inspector marked a requirement Pass, Fail or Not applicable.
How the work is organized
- Assigned inspection. The Inspector opens the Planned work and starts it through the guarded operation. The assigned person and scheduled date help the team organize what needs attention.
- Resolved checks. Save observations, results and evidence against the intended inspection. Pending checks need resolution before the inspection can be submitted for review.
- Disposition decision. The Quality Reviewer examines the Review-stage scope and accepts eligible passing work or rejects failed work through the decision procedure. Failed checks feed the linked nonconformance process.
What to agree during setup
Agree which requirements belong to each inspection type and what evidence the reviewer expects for them. Define when Not applicable is appropriate and how the Inspector explains that choice. The result label should be accompanied by enough observation detail to make the decision understandable to another person.
Configure the Inspector and Quality Reviewer identities through the person records used by the guarded actions. Rehearse a changed record during submission so the team understands how the current work is checked before a decision is accepted. Agree how the reviewer responds when evidence is incomplete and how the Inspector continues the work without bypassing the review state.
Check the handoff on an actual case
Prepare an incoming inspection for sample S-1042. The Inspector starts the Planned record, opens its requirements and records observations against the linked checks. Leave a check Pending in the rehearsal and attempt submission. Resolve it with an appropriate result and evidence before submitting the inspection to Review.
Ask the Quality Reviewer to inspect a passing scope and record acceptance. Then rehearse a separate case containing a failed check, using a clear observation and supporting evidence. The reviewer rejects that scope and inspects the resulting nonconformance. Repeat the disposition request under the guarded procedure and check that the earlier outcome is reused rather than creating another issue for the same failed check.
What your team sees
- Inspection Worklist — Find Planned, In progress and Review work with its assigned person.
- Pending Checks — Identify requirements still waiting for a resolved result.
- Inspection Review Queue — Inspect the scope ready for the Quality Reviewer’s decision.
Follow the work through
Follow inspection and disposition, then use corrective action verification for failed scope requiring follow-up.
What it keeps track of
Data model- 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.
- Nonconformances
- Nonconformances raised from failed inspection scope, with severity and disposition status.
- Soil samples
- Soil samples collected under an operational inspection record, with field reference, depth and receipt dates.
Who uses it
Permissions- Inspector
- , Quality Reviewer, Quality Auditor, Admin.
- The Inspector conducts the work; the Quality Reviewer decides the eligible scope.
Set up Soil Testing Lab System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.