What is a geotechnical hazard ranking for pipeline integrity management?
If you manage integrity on a long corridor, you already have a ranking for internal corrosion, a ranking for third-party damage, a ranking for stress corrosion cracking. Geotechnical hazard is the threat that often gets a flat "walk it every spring" treatment instead of an actual ranked list. That's the gap a geohazard ranking fills.
What the ranking actually ranks
A geotechnical hazard ranking is a scored, ordered list of corridor segments by their exposure to ground movement: slope creep, landslide, subsidence, and washout or scour at stream crossings. It's not a map of where pipe exists. You already have that in your GIS. It's a list that answers a narrower question: of the 40, 80, or 400 miles in this corridor, which 10 or 15 segments should a geotech crew look at first this season.
The inputs vary by shop. Some build the ranking from slope angle, soil type, and crossing density pulled from existing geodata. Some add field observations from past patrols. Increasingly, some add elevation differencing: comparing stereo-derived digital elevation models from one year to the next to flag where the ground surface moved. That distinction matters, because slope-prone terrain and slope-moving terrain are different lists, and a crew with a limited dispatch budget needs to know which segments changed this year rather than which ones simply look risky on a soils map.
Where it sits in the IMP
For anyone running a formal integrity management program, geohazard ranking sits in the same slot as the risk assessment step for other threats: identify, rank, prioritize inspection or mitigation, repeat on a cycle. The difference with geohazard is the inspection method. You can't run an ILI tool past a slope. The traditional alternative is walking or flying the right-of-way to eyeball exposed pipe, washed-out banks, and scarps, which works but doesn't scale cheaply across a corridor with hundreds of miles and limited geotech staff hours.
A ranking built from remote elevation differencing changes the order of operations. Instead of walking the whole ROW to find the handful of segments that moved, you get a shortlist first and send the crew to confirm and quantify what's there. The field visit still happens. It's just targeted instead of exhaustive, and it happens with some idea in advance of what you're walking out to look at.
This doesn't replace geotechnical instrumentation on known problem slopes, inclinometers, extensometers, or survey monuments on a site you've already flagged. Those stay in place and keep doing their job at the resolution only ground instruments can give you. A corridor-wide ranking is upstream of that: it's the triage step that decides which untracked segments deserve instrumentation or a closer look in the first place.
What a credible ranking needs to show
Whatever method produces the list, an auditable ranking needs three things an inspector or a regulator will ask about: what data it's based on, how often it's refreshed, and what a changed rank means on the ground. "Segment 14 moved up the list" should map to something concrete, like measured elevation change over the pipe centerline between this year's pass and last year's, not an opaque score nobody on your team can explain six months later when someone asks why that segment got a crew before another one did.
That's also why annual cadence, not continuous monitoring, is the honest frame for most corridor-wide geohazard screening right now. Slope creep and washout precursors build over a season, not a week, so a yearly pass that reliably flags where ground moved is a useful input to your ranking even without daily updates.
If you're putting together or refreshing a geohazard ranking for an existing IMP and want to see how elevation differencing over a corridor turns into that kind of shortlist, Geohazard Screening is worth a look before your next patrol season starts.