Capability matrix
Geotechnical software falls into two familiar categories: legacy desktop logging tools and enterprise cloud incumbents. This matrix sets G& against both on the capabilities that decide whether a submission passes first time — with no vendor names, so the comparison stays about the work.
The categories
File-based tools installed per machine, driven by templates and local project databases.
Hosted data estate paired with per-seat desktop clients inside a wider civil design suite.
One controlled line from field capture through laboratory, validation and signed AGS 4.1 delivery.
Line by line
Ratings describe the category as it is typically delivered, not any single product. Where G& does not compete, it says so.
| Capability | Legacy desktop | Enterprise cloud | Ground And |
|---|---|---|---|
| Field capture on siteRecording rig, sample and groundwater data at the point of work. | NoPaper sheets re-typed later | PartialMobile capture as a separate module | YesNative field capture, offline tolerant |
| Handwriting transcriptionTurning legacy or hand-written field sheets into structured records. | NoManual re-entry | NoNot part of the core estate | YesOCR with reviewer confirmation |
| Laboratory test lifecycleScheduling, results entry and status of each test against its sample. | PartialResult tables, limited lifecycle | YesLaboratory module available | YesTest lifecycle through to certificate |
| Validation before submissionRule checks on units, dictionary use, derived parameters and classification consistency. | NoChecked by the engineer, after export | PartialExport-time checks and reports | YesContinuous checks on the live record |
| AGS 4.1 output controlProducing an AGS package with its dictionary version and validation state recorded. | PartialExport depends on template fidelity | YesConfigurable AGS export | YesPackage carries its validation outcome |
| Approval and sign-off trailWho approved which record, at what state, and when. | NoHeld in email and file names | PartialWorkflow via configuration | YesApproval state stored on the record |
| Single source of truthOne authoritative record set across field, laboratory and engineering teams. | NoPer-machine project files | YesCentral hosted estate | YesOne estate, one record per artefact |
| Legacy archive migrationMoving historic project archives into a current, standards-aligned structure. | NoThe archive is the problem | PartialMigration as a services engagement | YesStructured migration to AGS 4.1 |
| Browser-only accessWorking without a per-machine desktop install. | NoDesktop install required | PartialCloud estate, desktop client for logging | YesBrowser for every role |
| Published, readable pricingBeing able to size the commercial exposure before a sales conversation. | PartialReseller-dependent | NoQuotation-led, split licensing | YesBands and seat rates published |
| Data exit without penaltyRetrieving the full estate in open formats on request. | PartialFiles are local but proprietary | PartialExport supported, process-led | YesAGS 4.1 and Excel, no exit fee |
| Design-suite integrationDirect hand-off into a wider civil design and digital-twin stack. | NoNot applicable | YesNative to the suite | NoOpen formats only, by design |
| Independent assuranceThird-party certification of the information security management system. | PartialDepends on the vendor | YesEstablished certification programme | PartialControls documented, certification in progress |
Use it in evaluation
Feature lists rarely separate the categories. These questions do, and G& is happy to be measured by them.
Where in the workflow does validation actually happen — on the live record, or at export time?
Can the vendor show the approval trail for a submitted package, per record?
What does the migration of a historic archive cost, and who carries the risk of a failed submission?
What is the total licensing exposure for the roles who only need to read the data?
In open formats, what exactly comes back if the contract ends tomorrow?
Next step
Bring a recent package and we will walk the same line: capture, laboratory, validation, approval, AGS 4.1 delivery — and show where the current toolchain lets errors through.