Water conferences concentrate equipment, technical expertise and peer experience in one place. They also concentrate distractions. A utility team can spend several days collecting product literature and still return without a clearer path for its most pressing process problem.
That risk will be especially relevant when WEFTEC convenes in New Orleans from September 26 through September 30, 2026. Water Finance and Management, in a preview of WEFTEC's return to New Orleans, reports that more than 23,000 registrants and 1,000 exhibitors are expected. The figures come from the outlet's summary and describe the expected scale of the event, not its eventual attendance.
A show of that size rewards preparation. Before staff compare technologies, they should agree on what operating condition they are trying to change, which constraints cannot move and what evidence would justify another conversation after the event.
Write the problem without naming the solution
A useful conference brief begins with a process statement, not an equipment category. “We need a new aeration system” already assumes the answer. “We cannot maintain the required dissolved oxygen profile during peak loading without exceeding the available blower capacity” gives an exhibitor something that can be tested.
The distinction matters because several interventions may address the same symptom. Controls, diffuser maintenance, mixing, process configuration or additional capacity could each affect aeration performance. The appropriate option depends on measurements, physical limits and operating objectives. A solution-first description can prevent staff from noticing alternatives that carry different energy, maintenance and integration demands.
The brief should identify where the problem occurs, when it appears, how it is detected and what operators do in response. It should also separate confirmed observations from working theories. A repeated instrument reading is evidence only if the instrument, sampling point and maintenance history support it. An operator's account of an intermittent condition is valuable, but it may point to the next measurement rather than establish the mechanism.
Carry the constraints that vendors cannot see
Exhibitors can explain what their systems are designed to do. They cannot infer the utility's electrical service, hydraulic profile, footprint, staffing pattern, discharge permit, communications architecture or tolerance for shutdowns.
A one-page constraint sheet should therefore travel with the team. Depending on the project, it might list available head, flow range, influent variability, space limitations, materials restrictions, control protocols and the hours when trained maintenance staff are present. It should distinguish firm limits from preferences. “No new building” is different from “reuse of the existing building is preferred.”
Utilities should also define the boundary of the proposed system. A device may perform well while shifting work upstream or downstream. Screening equipment can change solids handling. A treatment process can add residuals, chemical storage or ventilation needs. An analyzer can require sample conditioning, calibration materials and data validation. Conference discussions become more useful when the questions include these supporting systems.
Ask for evidence in comparable units
Vendor claims are difficult to compare when each conversation uses a different basis. The team should prepare a short set of repeatable questions: What influent conditions define the claimed performance? Is capacity stated at average, peak or design flow? What utilities and consumables are included? Which maintenance tasks require specialized labor? What happens when a sensor, pump or communications link fails?
Answers need not be complete on the exhibit floor. The objective is to learn whether a technology deserves structured follow-up. Staff should record assumptions and requested documents while the conversation is fresh. A simple form can capture the proposed application, required site data, relevant references, unresolved risks and the next responsible person on each side.
That record also reduces the influence of presentation quality. A polished demonstration is not a performance guarantee, while an unfamiliar product is not necessarily unsuitable. Both should advance through the same evidence gates.
Return with a shortlist, not a shopping bag
After the conference, the utility can sort contacts into three groups: no fit, possible fit with missing information, and candidate for formal evaluation. That last category still does not equal approval. Pilot testing, reference checks, procurement review, lifecycle analysis and engineering validation may remain necessary.
WEFTEC's scale creates access to many possible answers. The utility's preparation determines whether those answers address the actual question. A concise problem statement, an explicit constraint list and a standard evidence request can turn a crowded exhibit floor into the beginning of a defensible technical review.