Your data has a load path.
We engineered it.
G& carries every borehole, sample, and lab result from the rig to a certified AGS 4.1 submission — validated at every step, traceable at every value, signed by your engineers.
For ground investigation contractors · geotechnical consultants · laboratories · client PMOs
Field → AGS 4.1 in one system
Rig logs, lab results, engineering derivations and the submission package on one governed record.
Validated before it is issued
Four validation layers run continuously — a blocker stops the export, not the deadline.
Every value traceable to a clause
Derived values resolve to their inputs, the governing standard version, and the engineer who signed.
Location BH-01 · strata, SPT & groundwater
Area A · investigation coverage
Boreholes
CPTs
Ready
Captured once, at source.
Rig logs, in-situ tests, samples, and groundwater readings are entered on the rig against a location and depth interval — with author, method, instrument, and timestamp bound to the value on write.
- Location & depth bound
- Author + timestamp
- No anonymous rows
The journey
Field → Lab → Validation → Engineering → Deliverables.
Five stages, one record, no re-entry between them. What is drawn below is what the software actually does at each stage — screens from the platform follow, shown with all client, project, location and personnel identifiers removed.
- Field01
Captured once, at source
Strata, samples, SPT increments and groundwater logged on the rig, bound to location and depth on write.
- Lab02
Request to approved result
Scheduling, testing, calculation, checking and approval on the sample record — results autofill back into the log.
- Validation03
Four layers, continuously
Integrity, engineering logic, AGS compliance and plausibility. Blockers stop the export, not the deadline.
- Engineering04
Derived, never typed
The standards engine computes classification, indices and correlations against a versioned clause.
- Deliverables05
Signed, then issued
Borehole logs, factual tables, AGS 4.1 and IPC quantities built only from approved records.
Inside the platform
The software, not the brochure.
Field capture on the rig, laboratory results computed by the standards engine, the four-layer validation console, the map and data explorer, and the AGS 4.1 export — annotated to BS 5930, BS 1377, ASTM and BS EN ISO 14688 / 14689.
Area A / BH-01 / Shift 2
| Depth | Type | Value | Std |
|---|---|---|---|
| 1.50 | SPT | N = 8 | D1586 |
| 3.00 | SPT | N = 12 | D1586 |
| 4.50 | U100 | sample | BS 5930 |
| 6.00 | SPT | N = 21 | D1586 |
| 7.50 | D | bag | BS 5930 |
| 9.00 | SPT | N = 26 | D1586 |
| 11.50 | CORE | TCR 96% | BS 5930 |
Portfolio / Area A / Coverage
| Location | Depth | Tests | State |
|---|---|---|---|
| BH-01 | 24.00 m | 12 SPT · 6 lab | ok |
| BH-02 | 18.50 m | 9 SPT · 4 lab | ok |
| BH-03 | 21.00 m | 11 SPT · 5 lab | warn |
| BH-06 | in progress | 4 SPT | muted |
| CPT-01 | 16.20 m | trace | ok |
Area A / Lab register / Batch 41
Particle size distribution · BS 1377-2
Plasticity · ASTM D4318
Shear box · BS 1377-7
| Sample | Test | Result | Standard | State |
|---|---|---|---|---|
| S-1141 | Atterberg | LL 42 · PI 19 | ASTM D4318-17 | ok |
| S-1142 | PSD | Fines 8% | BS 1377-2 | ok |
| S-1147 | Shear box | φ′ 32° · c′ 6 kPa | BS 1377-7 | ok |
| S-1151 | Oedometer | mv 0.08 m²/MN | ASTM D2435 | warn |
Area A / Validation & QA / Run 118
Records checked
18,442
Blockers
2
Errors
14
Readiness
87%
| Layer | Rule | Location | Detail | State |
|---|---|---|---|---|
| Integrity | SAMP_TOP < SAMP_BASE | BH-03 · 8.40 m | Base above top | error |
| AGS 4.1 | ISPT heading not in dictionary | BH-06 | ISPT_NVAL expected | error |
| Eng. logic | Sample outside logged stratum | BH-03 · 11.20 m | No GEOL parent | error |
| Plausibility | PI vs. LL off A-line | LAB-2214 | Review classification | warn |
| Integrity | Groundwater vs. drilling record | BH-05 | Reconciled | ok |
| Client rules | Naming convention · area prefix | Area A | Passed | ok |
Area A / Approved records / AGS 4.1
1"GROUP","GEOL"2"HEADING","LOCA_ID","GEOL_TOP","GEOL_BASE","GEOL_DESC","GEOL_LEG","GEOL_GEOL"3"UNIT","","m","m","","",""4"TYPE","ID","2DP","2DP","X","PA","PA"5"DATA","BH-01","0.00","2.40","Made ground: sand and gravel","MG","MG"6"DATA","BH-01","2.40","6.80","Loose to medium dense calcareous SAND","SC","SAND"7"DATA","BH-01","6.80","11.50","Firm CLAY with silt partings","CL","CLAY"8"DATA","BH-01","11.50","18.20","Weak to moderately weak LIMESTONE","LS","LMST"
Groups written
- PROJok
- LOCAok
- GEOLok
- SAMPok
- ISPTok
- COREok
- WSTDok
- LLPLok
- GRADok
Aligned to the standards your submissions answer to
Ground & Trust
Every value enters through exactly one door.
Most submission failures are structural: a typed value where a computed one belongs, a lab result with no chain back to its sample, an AGS file that validates but describes the wrong ground. G& closes those paths by design.
Three-door data entry
Raw measurements, engine-derived values, and certified results each enter through a single controlled path.
Four-layer validation
Data integrity, engineering logic, AGS compliance, and plausibility — run continuously.
Full traceability
Every derived value resolves to its inputs, governing standard, and timestamp.
The load path — select a stage
01 · Raw
ViewField and lab measurements, captured once at source.
02 · Engineered
ViewComputed by the standards engine. Read-only, always.
03 · Certified
SelectedApproved by a signing engineer. The only door to a deliverable.
Approval is a named human act. Nothing enters an AGS file, a report table, or a payment certificate without it.
- Enters via
- QA review, then explicit approval by a named signing engineer
- Authority
- Signing engineer · QA reviewer · Project manager
What changes at this stage
- Record locked with user, timestamp, and standard version
- Released to AGS 4.1 export, borehole logs, report tables, and IPC quantities
- Extends the validated corpus — queryable by later investigations
- Any later change raises a new issue and a forward-only transition
Validations that run here
CONTINUOUSClient-specific headings, naming, and formats checked
Approved is the only state a deliverable can be built from.
Want the field-level view — every value as it changes from raw capture to certified approval? The full diff table lives on the platform page.
Open the field-level diffValidation layers
Select a layer to see what it rejects.
Ground & capture / handwriting OCR
The rig writes it by hand.
G& reads it into the record.
Handwritten field boring logs are photographed and transcribed into structured raw records — depth intervals, sample types, SPT blow counts per increment (75 mm to BS EN ISO 22476-3, or 150 mm to ASTM D1586), TCR / SCR / RQD, and BS 5930 descriptions — then put through the same four-layer validation as typed entry. Client, project, location, and personnel fields are never transcribed.
Digitise a field sheetSheet → structured rows
Every handwritten interval becomes one raw record bound to its depth, with the source photograph attached.
Confidence per value
Each transcribed value carries a confidence score; anything below threshold is flagged for engineer review.
Mapped to AGS 4.1
GEOL, SAMP, ISPT, CORE, and WSTD headings populated on import — dictionary-checked, not free text.
Raw stage only
OCR never produces a derived or certified value. Standards calculate. Engineers sign.
Example outputs
What leaves the building.
Borehole logs, laboratory summaries, gradation curves, and plasticity sheets — rendered from approved records to BS 1377, ASTM, and AGS 4.1. Sample outputs are shown with all client, project, location, and personnel identifiers removed.
Borehole log — soils
BS 5930 · ASTM D1586
Borehole log — rock coring
BS 5930 · ASTM D6032
Particle size distribution
BS 1377-2
Atterberg limits
ASTM D4318-17
Factual reports
Beta capabilitySend a report with a review trail behind it.
G& can generate factual report content from approved records and review an existing factual report for scientific issues, data accuracy, missing evidence, inconsistencies, and standards alignment. The result is a readiness view with comments for resolution before submission.
This review workflow is in beta and is not yet 100% available in the current release. A qualified engineer remains responsible for the final technical review, acceptance, and sign-off.
See report outputsReview console
Factual report / review pass
Source alignment
12 / 12
Pass
Scientific comments
03
Resolve
Submission readiness
Pending
Engineer
Table 4.2 / sample S07 does not match the approved laboratory record.
CommentCheck the stated soil description against the plotted grading and plasticity results.
CommentASTM D4318 and BS 1377 references identified; engineer confirmation required.
ReviewPlatform
Field to deliverable, one controlled line.
One central geotechnical database. Validation and QA before review. Review before approval. Approval before anything leaves the building. The five stages, the modules behind them, and the field-level diff are set out in full on the platform page.
Live from the central database
Ground truth, intelligently.
Boreholes
CPTs
Trial pits
Lab complete
Weekly drilled meterage · current week highlighted
Ready — 3 areas
Go / no-go view per area before every client submission
Data management
Your ground history is an engineering asset. Govern it like one.
Every investigation your firm has delivered describes ground that will be built on again. G& holds that record as one governed estate — projects, areas, locations, strata, samples, in-situ tests, laboratory results, and groundwater observations in a strict parent–child schema.
History under the same discipline as live data.
Legacy AGS and Excel records enter through the same import, mapping, and four-layer validation as current works. Digitised is not the same as verified.
Knowledge that compounds.
Each approved submission extends a validated corpus of regional ground conditions. Desk studies, adjacent-phase investigations, and tender responses draw on data whose provenance is already established.
The corpus cycle
Project delivered — submission approved
Records locked — inputs, standards, timestamps preserved
Corpus extended — validated, versioned, queryable
Next investigation — informed before the first rig mobilises
Data that passed validation once holds its integrity permanently. The estate appreciates; it never degrades.
Ground & speed
Legacy systems are changing.
Your data isn't.
Legacy subsurface systems face end-of-life on December 31, 2028, with new licences ending after December 2027. Templates don't carry forward. If your logs, lab sheets, and AGS exports still run through a legacy desktop workflow and Excel, the migration question is already on your desk.
AGS-native, both directions
AGS 4.1 in, AGS 4.1 out, with Excel round-trip for the workflows your teams already run.
Built for submission, not just storage
G& is organised around one question: is this package ready to submit without rejection or rework?
Coexists with your estate
Open formats mean G& works alongside your existing design tools and downstream workflows.
Ground & trust / laboratory lifecycle
From lab request to payment certificate — one record.
G& carries the complete laboratory lifecycle: request, scheduling, testing, calculation, checking, approval, reporting, and billing. Then it does what no other platform does.
Approved records only
Nothing enters a deliverable, an AGS file, or a quantity statement until a named engineer has approved it.
IPC generated from the data itself
Interim payment statements are built directly from approved records.
No re-entry, no reconciliation
The record that passed validation is the record that gets billed. One source, zero drift.
Result status ladder
Forward-only. Every transition logged with user, timestamp, and standard version.
Reporting & analytics
From raw measurement to publication-grade output.
Borehole Log — BH-115
Calcareous sand over oolitic limestone · 25.00 m
Direct Shear — Failure Envelope
BS 1377-7 · consolidated drained · 3 specimens
Shear Stress vs Displacement
Full shear stress–displacement curve retained per specimen
σ′ = 49 kPa
σ′ = 98 kPa
σ′ = 147 kPa
Particle Size Distribution
BS 1377-2 wet sieving · classification derived by the engine
Also rendered by the engine: Atterberg limits & plasticity chart · consolidation fitting · UCS stress–strain · groundwater hydrographs · chemical aggressivity screening
Ground & intelligence
An AI co-pilot with zero calculation authority.
The standards carry sole calculation authority. Your engineers carry sole signing authority. The co-pilot explains, searches, flags, and summarises — every interaction audit-logged.
Explains, never decides
Plain-language explanation of validation issues and suggested fixes — every suggestion a draft for engineer review.
Cites or declines
Every claim traces to a record ID, a rule, or a standard clause. No source, no assertion.
Fully auditable
Prompt, output, and engineer decision logged for every interaction.
PROMPT > Explain why sample depth conflicts with strata boundary.
RESPONSE > Review BH-115 / S-08 against BS 5930 clause mapping. Calculation authority remains with the standards engine.
Ground & region
Built where your tenders move.
G& is native to the Gulf: regional coordinate systems, tier-one client submission formats, tender-grade documentation, and sovereign hosting options — backed by five decades of geotechnical delivery on the ground it serves.
heritage
AGS groups
everything connected
Boreholes validated and exported to AGS 4.1 in a single area submission
Errors on first-pass validation of that submission
Warnings. Not resolved — never raised.
Live project results. References available under NDA.
Client testimony
A governed data path for a landmark coastal development.
Project
Modon Ras El Hekmah
Delivery partner
Horema
Consultants
Dar · HILL International
“G& gave our team a single, controlled environment to manage the geotechnical data for the Modon Ras El Hekmah project and generate the AGS 4.1 submission package. It connected field, laboratory, and quality-control records in one traceable workflow, helping us coordinate effectively with Dar and HILL International while maintaining confidence in the quality and readiness of every deliverable.”
Case studies
Borehole to submission, walked through.
Three walkthroughs of the same discipline applied to different work: a coastal area submission, a legacy estate migration, and the laboratory-to-payment cycle. Each shows the five stages, the failures caught on the way, and what changed against the previous workflow.
CS-01 · Scope
22 boreholes · 148 SPT tests · 96 lab tests · 25.00 m max depth · AGS 4.1 area package
Walkthrough
- 01 / Field
Logged once at source
Drilling, SPT increments, sampling, and groundwater readings entered on the rig against location and depth interval — descriptions to BS 5930, no re-typing at the office.
- 02 / Database
Bound to the schema
Every record landed under project → area → location → stratum, with referential integrity enforced at the database rather than at export.
- 03 / Validation
Four layers, continuously
Integrity, engineering logic, AGS compliance, and plausibility ran on entry — not the night before the deadline.
- 04 / Review
Signed, then locked
Derived values read-only from the standards engine; a named signing engineer approved each result before it could reach a deliverable.
- 05 / Deliverable
AGS 4.1 package exported
Submission package, borehole logs, factual report tables, and a validation report generated from the same approved records.
Failures prevented
Refusal recorded as N-value
Two SPT increments hit refusal. Typed as a numeric N-value they would have flowed into the correlation and understated stiffness; the engine plotted refusal at the limit instead.
Sample depth outside stratum
One sample sat 0.30 m below its logged stratum boundary. Structurally valid AGS, factually wrong ground — flagged before the lab schedule was issued.
Groundwater vs. drilling water
A standing level matched the drilling water return. Queried at entry, resolved in the field, never carried into the report.
Before — legacy systems & spreadsheets
- AGS file assembled by hand from logs, lab sheets, and spreadsheets
- Validation attempted at export, days before the submission date
- Two rework rounds typical per area, with re-issued logs each time
After — submission control
- First-pass validation errors
- 0
- Warnings raised
- 0
- Rework rounds after issue
- None
Walkthroughs described from anonymised project records. References available under NDA.
Modules
One platform, every subsurface workflow.
Field logging, in-situ testing, laboratory, GIS, borehole logs, and submission control — one governed schema underneath all of them, so no module holds a value the others cannot trace.
Field logging
Drilling, logging, sampling, and groundwater readings captured once at source — descriptions to BS 5930, offline-tolerant, synced into the central database.
In-situ testing
SPT, CPT, permeability, and pressuremeter records held against their location and depth interval, with method and standard version attached to every value.
Laboratory
Request, schedule, test, calculate, check, approve, report, bill — the full lifecycle on one record, with results autofilled back into logs.
Borehole logs & report tables
Publication-grade logs and factual report tables drawn directly from approved records, not re-plotted in a spreadsheet.
Maps & data explorer
Locations, strata, and test coverage on regional coordinate systems, queryable by formation, test type, or depth interval.
Submission control
Four-layer validation, client-specific rules, issue log, and a go / no-go readiness view per area before anything leaves the building.
Interoperability
Open formats in. Open formats out.
G& reads and writes the formats your estate already speaks, so it sits beside the tools your teams and clients use rather than replacing them.
Common questions
- Can we migrate legacy records without rebuilding templates?
- Yes. Legacy AGS and Excel records import through the same mapping and four-layer validation as live works, so migrated data arrives verified rather than merely digitised.
- Does G& replace our design and modelling tools?
- No. Open formats mean G& works alongside your existing design stack — it holds the governed record and controls the submission.
- Who can approve a value?
- Only a named signing engineer. Derived values are computed by the standards engine and are read-only; approval is the single door to any deliverable.
- Where is the data hosted?
- Regional and sovereign hosting options are available, with role-based access and every import, validation, and export audit-logged.
See a live project go from field data to a validated AGS 4.1 submission package.
Errors caught. Values traced. Engineers in command.
Book a Demo