Insights

Technical Notes on Geotechnical Practice & Engineering Risk

Practical, technically grounded writing on modelling judgement, geotechnical practice and infrastructure risk — written from direct experience across research and consulting, including where the answer is genuinely uncertain.

From Biomechanical FEA to Geotechnical Numerical Modelling

I spent several years building finite element models of porous biological tissue before I built one of a slope. The first time a senior geotechnical colleague looked over my shoulder at a PLAXIS model and asked how I’d chosen the permeability ratio between layers, my instinct was the same one I’d used on soft tissue models years earlier: don’t trust a single value, run the model across a plausible range, and see whether the conclusion changes. It usually does, and that’s the point.

Where the two fields actually diverge

Biological tissue and soil are both porous media, but the similarity has limits I try not to overstate. Tissue behaviour is often close to isotropic over the length scales I modelled, with material variability coming mainly from biological differences between samples. Soil is the opposite: variability comes from geological structure, layering, and history — anisotropy, fissuring and stress history matter far more than they did in my earlier work. Carrying over a biomedical mindset without adjusting for this is a real risk, and I’ve had to unlearn some instincts as much as apply them.

What carries across

What does transfer cleanly is the discipline around the model, not the material model itself: formulating the boundary conditions before touching the software, deciding in advance what "success" for the model looks like, and treating every parameter as a range rather than a point value until sensitivity analysis says otherwise. Model validation habits also carry over directly — in research, a model is not accepted until it reproduces independent experimental data; in consulting, I hold geotechnical models to the same standard against site monitoring or back-analysis of known behaviour wherever that data exists.

A concrete example

On a settlement assessment for underground works, I built the ground movement model the way I would have built a tissue deformation model: define the governing mechanism first, then decide which parameters the outcome is actually sensitive to, rather than refining every input equally. That approach flagged early that the predicted settlement was far more sensitive to the assumed stiffness profile with depth than to the exact permeability value the team had spent the most time debating — which redirected our effort to where it mattered.

Where I’m careful

I’m wary of engineers — including earlier versions of myself — who assume computational fluency in one domain transfers wholesale to another. It doesn’t. What transfers is the research habit of questioning the model before trusting the output. The material science, the failure modes and the consequence of getting it wrong are genuinely different, and I treat that difference as the starting point, not an afterthought.

What Numerical Modelling Can and Cannot Tell Us in Geotechnical Design

A finite element model will always produce a number. Whether that number means anything is a separate question, and it’s the one I try to answer before I answer the client’s.

What models are genuinely good at

Numerical models are strong at showing relative behaviour: how settlement changes if you stiffen a retaining system, how a tunnel face responds to a change in support sequence, how sensitive a slope is to a rise in pore pressure. Used this way, a model is a comparison tool, and comparisons are often robust even when the absolute numbers are not. I rely on this heavily during option comparison and design development.

Where they struggle

Models struggle to give reliable absolute predictions when input parameters are poorly constrained — which, in practice, is most of the time in geotechnical work. A settlement prediction is only as good as the stiffness profile it’s built on, and that profile is usually inferred from a handful of boreholes and empirical correlations. I’ve seen models presented with a false sense of precision — three significant figures on a settlement estimate built on SPT-derived stiffness — and that precision doesn’t reflect the actual uncertainty in the inputs.

A rule I use

Before I trust a modelling output for a design decision, I ask: has this been validated against something independent (monitoring data, back-analysis, a simpler hand-calculation check), and does the conclusion survive a reasonable range of the two or three parameters the outcome is most sensitive to? If either answer is no, I treat the result as indicative rather than definitive, and say so in the reporting rather than presenting a single number as fact.

Practical implication

This shapes how I write recommendations. Where a model result is well constrained and validated, I state it with confidence. Where it isn’t, I present a range, state the governing assumptions explicitly, and recommend a monitoring or verification step during construction rather than over-relying on the pre-construction prediction. Clients and project teams generally respond well to this — it’s more useful to know where the uncertainty sits than to be given a precise number that hides it.

Upcoming Articles

Seepage

How I Approach Seepage Problems in Embankment Dams

Seepage assessment in embankment dams is as much about identifying the governing mechanism — through-seepage, foundation seepage, or internal erosion at material interfaces — as it is about running a model. This note will outline a structured approach to mechanism identification before numerical analysis begins.

Machine Learning

Machine Learning in Engineering: Useful Tool or Overhyped Shortcut?

Machine learning is increasingly proposed for geotechnical correlation and prediction problems, but it inherits the same data-quality and extrapolation limitations as any statistical method — arguably more acutely, given how opaque the resulting model can be. This note will discuss where machine learning genuinely adds value in engineering practice, and where a simpler, more transparent method remains the better choice.