Register at collection
Create or confirm the sample identifier with project, location, depth, type and collection details.
Built for Australian geotechnical teams
Track geotechnical samples from field collection to laboratory handoff.
Keep sample identity, depth, location, custody events, requested testing and final disposition connected to the investigation and project.
Unique sample records
Custody history
Laboratory handoff
Australian geotechnical workflow
Preserve sample identity through every operational handoff.
A geotechnical sample must remain identifiable from collection through transport, receipt, preparation, testing, storage and disposal. Labels, handwritten sheets and disconnected registers make it harder to establish which specimen produced a result or where an exception occurred. GeoCRM connects the sample identifier to its project, location, depth or source, requested work and laboratory status. It supports traceable handovers while leaving sampling procedures, preservation, acceptance criteria and custody controls to the organisation's quality system.
[01] Sample management
/ Connected GeoCRM workflow
Keep sample identity and responsibility visible at every handoff. Connect samples to their investigation location, project, laboratory request and custody history so the evidence remains traceable.
Field origin
Create samples against the correct borehole, trial pit, depth and investigation.
Custody events
Record transfers, receipt and responsibility as samples move between people and locations.
Laboratory requests
Connect selected samples to requested methods, priorities and laboratory work.
Retention and disposal
Keep storage, condition and disposal context available for audit and operations.
Available capability A practical capability set for Australian geotechnical operations. Configure terminology, permissions and workflow to suit your business and technical procedures.
- Sample identifiers and depths
- Investigation and location linkage
- Chain-of-custody events
- Laboratory request handoff
- Condition and storage context
- Retention and disposal history
How it works in GeoCRM A practical workflow from setup and capture through review, delivery and retained project evidence.
Record transfer and receipt
Capture custody handover, transport context, laboratory receipt and condition or exceptions.
Connect tests and subsamples
Link preparation, specimens, worksheets and requested methods to the originating sample.
Retain final disposition
Keep results, storage location, retention period and authorised disposal history as required.
Operational detail for geotechnical teams Concrete capabilities for Australian consultancy, field and laboratory workflows.
Unique sample identity
Reduce ambiguity with controlled identifiers carried across field and laboratory records.
Source traceability
Retain project, borehole or test pit, depth, date and collector context.
Receipt checks
Record arrival, condition, quantity and exceptions before laboratory work begins.
Test linkage
Associate worksheets and results with the correct sample or prepared specimen.
Custody events
Document accountable handovers and status changes through the lifecycle.
Retention visibility
Support location, hold period and disposal records under the laboratory procedure.
Sample Tracking & Chain of Custody FAQs
Is chain of custody only for environmental samples?
No. The level of custody control varies, but geotechnical and construction-material samples also need reliable identity, source and handling records.
Can labels use barcodes or QR codes?
Identifier and scanning requirements can be assessed during configuration based on your label hardware and workflow.
Does software define our retention period?
No. Retention and disposal rules should come from contracts, methods, accreditation scope and the laboratory quality system.
Can damaged or unsuitable samples be recorded?
The receipt workflow can capture condition and exceptions so decisions are visible and traceable.
See it with your own workflow
Follow one sample journey in a GeoCRM demo.
Bring a real project, schedule, field record, laboratory request or report. We will show how the workflow can be configured without asking you to share confidential client data.