Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the City Permitting topic

No spam. Unsubscribe anytime.

Sammamish staff outline permitting process, pre-application steps and enforcement challenges

3281220 · April 8, 2025
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

David Pyle, the city’s permitting manager, told the Sammamish City Council on April 8 that the city has formalized project guidance, screening, pre-application and inspection steps to improve predictability and reduce code compliance cases.

David Pyle, Sammamish permit center manager, presented a detailed overview of the city’s permitting process to the City Council on April 8, explaining permit types, project guidance and pre-application services, plan review and inspections, and enforcement tools the city uses to protect critical areas and public infrastructure.

Pyle told the council the city requires a project guidance submission as an initial, no-cost step that creates a file and assigns staff. He described three broad permit categories: ministerial (routine, non-discretionary permits such as building and electrical), administrative (discretionary but director-level decisions and sometimes appealable) and quasi-judicial actions (fewer, formal hearings such as long subdivisions or shoreline permits). Pyle said pre-application conferences or optional paid predevelopment reviews are available for more complex projects, especially where wetlands, slopes or public-works standards are involved.

Why it matters: Pyle emphasized predictability and clear communication for applicants. He said the city changed its front-counter process to reduce later code compliance problems and now requests a project guidance form so staff have a written record of early advising.

Key points and clarifications - Project guidance and pre-application: Pyle said project guidance, submitted through the city’s online form, creates a record and assigns a staff reviewer. For complex proposals the city can perform optional paid predevelopment reviews to examine technical issues early, he said. He cautioned that environmental findings can change after public comment if neighbors provide new observations. - Permit screening and vesting: Pyle described an electronic screening step that checks whether submittal documents are complete. He said applications only vest to existing code when the application is deemed complete and fees are paid; an invoice alone does not vest an application. - Plan review and inspections: Plans are routed to multiple reviewers including Eastside Fire and Rescue and Sammamish Plateau Water and Sewer District where applicable. Pyle said first-review completeness is a goal but many projects require at least one round of corrections; resubmittals return to screening. Inspections are scheduled through the city portal (mybuildingpermit.com) and staff try to balance geographic routing and workload. - Shoreline and critical areas: Pyle explained that shoreline permitting is governed by the State Shoreline Management Act and the city’s shoreline master program, which requires approval by the Washington State Department of Ecology for updates. He said shoreline setbacks differ by lake and that changes to critical-area rules require coordination with Ecology. - Right-of-way and temporary permits: Pyle outlined right-of-way permits (work in the street), frontage improvements, and leases for permanent installations such as poles or cabinets; he also described temporary-use permits for events and noted these often require detailed traffic, sanitation and staging plans. - Performance agreements and bonds: For alternative tree-protection measures, Pyle said applicants may be required to post a bond (for example, $1,500 per diameter inch) and that bonds are held for multiple years while replacement trees establish. If tree protections fail, the city may require replacement at an 8:1 ratio and retain bond funds. - Compliance and enforcement: Pyle differentiated code compliance (unauthorized activity) from permit compliance (work that deviates from approved permits). He said construction volume sometimes strains inspection capacity and described plans to require clearer site-management plans and improve handoffs between plan reviewers and field inspectors. - Technology and process improvement: The city uses a shared portal (mybuildingpermit) that multiple jurisdictions use; Pyle said the portal’s governance requires adaptation to many agencies’ business practices. He described interest in better digital plan coordinates and the theoretical potential for AI-assisted checks or drone inspections, but said legal and practical limits remain.

Council questions focused on when applicants use optional predevelopment reviews, vesting confusion, what constitutes a "grant of special privilege" for variances and staffing for enforcement. Pyle said the optional predevelopment review is used when technical uncertainty (for example wetland delineations or stormwater approaches) would otherwise create unpredictability. He said the city is adding a required site-management submittal and will convene cross-discipline staff meetings to improve construction handoffs.

Ending: Council members thanked Pyle for the presentation and asked staff to continue streamlining and communicating permit steps; Pyle said staff will pursue process improvements, additional training, and clearer submittal checklists to reduce later corrections and compliance problems.