Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Service Boundary topic
No spam. Unsubscribe anytime.
Committee voices support for developer request to shift water service boundary to Washington Water Authority for part of proposed subdivision
Summary
Staff presented a developer request to have a portion of an 80-acre proposed subdivision served by Washington Water Authority rather than Fayetteville; the committee voted to express support in principle, noting pressure/pressure-elevation and pump‑station tradeoffs and potential sewer billing arrangements.
City staff and utilities engineering presented a developer-initiated request concerning a proposed subdivision adjacent to the shared water service boundary with Washington Water Authority. The developer and Washington Water requested that Washington Water provide water service to a portion of the site because Washington Water’s nearby infrastructure could serve the lots more quickly.
Corey Grama explained the hydrology and pressure constraints: portions of the parcel sit at elevations near or above Fayetteville tanks, so maintaining a minimum 20 psi could be feasible only with mains extended; the city’s standard specification, however, seeks a 45 psi minimum to provide operational headroom. Portions of the site that exceed available pressure would require a developer-installed booster pump station (public infrastructure if accepted by the city), which would add cost to lot development but could be proposed and assessed among lots.
Grama said sewer service would likely remain Fayetteville’s (via the city’s sewer operator) and noted prior examples where water service boundaries have been adjusted to align customers with the nearest water provider. The committee asked about regulatory standards and operational differences; staff confirmed Washington Water would own and operate any water infrastructure it installed and that sewer would follow Fayetteville standards and ownership.
Committee members voted to express support for the developer’s request to have Washington Water serve the identified portion, with the understanding that final legal exhibits, surveys and an interagency agreement would be required and that City Council would make any ultimate boundary adjustment decision.
Why it matters: changes to service boundaries affect territory served, future revenue, standards of construction and long‑term operations; staff flagged possible tradeoffs between near-term developer timelines and long-term utility planning.
Staff said Washington Water had provided a resolution authorizing its executive director to enter agreements and that staff would proceed with drafting the formal exhibits and agreements if the developer pursues the request.
