Stop Filing Photos. Start Filing Evidence.
Why Texas distribution utilities need an integrity layer under inspections — not another spreadsheet.
General managers, operations directors, and compliance leads at Texas electric cooperatives, municipal utilities, and distribution organizations are saturated with commentary about regulatory change. What operational leaders still lack is a clear product category.
Inspection software captures work in the field. Forensic evidence infrastructure keeps that capture checkable when a counterparty disputes it later — rather than merely stored in a shared drive.
As utilities build distribution pole management plans, the operational risk is not a shortage of images. It is relying on records that cannot survive independent scrutiny.
1. Process and records, not folder archaeology
Texas Utilities Code §38.103 (HB 144, 89th R.S., 2025) requires covered entities to maintain processes for documenting and responding to a report or complaint made by a landowner regarding the condition or repair of a distribution pole. The enacted subsection is Tex. Util. Code §38.103(b)(5).
The statute's recurring filing is an annual compliance update due not later than May 1 (§38.103(c)). HB 144 requires one recurring filing: an annual compliance update due not later than May 1 of each year (Tex. Util. Code §38.103(c)). It does not require monthly reporting to the PUCT. Monthly reporting and a 24-month transition to annual filing appeared in an earlier draft of the bill and were not enacted.
Separately, 16 TAC §25.63 sets the plan-filing schedule. Under 16 TAC §25.63, initial distribution pole management plans are due January 1, 2027. AcreSeal is not named in statute; the utility remains the regulated filer.
16 TAC §25.63 was adopted by the Public Utility Commission of Texas on July 30, 2026 under PUCT Project No. 59431 and takes effect August 19, 2026. It was adopted with changes to the proposed text published March 27, 2026. The operative authority for the annual compliance update remains the enacted statute, Tex. Util. Code §38.103(c). AcreSeal is completing review of the adopted text against prior published materials; any changes will be noted in a forthcoming correction brief.
Plan reviewers and auditors evaluate whether the documentation supports the program the utility filed — not whether staff intended to do good work.
2. The documentation gap leaders actually feel
Drones and mobile forms produce more images than ever, but most field photos still carry no integrity story a stranger can check.
When a pole fails or a dispute lands, a familiar pattern shows up:
- Scattered storage. Photos across drives, email, and contractor devices.
- Contractor packages nobody can re-check. PDFs that cannot be tested against the original stored bytes.
- Orphaned landowner reports. Safety calls logged as notes, with no clean link to a pole identity or a stored record.
- Turnover. Context leaves with staff. Unauthenticated media stays.
3. Capture versus integrity
AcreSeal is forensic evidence infrastructure designed to complement GIS and work-management systems, not to replace them.
| Tier | Examples (category) | Role |
|---|---|---|
| Work management / intake | Municipal 311, work-order and dispatch tools | Citizen intake, tickets, routing, crew assignment |
| GIS & asset systems | Enterprise GIS and utility asset platforms | Inventory, connectivity, spatial system of record |
| Forensic evidence layer | AcreSeal | Tamper-evident records, stored-bytes integrity, and a digest anyone holding the file can recompute |
AcreSeal does not replace engineering loading analysis, climb programs, or GIS as the asset system of record. It is built so field observations carry a tamper-evident documentation trail underneath those systems.
4. How integrity is established — glass box, not magic
Where a check cannot run honestly, AcreSeal returns null with a reason instead of an unearned label.
- Stored-bytes anchor. The load-bearing integrity claim is the SHA-256 digest of the evidence bytes as stored. Published digests are meant to be reproduced with standard tools against the downloaded file.
- Server recomputation. On upload, the platform recomputes the digest over the stored bytes. A client-supplied digest that disagrees with what was stored is not treated as a successful integrity result.
- Sealed work paths. Third-party attested time covers reports a utility has sealed into a work order. An unsealed landowner submission is labeled as unsealed — never quietly promoted.
- Refuse-to-sign discipline. A missing input, or a check that did not run, produces null or unsealed wording rather than a false positive.
Records are tamper-evident: alteration is designed to be detectable. Detectable is the honest word. It is not a claim that alteration is impossible, and it is not a promise about how any tribunal will treat the record.
5. The stranger test
Field records should be checkable by people who hold no AcreSeal account and who do not default to trusting a vendor badge.
The public case study at acreseal.com/verify/case-study walks a stranger through the check with shasum and openssl. The browser path and the terminal path do not run the same checks, and the page states what each one actually establishes. That distinction is deliberate: describing the check is honest, and describing more than the check is not.
6. A pilot that respects operations
You do not need a rip-and-replace program to start improving evidence quality.
- Scope small. One circuit, one complaint intake channel, or a limited pole-inventory slice.
- Keep IT light. Web-based intake. No full enterprise cutover on day one.
- Define success. Field observations your staff can export and a third party can check, supporting the annual May 1 update discipline the statute actually creates.
Frequently asked questions
How does AcreSeal complement our existing GIS or work-management software?
AcreSeal is forensic evidence infrastructure, not a GIS mapping tool or a municipal work-order system. Crews keep using enterprise GIS and work-management platforms for mapping, routing, and dispatch. AcreSeal sits beneath those tools as an integrity layer: field photos and observations are bound to stored-bytes digests, so the records stay checkable during an audit or a dispute.
What does Texas law require for distribution pole programs?
Texas Utilities Code §38.103 (HB 144, 89th R.S., 2025) requires covered electric utilities, cooperatives, and municipally owned utilities to maintain processes for documenting and responding to a report or complaint made by a landowner regarding the condition or repair of a distribution pole — the enacted subsection is Tex. Util. Code §38.103(b)(5). The statute's recurring filing is an annual compliance update due not later than May 1 (§38.103(c)). Separately, 16 TAC §25.63 (PUCT Project No. 59431) sets the plan-filing schedule, under which initial distribution pole management plans are due January 1, 2027. AcreSeal is not named in statute; the utility remains the regulated filer.
When are the plan and update filings due?
Under 16 TAC §25.63, initial distribution pole management plans are due January 1, 2027. The enacted statute's recurring filing is annual, due not later than May 1 each year (§38.103(c)). HB 144 requires one recurring filing: an annual compliance update due not later than May 1 of each year (Tex. Util. Code §38.103(c)). It does not require monthly reporting to the PUCT. Monthly reporting and a 24-month transition to annual filing appeared in an earlier draft of the bill and were not enacted.
How can a third party check an AcreSeal record without trusting the vendor?
The public case study at acreseal.com/verify/case-study is built so a counterparty can re-check the published digests with standard tools — shasum and openssl — holding no AcreSeal account. The browser path and the terminal path do not run the same checks, and the case study says so explicitly rather than implying they are equivalent.
What does AcreSeal do when a check cannot run?
It returns null with a reason, or says the record is unsealed, rather than printing a “verified” stamp it did not earn. In compliance evidence a confident wrong answer costs more than no answer, because somebody relies on it.
Does AcreSeal replace physical pole inspections or structural analysis?
No. It does not replace climbing inspections, wood-treatment programs, or engineering loading analysis. It provides a tamper-evident documentation layer for the observations and photos those programs produce.
How can a cooperative or municipal utility pilot AcreSeal?
Pilots are scoped for low IT overhead: one circuit, one landowner-complaint intake path, or a limited pole-inventory slice, using web-based tools. Define success as field observations your staff can export and a third party can check — not a dashboard nobody opens.
Related reading
- What Is Texas HB 144? The 2027 Compliance Framework
- Utility Pole Property Rights in Texas: The Complete Landowner Guide
- Utility Pole Replacement and Relocation Costs: A Texas Landowner's Guide
- How to Report a Utility Pole Problem: The Landowner Documentation Guide
About AcreSeal: AcreSeal is forensic evidence infrastructure operated by Ectropy Solutions, LLC (San Antonio, Texas). It provides a tamper-evident documentation layer for field observations relevant to utility infrastructure programs under Texas HB 144.
This guide is general information, not legal, accounting, or engineering advice. Consult qualified counsel or licensed professionals for a specific filing or dispute.
By the AcreSeal Team
AcreSeal builds forensic compliance documentation for Texas utility pole management. Records are hash-chained, so a later edit is detectable; anyone holding the file can recompute the digest at acreseal.com/verify. Third-party attested time covers reports a utility has sealed into a work order.
Test the evidence layer yourself
Open the public case study — no login — or book a short walkthrough of how AcreSeal fits under the stack you already run.