What is a no-notice excavation, and how do damage prevention programs track it?
A no-notice excavation is exactly what it sounds like: someone is moving dirt near your right-of-way and there's no locate ticket tied to the activity. No 811 call, no one-call request, nothing in the ticket management system that would have routed a locator to the site before the first bucket went in the ground.
That's different from a late ticket or a mismarked one. Those show up in your records because somebody at least started the process. A no-notice dig never enters the process at all. It's a third-party contractor, a landowner with a backhoe, a fence crew, a drainage project, or a developer grading a pad, working within your easement or close enough to it to matter, without ever triggering the one-call system that's supposed to be the first line of defense.
Why some digging never generates a ticket
Most states require a locate request before excavation near underground facilities, but the exemptions are where a lot of unauthorized excavation happens. Homeowner projects under a certain depth, agricultural tilling, and some emergency repairs can fall outside the notification requirement depending on the state. Even where the law is clear, enforcement depends on the digger knowing the rules and choosing to follow them.
In practice, damage prevention programs end up relying on a mix of things to catch what one-call misses: CGA DIRT data after the fact, landowner complaints, aerial patrol flyovers on whatever cadence the budget allows, and sometimes a local contractor who happens to call the pipeline company directly because they've worked near the line before. None of that is monitoring. It's a collection of lagging indicators that mostly tell you about a strike after it already happened, or a near-miss that got reported because someone felt like reporting it.
The gap is the time between when equipment shows up and when your integrity team hears about it. A grading job can move a lot of dirt in two or three days. If the first signal you get is a landowner call or a damage report, the equipment that caused the problem is often already gone, and so is a lot of the information you'd want about what happened at the crossing.
What tracking looks like day to day
For most programs, tracking no-notice activity is a manual, reactive process built around whatever reports come in. A GIS tech might run a periodic desktop review of recent aerial imagery for a few priority segments. A right-of-way agent might get a tip from a landowner. An inspector might notice fresh tire tracks on a routine patrol that happened to pass through at the right time. These are useful signals, but none of them run on a fixed schedule that matches how fast construction equipment moves onto a right-of-way.
The segments that matter most for this kind of tracking are usually the ones with known development pressure: pipeline crossings near subdivisions under construction, agricultural land that's changing hands, utility corridors shared with other infrastructure, and anywhere a county has recently issued grading or building permits nearby. Those are the places a no-notice dig is statistically more likely to show up, and they're the places where a weekly look at the ground, rather than a quarterly one, actually changes how fast someone gets dispatched.
That's the piece our weekly imagery briefings are built around: a dated, segment-by-segment check for machinery and material laydown near the line, so a no-notice job gets flagged while the excavator is still parked there, not after it's gone and the ticket history shows nothing at all.
If your team is still finding out about third-party digging from a landowner's phone call, it's worth seeing what a standing weekly check of your segments looks like instead.