On Oct. 22, Congresswoman Laura Gillen (D-N.Y.) and Rep. Brian Fitzpatrick (R-Pa.) introduced the bipartisan Protect Clean Water Act. According to Water Finance and Management, the measure is "legislation to help fund the removal of toxic per- and polyfluoroalkyl substances" from drinking water supplies. The report's summary covers the introduction and the stated purpose. It does not describe the bill's text, its cost, its eligibility rules, or any cost-share terms, and this article does not assume them.
Introduction Is Not an Appropriation
A bill that has been introduced has not yet told a utility how much money it will receive, which agency will administer it, or what conditions will attach. Those answers come from later steps: committee action, votes in each chamber, an appropriation that funds the program, and then program rules that define who qualifies. Each step can change the scope. A utility that waits for the final rules before preparing will usually find that the application window is short and that the supporting paperwork takes longer to assemble than the deadline allows.
What a Pre-Award File Holds
The practical response is to assemble a file now that could support most federal or state drinking water grants. Four parts carry most of the weight.
The first is an asset record. Pipe, treatment, and storage inventories should show what the system owns, how each item was assessed, and when. An entry without a date or a source is hard to defend in a scoring review, and reviewers tend to discount what they cannot trace.
The second is a sampling record. For PFAS, the file should keep the analytical method, the reporting limits, the sample locations, and the collection dates. A reviewer needs to see what a result means before a project is justified on it. Nondetect results, in particular, carry a reporting limit that defines how far the data can be pushed.
The third is a project scope with a documented cost basis. Engineering estimates should label which figures come from bids, which come from vendor quotes, and which are planning allowances. Cost sheets that mix these without marking them invite questions and slow approval, and an estimate that cannot explain its own assumptions is hard to carry through a board vote.
The fourth is the local decision trail: board resolutions, capital plan entries, and any rate study showing that the project fits the system's finances. Program staff and auditors look for this record because it shows the utility has already committed to the work it is asking the program to support.
Local Share and Operating Cost
Many federal water programs require a local share or attach other conditions. The report summary does not say whether this bill would. The utility should not assume a match is waived or required. It should identify which budget would carry a local share if one applies, confirm that the budget can support it, and map the approval steps the board would need to take on a short timeline.
Capital projects also create operating costs. Treatment media, residuals handling, sampling, and staff time continue after a grant closes. A file that describes only the construction cost will leave the board with an unfunded obligation years later. Including a multi-year operating estimate, even a rough one labeled as such, is more useful to a board than a capital figure alone.
Where the File Stops
The file cannot predict which program will exist, what it will reward, or how long review will take. What it can do is make the utility's position legible to any program that eventually appears. Once the bill text, the committee record, and any implementing guidance are public, the utility should check each against the file and close the gaps it finds. Until then, the sound position is to treat the Protect Clean Water Act as a reason to organize existing records, not as a line item to budget against.