MEASURE WHAT MATTERS. DEFINE WHAT HAPPENS NEXT.
Geotechnical Monitoring Design & Strategy
GeoSmar develops monitoring plans, instrument strategies, baseline requirements, trigger frameworks, data architecture and reporting specifications for infrastructure and construction projects worldwide.
Monitoring Design & Strategy
A monitoring plan should begin with the engineering question, not the instrument catalogue.
GeoSmar develops project-specific monitoring strategies that connect credible failure or movement mechanisms with measurable parameters, practical instrument locations, baseline requirements, monitoring frequency, trigger logic, data handling and reporting responsibilities.
Define the risk
What could move, change, fail or affect a third-party asset?
Define the evidence
Which parameter would provide meaningful evidence of that behaviour?
Design the system
Select instruments, locations, redundancy, baselines and data routes.
Define the response
Set review frequencies, trigger logic, notifications and escalation responsibilities.
Keep it useful
Make the data, charts and reports fit the construction sequence and engineering decisions.
FHWA guidance states that monitoring requirements and frequency should reflect construction progress and ground behaviour, and that the means of collecting, storing, analysing, documenting and following up instrumentation results should be established as part of the programme. GeoSmar uses the same underlying principle: the monitoring design is incomplete until the project knows what the data will be used for.
Design inputs
Before selecting instruments, establish what the project can actually tell us.
A credible monitoring strategy depends on the project geometry, geotechnical model, construction sequence, adjacent assets, predicted ground response, owner requirements and practical constraints. The exact geology and stratigraphy therefore cannot be invented for a generic service page; they must come from the project’s own official investigation and design information.
Geology, stratigraphy and groundwater
Review the available boreholes, geological sections, groundwater information and geotechnical parameters that control the expected mechanism. Instrument type and depth should follow the mechanism being investigated.
Construction sequence
Excavation depth, tunnelling advance, dewatering, loading, piling, staging, temporary works and access constraints affect both the expected response and the frequency at which measurements are useful.
Structures and third parties
Identify railways, utilities, buildings, tunnels, bridges, slopes, retaining systems or other assets whose movement, serviceability or operational limits may govern the monitoring design.
Expected behaviour
Monitoring locations should relate to predicted zones of influence, deformation patterns, pore-pressure response, load transfer, settlement or other project-specific behaviour.
Access, power and communications
Line of sight, site possessions, restricted access, tunnel obstructions, power availability, telemetry and safe maintenance access can determine whether a technically attractive instrument is practical.
Responsibilities and interfaces
Define who supplies, installs, protects, reads, validates, maintains, reviews and responds to each monitoring stream. Ambiguity here can be as damaging as poor instrument selection.
Risk to measurement
Choose the measured parameter because it answers a risk question.
The table below is a design framework, not a universal instrument schedule. Final selection, range, resolution, installation depth, spacing and redundancy must be checked against the project’s predicted behaviour and contractual requirements.
| Engineering question | Parameter to observe | Typical measurement families | Design issue to resolve |
|---|---|---|---|
| Is the ground or retaining system moving laterally? | Lateral displacement with depth or at selected points | Inclinometer, in-place inclinometer, shape array, survey targets | Where should the stable reference be, and what depth profile is needed? |
| Is groundwater or pore pressure changing? | Pore-water pressure or water level | Vibrating-wire piezometer, pneumatic piezometer, standpipe, water-level sensor | Which stratum and response time matter to the design mechanism? |
| Is settlement or heave occurring? | Vertical movement at surface, structure or depth | Precise levelling, automated total station, settlement points, extensometer, hydrostatic levelling | Is absolute movement, differential movement or depth-specific movement the key quantity? |
| Is a structure rotating or distorting? | Tilt, convergence, relative displacement | Tiltmeter, electro-level, total-station prism, convergence measurement | What geometry and reference system convert readings into meaningful structural behaviour? |
| Are cracks or joints changing? | Relative opening, closing or shear movement | Crack meter, joint meter, tell-tale, displacement transducer | Which defect is active and what baseline movement already exists? |
| Are loads or stresses changing? | Force, strain, earth pressure or structural response | Load cell, strain gauge, earth-pressure cell, fibre-optic strain sensing | Where is the load path, and what temperature or installation effects need correction? |
| Is movement occurring over a wide corridor or area? | Spatial pattern of surface or asset displacement | GNSS, survey network, remote sensing, InSAR where suitable | What spatial coverage, temporal interval and line-of-sight limitations apply? |
Instrumentation strategy
Use the smallest practical system that can still distinguish the behaviour that matters.
More instruments do not automatically create a better monitoring programme. A useful design balances measurement purpose, expected range, accuracy, response time, spatial coverage, redundancy, access, survivability, maintenance and the ability to interpret the resulting data.
Inclinometers
Useful where the depth and profile of lateral movement matter, such as retaining systems, embankments and slopes. The design must consider anchoring into a stable reference zone and the expected displacement range.
Piezometers
Used to observe pore-pressure or groundwater response. Selection depends on the target stratum, expected pressure range, required response time and whether manual or automated reading is justified.
Settlement & survey
Precise levelling, prisms, GNSS or settlement sensors can address surface and structural displacement. The reference network and expected movement pattern are part of the design, not an afterthought.
Extensometers
Useful when vertical or axial movement with depth must be separated into zones rather than represented by one surface reading.
Tilt, crack & convergence
Useful for structures, tunnels and sensitive assets where relative deformation, rotation or defect movement is more informative than absolute ground movement alone.
Load, strain & pressure
Load cells, strain gauges and earth-pressure cells can support direct observation of structural or ground-support response where the design question concerns force transfer rather than displacement alone.
Vibration
Where construction vibration affects sensitive structures, equipment or contractual limits, the monitoring design should define location, frequency range, event handling and reporting responsibilities.
Automated optical monitoring
Automated total stations can provide repeatable movement observations over networks of prisms, but line of sight, obstructions, reference stability and environmental effects must be considered.
InSAR as a complementary layer
Satellite-derived ground-motion information can support historical screening or wider-area monitoring where site conditions and data quality are suitable. It should not be treated as a universal replacement for ground instruments.
Baseline & frequency
A reading has little meaning if the project does not know what “normal” looked like before the works.
Baseline design and monitoring frequency should be tied to the behaviour being observed and the stage of work. FHWA guidance explicitly notes that monitoring frequency may vary with construction progress and ground behaviour.
Baseline design
Define when baseline starts, how many stable observations are required, what construction or environmental activities are excluded, how reference points are checked and how pre-existing movement is recorded.
Construction-stage frequency
Increase attention during the stages most likely to produce change. Frequency should reflect the response time of the mechanism and the time available for the project team to act.
Post-construction frequency
Reduce frequency only when the monitoring objective, observed behaviour and contractual requirements justify doing so. Close-out criteria should be defined rather than leaving the programme open-ended.
Event-driven frequency
Trigger exceedance, abnormal trends, nearby critical activities, heavy rainfall, dewatering changes or other defined events may justify a temporary increase in review frequency.
Why not set one fixed monitoring frequency for the entire project?
What should be recorded with the baseline?
Trigger framework
A trigger value is useful only when the action behind it is already defined.
GeoSmar does not recommend copying generic trigger numbers from another project. Trigger criteria should be linked to design predictions, asset tolerances, observed baseline behaviour, owner requirements, consequence of movement and the response time available to the project team.
Normal review
Continue the defined programme while checking trend, rate, completeness and consistency. “Normal” should still be an actively reviewed state.
Technical verification
Confirm the reading, compare neighbouring data, check the construction activity and determine whether the change is credible before escalation.
Pre-agreed response
Escalate to the responsible engineer or asset owner, increase monitoring where required and follow the project-specific response plan.
Data & reporting
Design the data route at the same time as the instrument layout.
A monitoring strategy should define how readings move from the instrument to the people making decisions. FHWA guidance explicitly calls for the means of collecting and storing data, the analysis method, relevant plots, documentation and reporting schedule to be determined as part of the programme.
Collection method
Manual, logger-based, automated survey, telemetry or API. The method should reflect required frequency, access, reliability and the importance of rapid response.
Data structure
Instrument ID, coordinates, units, calibration information, reference level, reading timestamp, status flags and construction-stage metadata should remain traceable.
QA/QC checks
Define missing-data checks, impossible values, sudden jumps, reference instability, instrument consistency and procedures for suspect readings.
Engineering plots
Specify the plots needed to answer the engineering question: displacement versus time, rate of change, depth profile, pore pressure versus stage, settlement contour or other project-specific views.
Notification route
Define who receives routine reports, who receives alerts, what constitutes an urgent notification and how acknowledgement is recorded.
Reporting cadence
Align daily, weekly, monthly or event-based reporting with the stage of work and the decisions the report is expected to support.
Contract & QA
Many monitoring disputes start at the interface between design, installation, data and response.
For tender and contract use, GeoSmar can structure the monitoring requirements so that technical responsibilities are explicit. The checklist below is GeoSmar’s engineering delivery framework rather than a substitute for project-specific legal advice or statutory requirements.
- Monitoring scope and purpose for each asset
- Instrument supply versus installation responsibility
- Location approval and permitted tolerances
- Calibration and factory documentation
- Installation records and as-built coordinates
- Baseline acceptance procedure
- Protection, access and maintenance responsibility
- Manual versus automated reading responsibility
- Data ownership, format and transfer frequency
- Reference-point and datum control
- Trigger notification and acknowledgement chain
- Response-time expectations
- Procedure for damaged or failed instruments
- Change control when construction sequence changes
- Close-out, archive and handover requirements
- Independent review or audit requirements
Common interface risk: “who owns the reading?”
The installer may own the hardware, a platform provider may hold the data, the contractor may issue the report and the engineer may own the interpretation. The tender should make the data route and technical accountability clear before construction starts.
Common interface risk: design changes without monitoring changes
If excavation sequence, temporary works, dewatering, tunnel staging or access changes, the monitoring plan may also need revision. Change control should include a review of monitoring implications.
Official case evidence
Public projects show why monitoring design must follow the mechanism and construction stage.
The examples below come from official public project or government sources. They are not GeoSmar projects and are included only as technical references for how monitoring objectives, ground conditions and instrument selection were connected on real infrastructure works.
FHWA — Central Artery/Tunnel pile-driving case
FHWA reports a sequence of fill, organic silt and sand, thick soft marine clay, glacial soils and bedrock at the case location. Monitoring around an existing building included deformation monitoring points, vibrating-wire piezometers, a multipoint heave gauge and an inclinometer as the project investigated pile-driving-induced heave and pore-pressure response.
Design lesson: the instrumentation was selected to separate vertical movement, pore-pressure generation and lateral ground response rather than relying on one measurement type.
Crossrail — Paddington Station box above tunnels
Crossrail’s Learning Legacy describes a 24 m deep station box in London Clay above twin segmentally lined tunnels. The in-tunnel system used automated total stations and prism arrays, with the line-of-sight arrangement modelled in a virtual tunnel environment. Baseline ovalisation was assessed before the relevant excavation stage.
Design lesson: accuracy requirements, tunnel obstructions, baseline geometry and construction staging were treated as part of the monitoring-system design.
Crossrail — Bond Street asset protection
Crossrail documents automated 3D geodetic prisms, manual building levelling points and hydrostatic levelling cells for real-time control, with tiltmeters, crack meters and tell-tales added where pre-construction defects had been identified. Real-time data were provided every 15 minutes while manual monitoring was undertaken daily during relevant works.
Design lesson: different assets and defects justified different sensors and frequencies, while the construction zone of influence controlled when intensified monitoring was needed.
USACE — dams and levees instrumentation
USACE Engineer Manual EM 1110-2-1908 provides guidance for personnel responsible for instrumentation, monitoring and assessing the performance of embankment dams and levees. It places instrumentation within the wider task of evaluating how the asset is performing.
Design lesson: the programme should be tied to performance questions and long-term assessment, not only construction-stage data collection.
GeoSmar deliverables
A monitoring strategy should be buildable, reviewable and contract-ready.
The exact deliverable package depends on project stage. GeoSmar can support concept design, tender preparation, independent review or revision of an existing monitoring plan.
Monitoring Design Basis
Objectives, assets, mechanisms, predicted behaviour, design assumptions, monitoring philosophy and limitations.
Instrument Schedule & Layout Concept
Instrument types, target parameters, indicative locations, depths, spacing, redundancy and interfaces with survey or remote sensing.
Baseline & Frequency Matrix
Baseline period, construction-stage frequencies, event-driven changes and close-out criteria.
Trigger & Response Framework
Trigger logic, verification requirements, escalation route, notification responsibilities and review actions.
Data & Reporting Specification
Data fields, QA/QC, plots, report frequency, alert distribution, archive and handover requirements.
I&M Technical Specification
Technical clauses for procurement, installation, calibration, access, maintenance, data delivery, failure replacement and close-out.
GeoSmar can develop the monitoring strategy and review the technical outputs while the client’s local contractor, survey team or instrumentation specialist performs installation, maintenance and site access activities. This keeps technical authorship and engineering review clear without forcing GeoSmar into a country-by-country installation model.
Frequently asked questions
Monitoring design questions clients often need resolved early.
What information does GeoSmar need to start a monitoring design?
Can GeoSmar design a monitoring plan without visiting the site?
Does GeoSmar specify one preferred sensor manufacturer?
Can GeoSmar review an existing I&M plan prepared by another consultant or contractor?
Can InSAR replace ground instrumentation?
Who should approve trigger levels?
Can monitoring design be packaged for tender?
Start with the engineering problem
Need a monitoring plan that can survive design review and construction reality?
Send GeoSmar the project brief, relevant drawings, geotechnical information and construction sequence. We can first define the monitoring questions, identify the data that would answer them and determine whether the next step should be concept design, an independent review or a tender-ready I&M specification.
Official technical sources
References used for this technical discussion.
Only official government, project-owner or company documentation has been used for the technical examples below. These sources do not imply endorsement of or partnership with GeoSmar.
Federal Highway Administration
Geotechnical Technical Guidance Manual; Soils and Foundations reference material; Central Artery/Tunnel lessons learned.
U.S. Army Corps of Engineers
EM 1110-2-1908, Instrumentation of Embankment Dams and Levees.
Crossrail Learning Legacy
Official project technical papers and close-out material covering tunnel, building and ground instrumentation and monitoring.
Trimble
Official Trimble 4D Control documentation describing supported geotechnical sensor types, alarms and reporting functions.