A large water request usually starts with a phone call, a rough site sketch, and a meeting added to someone's calendar. Each step draws on staff time, and often on outside engineering or legal help, before any agreement exists. Most utility accounting systems were not built to tag that early effort to a prospective customer, so the record of what an inquiry cost is often rebuilt later from calendars and email.
The American Water Works Association has released a report titled Cooling the Cloud: Considerations for Water Utilities Evaluating Data Center Development. Water Finance and Management's summary of the AWWA report says the document is meant "to help utilities navigate these conversations." That description frames the report as a planning aid. The summary does not address how a utility should account for the staff time those conversations consume, and nothing in this article assumes that it does.
Why the first hours matter
Costs incurred before a signed agreement are commonly charged to general operating accounts. That is convenient at the time and awkward later. If a rate study or a board presentation needs to show that large-load service carries its own planning cost, the file must separate inquiry hours from routine operations. Without a project code opened at first contact, the separation depends on reconstruction, and reconstructed hours are easy to dispute.
The problem is not limited to large customers. Any request that consumes modeling runs, legal review, or a public meeting can leave the same gap. Data center inquiries make the gap visible because the hours tend to be concentrated in a short period and the customer may be sizable enough to draw attention.
What to record from the first contact
A usable record starts with the basic facts of the inquiry: the date and channel of first contact, who initiated it, and whether the request named a site, a maximum daily demand, a peak demand, or a cooling method. These fields are often missing in early correspondence, and the gaps are worth noting as gaps rather than filling them from memory.
Staff hours should be logged by job class and task, with the reason for each entry. Outside consultant invoices belong in the same file, along with the scope each one covered. Any hydraulic or supply model run should record the model version and the input assumptions used. If a nondisclosure agreement was signed, its date and signatories belong in the file as well.
Estimates are not commitments
Informal capacity statements have a way of being repeated as firm answers. Record who gave each statement, the date, and any condition attached to it, such as seasonal supply limits or a pending permit review. A verbal "we can likely serve that" and a written capacity letter carry different weight, and the file should show which one exists.
Prospective customers sometimes bring their own equipment quotes. When a customer submits estimates from independent regional dealers such as Jones Air & Water, file them as the customer's submissions, not as utility findings. The utility's own analysis of available supply and treatment capacity should be kept in a separate record so that neither document is mistaken for the other later.
Where the uncertainty remains
General guidance does not set a tariff, a capacity figure, or a permit limit. Source type, treatment train, seasonal demand, and existing permit conditions differ from one utility to the next, and a national report cannot resolve those differences. How a specific utility codes its planning hours is a question for its finance director and its external auditor, and the answer should be written into policy before the next inquiry arrives.
The practical test is simple. Pick the most recent large-load inquiry at your utility, and see whether its hours can be totaled from the file alone, without asking anyone to remember. If they cannot, the first improvement is a project code opened at first contact, not a more detailed rate model.