Pole Audit Solutions for Texas Electric Utilities
Forensic chain documentation for utility pole audits. SHA-256 sealed records, EXIF-embedded photo evidence, C2PA chain-of-custody, and PUCT-aligned reporting — built for the January 2027 HB 144 deadline.
A pole audit solution is the system of record a Texas electric utility uses to prove — to landowners, to the PUCT, to Guidehouse reviewers, and to FEMA after a disaster declaration — that every distribution pole was inspected, classified, remediated, and reported on schedule.
AcreSeal is the forensic-grade version of that system. Every record is sealed with a SHA-256 hash chain anchored to the prior record. Every photo carries EXIF metadata and a C2PA signature linking it to the inspection. Every landowner complaint enters a structured lifecycle with timestamps, GPS, and chain-of-custody preserved indefinitely. The output meets HB 144 Sec. 38.103 plan-submission requirements today and stays ready for the monthly reporting cadence that begins after PUCT plan approval.
We built AcreSeal for the 75 Texas electric cooperatives, 72 municipal utilities, and 6 investor-owned utilities that need to file by January 2027 — and for the disaster-recovery filings that follow when wildfires, hurricanes, and severe weather damage that same infrastructure.
What modern pole audit solutions provide
Forensic SHA-256 hash chain
Each pole record is sealed and anchored to the prior record by SHA-256 hash. Tamper-evident by construction: changing any field in any record invalidates every record after it, and the break is immediately visible at the public verification endpoint.
EXIF embedding + C2PA photo signing
Every photo carries embedded EXIF metadata (capture time, GPS, device, AcreSeal-specific provenance tags) and a C2PA signature linking the image to its inspection record. Photo authenticity becomes cryptographically verifiable, not merely asserted.
Compliance reporting + audit trail
PUCT-aligned monthly reports with per-pole pass/fail status, remediation tracking, and Guidehouse-review-ready PDF + CSV exports. Every state transition is timestamped and signed; nothing leaves the chain.
FEMA Public Assistance Category-codified exports
FEMA Public Assistance Category-codified PDF exports for disaster recovery filings — Category-aware classification, municipality-namespaced packaging, ready for FEMA submission. The same forensic chain that documents day-to-day inspections becomes the substantiation packet when a federal disaster declaration follows a storm or fire event.
Public verification endpoint
Any record — landowner, regulator, insurer, or member-consumer — can independently verify the SHA-256 hash chain, GPS, and timestamp at acreseal.com/verify. No login. No subscription. The verification layer is part of the product, not a separate service.
Why traditional pole audits fall short
Paper forms, scanned PDFs, and shared spreadsheets all share the same structural weakness: nothing prevents a record from being edited after the fact, and nothing proves it wasn't. When a Guidehouse reviewer asks whether a 2026 inspection record has been modified since it was originally captured, “trust the source spreadsheet” is not an answer.
Manual workflows also drift. Field crews log inspections in one system, office staff transcribe into another, and the connection between the original field observation and the regulatory submission becomes a chain of human judgment calls. Every transcription step is a potential audit-trail gap.
The cost shows up under regulatory pressure. When the PUCT requests documentation for a specific complaint or inspection, recovering the original evidence — the photo a field tech took on March 14, the GPS coordinates at the time of capture, the weather conditions at the moment of inspection — can take days or weeks. During a disaster recovery filing, that same delay translates directly into delayed FEMA reimbursement.
A forensic-grade pole audit solution removes the gap by making the original evidence the record. There is no transcription step, no reconstruction phase, no “we believe this is what happened.” The hash chain is the audit trail; the photo is the evidence; the record is itself the submission.
AcreSeal's forensic chain methodology
Every record in AcreSeal — every inspection, every landowner complaint, every photo, every state transition — is sealed with a SHA-256 hash that incorporates the prior record's hash. The chain begins at a genesis record and extends forward indefinitely. The cryptographic property is simple: any change to any field in any record invalidates the hash of that record, which invalidates every record after it.
Photo evidence travels through the same chain. EXIF metadata is embedded at capture time with AcreSeal-specific provenance fields (record ID, hash anchor, capture context). C2PA signatures bind the image to its inspection so that even if a photo is extracted and circulated independently, its provenance is cryptographically traceable back to the original record.
Verification is public. Any document anchored to the AcreSeal chain — a landowner complaint receipt, a compliance export, a FEMA Public Assistance package — carries a verification URL that resolves at acreseal.com/verify. No login required. The chain itself is the proof.
This is the documentation standard HB 144 Sec. 38.103 implicitly assumes when it requires utilities to demonstrate compliance under Guidehouse review: tamper-evident records, intact chain-of-custody, and reviewer-independent verification. Most existing audit workflows assert these properties; AcreSeal proves them.
Built for Texas HB 144 and SB 1789 compliance
HB 144 Sec. 38.103 requires every Texas electric utility — roughly 153 entities including cooperatives, IOUs, and municipal utilities — to file an initial pole inspection and management plan with the PUCT by January 1, 2027. After plan approval, utilities file monthly progress reports on inspections, complaint resolution, and remediation under Sec. 38.103(e).
SB 1789 directs the PUCT to adopt statewide structural integrity standards that the pole inspection plans must align with. AcreSeal's data model is built around the Sec. 38.103 subsection structure so that the export packet maps cleanly to the criteria Guidehouse uses during review.
For utilities also navigating DCRF (Distribution Cost Recovery Factor) filings, the same forensic chain that documents HB 144 inspections supports the documentation standard DCRF reviewers now expect — pole replacements, condition assessments, and remediation tracking with intact audit trails.
For a plain-English walk-through of what HB 144 actually requires, see our HB 144 compliance guide.
How utilities use AcreSeal during the pilot phase
A typical AcreSeal pilot runs seven days from coverage configuration to steady-state operation. The pilot is shaped so that the utility's field and office workflows aren't disrupted: AcreSeal slots underneath existing inspection schedules and complaint intake rather than replacing them on day one.
- Day 1-2 — Coverage configuration. Utility service territory is loaded into AcreSeal's coverage layer (see /coverage); landowner complaint routing is configured to the utility's operations queue.
- Day 3-4 — Complaint flow testing. The landowner report-a-pole flow is exercised end-to-end against test records; SHA-256 hash chain integrity is verified on every submission; staff review the dashboard and acknowledge the SLA workflow.
- Day 5-6 — Operational integration. Inspection workflows are connected to AcreSeal's record format; staff are trained on the dashboard and export tooling; a representative subset of recent inspections is migrated to validate format compatibility.
- Day 7 — Steady-state operation. AcreSeal accepts live complaints and inspections; the forensic chain begins accumulating production records; monthly PUCT export tooling is validated against the first weeks of data.
Before scheduling a pilot, most utilities run the free five-minute HB 144 Readiness Assessment to map their current compliance posture against the Sec. 38.103 subsections and identify the highest-leverage gaps to close first.
See the forensic chain in action.
Twenty minutes to walk you through the SHA-256 chain, the EXIF + C2PA photo workflow, the FEMA Public Assistance export, and the PUCT-aligned monthly reporting cadence. No slide deck — a working demo.
Want to verify a record without scheduling anything? Try the public verification endpoint →