Prioritizing pipeline patrol routes when your crew is short-handed
Every ROW manager runs the same math eventually. You've got a corridor that stretches across three counties, a patrol frequency requirement tied to class location and HCA status, and a crew that didn't grow even though the construction permits around your line did. Something has to give, and it shouldn't be the miles where a backhoe is most likely to hit your pipe.
The instinct is to patrol everything on the same rotation, because that feels fair and defensible. It isn't the best use of a small crew. A mile of line running through unbroken pasture with one landowner who's held the same ground for forty years does not carry the same encroachment risk as a mile running past a new subdivision, a highway widening project, or a stretch where you've logged three unauthorized crossings in the last two years. Treating them the same means your highest-risk segments get the same attention as your lowest, which is really a way of under-patrolling the segments that matter.
Rank segments by what actually drives third-party damage
Start by splitting the corridor into segments short enough to score individually, a mile or two apiece depending on how your GIS already breaks it out. For each segment, weigh the factors that correlate with encroachment and strikes, not just the ones easiest to pull from a spreadsheet:
- Population and development trend. Class location changes for a reason. If a segment moved from Class 1 toward Class 2 in the last few years, or if you're seeing permit activity nearby, that's a flag before it's a regulatory requirement.
- One-call ticket volume. A segment generating more locate requests than its neighbors has more digging happening near it, full stop.
- Encroachment history. Past violations, whether it's a fence line creeping onto the easement or a shed that went up without a permit, predict future ones. Landowners who've crossed the line before tend to do it again, or their neighbors do.
- Access and visibility. A segment with dense tree cover, standing water half the year, or a locked gate three miles from the nearest road takes longer to patrol and gets skipped more often when crews are stretched. That's exactly why it needs a plan, not a shrug.
- Time since last eyes-on. If your last foot or aerial patrol of a segment was eight months ago and the requirement is quarterly, that segment jumps the queue regardless of what else is going on.
Score each segment against these factors, even roughly on a 1-to-3 scale per item, and you get a ranked list instead of a gut feeling. The segments at the top get your foot crews and your aerial patrol slots first. The segments at the bottom still get covered inside the regulatory window, just not ahead of the ones where something's more likely to happen.
Build the schedule around the ranking, not the calendar
Once you've got a ranked list, the patrol calendar stops being "drive the whole line every X weeks" and becomes "hit the top-tier segments on the tightest rotation your crew can sustain, and let the quiet segments ride the minimum interval." That's where most ROW teams find they've got more slack than they thought, because the ranking tells you which 20% of the corridor is producing most of the encroachment reports.
The gap in this approach is the same one it's always been: a ranked list is only as good as its last update, and ground crews can't physically re-survey the whole corridor every two weeks to check if the ranking still holds. That's the stretch between patrols where a contractor grades a new access road or a landowner starts clearing for a pole barn, and nobody with a clipboard happens to be driving past that week.
That gap is what a mileage-indexed encroachment log is for, built from imagery pulled over the whole corridor on a cadence no foot or aerial patrol can match, so new structures and excavations near the easement get flagged before the next scheduled drive-by rather than after. Pipeline Encroachment turns that imagery into exactly that kind of log, routed straight to patrol or landowner outreach, so your ranking stays current between the patrols you have crews for.
If limited crews are forcing you to guess which miles to cover first, it's worth seeing what a biweekly flag on the whole corridor would do to that guesswork.