{"resourceId":"svlg-california-local-ai-capacity-study-2026","versions":[{"version":"external-22d54ed05e636be4bb0be67f1d24f31ae196c27b747fa9efa6b1135d1a25bed3","resource":{"id":"svlg-california-local-ai-capacity-study-2026","title":"California interview study links AI purchasing difficulties to data and workforce capacity","organization":"Jake Brymner; Institute for California AI Policy at Silicon Valley Leadership Group","sector":"City and county AI procurement and implementation","geography":"California, United States; nonrepresentative qualitative evidence","publishedAt":"June 11, 2026 (PDF cover; URL directory is not publication date)","publicationDate":"2026-06-11","eventDate":null,"sourceName":"Silicon Valley Leadership Group / ICAP","sourceLabel":"Technology-business association's original policy research; not a government audit","sourceUrl":"https://www.svlg.org/wp-content/uploads/2022/06/A-California-Strategy-to-Leverage-Artificial-Intelligence-to-Enhance-Public-Service-Delivery-in-Local-Government-and-Manage-Risks.pdf","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["developers-agents","infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"Stakeholder research identifies procurement disclosure and organizational readiness as barriers to municipal AI adoption.","sledRelevance":"Direct U.S. local-government evidence; smaller jurisdictions were not directly covered by the municipal policy review, limiting claims about their prevalence of controls.","evidence":"The report describes 15 semi-structured interviews conducted February–April, mainly with local-agency practitioners plus vendors and experts, supplemented by an unfinished survey. Findings include inconsistent vendor information, literacy gaps and fragmented data practices. It acknowledges disclosure and success-reporting bias.","architectureImplications":"Interpretation: Inventory reusable datasets and existing interfaces before choosing build versus buy. Hosting and token costs need separate workload estimates.","governanceImplications":"Interpretation: Define who can approve, challenge and stop a pilot across departments.","securityPrivacyImplications":"Interpretation: Ask suppliers explicitly about reuse, retention and onward transfer of agency inputs; verify answers with the proposed configuration.","caveats":"Business-association publisher with an AI-adoption policy agenda. Qualitative, selected participants; survey response denominator is not stated in the inspected methods passage. No causal estimate of service benefit. Statutory summaries and third-party deployment figures are not adopted as independently verified facts.","streamIds":["local-government"],"roles":{"sales":"Interpretation: Work with the city manager, procurement lead, CIO and department sponsor to identify an actual service bottleneck before discussing products. Ask who understands the data, who evaluates vendor claims and how much internal support the municipality can sustain. A bounded engagement could compare two approaches on one administrative task and produce a costed operating plan. The value hypothesis is a more supportable purchasing decision; these interviews do not prove savings. Avoid assuming smaller jurisdictions lack controls merely because public disclosures are absent. Clarify what existing shared services can supply and what responsibility must remain with the local service owner.","engineering":"Interpretation: Treat build-versus-buy as a maintainability and data-boundary decision. Map source systems, permissions, model access, interfaces and recurring usage costs before prototyping. Prerequisites include an approved test dataset, reproducible tasks and staff able to inspect outputs. Compare products under the same quality and security criteria, then test export and replacement. For generated code or action-taking agents, use isolated repositories, limited credentials and human approval for consequential changes. Proposed proof of value should demonstrate the workflow on representative data and expose operating costs and failure recovery. Neither in-house development enthusiasm nor a shared platform establishes a secure cloud, on-premises or hybrid fit.","delivery":"Interpretation: The department head should own the service outcome, with procurement, IT, privacy and workforce leads jointly responsible for their controls. Establish a pilot charter, train internal champions, track assistance requests and document how roles change. Dependencies include data cleanup, time for staff participation and authority to resolve cross-department disputes. Proposed acceptance requires a named support owner, tested recovery and export, completed supplier disclosures and documented staff competence on agreed scenarios. Assess quality and net workload before expansion; these are suggested criteria rather than reported achievements. Risks include dependence on one enthusiastic employee, unbudgeted usage costs and a pilot that cannot be maintained after vendor onboarding ends."},"retrievedAt":"2026-09-09T03:01:08Z","enrichedAt":"2026-09-09T03:04:04Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Include frontline staff and labor representatives in workflow design; assess accessibility separately because this study establishes no inclusion effect.","procurementImplications":"Interpretation: Standardize disclosure questions and test competing tools on the same bounded service task.","operatingModelImplications":"Interpretation: Budget internal ownership, training and maintenance alongside supplier fees; collaboration does not remove local accountability.","updateExplanation":"New-to-archive original report, using one canonical PDF rather than its press release. Newly relevant U.S. context for the edition's planning dependencies; not presented as evidence released since the last run.","sourceVerification":{"openedUrl":"https://www.svlg.org/wp-content/uploads/2022/06/A-California-Strategy-to-Leverage-Artificial-Intelligence-to-Enhance-Public-Service-Delivery-in-Local-Government-and-Manage-Risks.pdf","referenceExcerpt":"agencies found that they often encountered barriers in receiving sufficiently detailed information on tools.","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}