811 locate marks need excavation-specific scope

Define one intended excavation before contacting 811

PHMSA describes the one-call process job by job. The center collects information about the location of the intended dig and contacts companies that may operate underground facilities there. A jurisdiction, utility coordinator, or project team should therefore preserve the specific planned excavation that initiated the contact: project and responsible excavator, site and bounded work area, described activity, planned timing, submitted location information, contact event, and the one-call reference returned by the applicable process.

Those fields are buyer-control recommendations, not a universal PHMSA ticket schema. State law and the responsible one-call program govern required notice content and timing. The record should retain what was actually submitted rather than reconstructing scope from the later permit, drawing, or completed trench. A general project address is not enough when the planned dig area is narrower, shifted, phased, or described through another location method.

Keep each operator determination and field mark distinct

PHMSA says the one-call center contacts companies that may have facilities in the intended area and those companies determine whether their facilities could be affected. If so, the guidance says they must visit and mark the exact location of the facilities. The operating record should connect the submitted excavation scope to each operator notification, the operator's documented determination or response made available through the applicable process, the field visit, and the physical marks observed for that operator.

Do not turn one operator's mark into evidence about another operator, or silence into proof that every underground facility was cleared. PHMSA's page does not define a universal positive-response code set, color semantics, tolerance zone, photograph requirement, or completeness verdict. Where the state or local process supplies those requirements, cite that authority separately. Unknown or unavailable responses should remain visible and route to the responsible owner instead of being normalized into a green project status.

Match the locate-response set to the field job

PHMSA tells excavators to wait the required time under state law, respect the marks, and dig carefully. Before field work, compare the planned excavation now being performed with the area and timing described to the one-call center and the operator determinations and marks returned for that job. Preserve the comparison, observed discrepancies, damaged or unclear marks, changed field conditions, escalation, and accountable decision under the applicable state and local process.

A project may share a parcel, permit, contractor, or drawing with another excavation and still require a different locate scope. If the route, limits, depth description, method, phase, or timing changes materially, the team should stop relying on the earlier evidence until the applicable one-call requirements are reviewed. This article does not assert a universal ticket expiration, renewal, re-mark, or re-notification rule; those details must come from the governing state and program record.

Keep locate evidence outside authorization and outcome claims

An 811 contact, operator determination, or field mark does not establish municipal permit issuance, planning approval, contractor licensing, property access, traffic control, environmental authorization, inspection acceptance, utility shutdown, excavation competence, or safe completion. Those are separate records and authorities. A permitting platform can link them for coordination while preserving the exact purpose and status of each. The locate-response set answers which potentially affected operators were contacted and what facility-location evidence was returned for the planned dig; it does not authorize the work.

Civic Permit Review reviewed PHMSA's official Call Before You Dig page on September 17, 2026. The source supports the per-job contact, intended-location intake, potentially affected operator notification, operator impact determination, facility marking, state-law timing, waiting, respecting marks, and careful-digging statements. It does not establish a project's complete facility population, ticket validity, state-law compliance, permit, authorization, mark accuracy, damage prevention, safety, or outcome. Applicable state law, one-call records, operator evidence, field conditions, and qualified local review remain necessary.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Civic Permit Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.