| Field capture on siteRecording field, sample and groundwater data at the point of work. | ○NoPaper sheets re-typed later | ◐PartialMobile capture as a separate module | ◐PartialOnline-first data entry for field and office teams |
|---|
| Handwriting transcriptionTurning legacy or hand-written field sheets into structured records. | ○NoManual re-entry | ○NoNot part of the core estate | ◐PartialOCR 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 reported results |
|---|
| 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 |
|---|
| Review 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 | ◐PartialgINT importer planned; AGS and Excel intake availableIn development |
|---|
| Browser-only accessWorking without a per-machine desktop install. | ○NoDesktop install required | ◐PartialCloud estate, desktop client for logging | ●YesBrowser for every role |
|---|
| Data exit in open formatsRetrieving the full estate in open formats on request. | ◐PartialFiles are local but proprietary | ◐PartialExport supported, process-led | ●YesAGS 4.1 and Excel export on request |
|---|
| Design-suite integrationDirect hand-off into a wider civil design and digital-twin stack. | ○NoNot applicable | ●YesNative to the suite | ◐PartialLandXML, IFC, DXF and GeoJSON exports |
|---|
| Factual report reconciliationComparing report statements, investigation census and quantities with the governed source record. | ○NoManual cross-check across files | ◐PartialDocument workflow varies by configuration | ◐PartialReport, BOQ and source-data comparison with traceable comments |
|---|
| Design-parameter optionsPublished methods run inside their limits; the project's engineer decides. | ◐PartialCalculations distributed across templates | ◐PartialAvailable across separate analysis tools | ◐PartialSources, limits, confidence and exclusions; no design calculations |
|---|
| Independent assuranceThird-party assurance of information security controls. | ◐PartialDepends on the vendor | ●YesEstablished assurance programme | ◐PartialControls in progress; not independently assured |
|---|