How Seattle connects watersheds, services and separate funds

Watershed supply connects resource protection with delivery

Seattle’s drinking-water service connects Cedar and Tolt surface-water resources with treatment, conveyance and customer delivery. Watershed protection supports that physical supply relationship through habitat and resource responsibilities. Those functions establish a connected operating portrait rather than a universal assessment that every future supply or climate exposure is resolved.

Treatment facilities, treated-water storage and pumping serve different delivery functions. Rated processing or pumping capacity does not measure the amount supplied during a reporting year, and storage capacity is not daily output. Reading those categories separately explains how assets contribute without inventing a combined operating total.

Produced water and billed consumption also describe different points in the service chain and preserve their published units. An apparent difference between them cannot be turned into a newly calculated physical-loss measure. Annual leakage and the rolling compliance account retain their own definitions, periods and distinct reporting purposes.

Retail, wholesale and regional relationships preserve different scopes

The water system combines Seattle-area retail service with wholesale relationships through suburban districts, municipalities and the Cascade Water Alliance. Its wider service population differs from the municipal population and from billed-account counts. Those institutional distinctions locate the utility’s services without assigning every regional resident the same customer relationship.

The Saving Water Partnership provides another regional boundary for conservation goals and reported use. Partnership membership differs from Seattle-only production or consumption. Its conservation account adds context to demand management without replacing the Water System’s own operating measures or establishing a uniform outcome for every retail customer.

Drainage and wastewater collection connect with County treatment and shared project responsibilities. Regional treatment charges have a different basis from the City’s retail volume charge. That relationship explains how collected wastewater reaches another service function without turning the County’s whole treatment system into Seattle-owned utility infrastructure.

Water-quality indicators and collection events need specific definitions

Coliform annual averages and highest-month results summarize different sampling periods. Lead and copper percentiles describe a sampled-home distribution rather than exact system means. A result within its stated sample does not independently establish the condition of every property or blanket compliance with every drinking-water responsibility.

The earlier Cedar ultraviolet monitoring violation has another operating and historical boundary. Its account describes missing monitoring data for part of a treatment unit’s operation, with treatment continuing. The event-specific statement about public-health implications is not a current-year incident account or a universal certification of future performance.

Wastewater overflow measures follow their own definitions. Annual system events and volume differ from an outfall-specific moving-period control objective, while sanitary events form another category. Recorded events, the subset used in performance calculations and a reported cause such as root intrusion should remain separate rather than implying a system-wide asset-condition score.

Distinct fund accounts relate services to financial outcomes

The Water Fund and Drainage and Wastewater Fund provide separate operating accounts. Their revenues and expenses relate financial results to different services. Combining them into one invented performance score would erase the service boundary, while a broader utility measure including solid waste cannot be assigned entirely to drinking water.

Audited operating expenses include depreciation and amortization, whereas official-statement rows use a different expense definition. These accounts do not establish a contradiction or two independent costs to add together. Intergovernmental payments within the drainage and wastewater account are also already part of its reported expense category.

Financing stock, newly issued principal and a reported loan draw have separate financial meanings. The drainage and wastewater parity-bond stock already includes its federal infrastructure-financing bond. Agency cash and coverage calculations retain their methodologies rather than becoming matched substitutes for fund accounting or an independently refreshed credit assessment.

Compatible histories add context without changing accounting definitions

Co-published operating-revenue rows provide a within-fund historical reference for the Water System and Drainage and Wastewater System. Each table follows a specific published row and unit. The two service histories consequently remain separate accounts rather than one combined trajectory attributed to every Seattle utility function.

The later tables do not splice earlier official-statement rows into a newly harmonized series. Published expense rows before debt service also differ from audited expense definitions including depreciation. Those differences matter when a historical account is connected with the latest financial portrait rather than silently scaled into a common-looking number.

Historical revenue context does not independently establish physical service improvement or customer affordability. Nor does the existence of revenue and expense rows authorize a new margin or coverage ratio. Their value lies in retaining a comparable reported boundary within each series while preserving the separate meaning of other accounts.

Customer and development accounts explain specific relationships

Adopted retail wastewater charges, a typical residential water bill and County treatment rates have different services and units. A typical-bill example is not a universal household charge. Adding unlike regional and retail units would manufacture a bill rather than explain the actual relationship between treatment funding and customer services.

Eligibility-based assistance and reported participation also have specific customer boundaries. They do not establish a uniform affordability benefit for all accounts. Survey responses provide a baseline of responding opinions, while a combined past-due balance including other utility funds cannot be relabeled as water-only customer debt.

Asset renewal, overflow storage and operational sustainability aims then add a development portrait to those operating relationships. Adopted programs, shared costs and future completion expectations occupy different stages. Seattle’s system is most intelligible when these plans accompany reported outcomes without being substituted for completed construction or matched later operating results.