Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Development Agreements topic
No spam. Unsubscribe anytime.
Planning Commission unanimously recommends new development-agreement code to council
Summary
After a public hearing with no public testimony, the City of Fife Planning Commission voted unanimously May 4 to recommend replacement language for the municipal code governing development agreements; staff said the changes increase flexibility while requiring public-benefit criteria for negotiated deals.
Get email alerts on the Development Agreements topic
No spam. Unsubscribe anytime.
The City of Fife Planning Commission voted unanimously May 4 to recommend staff-drafted amendments that replace the city’s existing development-agreement code and add a clearer framework for negotiated agreements. The recommendation now moves to the city council for further study and formal action.
Staff presented a clean and tracked version of the ordinance that would repeal section 19.6811 and replace it with a new, more detailed development-agreement section. Staff told commissioners the update defines the purpose of development agreements, clarifies what must be included in an agreement, sets decision criteria and limitations, and establishes procedures for minor and major amendments. Staff’s written findings, presented at the hearing, conclude the proposal is consistent with the comprehensive plan and promotes public health, safety and welfare.
Director Larson told the commission these changes are intended to give the city “a little bit more flexibility” in negotiating site-specific public benefits while preserving review against municipal code and comprehensive-plan policies. Staff clarified that where the municipal code already mandates a development agreement for specific approvals (for example, multifamily tax-exemption projects or high-capacity transit stations), the new public-benefit requirement would not add an extra constraint in those limited instances.
Commissioners asked procedural and oversight questions before the hearing. Staff explained that the commission is not bound by the council’s no-decision-on-hearing-day practice and that state oversight is limited to statutory requirements (consistency with local code, a hearing, and recording the agreement on title); larger projects might trigger SEPA or shoreline notices that bring additional state notice requirements.
Chair Waldner opened the public hearing and invited in-person and virtual testimony. No members of the public attended or submitted testimony, and the hearing was closed. Commissioner Nicholas Carlson moved to recommend the proposed code language as drafted by city staff; the motion was seconded and passed with no recorded opposition.
Next steps: staff will forward the commission’s recommendation to the city council. Council is expected to consider the amendments at a study session in May and to proceed with a public hearing and adoption process in June–July, according to staff. The commission’s recommendation and staff findings are part of the record that council will review.
Authorities referenced in the hearing include the cited municipal-code sections and the RCW standards staff used to assess procedure and notice.
