Every easement grant has a line in it about keeping the right-of-way clear of trees and brush, and every planning lead has had the argument about what that means on the ground. "Incompatible vegetation" is a functional test: does this growth threaten the ability to patrol, inspect, locate, or excavate the line safely. There's no single master list of banned species. Species matter, but what matters more is root depth, mature height, and how fast something comes back after a cut.
The functional test, not a species list
Most easement language and most company vegetation management plans define incompatible growth by what it does to the corridor. The name of the species matters less than the effect it has once it reaches a certain size or root depth. Three things usually put a plant on the list:
Root systems that reach pipe depth or close to it. A cottonwood or willow seedling that looks harmless at two feet can send roots deep enough in a few seasons to threaten coating, especially on shallower-lay segments or at road and water crossings.
Mature height that creates a danger-tree situation. Anything capable of growing tall enough to fall across the ROW and strike the pipe, or tall enough to block aerial patrol sightlines, gets treated as incompatible regardless of species, as long as it's inside the corridor or close enough on adjacent land to be a fall-zone risk.
Regrowth habit. Species that coppice hard after cutting, meaning they throw up a dozen stems from one cut stump instead of dying back, cost more in repeat visits than they're worth leaving standing. This is why willow, some maples, and black locust show up so often on incompatible lists even where they're not a root-depth concern. They just come back faster than the mow cycle can keep up with.
Herbaceous cover, grasses, and low forbs are the opposite case. They're compatible almost everywhere because they don't put down woody root structure and they don't block sightlines once mowed. A lot of vegetation management plans want grass cover on the ROW, both for erosion control and because bare soil draws more complaints than a mowed strip ever does.
Where the gray area lives
The disputes don't happen over obvious danger trees. They happen in the three-to-six-foot range, saplings and shrub-stage woody growth that isn't tall enough to be a fall risk yet but is clearly headed there. A planning lead has to decide: is this basal cluster of regrowth from last year's mow still herbaceous-stage, or has it gone woody and crossed into the next cutting window early.
That call used to get made by whoever walked the segment last, which meant it varied by crew, by season, and by how overgrown a given stretch of corridor had gotten before anyone noticed. Agricultural crossings and wetland buffers make it worse, because the species mix there skews toward exactly the fast-coppicing, root-aggressive stuff (willow, alder, dogwood) that's hardest to tell apart at a distance and most expensive to let get ahead of schedule.
Encroachment definitions add another layer. A landowner's ornamental tree planted ten feet off centerline isn't incompatible vegetation in the species sense, but if its root zone or canopy reaches the corridor, it falls under the same clearing authority as volunteer growth. That's usually a notification-and-negotiation problem more than a mowing one, but it starts with the same question: is this plant, where it's standing, a threat to the line.
Keeping up with all of that segment by segment, every growth season, is the job behind the easement language. Pipeline Vegetation turns that into a quarterly, segment-ranked read on where woody stems are closing in on the mow line, so the crews go to the stretches where regrowth has actually crossed the threshold instead of mowing the whole corridor on a calendar because nobody's sure which segments can wait.
If you're tired of guessing which segments earned a visit this quarter, that's the problem this is built to solve.