QA/QC & KPI Tracking in Utility Locating Programs

Utility locating programs, especially 811 contract locating, perform best when quality is measurable and repeatable. Quality assurance (QA), quality control (QC), and KPI tracking are how utility owners and facility operators reduce risk, improve consistency, and maintain accountability at scale.

Why QA/QC Matters

Locating is not just a "paint and move on" task. The downstream impact of a missed or incorrect mark can include damages, outages, emergency repairs, schedule delays, and liability exposure. QA/QC helps ensure the program produces consistent, defensible outcomes.

The connection between QA/QC and damage prevention is direct. Programs that track quality metrics consistently see damage rates drop because they catch problems before they become incidents. A missed locate that gets flagged in a random audit can be corrected. A missed locate that gets flagged by a backhoe cannot.

Common Oversight Gaps

Many locate programs struggle when oversight is informal or inconsistent. Common gaps include:

• No standardized documentation expectations
• Limited auditing of completed tickets
• Inconsistent field verification practices
• Little visibility into repeat calls or rework
• Performance tracked anecdotally instead of with metrics

KPIs Utility Owners Should Track

Tracking a few core KPIs provides immediate clarity on performance and risk. Useful metrics may include:

• On-time response rate: percentage of tickets completed within SLA windows
• Damage ratio: damages per X tickets (tracked by facility type and root cause)
• Rework / repeat locate frequency: how often sites require return trips
• Documentation completeness: ticket notes, photos, and required fields completed
• Exception handling: percentage of tickets with access issues, no-trace conditions, or special coordination needs

KPIs don't exist to punish field staff, they exist to identify patterns early and improve program reliability over time.

What a Structured QC Process Looks Like

A strong QC process typically includes:

• Standardized closeout notes and documentation requirements
• Random audits of completed tickets
• Targeted reviews after damages or repeat calls
• Field coaching and corrective action when patterns appear
• Clear escalation paths for complex or high-risk sites

Building a QA/QC Program from Scratch

If your locating program does not have a formal QA/QC process today, start simple. Trying to implement everything at once leads to overwhelm and abandonment. A practical rollout looks like this:

• Week 1-2: Define your documentation standard. What fields must be completed on every ticket? What does a good closeout note look like? Write it down and share it with every technician.
• Week 3-4: Begin random audits. Pull 5-10 completed tickets per week and review them against your documentation standard. Note gaps but focus on coaching, not punishment.
• Month 2: Start tracking two or three KPIs. On-time response rate and documentation completeness are good starting points because the data is usually available in your ticket management system.
• Month 3: Add damage tracking and rework frequency. Correlate patterns with specific territories, technicians, or facility types.
• Ongoing: Review KPI trends monthly. Share results with the team. Adjust standards as you learn what matters most for your specific program.

The key is consistency. A simple QA/QC process that runs every week is more valuable than an elaborate one that only happens when someone remembers. If you are working with a regional locating partner, align on these expectations during onboarding so both sides are working from the same playbook.

Technology Tools That Support Quality Tracking

You do not need expensive software to run an effective QA/QC program, but the right tools make it easier to sustain. Common technology components include:

• Ticket management systems: Most 811 contract programs use platforms like Utilocate, PelicanCorp, or proprietary systems. These are the foundation for tracking response times, closeout data, and volume metrics.
• Photo documentation apps: Standardized photo capture with timestamps and GPS coordinates provides evidence that markings were placed and conditions were documented. This is invaluable during damage investigations.
• Dashboards and reporting: Even a simple spreadsheet dashboard that tracks weekly KPIs gives program managers visibility. More mature programs use tools like Power BI or Tableau to visualize trends over time.
• Field audit forms: Digital forms (built in tools like ArcGIS Survey123, Microsoft Forms, or Google Forms) allow supervisors to conduct standardized field audits with consistent scoring criteria.

The goal is not to automate everything. It is to make quality visible. When a program manager can pull up last month's damage ratio and compare it to the previous quarter without digging through emails, the program is on solid footing.

Using KPI Data in Contract Negotiations

KPI data is not just an internal management tool. It is leverage in contract negotiations and renewals. Utility owners who track performance metrics can have data-driven conversations with their locating providers instead of relying on subjective impressions.

During contract renewals, KPI history allows you to:

• Demonstrate whether the provider met agreed-upon SLA targets
• Identify specific areas where performance improved or declined
• Negotiate performance-based pricing tied to measurable outcomes
• Set clear expectations for the next contract period with defined benchmarks
• Compare provider performance if evaluating multiple partners

Providers who know their performance is being measured tend to perform better. This is not about creating an adversarial relationship. It is about building a partnership where both sides have clear visibility into what is working and what needs improvement.

Audit-Ready Documentation

When questions arise, whether from a contractor, a facility owner, or a damage investigation, the ability to produce clear documentation matters. Strong documentation includes:

• Clear scope notes and site access details
• Marking method notes when relevant (direct connect vs induction vs passive)
• Photos where visibility or conditions are complex
• Exception notes when utilities are not traceable
• Repeatable closeout structure

Why This Improves Outcomes

Programs that treat QA/QC and KPI tracking as core infrastructure typically see:

• Fewer damages and fewer repeats
• Improved contractor experience
• More predictable field performance
• Better defensibility when incidents occur
• Higher trust from stakeholders

Utility locating is a safety function and a risk function. When quality is measurable, accountability becomes clear and performance improves.