Managing Lead Service Line Replacement Programs: What Utilities Need to Track

# Managing Lead Service Line Replacement Programs: What Utilities Need to Track

The EPA's revised Lead and Copper Rule Improvements (LCRI) established a 10-year deadline to replace every lead service line in the United States. For water utilities, that mandate is not a distant policy concern — it is an active program management challenge requiring systematic data collection, precise tracking across thousands of individual assets, and documentation that withstands federal audit.

This article covers what the rule requires, what data you need at the asset level, common program management failures, and what a PMIS must do to support LSLR compliance at scale.

What the Mandate Actually Requires

The LCRI, finalized in 2024, requires all community water systems and non-transient non-community water systems to:

• Complete a full lead service line inventory and make it publicly available
• Replace all lead service lines — including galvanized lines downstream of lead — within 10 years
• Notify affected customers within 24 hours of confirming lead service line presence
• Replace lead service lines found during any excavation regardless of the trigger

The rule does not distinguish between utility-owned and customer-owned pipe segments. Both must be replaced. If a utility replaces only its portion of the service line, the partial replacement must be documented and the customer-side line must still be replaced — typically within one year or under a state-approved timeline.

For utilities in EPA Region 10 — Oregon, Washington, Idaho, and Alaska — this rule is administered through state primacy agencies. Oregon DEQ and Washington Department of Health (DOH) have each issued guidance layering state-specific requirements on top of the federal baseline.

The Inventory Problem

Before any replacement can happen, a utility must know what it has. That sounds simple. It is not.

Many utilities — particularly those serving communities built before 1986 — have incomplete or inaccurate service line material records. Historical records may show "iron" for what was actually lead. Galvanized lines that appear safe may have been connected downstream of lead mains decades ago, making them GRR (galvanized requiring replacement) under the rule's definitions.

The inventory process requires:

Record review: Tap cards, installation permits, inspection records, and historical as-builts. For most utilities, this means digitizing paper records that may span 60 or more years.

Field verification: For any record classified as "unknown," the rule requires physical verification — either excavation, in-line inspection, or a state-approved predictive methodology. Unknown lines cannot simply be assumed non-lead.

Probability scoring for unknowns: Utilities with large unknown populations may use statistical models based on construction year, permit data, parcel age, and replacement history. This approach still requires a state-approved methodology and documentation of the model's basis.

The inventory is not a one-time deliverable. It must be updated as replacements occur, new unknowns are discovered, and customer-reported information changes classifications.

What Data to Collect at the Asset Level

Every service line in your system needs a record that tracks:

• Unique asset identifier tied to your GIS parcel layer
• Service line material classification: lead, GRR, unknown, or non-lead
• Classification basis: record review, excavation, predictive model, customer-reported, or other
• Date of last classification update
• Replacement status: not started, scheduled, in progress, or complete
• Replacement date (actual or projected)
• Verification method post-replacement (photo documentation, inspection certificate)
• Contractor name and license number
• Permit number (where required by jurisdiction)
• Funding source: DWSRF, IIJA, rate revenue, or other federal grant
• Customer notification dates and method (required within 24 hours of lead confirmation)
• Customer-side status: replaced, not replaced, owner-refused, or pending
• Any partial replacement status with required follow-up dates

If your utility is receiving IIJA Drinking Water SRF funds, your state SRF administrator will require documentation at this level of detail before disbursing reimbursements. An Excel spreadsheet managing thousands of rows will not survive this process without errors.

How Progress Tracking Works at Scale

A utility replacing 500 service lines per year over 10 years is managing 5,000 distinct asset actions, each with multiple sub-tasks: scheduling, notification, permitting, excavation, inspection, customer coordination, and documentation.

Effective LSLR program management requires:

A geographic view: Your replacement queue should be mappable. Clustering replacements by block or pressure zone reduces mobilization costs. Proximity to other planned excavations — road projects, water main replacements — creates efficiency opportunities if surfaced in time.

Status tracking at the task level: The line is not "in progress" or "complete." It moves through discrete states — inventory confirmed, customer notified, permit issued, contractor scheduled, excavation complete, inspection passed, record updated. Each state has a timestamp and responsible party.

Customer coordination workflow: LSLR involves private property access. Customer refusals must be documented, follow-up attempts recorded, and escalation paths (including regulatory notification of refusals) tracked per state requirements.

Funding attribution: Not all replacements are funded the same way. Some may be rate-funded, others DWSRF, others tied to specific IIJA grants with Davis-Bacon wage compliance and Buy American requirements. Your records must tie each replacement to its funding source and meet that source's documentation standard.

Reporting outputs: Annual reporting to your state primacy agency, public-facing inventory updates, and board-level progress dashboards all need to pull from the same data source. If your tracking system can't generate these outputs on demand, you are doing double work.

Common Program Management Failures

The most common LSLR failures utilities face are not technical — they are data and coordination failures.

Losing sight of customer-side lines: Utilities that replace their portion and close the work order without tracking customer-side completion are creating future compliance exposure. The rule requires both sides. Partial replacement timelines must be monitored.

Notification gaps: Failing to notify a customer within 24 hours of confirming lead is a compliance violation on its own, separate from the replacement requirement. If your field crew confirms lead during an excavation, the notification clock starts immediately. Without a system that triggers notifications automatically, this falls through the cracks.

Funding documentation failures: IIJA SRF funds come with federal strings — Davis-Bacon prevailing wages, Buy American material requirements, and detailed reimbursement documentation. Utilities that don't capture these records at the time of construction face disallowed costs during audit.

Inventory drift: Replacements that don't trigger immediate inventory updates create discrepancy between your public-facing inventory and your actual completion status. Regulators check both.

Staff turnover: LSLR programs run 10 years. If program knowledge lives in one coordinator's head or a spreadsheet on a shared drive, staff turnover creates a reset that can set the program back years.

What a PMIS Must Do to Support LSLR

A project management information system supporting LSLR compliance needs to do more than store records. It must:

• Maintain a live, GIS-integrated inventory with per-line classification and status
• Track task-level workflow for each service line through the replacement lifecycle
• Generate customer notification records with timestamps and delivery method
• Attribute each replacement to a funding source and store associated compliance documentation
• Produce inventory reports in the format required by your state primacy agency
• Flag partial replacements with automated follow-up reminders
• Track contractor and permit data at the record level
• Allow field crews to update records from the field, not days later at the office

AMP Essentials PMIS is designed to support exactly this kind of asset-level program tracking, connecting field data collection to capital program records and compliance reporting outputs. For utilities managing LSLR alongside other capital programs, a unified PMIS prevents the fragmentation that creates audit risk.

Practical Takeaways

• Start your inventory now if you have not. The longer you operate with a large unknown population, the more compressed your replacement timeline becomes.
• Build your data schema before you start replacing. Retrofitting records after hundreds of replacements have occurred is painful and error-prone.
• Understand your state SRF administrator's documentation requirements before you spend a dollar of IIJA funding. Disallowed costs are real.
• Treat the customer-side line as part of the asset. Close that loop in your records, not just the utility-side.
• Plan your replacement geography. Clustering with other capital work reduces cost per replacement and extends your funding further.
• Do not let program knowledge live outside your PMIS. Staff turnover is not a question of if — it is when.

The LSLR mandate is the largest drinking water infrastructure program most utilities have ever managed. The utilities that execute it successfully will be the ones that built their data and tracking systems before they needed them.