Road crossing vs utility crossing: what counts as encroachment
Field techs get this question from landowners, contractors, and sometimes from inspectors who should know better: if there's already a road over the line, why does a new fiber run next to it count as encroachment? A road crossing and a utility crossing are governed by different paperwork, and encroachment review checks both against the agreement or permit on file, regardless of how normal the crossing looks from the fence line.
Road crossings: usually authorized, rarely reviewed
Most road crossings on a mature corridor predate the current ROW team. They were set up under a road crossing agreement with the county, the state DOT, or a private landowner, and that agreement specifies depth of cover, casing requirements, and sometimes a maximum axle load for anything driving over the line. Because the crossing has existed for years, it tends to get treated as background, not as something anyone checks.
That's where the gap shows up. A county regrades the road and deepens the ditch on one side. A landowner widens a farm crossing and adds a culvert without telling anyone. None of that is in the original agreement, and none of it gets caught by a patrol that's looking for obvious strikes, not for six inches of lost cover at mile marker 114. The agreement authorized a crossing. It didn't authorize whatever the crossing has quietly become five or ten years later.
Utility crossings: the permit sets the terms, not the crossing itself
A utility crossing permit works the same way in principle but gets violated more often in practice, mostly because there are more parties involved. Telecom, fiber, water main, a buried power feed: each one needs a crossing permit from the operator before anyone puts a trencher in the ground, and that permit sets the crossing angle, the minimum vertical separation, and the depth. One-call tickets are supposed to catch this before the bucket hits dirt, but tickets get called in late, locates get missed, and crews occasionally just don't call.
So the encroachment question for a utility crossing isn't "is there a crossing here." It's "does this crossing match the permit on file, at this location, at this depth." A fiber line that drifted thirty feet from its permitted alignment during construction is still an encroachment even though a permit exists, because the permit doesn't cover where the line ended up.
What actually counts as encroachment
Strip it down and encroachment is any of three things: a structure, excavation, or crossing with no agreement or permit on file at all; one that exists on file but was installed somewhere other than what the paperwork says; or one that's drifted out of compliance since, a shed built over the easement, a fence line that's crept six feet into the ROW, a ditch that's been deepened past the authorized cover. The agreement or permit is the baseline. Encroachment is whatever doesn't match it anymore, whether it was never authorized or just stopped matching what was authorized.
The hard part is finding which of the hundreds of road and utility crossings on a given corridor have drifted since the last time anyone looked, before the next scheduled foot patrol happens to pass that exact stretch. Our biweekly encroachment log flags new structures, excavations, and road or utility crossings against the mile markers where they show up, so your team can check them against the agreement register instead of relying on whoever last walked that section.
If you're trying to close the gap between what's on file and what's sitting on your right-of-way, that's the problem Pipeline Encroachment was built to catch.