Skip to main content
Categories compared
Two + G&
Capabilities
14 lines
Basis
Submission outcome
Named vendors
None

The categories

Three delivery models, three different failure points.

CAT ACategory

Legacy desktop logging

File-based tools installed per machine, driven by templates and local project databases.

Strength
Familiar log layouts and offline drafting.
Limit
Files fragment, templates drift, and validation happens after the deliverable is assembled.
CAT BCategory

Heavyweight enterprise platform

Hosted data estate paired with per-seat desktop clients inside a wider civil design suite.

Strength
Central storage, wide standards library and large-programme procurement track record.
Limit
Long configuration effort, split licensing, and submission control still handled by process, not the system.
G&Category

Ground And

G& is the geotechnical data platform where every value is traced, checked and approved.

Strength
Validation and review are built into the record, not bolted onto the export.
Limit
Newer entrant: assurance programme in progress and no design-suite integration.

Line by line

The capability matrix.

Ratings describe the category as it is typically delivered, not any single product. Where G& does not compete, it says so.

  • Yes
  • Partial
  • No

G& ratings describe the current release. Items marked in development are not yet generally available.

Capability comparison between legacy desktop logging tools, heavyweight enterprise platforms and G&
CapabilityLegacy desktopEnterprise cloudGround And
Field capture on siteRecording field, sample and groundwater data at the point of work.NoPaper sheets re-typed laterPartialMobile capture as a separate modulePartialOnline-first data entry for field and office teams
Handwriting transcriptionTurning legacy or hand-written field sheets into structured records.NoManual re-entryNoNot part of the core estatePartialOCR with reviewer confirmation
Laboratory test lifecycleScheduling, results entry and status of each test against its sample.PartialResult tables, limited lifecycleYesLaboratory module availableYesTest lifecycle through to reported results
Validation before submissionRule checks on units, dictionary use, derived parameters and classification consistency.NoChecked by the engineer, after exportPartialExport-time checks and reportsYesContinuous 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 fidelityYesConfigurable AGS exportYesPackage carries its validation outcome
Review trailWho approved which record, at what state, and when.NoHeld in email and file namesPartialWorkflow via configurationYesApproval state stored on the record
Single source of truthOne authoritative record set across field, laboratory and engineering teams.NoPer-machine project filesYesCentral hosted estateYesOne estate, one record per artefact
Legacy archive migrationMoving historic project archives into a current, standards-aligned structure.NoThe archive is the problemPartialMigration as a services engagementPartialgINT importer planned; AGS and Excel intake availableIn development
Browser-only accessWorking without a per-machine desktop install.NoDesktop install requiredPartialCloud estate, desktop client for loggingYesBrowser for every role
Data exit in open formatsRetrieving the full estate in open formats on request.PartialFiles are local but proprietaryPartialExport supported, process-ledYesAGS 4.1 and Excel export on request
Design-suite integrationDirect hand-off into a wider civil design and digital-twin stack.NoNot applicableYesNative to the suitePartialLandXML, IFC, DXF and GeoJSON exports
Factual report reconciliationComparing report statements, investigation census and quantities with the governed source record.NoManual cross-check across filesPartialDocument workflow varies by configurationPartialReport, BOQ and source-data comparison with traceable comments
Design-parameter optionsPublished methods run inside their limits; the project's engineer decides.PartialCalculations distributed across templatesPartialAvailable across separate analysis toolsPartialSources, limits, confidence and exclusions; no design calculations
Independent assuranceThird-party assurance of information security controls.PartialDepends on the vendorYesEstablished assurance programmePartialControls in progress; not independently assured

Use it in evaluation

Five questions worth asking every vendor.

Feature lists rarely separate the categories. These questions do, and G& is happy to be measured by them.

  1. 01

    Where in the workflow does validation actually happen — on the live record, or at export time?

  2. 02

    Can the vendor show the review trail for a submitted package, per record?

  3. 03

    What does the migration of a historic archive cost, and who carries the risk of a failed submission?

  4. 04

    What is the total licensing exposure for the roles who only need to read the data?

  5. 05

    In open formats, what exactly comes back if the contract ends tomorrow?

Next step

Test the matrix against your own submissions.

Bring a recent package and we will walk the same line: capture, laboratory, validation, review, AGS 4.1 delivery — and show where the current toolchain lets errors through.