From the Local Government edition of September 15, 2026
Seattle Q2 AI report pairs favorable CivCheck proof-of-value with unspent permitting funds
City of Seattle Information Technology Department · Municipal IT and construction permitting · Seattle, Washington, United States
- Publisher
- Seattle City Clerk filing / Seattle IT Artificial Intelligence Usage Report 2026 Q2
- Original publication
- Quarterly report dated July 1, 2026
- Source retrieved
- 2026-09-15
- Event date
- 2026-07-01
What happened
SDCI completed a CivCheck proof-of-value finding automated checks accurate and capable of reducing intake screening times by up to 46 days, yet $750,000 appropriated for an AI permitting tool remained unspent while several pilots were still being evaluated.
Why it matters
New-to-archive official status report showing that favorable component evaluation does not automatically trigger procurement spend or production deployment in a major U.S. city.
Evidence and measured results
Executive summary and Lessons Learned state CivCheck PoV completion focused on middle housing dwellings, with automated checks described as accurate, comprehensive, and capable of reducing intake screening times by up to 46 days. Financial section states SDCI has not moved forward on implementing an AI permitting tool yet while evaluating several pilots, and that no amount of the $750,000 Construction and Inspections Fund appropriation had been spent to date. Broader inventory notes 21 approved AI software in active use and 18 pilots/PoCs. The report does not republish the full Innovation Hub methodology tables in the inspected Lessons Learned excerpt.
Limitations and uncertainty
Distinct from the already-archived Innovation Hub CivCheck study URL; this filing adds budget and deployment status. 'Up to 46 days' is a city-reported upper bound without the full comparator table in the excerpted Lessons Learned section. PDF text extraction may miss figures. Copilot usage stats are separate from permitting outcomes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-15; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Permitting backlog pressure coexists with unused AI appropriations and incomplete production decisions.
- Stakeholders
- Construction & Inspections leadership
- City IT / Responsible AI program
- Budget and council staff
- Labor partners
- Pilot vendors under evaluation
- Discovery questions
- What remains unresolved after the CivCheck PoV?
- Which supportability and funding gates block spend?
- Are multiple pilots still competing?
- How will quarterly public reporting treat a deferral?
- Value hypothesis
- Structured go/no-go analysis can convert pilot findings into an accountable procurement or deferral decision without equating PoV metrics to live savings.
- Potential engagement
- Decision-support engagement that maps PoV evidence to production prerequisites and residual risks.
- Unsupported claims
- Seattle has production-deployed CivCheck
- Guaranteed 46-day savings after purchase
- Unused funds imply vendor failure rather than deliberate evaluation
Pre-sales engineering
Role takeaway
- Fit
- Post-PoV production readiness assessment for permitting pre-screening tooling.
- Architecture and integration
- Reconnect PoV findings to intake systems, identity, logging and reviewer workflows only after go-live criteria are met.
- Prerequisites
- Complete post-pilot evaluation packet
- Funding authority
- Responsible AI recommendation
- Defined production success metrics
- Constraints
- Parallel pilots
- Unspent appropriation
- Council reporting expectations
- Security
- Re-validate application-data handling, vendor access and audit logging before any production path.
- Proof of value
- Restated clocks and coverage for production scope
- Supportability/scalability sign-off
- User-experience threshold checks
- Spend-versus-benefit tracking plan
Delivery
Role takeaway
- Work
- Produce an explicit deploy, defer or re-compete decision with public-facing rationale.
- Dependencies
- Quarterly AI usage reporting
- Labor and department coordination
- Competing pilot evidence
- Ownership
- SDCI business owner with Seattle IT AI Review Team recommendation path.
- Skills and adoption
- Maintain reviewer capacity and interim procedures while evaluation continues.
- Governance checkpoints
- After PoV packet complete
- Before any appropriation spend
- Before production applicant exposure
- Acceptance criteria
- Written production recommendation
- Appropriation spend status explained
- No silent scope expansion beyond evaluated use
- Risks
- Spending to exhaust funds
- Indefinite stall without documented rationale
- Confusing PoV upper bounds with guaranteed outcomes
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Keep proof-of-value environments separable from production permitting systems until funding, supportability and scale criteria are met.
Governance
Who approves, reviews and stays accountable for outcomes?
Use council-facing quarterly reporting to make the gap between pilot findings and purchase decisions visible to oversight bodies.
Security and privacy
What data, permissions and controls need testing?
Continue applying the city’s Responsible AI review and accuracy/hallucination audit criteria before any permitting production path; the Q2 narrative does not replace a security assessment.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Continue workforce training and labor engagement noted in the report before any permitting production change that alters staff or applicant workflows.
Procurement
What should contracts, pricing and exit terms secure?
Keep appropriations and vendor selection gated on post-pilot supportability evidence; unspent funds can be a control signal rather than delay alone.
Operating model
Which teams own the service once it runs?
Separate innovation-fund and permitting-tool budget lines from automatic deployment authority after a favorable PoV narrative.
What changed
New-to-archive July 1, 2026 clerk-filed quarterly report; adds deployment and appropriation status beyond the earlier Innovation Hub CivCheck study already in the archive.
Publication history
- 2026-09-15Local Government · Issue 104 resources
Stable resource ID: seattle-q2-2026-ai-usage-report