811 one-call tickets: managing locate requests and positive response

Reference article · 6 min read

Any agency that owns buried pipe, conduit, duct, or cable is a facility operator under its state's damage prevention law. When an excavator calls 811 or files online, the state one-call center sends a locate request, usually called a ticket, to every member whose registered service area overlaps the described dig site. From that moment the agency is on a clock it did not set: decide whether its facilities are in the dig area, mark them if they are, and report back what it did.

The work looks routine until something is hit. After a damaged gas service, a cut fiber trunk, or a broken force main, the argument moves quickly to records. Was the ticket received and screened. Were marks placed, and where. Was a response posted, and when. Almost everything that protects the agency in that conversation is created in the first hours after the ticket arrives, by staff who were not thinking about litigation at the time. That is why ticket handling deserves a real system rather than a shared inbox.

The ticket, the clock, and the ticket's life

Notice periods, ticket types, and response deadlines are set by state statute and rule, and they differ meaningfully across states. Most states require advance notice measured in business days before digging, with holidays excluded and specific rules about when the clock starts. Confirm the exact requirements with your state one-call center and your counsel rather than relying on a summary.

Ticket types matter. Normal or routine tickets carry the standard clock. Emergency tickets demand immediate attention. Design or planning tickets usually ask for records rather than field marks. Meet tickets require a scheduled site visit. Update, refresh, and remark tickets extend or repeat work already done.
Tickets expire. Marks have a valid life, and the excavator must request an update to keep working legally. Track expiring and remark-eligible tickets as deliberately as you track new ones.
Your registration drives your volume. The service area polygon or grid you file with the one-call center determines which tickets you receive. Under-registering produces missed notices and unmarked facilities. Over-registering buries locators in clears. Review the registration annually and after every annexation, extension, or system acquisition.

Screening the dig area against your facility map

Dig site descriptions arrive as free text plus geometry of varying quality. Practical ticket software geocodes the described area, applies a configurable buffer, and intersects it with your GIS layers so a screener can make a defensible clear or locate decision at a desk, with the reasoning recorded.

A thin or inaccurate map shows up in two places. It shows up as avoidable truck rolls, when staff drive out because nobody can tell from the office whether a line is there. It shows up again as damages, when a service lateral, an abandoned segment, or a line captured only on a paper as-built is never marked. Both are ordinary budget items that agencies rarely attribute to map quality. Close the loop by letting locators submit field corrections from the device they already carry, and by requiring surveyed or GPS-captured as-builts before new construction is accepted.

Positive response as a legal record

Many states operate a positive response system that requires operators to report ticket status through a code by a deadline, using a web portal, phone system, or API. Where it is not mandated, excavators generally expect it anyway, and industry damage prevention practice supports it. Code sets vary by state but usually distinguish marked, clear or no conflict, marked except for a described portion, unable to complete because of access or other obstruction, and delayed by agreement with the excavator.

Two rules keep this clean. First, post the response automatically from the field closeout rather than re-keying it later, because manual transcription is where late and incorrect responses come from. Second, never post marked before the marks exist. A response that does not match the ground is a credibility problem long after it stops being a paperwork problem.

Marks and the evidence file

Marking uses the APWA uniform color code: white for proposed excavation, pink for temporary survey markings, red for electric, yellow for gas, oil, and steam, orange for communications, blue for potable water, purple for reclaimed water and irrigation, and green for sewer and drain. State rules add the details that get argued about later, including tolerance zone width, offset marking, use of paint, flags, and whiskers, and how to treat facilities that cannot be located.

Build the evidence file as part of the job, not afterward:

GPS-captured marks. Record the points and lines actually painted, with coordinates and timestamps.
Photographs. Before and after images showing marks in context, with visible landmarks.
Ticket and response history. The received ticket, screening decision, assignment, closeout, and the response code with its timestamp.
Retention. Keep this package for a period aligned with your records retention schedule and the relevant statute of limitations, and make sure the system supports legal hold.

In-house locators, contract services, or both

In-house locators learn the system, recognize anomalies, and can correct the map as they go. They also carry fixed cost through seasonal volume swings and require training, equipment, and on-call coverage. Contract locate services absorb volume swings and bring trained staff quickly, but statutory responsibility stays with the agency no matter who holds the paint gun. Many agencies run a hybrid, keeping complex, critical, or high-consequence facilities in house and sending routine residential tickets to a contractor.

Whichever model you choose, the ticket system of record should belong to the agency. If the contractor's platform holds your history, a transition becomes a data recovery project at the worst possible time.

What to ask and what to require

Ask vendors:

Does the system receive tickets directly from our state one-call center in its native format, and post positive response back automatically on field closeout, including every state we operate in?
How does screening work against our GIS, which data formats are supported, how often are layers refreshed, and is the buffer configurable by facility type?
Do field crews work offline and sync, since many dig sites have poor coverage?
Can staff export a complete evidence package for a single ticket, and produce on-time response and damage-per-ticket reporting without a custom request?

Require in the contract: agency ownership of ticket, response, photo, and location data, with documented export on demand and at termination; service levels tied to the statutory clock rather than vendor business hours; retention and legal hold support; hosting and security terms consistent with your state's policy; and, for locate services, defined scope for remarks and emergencies, sampled quality audits, and cooperation in damage root cause investigations.

HQT builds and integrates software systems for state and local government, including GIS-connected workflow and field data collection applications of the kind described here.

Frequently asked questions

How long does an agency have to respond to an 811 locate request?

Response deadlines are set by each state's damage prevention statute and rules, and they vary. Most states measure the excavator's advance notice in business days and excluding holidays, with specific rules about when the clock starts and how emergency and short-notice tickets are handled. Confirm the exact deadlines, ticket life, and remark rules with your state one-call center and your legal counsel, because these requirements are amended periodically.

What is positive response and is our agency required to use it?

Positive response is the practice of reporting back to the one-call center what the facility operator did with a ticket, using a defined status code such as marked, clear, or unable to complete. Many states require it by rule and operate a portal, phone system, or API for posting status by a deadline. Where it is not required, excavators still generally expect it, and posting a status creates a timestamped record that helps the agency after a damage.

Should we use in-house locators or a contract locate service?

In-house locators develop deep familiarity with the system and can correct mapping errors as they find them, but they carry fixed cost through seasonal volume swings. Contract services scale quickly and absorb peaks, though the agency keeps statutory responsibility as the facility operator regardless of who performs the locate. Many agencies use a hybrid model, keeping critical or complex facilities in house. In either case, keep the ticket system of record and its data under agency ownership.

What do the 811 locate marking colors mean?

The APWA uniform color code assigns white to proposed excavation, pink to temporary survey markings, red to electric, yellow to gas, oil, and steam, orange to communications, blue to potable water, purple to reclaimed water and irrigation, and green to sewer and drain. State rules add requirements for tolerance zone width, offset marking, and marking materials such as paint, flags, and whiskers. Check your state's rule for the specific marking standards that apply to your facilities.

What records should we keep after marking a locate ticket?

Keep the received ticket, the screening decision and its basis, the field closeout, the positive response code with its timestamp, GPS-captured mark locations, and dated photographs showing the marks in context. After a damage the central questions are whether marks were present, accurate, and visible, and these records are the agency's answer. Retain the package according to your records retention schedule and the applicable statute of limitations, and make sure your system supports legal hold.