What should a chief or sheriff audit before expanding emerging technology?

Start with eight areas: inventory, mission, authority, people, policy, data, vendor accountability, and evaluation. The goal is not to stop innovation. It is to make sure the organization can explain what the technology does, govern how it is used, support the people responsible for it, and respond when evidence or conditions change.

1. Inventory the technology already in use

Leaders need a current view of systems, features, pilots, integrations, data flows, and informal tools used across the organization. AI-enabled functions may appear inside products purchased for another purpose. An inventory should identify the business owner, technical owner, users, data touched, vendor, contract status, and whether the use has been formally approved.

2. Define the mission and boundaries

Each capability should have a clear operational purpose. What task or decision does it support? What may it recommend, generate, detect, prioritize, or automate? What is it prohibited from doing? Who owns the final decision? Boundaries should be understandable to users, supervisors, executives, counsel, and the public.

3. Map authority and decision ownership

Technology governance fails when everyone participates but no one owns the decision. Clarify the roles of the chief or sheriff, governing authority, command staff, legal counsel, IT, cybersecurity, records, procurement, labor, risk, communications, and end users. Higher-impact uses may require a more formal review and approval path.

4. Audit people, workflow, and training

A system is not ready merely because it works in a demonstration. Leaders should understand how it changes dispatch, field work, supervision, reports, evidence, records, maintenance, after-hours support, and critical-incident response. Training should cover purpose, limits, prohibited uses, documentation, supervision, error reporting, and escalation—not only button clicks.

5. Review policy against actual practice

Written policy should match authority, current system features, real workflows, records obligations, access controls, supervisory practice, and public commitments. Audit logs, complaints, quality assurance, corrective action, and periodic review should be part of the operating model. If practice has moved beyond policy, that gap deserves executive attention.

6. Follow the data

Identify what data enters the system, what the system creates, where information is stored, who can access it, how long it is retained, whether vendors or subcontractors may use it, and how records requests, evidence, deletion, breach response, and system exit will be handled. Privacy, security, civil-rights, and public-records questions should be addressed according to the use and jurisdiction.

7. Test vendor accountability and continuity

Contracts and operating plans should address performance, support, updates, security, auditability, data ownership, subcontractors, material feature changes, service interruption, export, and termination. The agency should also understand what happens if a key integration fails, the vendor changes direction, or the product no longer fits the mission.

8. Define evaluation and stop conditions

Decide in advance what evidence will show whether the capability is useful, safe, reliable, and worth sustaining. Measures should match the approved purpose and include user feedback, errors, policy compliance, workload, complaints, availability, unintended effects, and vendor changes. Establish who reviews the evidence and what would trigger modification, restriction, suspension, or retirement.

When is outside advisory support useful?

An experienced outside advisor can help when the decision crosses multiple functions, the command team needs a shared framework, a current-state assessment must be independent, or implementation has outpaced governance. The advisor should help the agency clarify decisions and ownership while preserving the authority of agency leadership and the roles of qualified legal, labor, procurement, technical, aviation, and regulatory specialists.

By Darrell Lowe, Founder, The Lowe Group.AI, LLC