Prepare the location
Load the project, coordinates, planned depth, drilling details and required logging fields.
Capture soil and rock strata, samples, SPT and other in-situ tests, core runs, groundwater observations and field evidence in one structured ground log.
Australian geotechnical workflow
A borehole log is a technical record, not a transcription exercise. Field observations, sample intervals, groundwater, drilling progress and test information need to remain tied to depth and location, then pass through competent review before issue. GeoCRM supports structured digital logging linked to the project and investigation location. Configured templates can improve consistency and reduce rekeying while leaving geological description, interpretation and approval with qualified personnel.
Record depths, descriptions, classifications, colours, weathering and strength context.
Capture samples, SPT, DCP, vane, strength, environmental and other test records.
Retain core runs, recovery information, discontinuities and groundwater observations.
Preview and export dedicated paginated borehole and trial-pit log PDFs.
Load the project, coordinates, planned depth, drilling details and required logging fields.
Record material descriptions, recovery, sampling, groundwater, tests and drilling notes as work progresses.
Check completeness, terminology, intervals and supporting evidence under your technical procedure.
Produce the required log or data output, record revision status and keep it linked to the project.
Keep strata, samples, tests and observations aligned to their measured intervals.
Support controlled fields and organisation-specific logging templates.
Connect each borehole to its project, coordinates, site map and investigation context.
Associate photos, drilling notes and related records with the location.
Make technical checking and issue status visible before a log is treated as final.
Reduce repeated transcription when data is needed for reports, schedules, sections or migration outputs.
No. It can support structured logging and configured terminology, but competent staff remain responsible for applying the current standard, project specification and company procedure.
Offline requirements are important for remote work and should be validated during the demo against the specific devices and workflows you intend to use.
Often yes. Data mapping depends on the quality, structure and identifiers in the source files or legacy database.
The workflow can separate draft capture, technical checking, approval and issued status.
See it with your own workflow
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.