Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Capacity Allocation Policy topic
No spam. Unsubscribe anytime.
Council reviews draft wastewater capacity-allocation policy, weighing priorities and reserves
Summary
Staff presented a draft wastewater-capacity allocation policy that would prioritize economic-development projects and previously approved developments, propose reserve percentages (example: 30% residential / 70% nonresidential), and set application and transfer rules; council asked for additional detail on buyback, escrow and fees.
Get email alerts on the Capacity Allocation Policy topic
No spam. Unsubscribe anytime.
Council spent substantial time reviewing a draft policy to govern how the city allocates wastewater-treatment capacity. Joe explained the policy's applicability (existing parcels with service connections would be considered to already have capacity), two narrow exemptions for accessory structures, and three priority categories: a strategic economic-development reserve, previously approved projects with investment, and a waiting-list category for approved site plans that had not yet received allocation.
Staff provided an example split of reserves — suggesting a 30% residential / 70% nonresidential starting point — and emphasized the policy would be adjustable as conditions change. Council and staff discussed whether allocation permits should be transferable only upon written council consent, whether the city should include a formal buyback option if reserved capacity sits unused, and how to structure administrative fees and escrow accounts to fund future expansion without overcharging applicants.
Council asked staff to prepare a table-format evaluation and to return with comparisons of how neighboring jurisdictions handle reservations, buybacks and time windows for reserved capacity. Staff also committed to clarifying eligibility cutoffs (for example, projects with construction plans filed by 07/30/2026) and tracking mechanisms to measure allocated capacity versus actual usage.

