Positive response vs. locate ticket: what's the difference?
If you work damage prevention or integrity management long enough, you'll hear these two terms used almost interchangeably by people who should know better. They're not the same thing, and mixing them up is how a crew ends up digging near a line nobody flagged in time.
What a locate ticket is
A locate ticket is the request. An excavator, contractor, or homeowner calls 811 (or submits online) before they dig, and that call generates a ticket number tied to a specific address or GPS point, a work description, and a start date. The one-call center routes that ticket to every member utility with facilities in the area, your operator included.
The ticket is the trigger. It's what tells your locate department, or your contract locator, that someone has planned excavation near your right-of-way and that a member needs to go mark the line before the backhoe shows up. No ticket means no formal notice went out. It doesn't mean nobody's digging.
What a positive response code is
Positive response is what happens after the ticket. Most states run a positive response system where the locator (your staff or a contract locating company) goes out, does the locate, and then logs a status code back into the one-call system: marked, clear, conflict, unable to locate, or a handful of other codes depending on the state's format.
That code is a compliance record. It tells the excavator and the one-call center that someone responded to the ticket and what they found. It's the proof of locate that keeps the ticket from sitting open and keeps your operator out of a documented negative-response violation.
Where the gap sits
Here's the part that doesn't show up in any training deck: both of these systems run on paperwork, not on dirt. A ticket tells you a dig was requested. A positive response tells you a locator responded to that request. Neither one tells you whether the excavator actually showed up, whether they started on the date they said they would, whether the work grew past the original ticket boundary, or whether a second crew started digging nearby without pulling a ticket at all.
Integrity teams know this gap by a different name: the landowner call. Somebody drives past a right-of-way, sees a trencher sitting next to the pipe, and calls the operator's hotline. By then equipment has already been on site for days, sometimes longer, and whatever locate marks were painted have long since worn off or been driven over.
No-ticket digging is the harder problem. DIRT report data year after year puts failure to call 811 among the top root causes of third-party damage, and those are by definition excavations your ticketing system never saw coming, because no ticket means no positive response, no locate, and no record at all until something gets hit.
Why this distinction matters for dispatch
If you're deciding where to send an inspector today, a ticket count or a positive response log only tells you where excavation was scheduled. It says nothing about where equipment is staged on the ground this week. A segment can have a clean positive-response history and still have machinery parked on it this week, either because the dig is still within its ticket window or because nobody called it in at all.
That's the layer paperwork can't cover: eyes on the ground, or the next best thing to it. Pipeline Threat Alert checks VHR imagery over your segments weekly and flags machinery and material laydown near the line, ticketed or not, so an inspector gets sent while the equipment is still parked there instead of after a landowner beats you to the call.
If your damage prevention program is still leaning entirely on ticket counts and positive response logs to know where the risk is this week, it might be worth seeing what a weekly imagery pass over your right-of-way turns up.