Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Development Agreements topic
No spam. Unsubscribe anytime.
Fife planners review draft development-agreement code, including 20-year vesting cap and limits on arbitration
Summary
Planning staff proposed draft code to clarify how Fife will negotiate development agreements, outlining allowable modifications, public‑benefit incentives such as impact‑fee credits and utility capacity reservations, and limits including a proposed maximum vesting period and no binding arbitration clause.
Planning Director Larson presented draft code language at the March 2, 2026, City of Fife Planning Commission meeting to govern development agreements, saying the rules are meant to spell out “what is Fife’s process” and to give clarity to both the city and private developers.
The draft divides the code into purpose, process, contents, authorized flexibility, decision criteria, limits and amendment procedures. Larson said the code would allow the city to modify or authorize project-specific changes to street construction standards, administrative building-design review, performance standards, bulk and dimensional standards (including heights and setbacks), landscaping (excluding critical areas), and density up to existing planned-residential maximums. He described incentives staff has proposed, including credits against transportation and parks impact fees and possible reservations of utility capacity for the life of an agreement.
Larson emphasized that proposed decision criteria require an agreement to advance the comprehensive plan and deliver public benefits that the municipal code would not otherwise secure. He gave examples of potential public-benefit language to be refined in later drafts — for instance, tying affordable‑housing incentives to a portion of units at an income target or specifying sustainability standards for projects that seek credit. “If you are going to modify it, we might as well say we’re willing to keep that modification for the life of the development agreement,” he said, explaining the vesting concept.
The draft also lists explicit limitations: the city would not allow vesting of critical areas, shoreline or floodplain regulations, international building code requirements, or federal/state mandates; it would not permit a binding arbitration clause; and it contemplates a practical vesting ceiling (Larson discussed limits “no longer than 10, 20 years,” with milestones required for vesting extensions longer than five years).
Commissioners pressed staff on several points. One asked whether liability or indemnity language should be spelled out in the required agreement contents; Larson said he would check with the city attorney and expected such language is likely already included in contract boilerplate. Another commissioner asked whether project‑level deviations would allow designs inconsistent with surrounding properties; Larson said the code allows targeted modifications but that the council — informed by staff and planning‑commission recommendations — would determine whether a proposed deviation aligns with overall policy. On transferability he clarified that recorded agreements typically “run with the land” and have been transferred in past Fife cases.
Larson said the draft borrows examples used successfully (and unsuccessfully) in nearby jurisdictions and that the commission’s feedback would guide narrowing the draft lists of allowable changes and public‑benefit definitions before staff returns with a revised version.
Next steps: staff will refine the language, consult the city attorney on indemnity and hearing/notice questions, and bring updated code language back to the commission for further recommendation to the city council.
