Heat, water, and impact fees: summer infrastructure stress signals to watch

Summer makes infrastructure visible. Water utilities publish conservation messages, operations staff watch demand, and councils discuss treatment, transmission, storage, streets, drainage, or emergency facilities. The Texas Water Development Board's Water Data for Texas site gives the public a direct view of reservoir conditions. That source can explain why water capacity is receiving attention, but it does not say that a particular city is preparing an impact-fee change.

The same distinction applies to heat. High temperatures can coincide with heavier water use and strain on field operations. A city may respond with restrictions, maintenance, conservation outreach, or a capital project. Those actions have different funding paths. An agenda item for a pump, tank, road, or drainage project is evidence of a public investment decision only at the stage stated in the item. It is not evidence of a new development charge unless the record says so.

For project teams, the first rule is simple: save the condition and the municipal action as separate facts. A reservoir dashboard belongs in the background file. A council packet that names an impact-fee study, service area, or proposed rate belongs in the cost-risk file. Joining them without an official bridge creates a claim the sources do not support.

Chapter 395 of the Texas Local Government Code supplies the process for covered impact fees. The public trail includes land use assumptions and a capital improvements plan, then notices, hearings, advisory committee work, and action by the governing body. Those records matter because the fee calculation depends on expected growth, eligible facilities, service units, and the geography served. A study can produce a maximum calculated amount without requiring a city to charge that amount.

SB 1883, effective September 1, 2025, changed several steps. Its enrolled text requires land use assumptions and the capital improvements plan to be available at least 60 days before the first publication of hearing notice in covered proceedings. It also requires a two-thirds affirmative vote to impose an impact fee and bars an increase for three years from the later of adoption or the most recent increase. For certain new or increased fees in a service area where a fee was previously adopted, the law adds an independent financial audit and a hearing on the audit results.

Those requirements create observable milestones. A consultant contract means analysis is being commissioned. An advisory committee appointment identifies a body that will review the work. Draft assumptions and a capital plan show inputs. A hearing notice starts a formal public step. Proposed ordinance language shows what the governing body may act on. Only adopted action, read with its effective date and exhibits, establishes the decision.

An impact-fee caption can sound citywide while the exhibits tell a narrower story. Roadway service areas, water and wastewater systems, meter sizes, land uses, credits, and service units can produce different results for two projects in the same city. The current fee schedule is only a starting point. The study and ordinance exhibits show which facilities and assumptions support the number.

Fort Worth's official transportation impact-fee update materials illustrate the level of detail worth saving. The record includes the policy and ordinance context behind the schedule. That does not predict what another city will do. It shows why a developer should keep the source document, service-area map, calculation table, meeting date, and final action together instead of recording a fee number without its conditions.

Project status matters too. A tract under contract, an entitled phase, and a future acquisition do not necessarily face the same timing. Teams should ask municipal staff or their own advisers how an adopted provision applies to a particular filing or permit. Agenda monitoring supplies source-linked notice of public action. It does not decide project-specific treatment.

Start with a watchlist for every city and utility connected to the pipeline. Add the council, planning body, capital improvements advisory committee, and any utility or mobility committee that publishes records. Search new agendas for land use assumptions, capital improvements plan, impact fee, service area, financial audit, public hearing, fee schedule, water capacity, wastewater capacity, and roadway capacity. A generic budget workshop is not a match unless its packet contains a relevant item.

When a signal appears, record exactly what happened. Save the source URL, meeting body, date, item number, fee type, geography, stage, proposed amount if one exists, and the next scheduled action. Label the entry as background, study, hearing, proposed action, adopted action, or effective change. That one field keeps a preliminary discussion from entering a pro forma as a final cost.

Use scenarios while the process is open. A team can retain the current adopted fee as its baseline and add a clearly labeled sensitivity using a published proposal. Replace the sensitivity only after the governing body acts and the effective-date rules are understood. If a summer capacity discussion never produces fee-study language, leave it in the infrastructure file. The official record, not the temperature, determines whether a fee decision has entered the project timeline.