Lake Forest Park council reviews middle-housing, ADU and unit‑lot subdivision code amendments

Lake Forest Park City Council members on June 16 discussed proposed code amendments in two ordinances—25‑13‑09 (unit‑lot subdivision) and 25‑13‑10 (middle housing and accessory dwelling units)—with staff recommending approval and asking the council to consider minor clarifications before final action.

The measures update the Lake Forest Park Municipal Code to implement recent state housing legislation and to clarify how ADUs and unit‑lot subdivisions are treated locally. Mark Hoffman, Community Development Director, told the council that the city completed a Department of Commerce 60‑day review and a SIPA determination of nonsignificance with no appeals and that the ordinances incorporate planning commission and public comments. “The recommendation is for approval, and then we'll go from there,” Hoffman said; he noted a regular meeting is scheduled at 7 p.m. on June 26 for potential adoption.

Why it matters: the amendments respond to state middle‑housing requirements and the city’s comprehensive plan, and they affect whether ADUs are permitted on lots that are substandard for minimum lot area. Those changes would alter development rights and the application of development standards (setbacks, height, lot coverage, impervious surfaces) for parent and unit lots.

Council and staff discussion focused on clarity and scope rather than major policy reversals. Planning commission recommended splitting a subsection of the ADU provision so the council can consider whether ADUs should be allowed on existing lots that do not meet the current minimum lot area; staff’s reading of planning commission intent was that ADUs should be permitted on substandard lots when development standards can be met. “The motion and the recommendation from planning commission was no. Bring the language to city council,” Hoffman said, summarizing the commission’s action and staff’s view that the change is consistent with the comprehensive plan.

City Attorney Pratt raised a statutory‑consistency concern about suggested draft language for unit‑lot provisions and said the simpler version in the current draft was less likely to be read as inconsistent with state law. “I think the longer version can be confusing,” Pratt said, cautioning that phrasing that appears to cascade parent‑lot rules onto unit lots could be misread. After discussion the council accepted withdrawing the suggested substitution and kept the simpler draft language for further review.

Councilors and staff also reviewed items the planning commission has placed in a “parking lot” of follow‑up topics. Hoffman listed several parking‑related state bills and local items that will be addressed later, including parking changes associated with transit‑oriented development (citation referenced in the packet as “51 48”) and provisions tied to “house bill 11 10 and 13 37” as noted in staff materials. Staff said not all recent state legislation was incorporated because some items came late in the process; one such law on lot splitting (referenced in the packet as HB 10 96) takes effect July 27, 2025 and staff recommended removing draft references to a new “lot split” definition from the current ordinances until the city completes a focused update.

Staff offered targeted edits in exhibit A (the redline in council packets). Hoffman and planning‑commission staff asked council to review highlighted text (examples noted at packet page 11 and the ADU exhibit at page 37) and return final comments before June 26. Council members who spoke expressed general support for the staff recommendations, emphasizing careful, incremental change; one councilor said the package represented “a sensible way to go” and supported deferring more extensive items to the planning commission’s parking lot.

What the council directed: staff will produce a clean revised draft reflecting the clarifications discussed, remove or hold the draft lot‑split definition pending the separate lot‑split work, and return the ordinances for potential adoption at the June 26 regular meeting. No final vote was taken at the June 16 special meeting.

The council’s next formal action on these ordinances is scheduled for the June 26 regular meeting; staff advised council members to raise any remaining technical edits with staff before that date.