{"resourceId":"everett-ai-permitting-pilot-funding-validation-2026","versions":[{"version":"external-6bd7edfd816e6ea2ce78297fb20acbf5780fcabb574aa5ca70f406c971b1014a","resource":{"id":"everett-ai-permitting-pilot-funding-validation-2026","title":"Everett links permitting pilot funding to internal validation","organization":"City of Everett","sector":"Local government","geography":"Everett, Washington, United States","publishedAt":"Exact publication date unknown; June 24, 2026 council agenda","publicationDate":null,"eventDate":"2026-06-24","sourceName":"City of Everett","sourceLabel":"Government pilot plan and fiscal agenda item; not a completed evaluation","sourceUrl":"https://www.everettwa.gov/AgendaCenter/ViewFile/Item/19782?fileID=107394","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["knowledge-work","infrastructure","governance-procurement","accessibility-workforce","operating-model"],"finding":"The agenda describes a funded residential-intake test, not completed efficacy evidence.","sledRelevance":"Current relevance is its planned September validation window; no launch or successful evaluation is inferred.","evidence":"Up to $130,000 covers expected pilot costs and half the first full SaaS implementation year. Internal tests are planned through September, with a potential October launch. Quality, resubmissions and staff efficiency are evaluation aims, without baselines or sample sizes.","architectureImplications":"Interpretation: Map SaaS intake to the system of record and reconciliation process; hosting details and integration performance remain unspecified.","governanceImplications":"Interpretation: Make launch conditional on documented review, not the calendar.","securityPrivacyImplications":"Interpretation: Establish approved application-data handling, retention, access controls and incident routing before testing.","caveats":"Prospective agenda item, not a results report. Exact publication date is unknown. The separate June 24 city announcement corroborates grant acceptance; current milestone completion is unverified.","streamIds":["local-government"],"roles":{"sales":"Interpretation: Discuss incomplete residential applications with the permitting manager, finance lead and IT sponsor. Ask how many resubmissions are avoidable, how much review time they consume, and what funding remains after external support. A bounded pilot-design engagement can define a realistic decision before a public launch. The value hypothesis is improved application completeness with lower net handling effort, measured locally. Do not turn the grant amount into a software price or an ROI estimate. Include applicants and staff in discovery, and clarify who can authorize continued spending. Evidence of funded experimentation alone does not establish an opportunity, vendor superiority or housing-production gains.","engineering":"Interpretation: Evaluate an intake-assistance workflow that leaves permit decisions with authorized reviewers. Document the form platform, attachments, SaaS interfaces and records reconciliation. Prerequisites include representative consented or synthetic applications, a completeness rubric and failure-routing rules. Test missing plans, contradictory attachments, incorrect addresses and interrupted transfers. Require least-privilege access, auditable data flows and confirmed retention behavior. Validate the full workflow against ordinary intake, recording reviewer corrections and processing effort. The source does not establish integration readiness or hosting controls. Compare proposed deployment constraints against local security requirements before choosing a live test population.","delivery":"Interpretation: Establish a permitting owner, IT support lead and finance checkpoint before internal testing. Schedule staff training, applicant usability sessions, issue triage and a launch decision with an explicit fallback. Dependencies include integration access and enough reviewers to score test cases independently. Proposed acceptance criteria are fewer avoidable resubmissions without more missed requirements, lower net review effort and successful accessibility and data-handling checks; agree thresholds in advance. These are proposed measures, not pilot results. Keep rollout conditional if evidence is incomplete. Include recurring licenses, maintenance and human assistance in the handover budget so a subsidized start does not conceal an unfunded operating commitment."},"retrievedAt":"2026-09-10T03:03:45Z","enrichedAt":"2026-09-10T03:04:50Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Preserve assisted intake and test with residents who have limited digital access.","procurementImplications":"Interpretation: Model recurring costs after subsidy and require transition support before renewal.","operatingModelImplications":"Interpretation: Planning should own acceptance; IT and administration should fund support and review effort.","updateExplanation":"New to the full archive; no source update claimed.","sourceVerification":{"openedUrl":"https://www.everettwa.gov/AgendaCenter/ViewFile/Item/19782?fileID=107394","referenceExcerpt":"potential public launch in October of 2026","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}