Imagine a damage-prevention team doing everything right. Every ticket gets filed. Every crew gets sent out. Every pipeline gets marked before anyone digs near it.
And still, sometimes, something goes wrong.
That's not a story about a team failing at its job. It's a story about a system that was only ever built to watch part of the picture.
Here's how most damage-prevention programs work: someone plans to dig, they call it in, a ticket gets created, and the pipeline operator sends someone out to mark where the pipeline is before any digging starts. When that happens the way it's supposed to, the system has done exactly what it was designed to do.
But what about digging that never gets called in? A landowner clearing brush. A contractor who skips the call. Construction activity near a pipeline that wasn't reported.
That activity doesn't show up in a ticket. Which means, from the system's point of view, it doesn't exist - until, sometimes, it becomes a real problem.
This is the blind spot. It isn't a mistake; it's simply what happens when a safety system is built to track reported activity, and some activity never gets reported at all.
If you ask a damage-prevention team which stretch of pipeline needs attention today, the honest answer is: it depends on a handful of different things, usually scattered across different systems. Is there an open ticket nearby? How close is that activity to a pipeline that would cause serious harm if it were hit? Has this area had problems before? Is there any sign that ground has recently been disturbed, even without a ticket?
On their own, each of those is just one piece of information. But put them together, and a much clearer picture appears. A spot with no ticket, but recent unexplained digging, right next to a sensitive pipeline, and a history of past incidents - that's a very different level of concern than a routine, low-risk job with a ticket already filed. But if your only lens is "is there a ticket," those two situations can look confusingly similar, or worse, the first one won't show up as a concern at all.
Damage-prevention teams already lean on two main tools, and both are genuinely useful. It's just worth being honest about what each one can't do.
Ticketing systems are built to track work that gets reported. That's the whole design, so activity that was never called in simply isn't something they're built to show.
Right-of-way monitoring - patrols and inspections - exists specifically to catch the digging that never gets reported, and they do that well. What they usually don't do is connect a finding to how serious it is: whether it's next to a critical pipeline, or somewhere that wouldn't cause much harm at all.
Both tools do their job. They just answer narrower questions than the one that actually matters most: out of everything going on near our pipelines - reported and unreported - where should we be paying attention right now?
This is the idea behind KartaSoft's Excavation Intelligence: instead of treating "what's ticketed" and "what's not ticketed" as two separate problems, bring them into one shared view.
That means:
Once you look at it this way, a spot with no ticket but a real warning sign next to it stops blending in with routine, low-concern activity. It gets the attention it deserves - instead of sitting invisible in a system that was never built to notice it.
| What tickets show | What KartaSoft adds |
|
Work that's been reported Where a called-in job is happening Basic job details for that ticket |
Signs of digging that was never reported How close that activity is to a sensitive pipeline Whether that area has had problems before |
When an incident does happen, a regulator or an internal review will usually ask more than "what happened." They'll ask what was known beforehand, and when.
Most teams can answer that for anything that had a ticket, because the paperwork already exists. Far fewer can answer it for activity that was never reported at all, not because anyone hid anything, but because there was nothing to point to.
A running record of possible risk, built as things happen rather than pieced together afterward, makes that conversation more straightforward. It's easier to explain a decision backed by evidence than to reconstruct one after the fact.
This isn't about replacing the people who currently do this work, or the tools they already trust. Field teams still make the calls. Ticketing still matters. Patrols still matter. There simply aren't enough time or people to check everything, everywhere, all the time - so the goal is making sure whatever attention is available goes to the places that need it most.
KartaSoft's role is to add a clearer, more complete picture underneath decisions that already must be made - not to make those decisions instead of the people responsible for them.
Curious how this looks in practice? Take a closer look at KartaSoft Excavation Intelligence.