From the Public Safety edition of October 12, 2026
San Diego police union president opposes AI report software for now, citing unfunded existing technology
San Diego Police Officers Association (reported by Voice of San Diego) · Policing / technology funding and labor · San Diego, California, United States
- Publisher
- Voice of San Diego
- Original publication
- Oct. 12, 2026
- Source retrieved
- 2026-10-13
- Event date
- 2026-10-12
What happened
SDPD says it has no timeline to acquire AI report-writing software. Union president Jared Wilson is not opposed to the technology in principle but objects to buying it while the city has not found sustainable funding for existing technology, citing cuts, hiring freezes and eliminated positions, and warns that agencies become dependent on vendor tools that are hard to drop.
Why it matters
Labor opposition here rests on total cost and dependency, not accuracy, adding a sustainment test to AI policing procurements alongside civil-liberties objections.
Evidence and measured results
Opened original source from Voice of San Diego and drew findings from its text. One interview with a labor leader; budget claims are not documented with figures, and no data on existing technology costs are given.
Limitations and uncertainty
Opinion of one stakeholder; city budget figures were not reported.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-13; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- The city wants efficiency from AI but the officers' union says existing technology is already unfunded.
- Stakeholders
- San Diego Police Officers Association
- SDPD command staff
- City budget office
- City Council
- Discovery questions
- What does the current police technology stack cost to sustain each year?
- Which existing tools are underfunded?
- What would the union need to see before supporting a pilot?
- What are the exit costs of current vendor contracts?
- Value hypothesis
- A sustainment and total-cost review could clarify whether new AI tools are affordable without cutting existing capability; no savings are implied.
- Potential engagement
- Police technology portfolio and total-cost-of-ownership review with labor participation.
- Unsupported claims
- Officer support for AI reports
- Budget capacity for new subscriptions
- Any efficiency gain
Pre-sales engineering
Role takeaway
- Fit
- Departments adding subscriptions on top of an existing vendor ecosystem under budget pressure.
- Architecture and integration
- Assess exportability of reports, metadata and evidence from current platforms and dependencies between add-on modules.
- Prerequisites
- Current contract inventory
- Data export terms
- Integration map of existing tools
- Constraints
- City budget cycle
- Collective bargaining obligations
- Existing vendor contract terms
- Security
- Exit planning must preserve chain of custody and access controls when moving or archiving data.
- Proof of value
- Test a full data export from the current platform
- Price five-year subscription costs including add-ons
- Document manual fallback for report writing
Delivery
Role takeaway
- Work
- Build a funded sustainment plan and labor-inclusive pilot charter before any AI acquisition.
- Dependencies
- Budget office cost data
- Union participation
- Vendor pricing disclosure
- Ownership
- SDPD administration with the city budget office
- Skills and adoption
- Supervisors and officers need a say in workflow changes and training time built into schedules.
- Governance checkpoints
- Total-cost review presented to council
- Labor consultation
- Pilot charter approval
- Annual sustainment review
- Acceptance criteria
- Proposed: multi-year cost funded in the adopted budget
- Proposed: union consulted on pilot design
- Proposed: tested data export and fallback plan
- Risks
- Labor opposition
- Budget shortfall
- Vendor dependency
- Displacement of community policing time
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?
Assess exportability of reports, metadata and evidence from current platforms and dependencies between add-on modules.
Governance
Who approves, reviews and stays accountable for outcomes?
Build a funded sustainment plan and labor-inclusive pilot charter before any AI acquisition.
Security and privacy
What data, permissions and controls need testing?
Exit planning must preserve chain of custody and access controls when moving or archiving data.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Supervisors and officers need a say in workflow changes and training time built into schedules.
Procurement
What should contracts, pricing and exit terms secure?
Police technology portfolio and total-cost-of-ownership review with labor participation.
Operating model
Which teams own the service once it runs?
Operational owner: SDPD administration with the city budget office.
Publication history
- 2026-10-12Public Safety · Issue 354 resources
Stable resource ID: san-diego-police-union-opposes-ai-reports-budget-20261012