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
- Soil sample intake
Soil sample intake
Record the sample's field, depth and receipt context against its inspection.
OverviewReceived Soil Samples×
Soil Testing Lab System · Soil sample intake
New
Received Soil Samples
Soil samples
| Sample number | Field reference | Depth CM | Collected at | Received at | Operational record | |
|---|---|---|---|---|---|---|
| SS-94246 | FR-678 | 350 | 08 Oct | 10 Oct | INS-44643 | |
| SS-70638 | FR-940 | 160 | 07 Oct | 10 Oct | INS-36167 | |
| SS-87436 | FR-157 | 790 | 22 Oct | 15 Oct | INS-57750 | |
| SS-14630 | FR-410 | 430 | 03 Oct | 07 Oct | INS-65592 | |
| SS-80885 | FR-446 | 30 | 18 Oct | 15 Oct | INS-88576 |
6 of 6 records
FR-678Soil samples · SS-94246
Depth CM350
Collected at08 Oct
Received at10 Oct
Operational recordINS-44643
What you can do
Give each sample a recognizable starting point
The Inspector captures a soil sample against the operational inspection that will carry its quality checks. Record the sample number, field reference and depth in centimeters, then enter the collection and receipt dates. A Lab Analyst should be able to open the sample and understand which material arrived without relying on a handwritten label alone.
The inspection link gives the sample a place in the laboratory’s operating work. Use the inspection subject reference and assigned person to clarify who will resolve a receipt question. When a sample’s identity or dates need correction, follow the capture procedure so the next stage receives a coherent record rather than a second sample created to work around an unclear entry.
How the work is organized
- Sample identity. The sample number and field reference distinguish the material being received. Agree how the laboratory uses those values before importing or capturing a wider set of samples.
- Collection context. Depth and collection date describe the sample as received by the lab. Keep those values with the sample so the analyst can check the intended material before entering a result.
- Receipt handoff. The receipt date and linked inspection identify the operational context. The Inspector resolves a questionable reference or date before the sample moves into result capture.
What to agree during setup
Agree the sample numbering convention and the field reference used by the people supplying material. Define how depth is entered in centimeters and which unit rules the capture procedure accepts. Rehearse a date sequence in which receipt precedes collection so the team understands how an impossible interval is rejected and corrected.
Also agree who may capture or amend samples under an inspection. Map the Inspector’s signed-in account to the correct person record before using the guarded operation. Decide how repeated source submissions are recognized and how the team investigates a changed submission. A capture result should identify the existing sample clearly enough that the next person does not create another record unnecessarily.
Check the handoff on an actual case
Use an illustrative sample numbered S-1042 from the north field at a depth of 15 centimeters. The Inspector selects the intended inspection, enters the collection and receipt dates and submits the sample. Ask the Lab Analyst to open the resulting record and identify the field, depth and inspection before preparing an analyte entry.
Rehearse the same request with an incorrect inspection reference, then with a receipt date earlier than collection. Resolve the rejected input before submitting again. Finally, repeat a sample submission under the agreed identity procedure and inspect the resulting records. The Inspector and analyst should be able to point to the intended sample and explain why the next result belongs to it.
What your team sees
- Received Soil Samples — Find samples whose recorded receipt date has arrived and inspect their field and depth context.
- Inspection Worklist — Locate the operational inspection and person responsible for the next checks.
Follow the work through
Continue with sample and result capture and review the implementation plan.
What it keeps track of
Data model- Soil samples
- Soil samples collected under an operational inspection record, with field reference, depth and receipt dates.
- Inspections
- Quality inspections covering incoming, in-process, final and service checks for soil testing operations.
- People
- Laboratory staff and quality personnel referenced by inspections, audits, corrective actions and result reviews.
Who uses it
Permissions- Inspector
- , Lab Analyst, Quality Reviewer, Admin.
- The Inspector captures the sample; Admin supports the person-to-account mapping.
Set up Soil Testing Lab System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.