ESRI Shape
Use spatial network records in the clearing workflow.


Ticket clearing
CLI combines configurable buffer-zone logic with trained-technician review to determine whether a ticket can be cleared or requires a field locate.
Clearing method
Each ticket moves through a defined decision path before it is cleared or routed to a locate.
Configurable zones compare the request against the network information provided for the contract.
Configurable rulesA trained technician reviews the ticket and the available record before status is assigned.
Trained decisionThe ticket is recorded as cleared or locate required, then included in the reporting record.
Two outcomesData and integration
CLI's documented clearing formats support common GIS, CAD, and image records.
Use spatial network records in the clearing workflow.
Bring contract drawings into the review record.
Use mapped image files where they are part of the source record.
Connect the ticket decision to the wider operating and reporting record.
Contract accountability
Monthly cleared-versus-required reporting gives the facility owner a plain operating view. It supports review of volumes, decisions, and the tickets that moved to the field without relying on an unexplained dashboard.
Clearing questions
Each ticket is recorded as cleared or locate required, and the decision is included in the reporting record.
Documented clearing formats cover ESRI Shape, DXF and DWG drawings, and mapped JPEG and TIFF image files.
Monthly cleared-versus-required reporting gives the facility owner a plain operating view of volumes, decisions, and the tickets that moved to the field.
A trained technician reviews the ticket and the available record before any status is assigned. Buffer logic alone does not clear a ticket.

Network contract
Bring the network formats, contract geography, and reporting requirements you need the team to assess.