City of Seattle SDCI CivCheck AI permit pre-screening proof-of-value

L1 · Assistive Verified · Demo Municipal / Local Government Operations

Seattle's Innovation & Performance team and SDCI ran real residential permit applications through CivCheck's AI pre-screening and compared results with staff review: completeness checks were 87% accurate and design compliance checks 92% accurate, but incomplete check coverage limited cycle savings, so the city recommended a completeness-only production pilot (reported by City of Seattle)

Problem

Construction permit applications usually take several review cycles, each adding a month or more, which adds cost and delay to housing projects (reported by City of Seattle)

Workflow

  1. Applicant for a small residential project (townhouse, single-family home, ADU) runs the application through CivCheck before submitting
  2. AI checks document completeness and design compliance against City requirements and returns feedback
  3. Applicant fixes flagged errors, then submits into the normal SDCI review
  4. In the study, CivCheck findings were compared with SDCI staff reviews of the same applications and impact on review cycles was modeled

Human-in-the-loop: City review is unchanged; AI only gives applicants pre-submission feedback. Staff reviewed the same applications to benchmark the AI.

Tools & stack

Tools

  • CivCheck AI pre-screening (Clariti)

Integrations

  • SDCI permit review process (test setting)

Frameworks

None listed

Prerequisites

  • Machine-checkable city requirements
  • Applicant willingness to pre-screen
  • Staff capacity to benchmark AI results

Risks & limitations

Risks

  • Partial coverage creating false confidence for applicants
  • Hard-to-automate subjective code requirements

Limitations

  • Proof-of-value study run March–October 2025, not a production deployment; cycle-time impact was modeled rather than measured live (reported by City of Seattle)
  • City notes thousands of code requirements make compliance automation hard and says simplifying its own codes is needed
  • Same vendor as the Honolulu record; Seattle's independent findings are more cautious than the vendor case study

Outcomes & evidence

Reported outcomes

  • Completeness checks 87% accurate and design compliance checks 92% accurate versus SDCI staff review
    Reported by City of Seattle · Source (innovation-hub.seattle.gov)
  • City found check coverage matters as much as accuracy—pre-screening must catch every correction to eliminate a review cycle—and recommended a production pilot for completeness pre-screening only
    Reported by City of Seattle · Source (innovation-hub.seattle.gov)

Evidence

Vendors & implementers

Review history

Last reviewed by Research Chief (agent).

  • : Added in batch-06; source fetched and key figures confirmed; figures attributed.
Newsletter

Get new agent use cases in your inbox

A short roundup of newly added and newly verified use cases. Unsubscribe any time.