How to brief a field inspector before a dig-up near a pipeline
An inspector who shows up to a reported dig-up with nothing but a segment number and a landowner's name spends the first twenty minutes doing work the office could have done first. Walking a line cold, figuring out what's there, who's digging, and whether it's close enough to matter, burns daylight you don't have if the excavator is still running.
The brief is what turns a drive-out into a response. Here's what needs to be in it.
What to tell an inspector before a site visit
Lead with where, not just the segment ID. Give a milepost or station range tight enough that the inspector isn't walking a half-mile of right-of-way looking for a backhoe. Put a last-known GPS point or cross street in the brief itself, where the inspector can read it without hunting through a separate email.
Tell them what triggered the dispatch. A landowner call, a one-call ticket, a contractor notification, or something spotted in imagery are four different levels of confidence, and the inspector should know which one they're walking into. "Reported by adjacent landowner, unconfirmed" sets different expectations than "ticket on file, excavator confirmed on site Tuesday."
Give them the pipe. Depth of cover at that station, diameter, product, and whether it's near a class location change. An inspector standing at the fence deciding how close is too close needs that number in hand already, without a callback to engineering.
Note what's already been done. If dispatch called the one-call center, if a locate request is on file, if the contractor has been contacted and claims they're outside the easement, say so. The inspector then confirms the record on site instead of discovering nothing was checked at all.
Last, tell them who to call and what authority they have on site. Dispatch should answer, before anyone leaves the yard, whether the inspector can ask the crew to stop work directly or has to document and escalate. That's not a call an inspector should be making for the first time standing at the fence.
A dig-up inspection checklist that holds up in the field
Boiled down, a brief that holds up in the field covers:
- Segment and station range, with a map point if you have one
- Source of the report and how solid it is
- Equipment type and activity observed, if known, and when
- Depth of cover, diameter, and product at that station
- One-call ticket number and locate status, if any
- Landowner or contractor contact already on file
- Who the inspector calls if the crew is still working when they arrive
- What the inspector is authorized to do on site
None of this is complicated. It's also the exact set of things that gets skipped when the only information dispatch has is a voicemail from a landowner saying there's "some kind of digging going on out by the fence line."
The stretch of line nobody's watching
The checklist above assumes dispatch already knows something is happening. Most third-party dig-ups near buried pipe still get caught the way they did twenty years ago: a landowner notices and gets annoyed enough to pick up the phone, or doesn't. Construction crews don't call integrity teams before they bring in machinery, and a locate request on file doesn't guarantee the crew staged anywhere near the actual line.
A weekly check of the right-of-way against fresh imagery closes that gap by flagging new equipment or material laydown on a segment before anyone has to wait on a call. That's the difference between briefing an inspector off a vague tip and briefing them off a dated note that says what showed up, where, and when.
Pipeline Threat Alert builds that dated briefing per segment, so the next dig-up near your line gets caught while the excavator is still parked there.