Your Inspections Are Done. Can You Prove It? The Documentation Gap Facing Texas Utilities Before January 2027

The first round of PUCT annual filings under Project No. 59287 landed in April 2026. Cooperatives across Texas submitted their pole inspection and maintenance reports — documenting how many poles they inspected, how many they remediated, and how many they replaced.

The numbers are impressive. One cooperative inspected over 21,000 distribution poles in a single year. Another replaced 3,649 poles — a 14.4% replacement rate. A third managed 57,000 poles across a territory that spans two states.

The inspections are getting done. That was never the question.

The question — the one Guidehouse will ask when they review your January 2027 submission — is whether you can prove it.

The standard of proof has shifted

Before HB 144, pole inspection was an operational practice. You inspected poles, you kept records, and if someone asked, you produced them from wherever they lived — a spreadsheet, a filing cabinet, an email chain, an inspector's memory.

HB 144 changed the standard. The law requires every electric utility, cooperative, and municipally owned utility to submit a plan to the PUCT that includes documented processes for inspection, training, complaint response, and remedial action — with per-pole deadlines and monthly reporting on results. Senate Bill 1789 adds structural integrity standards and uniform serviceability classifications.

The PUCT contracted Guidehouse — a global consulting firm — for up to $3.5 million to review every submission. This isn't self-certification. It's an external audit of 153 utility compliance programs by professional consultants working against defined criteria.

When a Guidehouse reviewer pulls a sample of your remediation records and traces them from the inspection finding through the work order through the field completion, the documentation chain needs to hold up. Not because the work wasn't done — but because the standard now requires that the evidence be demonstrable, consistent, and independently verifiable.

Where the gap lives

The documentation gap isn't in the inspection itself. Cooperatives have been inspecting poles for decades. Many use experienced third-party contractors like Osmose, Alamon, or their own well-trained crews.

The gap lives in the space between the inspection and the audit.

When an inspector finds a deficient pole, the finding gets recorded — often in a work order system, a GIS layer, or a field notebook. When the remediation happens, the crew records the work — in a different system, a different format, sometimes weeks later. When the monthly PUCT report is due, someone assembles these records from scattered sources into a submission-ready format — under time pressure, on a deadline, hoping nothing was missed.

Each handoff is a potential break in the evidence chain. Each system transition is a point where records can be lost, altered, or disconnected from their source finding. Each manual assembly step introduces the possibility that the documentation doesn't match the reality — not because anyone was dishonest, but because humans operating under time pressure in fragmented systems make mistakes.

That fragmentation is what creates risk. Not the inspection quality — the documentation quality.

What Smokehouse Creek revealed about documentation

The Smokehouse Creek Fire illustrated this gap in the most devastating way possible. The pole that broke and ignited the fire had been inspected by a third-party contractor in January 2024. The inspector identified the decay and gave it a priority-one replacement designation. The pole was tagged as unsafe to climb. Xcel Energy was notified on February 9.

Seventeen days later, the pole broke. Over a million acres burned. Three people died. The utility now faces a billion-dollar lawsuit from the Texas Attorney General, and a judge has issued an injunction requiring 35,000 pole inspections per year.

The inspection happened. The finding was documented. The documentation existed. What didn't exist was an evidence chain that forced the remedial action to happen within a defensible timeline — and a record that proved, cryptographically, that every step from finding to action was captured in real time and couldn't be altered after the fact.

HB 144 is the legislative response to that gap.

What Guidehouse is looking for

Based on the PUCT's published contract scope with Guidehouse, the review will evaluate whether utility compliance programs meet the requirements of Sec. 38.103. The key documentation elements include:

Processes for managing and inspecting poles — not just that you inspect, but that your process is documented, repeatable, and verifiable.

Processes for training and certifying inspection personnel — including third-party vendors. If Osmose inspects your poles, your plan needs to document how you verify their qualifications.

Complaint documentation and response — every landowner complaint about a pole must be documented, tracked from intake through resolution, and included in your compliance reporting.

Per-pole inspection deadlines with remedial action timelines — each deficient pole needs a documented timeline for remediation, and the actual remediation needs to be recorded against that timeline.

Monthly reporting — inspection results, pass/fail determinations, and remedial actions, submitted to the PUCT in a prescribed format.

The common thread across all of these requirements is evidence. Not that the work happened — that the work is provable.

What “provable” means in practice

For a cooperative with 50,000 poles on a 10-year inspection cycle, “provable” means 5,000 inspection records per year, each linked to a specific pole with GPS coordinates, each containing a pass/fail determination, each triggering a remedial action workflow for deficient findings, each flowing into an automated monthly report.

For the remediated poles specifically, “provable” means a chain from the original finding (with timestamp, GPS, inspector ID, and photo evidence) through the work order (with assignment, timeline, and scope) through the field completion (with GPS-verified location, timestamped photos, and inspector attestation) — all connected and all verifiable.

The question every cooperative should ask before January 2027: if a Guidehouse reviewer selects 50 remediation records at random from our submission and traces each one from finding to completion, how many of those chains are complete, consistent, and independently verifiable?

If the answer is “all of them” — you're ready.

If the answer is “most of them, but some might take a few days to assemble from different systems” — that's the gap HB 144 was written to close.

The nine months ahead

The January 2027 deadline is nine months away. The PUCT is already collecting annual reports under Project 59287. Guidehouse has the consulting contract. The review framework is being built from the data utilities are submitting today.

Cooperatives that address the documentation gap now — before the plan submission deadline — get to build their compliance evidence chain on their own terms. Cooperatives that wait until Q4 will be assembling documentation packages under pressure, hoping their scattered records can be stitched together into a defensible submission.

The inspection work is already happening. The question is whether the evidence trail behind it is audit-ready.