Committee debates whether single-exit multiplex changes belong in base code or appendix

Washington State Building Code Council Executive Committee · March 6, 2026

Get AI-powered insights, summaries, and transcripts

Subscribe
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

During other business the chair raised whether single-exit/multiplex housing rules — discussed by a tag that recommended no action — should instead be developed as base-code language; members disagreed over process and legislative intent and agreed to discuss the matter at BRFW as a technical public forum next week.

During the meeting's other business the chair asked the executive committee whether BRFW should examine code language for single-exit multiplex housing and potentially move elements from the appendix into the base code.

The chair said the full council had previously voted 10-1 to ask the tag to consider Type 3 construction up to six stories; the tag recommended no action. The chair raised whether the council should nevertheless examine potential base-code language, noting differing views about legislative intent.

Tom Handy questioned whether bylaws or policy really belong in the governing documents and urged caution about changing bylaws too frequently. Jay and Roger noted that the conventional code proposal process delegates initial code writing and recommendation to tags, and that moving beyond a tag's recommendation late in a cycle raises procedural concerns.

Roger, chair of the single-exit multiplex tag, said he had not found explicit legislative intent in the RCW supporting a base-code change for single-exit; he urged careful consideration. Patrick Hanks agreed that the tag generally saw the change as appropriate for the 2027 cycle, not an immediate adoption for the current cycle.

The chair said he was open to using BRFW as a technical public forum next week to explore what base-code language might look like and to ensure transparency before any council action. No formal motion or vote was taken; the committee left the question open for further technical review and possible inclusion on the BRFW agenda.