MOVEMENT. WATER. EVIDENCE. DECISIONS.
Slope & Landslide Monitoring Intelligence
RAUZ combines slope movement, groundwater, rainfall, survey, remote-sensing and InSAR evidence to support monitoring strategy, data QA/QC, independent review and engineer-reviewed interpretation worldwide.
Slope & Landslide Monitoring
Monitoring starts with the movement mechanism—not the instrument catalogue.
Slope and landslide monitoring is the structured observation of movement, water conditions, weather and other evidence so that a project team can judge whether a slope is stable, changing or requires closer investigation. RAUZ approaches the problem as a multi-source interpretation task: define the mechanism, test the data, compare independent evidence and make uncertainty visible before a decision is taken.
Where is the slope moving?
Compare surface and subsurface displacement, direction, depth, rate and spatial pattern rather than relying on a single maximum value.
What is the hydraulic context?
Review rainfall, groundwater and pore-pressure behaviour because water conditions can change the forces and effective stresses acting within a slope.
What needs to happen next?
Separate measurement, interpretation and response so that a trigger, anomaly or acceleration leads to a traceable technical review rather than an automatic conclusion.
Risk Context
Landslides rarely have one cause, and a monitoring plan should reflect that.
The U.S. Geological Survey describes landslides as downslope movement of rock, debris or earth and identifies rainfall, snowmelt, groundwater change, erosion, earthquakes, volcanic activity and human disturbance among important triggers or contributing factors. The practical implication is simple: the same instrument list is not appropriate for every slope.
Rainfall, infiltration and groundwater
Geology, stratigraphy and discontinuities
Earthquakes and rapid loading changes
Construction, drainage and human modification
RAUZ interpretation rule: a rainfall threshold, pore-pressure rise or displacement trigger can be useful, but none automatically proves a failure mechanism. The evidence should be compared with site geology, drainage, movement depth, spatial pattern and the timing of known events.
Site Conditions
Climate, geology and project geometry determine what “good monitoring” looks like.
Before recommending instruments or alert logic, RAUZ would first establish the site conditions and the decision the monitoring must support. For a real project, local conditions must come from official project information, verified ground investigation, recognised meteorological or geological sources and the project’s own records.
Climate & hydrology
Rainfall intensity and duration, antecedent wetness, snowmelt where relevant, drainage, seepage, groundwater levels, seasonal variation and known watercourses can all change how movement data should be interpreted.
Geology & stratigraphy
Soil and rock profile, weathering, weak layers, discontinuities, existing slip surfaces, fill, erosion and the location of stable reference zones affect both monitoring design and interpretation.
Exposure & consequence
A natural hillside above a road, a railway cutting, an embankment, a dam abutment, a mine slope and a slope beside occupied buildings can require very different monitoring frequency, redundancy and escalation routes.
Works & interventions
Excavation, stabilisation, drainage, anchors, retaining structures, vegetation works, loading changes and maintenance activities should be placed on the same timeline as monitoring observations.
- Site location and slope geometry
- Ground investigation and geological model
- Groundwater and drainage information
- Known landslide or instability history
- Rainfall / weather data source
- Existing monitoring and baseline records
- Construction / maintenance chronology
- Approved trigger and response framework
RAUZ does not infer local geology or climate from a generic webpage. Project-specific advice begins only after the location, ground conditions, monitoring purpose and available evidence are defined.
Monitoring Strategy
Design the evidence chain around the engineering question.
A monitoring plan becomes defensible when each measurement has a reason to exist, a baseline, a review frequency, a quality check and a defined role in the response process.
What kind of movement or hydraulic change is credible at this site?
Choose movement, water, weather, survey and remote-sensing data that can test the mechanism.
Control references, instrument identity, timing and pre-event or pre-work behaviour.
Assess magnitude, rate, acceleration, depth, spatial coherence and cross-sensor consistency.
Link findings to inspection, remeasurement, specialist review and project-approved response routes.
- Frequency: routine, event-driven or near-real-time monitoring should match the expected behaviour and consequence, not a generic timetable.
- Redundancy: where consequence is high, independent measurement types can help distinguish real movement from instrument or reference problems.
- Trigger logic: magnitude alone may be insufficient; rate of change, acceleration, persistence and independent confirmation can matter.
- Traceability: raw observations, corrections, exclusions, baselines, alerts and engineering comments should remain reviewable.
Instrumentation
Different instruments answer different parts of the slope-stability question.
Instrument selection should follow the expected failure mechanism, geometry, access, required frequency and consequence. ISO 18674-3 covers inclinometer measurement of displacement across a line and explicitly includes natural slopes and slope cuts; ISO 18674-4 covers pore-water-pressure and piezometric-level measurement for geotechnical monitoring, including slopes and embankments.
| Engineering question | Typical evidence | What it can add | Key interpretation issue |
|---|---|---|---|
| Where is subsurface deformation developing? | Borehole inclinometer / in-place inclinometer | Displacement profile with depth; possible shear-zone localisation | Stable reference, casing orientation, baseline, repeatability and depth continuity matter. |
| How are groundwater or pore pressures changing? | Vibrating-wire piezometer, standpipe, groundwater observation | Hydraulic context and response timing | Sensor type, response time, elevation datum and installation zone must be understood. |
| How is the surface moving in 3D? | GNSS, total station, survey targets | Surface displacement, direction and network-wide comparison | Control-network and reference-point stability can mimic or mask movement. |
| Is local rotation or opening changing? | Tiltmeter, crackmeter, extensometer | Local deformation around cracks, structures or selected slope features | A local sensor does not by itself define the overall landslide mechanism. |
| How is weather linked to behaviour? | Rain gauge, weather station, soil-moisture / hydrologic observations | Event timing, antecedent wetness and environmental context | Rainfall alone may not represent pore-pressure conditions at the movement surface. |
| What is changing across the whole slope? | LiDAR, photogrammetry, imaging, InSAR | Spatial context, terrain change and wider-area deformation screening | Resolution, geometry, line-of-sight, vegetation, coherence and revisit interval can limit interpretation. |
Physical instrumentation supply is a separate scope.
Where a project also requires inclinometer casing or groundwater-monitoring pipe systems, RAUZ can discuss the monitoring logic while the GEOOE ecosystem’s separate supply platform GEOLUR publishes product information for slope and embankment applications.
Data Logic
A slope alarm is a starting point for review—not the end of the analysis.
RAUZ is designed to sit above the measurement layer. Existing sensors, survey systems, contractor reports and satellite-derived products can remain in place while RAUZ checks data quality, compares independent evidence and records what is known, uncertain and worth investigating next.
Validate the record
Check instrument identity, units, timestamp continuity, baseline, missing data, sudden steps, reference behaviour and any processing that separates raw from reported values.
Test the movement
Review magnitude, rate, acceleration, displacement depth, neighbouring instruments and whether the pattern is spatially and mechanically coherent.
Add the context
Compare rainfall, groundwater, drainage, construction events, inspection observations and wider-area movement evidence where suitable data exists.
What RAUZ can investigate
Is the movement credible? Is it accelerating? Is the change local or slope-wide? Does the groundwater response support the interpretation? Did a baseline, reference or sensor condition change? What additional evidence would reduce uncertainty?
Decision-ready records
QA/QC findings, trend and rate plots, cross-sensor comparisons, anomaly notes, trigger review, engineering commentary, limitations, follow-up questions and engineer-reviewed reporting.
InSAR & Remote Sensing
Use wide-area ground motion to add context—not to replace site evidence.
Satellite InSAR can add a broad spatial and historical view of slow surface deformation where suitable radar targets and acquisition geometry exist. The European Ground Motion Service provides InSAR-derived ground-motion products across Europe, while commercial services can provide project-specific processing elsewhere. For slope work, RAUZ treats InSAR as one evidence layer alongside ground instrumentation, survey, geology and hydrology.
Look beyond isolated points
Review whether deformation extends across a larger part of a hillside, corridor or catchment than the existing field network can show.
Reconstruct longer-term behaviour
Where suitable satellite archives exist, historical time series can help frame whether observed movement is new, persistent or spatially changing.
Compare independent evidence
Where geometry and reference systems permit, compare satellite-derived trends with GNSS, survey, inclinometer or other ground observations.
Important limitation: basic InSAR displacement is measured along the radar line of sight. Vegetation, rapid movement, geometric shadow/layover, atmospheric effects and poor coherence can limit a slope application. Field verification remains important where a project decision depends on the interpretation.
Official Public Cases
Real monitoring programmes show why slope intelligence needs more than one data stream.
The examples below come only from official public agencies and research organisations. They are not RAUZ projects and do not imply partnership, endorsement or commercial association. They are included because they demonstrate established multi-source approaches to landslide monitoring.
U.S. Highway 50 landslide monitoring
USGS publicly reports rainfall, groundwater pressure and slope movement from its Highway 50 monitoring site. The case demonstrates a direct hydrology–movement evidence chain rather than relying on surface displacement alone.
Hollin Hill Landslide Observatory
The British Geological Survey combines geomorphological mapping, LiDAR, geophysics, engineering and hydrogeology. Its ALERT system has also integrated rainfall, pore-pressure and movement observations for long-term landslide research.
Rest and Be Thankful operational monitoring
Transport Scotland describes a regime combining remote weather monitoring, expert forecasting, ground-saturation estimates, time-lapse photography, site observations and hillside movement surveys to support route-management decisions.
Engineering lesson: the cases differ in geology, climate, asset and monitoring purpose, but all show the value of combining movement with hydrologic, environmental or spatial context. RAUZ uses the same principle when reviewing mixed monitoring evidence for a project.
RAUZ Role
Independent interpretation above the measurement layer.
RAUZ does not require a project to replace a functioning field system. The engagement can begin with existing monitoring exports, survey files, contractor reports, weather records or InSAR products and then add a structured engineering-intelligence layer around the evidence.
Monitoring review
Review monitoring plans, baselines, trigger logic, data quality, anomalies, contractor interpretation and whether the evidence supports the reported conclusion.
Data integration
Work from client-owned, contractor-owned or third-party datasets where a suitable export or agreed data route exists.
Interpretation & reporting
Separate automated screening from engineering judgement and document uncertainty, follow-up questions and limitations with the conclusion.
Potential technical cooperation routes
A slope project can require capabilities that are deliberately outside RAUZ’s remote intelligence layer. Depending on scope and location, RAUZ can coordinate technically with the client’s or project’s geotechnical designer, drilling/instrumentation contractor, land surveyor, environmental or hydrometeorological provider, InSAR/remote-sensing supplier, telecommunications provider and responsible local engineer. These are potential project interfaces, not claims of standing partnerships.
Scope boundary: monitoring intelligence, independent review and technical interpretation do not replace any jurisdiction-specific statutory design, emergency authority, regulated professional sign-off or Engineer-of-Record responsibility. Those duties must be defined separately for the project location.
Official References
Public sources used to frame this technical discussion.
Only official public sources are listed below. External organisations are included for technical context and source transparency; listing them does not imply a partnership, client relationship or endorsement.
- U.S. Geological Survey — What is a landslide and what causes one?
- U.S. Geological Survey — Overview of Rainfall-Induced Landslides
- U.S. Geological Survey — Real-Time Monitoring for Potential Landslides
- U.S. Geological Survey — U.S. Highway 50 Landslide Monitoring Site
- British Geological Survey — Hollin Hill Landslide Observatory
- British Geological Survey — Landslide Observatories
- Transport Scotland — A83 Taskforce / Hillside Monitoring Regime
- Transport Scotland — Landslide Forecast, Detection and Notification Research
- Copernicus Land Monitoring Service — European Ground Motion Service
- ISO 18674-3:2017 — Geotechnical monitoring by field instrumentation: Inclinometers
- ISO 18674-4:2020 — Geotechnical monitoring by field instrumentation: Piezometers
Frequently Asked Questions
Slope and landslide monitoring questions.
These answers are intentionally general. Site-specific conclusions require verified information about the slope, geology, groundwater, monitoring system and project responsibility.
What should be monitored on a landslide-prone slope?
Is an inclinometer enough for slope monitoring?
Can rainfall thresholds predict every landslide?
Can InSAR replace ground instrumentation?
Can RAUZ review monitoring installed by another contractor?
What information should we send first?
Discuss a Slope or Landslide Project
Start with the site, the evidence and the engineering question.
You do not need a complete monitoring database before speaking with RAUZ. A short project brief, recent monitoring report, representative dataset or slope plan is enough to establish what should be reviewed first.
- Project country / location
- Slope, cutting, embankment or landslide type
- Current project / asset stage
- Ground and groundwater information available
- Existing instrumentation and survey
- Rainfall / weather records available
- Recent trigger, anomaly or movement
- Decision or review required
For immediate site-safety or emergency response, use the project’s established emergency procedures and responsible local engineer. This page is for technical discussion, monitoring intelligence and commercial enquiries.