Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Comprehensive Plan Update topic
No spam. Unsubscribe anytime.
Planning commission presses staff for more review time on comprehensive plan, capital facilities and code updates
Summary
Planning staff outlined a three‑ordinance adoption schedule for Tumwater’s comprehensive plan update, capital facilities plan and development code changes; commissioners asked for more time and clearer materials, citing a tight timeline and the need for director‑level briefings on capital projects.
Get email alerts on the Comprehensive Plan Update topic
No spam. Unsubscribe anytime.
Planning staff outlined the City of Tumwater’s adoption path for its comprehensive plan update at the Sept. 9 Planning Commission meeting, describing a three‑ordinance approach and a schedule that would aim to meet state update requirements by year‑end. Commissioners pressed staff for more time to review the Capital Facilities Plan (CFP) and the development code changes, saying earlier access to draft materials and director‑level briefings are needed to provide informed recommendations.
Staff presented the proposed adoption approach: three separate ordinances covering (1) the Capital Facilities Plan, (2) the comprehensive plan text, maps and appendices, and (3) the development code updates tied to the comprehensive plan. Staff said the schedule includes briefings and work sessions beginning in September and public hearings in the fall, with a target to complete required updates before the statutory deadline of Dec. 31, 2025. The department also said it will file required notices with the Department of Commerce.
Commissioners urged additional review time for the CFP in particular, noting the CFP contains numerous department‑level projects across transportation, utilities, parks and public safety and that a useful review requires direct access to department directors who can explain project scope, funding and prioritization. One commissioner said the proposed schedule was “much too tight” for a thorough review; several suggested brief, director‑led sessions (often run at noon or as special meetings) to walk through major project groups rather than expecting the full commission to absorb the entire packet at the meeting immediately prior to a hearing.
Staff responded that the schedule was designed to align the plan and code adoption—citing legal risks the city can face if the plan is adopted without the implementing code in place—and to meet state timing and funding cycles. Staff also said that, where possible, the commission would receive draft materials earlier in the week ahead of the Sept. 23 briefing and that additional director briefings can be pursued where feasible.
The conversation included formatting and accessibility feedback on the plan introduction document (readability and column layout), priority‑setting concerns (what the council will be able to fund and staff to implement), and the mechanics of monitoring and reporting implementation: commissioners asked staff to clarify how lead roles, reporting cadence and progress monitoring will be handled once the plan is adopted. Staff confirmed many policy actions include an identified lead department in draft implementation tables and said reporting mechanisms could be a topic at the joint work session with the City Council.
No formal vote was taken on adoption dates at the Sept. 9 meeting; commissioners and staff agreed to provide early copies of the draft CFP and the comp plan packet ahead of the Sept. 23 meeting and to consider special briefings so commissioners can review department capital projects before public hearings.

