ROADS. BRIDGES. MOVEMENT. ENGINEERING JUDGMENT.

Geotechnical Monitoring Intelligence for Roads & Bridges

GeoSmar interprets settlement, deformation, groundwater, slope, foundation and scour monitoring for roads and bridges, helping teams understand where movement is occurring, whether it matters and what to review next.

Roads & Bridges

Monitor the ground, the structure and the interface between them.

Road and bridge performance is rarely explained by one sensor. Embankment settlement, approach movement, groundwater change, slope deformation, retaining structures, foundations, bearings, piers and scour can interact. GeoSmar approaches the problem as a connected monitoring system: first establish what can move, then decide what evidence is needed to understand whether the movement is credible and significant.

1

Define the asset behaviour

Separate road formation, embankment, slope, bridge foundation, superstructure, approach and waterway risks before selecting instruments.

2

Establish a reliable baseline

Reference points, initial readings, seasonal groundwater and construction sequence need to be understood before change is interpreted.

3

Review movement in context

Magnitude, rate, direction, persistence and agreement between related datasets matter more than one isolated threshold exceedance.

4

Turn observations into action

Findings should lead to a defined technical response: verify, investigate, increase review frequency, inspect, model or change the monitoring plan.

The monitoring question comes before the instrument list.

FHWA guidance states that instrumentation should be installed where necessary to answer specific critical questions relevant to project features and designs. GeoSmar follows the same logic: the design should begin with the mechanism and decision that need to be understood.

Engineering risks

Roads and bridges concentrate several monitoring problems in one corridor.

The following are common engineering questions that may justify monitoring. They are not assumptions about any particular project; the final scope depends on the actual design, ground investigation, construction method, operating condition and owner requirements.

Road formation

Embankment settlement

How much is the foundation soil consolidating, how fast is settlement progressing and is lateral movement developing as fill is placed?

Bridge interface

Approach settlement

Is differential movement developing between the approach embankment and the bridge structure, and is the rate changing with time?

Foundations

Pier and abutment movement

Are foundations, columns or abutments moving relative to stable references, and is the observed behaviour consistent with the design and construction sequence?

Earthworks

Slopes and retaining structures

Are cut slopes, reinforced fills, retaining walls or adjacent ground showing lateral movement, rotation, pore-pressure change or progressive deformation?

Water

Scour and channel change

For bridges over water, bed level, scour depth, hydraulic conditions and foundation exposure can become part of the monitoring problem.

Construction

Temporary works and adjacent activity

Excavation, dewatering, surcharge, piling, traffic staging and temporary support can change the behaviour of existing road and bridge assets during works.

Ground conditions

Geology and groundwater determine what “normal” movement looks like.

This is a global Roads & Bridges industry page, not a site-specific design. GeoSmar therefore does not assign a geology or stratigraphy to an unnamed project. Actual monitoring design should be based on the project ground investigation, geological model, groundwater regime, foundation arrangement and construction sequence.

Soft or compressible ground

For highway embankments on soft ground, FHWA describes settlement devices for measuring settlement magnitude and rate, piezometers for pore-water pressure and inclinometers for lateral movement. The relationship between settlement and pore-pressure dissipation can be important when reviewing consolidation behaviour.

Fill and approach embankments

Made ground, staged fill placement, surcharge and transitions between soil-supported roadways and pile- or footing-supported bridge structures can create differential movement that needs to be separated from survey or reference-point effects.

Slopes and variable geology

FHWA guidance identifies groundwater and ground-deformation instrumentation as standard tools for major landslides that may affect roadway construction. Instrument locations should support the stability and deformation questions being analysed.

River and coastal foundations

For bridges over waterways, bed material, flow regime, foundation type and channel instability influence the suitability of scour-monitoring methods. The monitoring plan must be coordinated with hydraulic and structural assessment rather than treated as a stand-alone sensor task.

Project-specific requirement: before GeoSmar recommends an instrument layout, the preferred input set is the latest geotechnical interpretative report, borehole and laboratory data, groundwater information, road/bridge drawings, foundation details, earthworks staging, hydraulic information where relevant, and the owner’s monitoring or asset-management requirements.

Monitoring strategy

The same asset needs a different monitoring strategy at design, construction and operation.

A useful monitoring plan defines the decision that each dataset supports, the period over which the trend matters, the expected construction or operating change, and the person responsible for reviewing the result.

Design

Characterise behaviour before work starts

Monitor groundwater, slope movement or existing asset behaviour early where seasonal change or pre-construction movement could affect design assumptions.

Construction

Link readings to work sequence

Fill placement, excavation, dewatering, piling, temporary traffic stages and structural works should be reflected in the monitoring timeline so cause and response can be compared.

Operation

Focus on asset condition and change

Long-term monitoring should concentrate on persistent trends, known vulnerabilities, structural response, scour risk or locations where inspection alone does not provide enough information.

Baseline Construction sequence Seasonal groundwater Rate of change Reference stability Trigger response

Instrumentation

Choose instruments by parameter, mechanism and decision.

The table below is a preliminary selection guide, not a project specification. Final instrument type, range, accuracy, location, redundancy, frequency and protection requirements should follow the actual design basis and site conditions.

Engineering question Parameter Candidate monitoring method Typical review focus
Is an embankment settling? Vertical displacement / settlement rate Settlement plates, precise levelling, survey monuments, GNSS where appropriate Total settlement, differential settlement, rate and relationship to fill stages
Is lateral ground movement developing? Lateral displacement with depth Inclinometers or in-place inclinometer arrays Depth and shape of movement, rate, possible shear zone and correlation with pore pressure
Is groundwater or excess pore pressure changing? Water level / pore-water pressure Standpipes, vibrating-wire piezometers or other project-suitable piezometers Seasonal variation, response to dewatering or fill placement, dissipation and stability relevance
Are bridge elements moving? 3D displacement / rotation Automatic total station and prisms, precise survey, GNSS, tiltmeters Relative movement, reference stability, construction influence and long-term trend
Are cracks or joints changing? Opening / closing / relative movement Crack meters, joint meters, displacement sensors Progression, reversibility, temperature correlation and construction events
Is structural demand changing? Strain, load, acceleration or vibration Strain gauges, load cells, accelerometers, vibration sensors Load response, dynamic behaviour, construction effects and operating condition
Is scour changing the bed around foundations? Bed level / scour depth Fixed or portable scour instrumentation, including sonar-based methods where suitable Bed-elevation change, critical scour levels, high-flow events and inspection triggers
Is movement occurring along a wider corridor? Spatial ground-motion pattern InSAR-derived ground-motion data, supported by ground monitoring where needed Screening, historical trend, hotspots and locations for targeted field investigation
Instrument redundancy should be purposeful. Two sensors that share the same failure mode do not necessarily provide independent confirmation. Where consequences are high, GeoSmar prefers cross-checks between different measurement principles, stable references and physical inspection.

Scour & waterways

For bridges over water, monitoring has to connect hydraulic change to foundation risk.

FHWA HEC-23 provides guidance on scour monitoring using portable and fixed instrumentation. FHWA’s scour Plan of Action framework also calls for the instrument type, location, sample interval, data-review frequency, alert elevations and critical elevations to be defined where fixed monitoring is used.

What to monitor

Depending on the waterway and risk assessment, the monitoring question may concern local scour at piers or abutments, contraction scour, channel instability, bed-level change or foundation exposure.

When to monitor

High-flow events can change the required inspection or monitoring frequency. A long-term fixed system and a rapid high-flow inspection plan serve different purposes and should not be confused.

What triggers action

A monitoring system is useful only when alert levels and the response chain are tied to agreed foundation or scour criteria, inspection requirements and owner decisions.

Data & trigger intelligence

A trigger is a decision point, not an explanation.

Road and bridge monitoring often produces automatic alarms. The engineering task is to decide whether the change is credible, what mechanism could explain it, how quickly it is developing and whether independent confirmation is available.

Magnitude How far has the measurement moved relative to baseline or the applicable criterion?
Rate Is the rate stable, slowing, accelerating or responding to a construction or hydraulic event?
Persistence Does the change remain in subsequent readings or revert when an interference or temporary condition disappears?
Correlation Do nearby instruments, groundwater data, survey results or construction records show a compatible response?
Reference quality Could the apparent change come from reference movement, survey geometry, sensor disturbance or a baseline problem?
Engineering consequence Does the observed behaviour affect serviceability, stability, construction control, inspection or the need for further assessment?
What should happen after an automatic alert?
The response should be defined before the alert occurs. Typical steps can include data validation, repeat measurement, comparison with neighbouring instruments, site inspection, review of construction or hydraulic events, escalation to the responsible engineer and, where required, implementation of the project’s action plan.
Why can bridge monitoring produce false or non-structural alarms?
Construction interference, reference changes, temperature effects, loss of line of sight, sensor disturbance or temporary local activity can affect measurements. The official Trimble Story Bridge case reported alerts that were investigated and attributed to construction interference rather than actual column movement.
Should monitoring frequency stay constant?
Not necessarily. Frequency should match the mechanism, project stage, expected rate of change and consequence. Baseline, active construction, high-flow events and long-term operation may require different intervals.

Contract & QA

Monitoring failures often start at an interface that was never clearly assigned.

The points below are GeoSmar technical recommendations for defining a project scope. They are not claims about a particular road or bridge contract. They should be adapted to the owner’s contract form, statutory requirements and local practice.

  • Who approves final instrument locations and changes?
  • Who owns installation access, traffic management and working-over-water permits?
  • Who supplies calibration certificates and installation records?
  • Who establishes and verifies stable survey references?
  • Who accepts the baseline and decides when it is complete?
  • Who maintains power, telemetry and communications?
  • Who replaces damaged, buried, flooded or inaccessible sensors?
  • Who owns raw data, processed data and final reports?
  • Who reviews data after an alert and within what response time?
  • Who can change trigger values and how is change control recorded?
  • How are construction events and instrument outages logged?
  • What is the close-out criterion and long-term handover requirement?
A monitoring specification should separate installation responsibility from engineering interpretation. This is particularly important for GeoSmar’s remote-first model: a local contractor can own field deployment and maintenance while GeoSmar independently reviews data, design logic, trends, triggers and reporting.

Official international cases

Public cases show why roads and bridges need more than one monitoring technique.

The examples below come from official government or supplier sources. They are not GeoSmar projects and do not imply a partnership, endorsement or commercial relationship with GeoSmar.

Story Bridge, Brisbane — construction influence monitoring

Trimble’s official case describes monitoring of Brisbane’s heritage-listed Story Bridge during underpass excavation. Seven tilt sensors were installed on columns, readings were taken hourly and alerts were investigated. The case reports that several alerts were caused by construction interference rather than actual column movement.

GeoSmar takeaway: an alarm needs verification and engineering context before it is treated as structural movement.

Official Trimble case ↗

Victoria Park Bridge, Perth — bridge and ground monitoring

Worldsensing’s official case for construction around Optus Stadium reports a monitoring system using vibrating-wire piezometers, pressure transducers, tiltmeters, settlement plates and inclinometers to track groundwater, bridge tilt and surcharge settlement, with remote data access and automated alerts.

GeoSmar takeaway: bridge behaviour and geotechnical behaviour often need to be reviewed together rather than in separate reporting silos.

Official Worldsensing case ↗

Hammersmith Bridge, London — condition monitoring and operational decisions

The UK Department for Transport states that cracks identified in cast-iron pedestals led to closure to motorised traffic and installation of an acoustic monitoring system. During hot weather in August 2020 the monitoring system detected an event and the bridge was closed to all traffic.

GeoSmar takeaway: monitoring becomes most valuable when the owner has a defined link between observed behaviour, engineering review and operational action.

Official UK DfT source ↗

Forth Replacement Crossing, Scotland — structural health monitoring architecture

Transport Scotland’s scheme assessment describes a Wind and Structural Health Monitoring System intended to provide real-time data, identify anomalies and track long-term changes in bridge behaviour, with data collection, preprocessing, transmission and central processing arranged as a system architecture.

GeoSmar takeaway: reliable monitoring needs an end-to-end data path, not only field sensors.

Official Transport Scotland source ↗

GeoSmar role

An independent intelligence layer for road and bridge monitoring.

GeoSmar is designed to work with the project’s existing surveyors, instrumentation contractors, consultants, asset owners and technology providers. The objective is not to replace a functioning field system, but to make the resulting evidence easier to trust, compare and act on.

Monitoring Design & Strategy

Define the monitoring philosophy, risk-to-measurement logic, instrument requirements, baseline, frequency, trigger framework, data architecture and reporting expectations.

Monitoring Design →

Monitoring Intelligence

Review recurring road and bridge data for trends, rate of change, consistency, anomalies, thresholds and engineering significance.

Monitoring Intelligence →

Independent Review

Provide a separate technical view of monitoring plans, contractor reports, trigger logic, data quality and observed behaviour.

Independent Review →

Data Diagnostics

Investigate sudden settlement, apparent bridge movement, conflicting instruments, baseline shifts, questionable alerts or unexplained changes.

Data Diagnostics →

InSAR Ground Motion

Use satellite-derived ground-motion information for wider corridor screening, historical context and comparison with local monitoring where the method is suitable.

InSAR Ground Motion →

Automated Reporting

Reduce repetitive charting and data preparation while retaining engineer review for interpretation, limitations and technical conclusions.

Automated Reporting →

Field delivery can remain local. Engineering interpretation can be independent and global.

This separation is deliberate. It lets road and bridge owners retain the contractors and instrumentation already suited to local access, traffic management, safety and maintenance while adding a consistent monitoring-intelligence layer across projects or portfolios.

Frequently asked questions

Road and bridge monitoring questions that should be answered before instruments are ordered.

What should be monitored on a road embankment over soft ground?
The answer depends on the design and ground conditions. FHWA guidance for embankments on soft ground describes settlement devices, piezometers and slope inclinometers as typical instruments for settlement, pore-pressure and lateral-movement behaviour. The final layout should follow the project’s stability and consolidation questions.
What is the difference between bridge monitoring and geotechnical monitoring?
Bridge monitoring may focus on displacement, tilt, strain, vibration, bearings, joints or structural response. Geotechnical monitoring focuses on the ground, groundwater, slopes, embankments and foundations. Many road and bridge projects require both because the structure and the ground influence each other.
Can InSAR replace local bridge or geotechnical instruments?
Usually it should be treated as a complementary source rather than an automatic replacement. InSAR can provide wider-area and historical ground-motion context, while local instruments can provide project-specific measurements at selected locations and depths. Suitability depends on the asset, required accuracy, line of sight, coherence and the engineering question.
How should monitoring trigger levels be set?
Trigger values should come from the design basis, asset tolerances, risk assessment, owner requirements and agreed response plan. They should not be copied from another project without checking whether the mechanism, ground conditions, structure and consequence are comparable.
Can GeoSmar review monitoring installed by another contractor?
Yes, where sufficient data and project context are available. The GeoSmar model is vendor-neutral and can support independent review of monitoring plans, raw data, trends, thresholds, anomalies and contractor reporting without taking over field installation.
What information is useful for a first GeoSmar road or bridge review?
A useful starting package normally includes the latest monitoring report or sample data, drawings, ground investigation or geotechnical interpretation, construction sequence, foundation information, trigger criteria, monitoring layout and a clear description of the engineering concern that needs to be resolved.

Official technical sources

References used for this technical discussion.

Only official public sources are cited below. The project examples belong to the organisations identified and are not presented as GeoSmar experience.

FHWA — Geotechnical instrumentation and monitoring

FHWA Project Development and Design Manual, Chapter 6: instrumentation to answer specific critical questions, groundwater and slope monitoring, timely data collection and communication.

Official FHWA PDF ↗

FHWA — Soils and Foundations

FHWA NHI-06-088: settlement devices, piezometers, inclinometers and typical instrument locations for embankments on soft ground.

Official FHWA PDF ↗

FHWA — Bridge scour guidance

HEC-23 and FHWA scour resources covering bridge scour, countermeasures, portable and fixed monitoring instrumentation and Plans of Action.

Official FHWA Scour Portal ↗

Trimble — Story Bridge case

Official customer story on automated monitoring of a heritage-listed bridge during adjacent excavation and investigation of alarms.

Official Trimble source ↗

Worldsensing — Victoria Park Bridge case

Official case covering piezometers, pressure transducers, tiltmeters, settlement plates and inclinometers for bridge and ground monitoring.

Official Worldsensing source ↗

UK DfT & Transport Scotland

Official public material on Hammersmith Bridge condition monitoring and the Forth Replacement Crossing structural-health-monitoring architecture.

UK DfT ↗   Transport Scotland ↗

Technical content on this page is for preliminary discussion. It is not a substitute for project-specific design, inspection, statutory approval, geotechnical investigation, structural assessment or the responsible engineer’s judgement.

Start a technical discussion

Have road or bridge monitoring data that needs a second engineering view?

Send a monitoring report, sample dataset, drawings or a project brief. GeoSmar can first help define whether the issue is best approached through monitoring design, independent review, data diagnostics, InSAR ground-motion assessment or a recurring monitoring-intelligence workflow.

Scroll to Top