From the Public Safety edition of November 10, 2026
Independent audit of Seattle’s real-time crime center finds useful guardrails but urges binding policy, shorter retention, case-number logging and AI-feature logging
Policing Project at NYU School of Law; City of Seattle and Seattle Police Department · Policing / real-time crime centers, cameras and AI tools · Seattle, Washington, United States
- Publisher
- Policing Project (via Seattle City Council)
- Original publication
- Policing Project audit PDF posted on Seattle City Council site, November 2026
- Source retrieved
- 2026-11-11
What happened
The Policing Project, retained by the Mayor’s Office in May 2026, reviewed Seattle’s real-time crime center (RTCC) through documents, site visits in May and September 2026 and interviews. It finds clear rules against personal use and immigration or certain health care investigations, but gaps in data governance. It recommends that SPD require Axon to add a case number or reason for any camera activation and to log any use of object detection or other AI features, set up formal internal audits, and put the five-day raw footage retention practice into policy (policy allows 30 days). It also says case-file data is kept indefinitely and should not be. It states many guardrails exist only as informal practice and should become binding written policy, and that tracking people across cameras should generally need a warrant.
Why it matters
Gives a concrete, independent control checklist for AI-enabled camera and crime-center platforms that integrators and vendors can map to their own products and to buyer reviews.
Evidence and measured results
Independent audit with site visits and interviews; the authors retained editorial control after the city reviewed a draft for factual accuracy. No outcome or accuracy data on AI features.
Limitations and uncertainty
Report reviews governance only and does not assess effectiveness or whether the center should continue; findings apply to Seattle; recommendations are not binding.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Cities face public and council pressure over crime center cameras, AI features and data retention, and many guardrails exist only as informal practice.
- Stakeholders
- Police chief
- City council
- Mayor’s office
- Inspector general
- Privacy advocates
- Discovery questions
- Which guardrails are written policy versus habit?
- Can the platform log AI feature use?
- How long is footage and case-file data kept?
- Value hypothesis
- A control gap review against an independent audit can speed council and oversight review; no crime or cost outcomes are claimed.
- Potential engagement
- Crime center governance gap review with a written policy backlog.
- Unsupported claims
- That the controls reduce crime
- That AI features are accurate
- That a warrant rule is required everywhere
Pre-sales engineering
Role takeaway
- Fit
- Audit logging, AI feature logging and retention controls for camera and crime center platforms; not an accuracy evaluation.
- Architecture and integration
- Tie activation logs to case numbers and route AI feature logs and retention settings to an audit report.
- Prerequisites
- Vendor log export
- Case number or reason field at activation
- Configurable retention by data type
- Constraints
- Vendor must build missing features
- Private camera feeds with limited retention control
- Seattle-specific findings
- Security
- Restrict access, log every activation and AI use, and shorten retention to limit exposure to subpoenas and breaches.
- Proof of value
- Share of activations with case number or reason
- AI feature use logged and reviewable
- Retention periods enforced in system
Delivery
Role takeaway
- Work
- Assess current practice against the audit list and draft written policy, audit schedule and retention periods.
- Dependencies
- Vendor feature roadmap
- Agency counsel
- Oversight body review
- Ownership
- Police administration with an internal audit owner.
- Skills and adoption
- Train analysts to decline requests whose purpose cannot be confirmed and to log each decision.
- Governance checkpoints
- Policy review with oversight body
- Annual audit
- Public tool list updates
- Acceptance criteria
- Written policy for each informal guardrail
- Internal audit schedule adopted
- Retention periods codified
- Risks
- Vendor features arrive late
- Policies remain informal
- Council disputes warrant standard
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?
Audit logging that forces a case number or reason, logging of AI feature use, and configurable retention are the technical requirements named; vendor feature gaps are called out.
Governance
Who approves, reviews and stays accountable for outcomes?
Binding written policy, regular internal audits, codified retention and warrant expectations for tracking across cameras are recommended.
Security and privacy
What data, permissions and controls need testing?
Retained data can be reached by breaches, public records requests and subpoenas, so the audit treats collection and retention as the key boundary.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Audit asks for formal internal audits and trained analysts who decline unverifiable requests; staffing needs are not quantified.
Procurement
What should contracts, pricing and exit terms secure?
Report urges requiring vendor features (case number, AI logging) and says tools in use should be disclosed; contract terms are not detailed.
Operating model
Which teams own the service once it runs?
Shows a crime center moving from informal practice to written rules, audits and public disclosure.
Publication history
- 2026-11-10Public Safety · Issue 654 resources
Stable resource ID: seattle-rtcc-policing-project-governance-audit-20261110