Public accountability dossierSource-linked record · Updated as evidence becomes available
MOVING BEAUMONT FORWARDConnecting Today's Decisions to Tomorrow's Beaumont.
Police technology dossier · Systems, policy and accountability

Beaumont PD Technology

What technology Beaumont Police uses, what each system is designed to do, what Council authorized, how the systems are governed, and what the public record still does not establish.

Executive summary

One accountable record for Beaumont PD technology

Four verified systems · additional systems under review

The verified record currently identifies four major technology areas: Flock fixed automated license plate readers, Axon body-worn cameras and digital-evidence services, a Flock Drone-as-First-Responder program, and the Peregrine investigative and analytics platform.

Each system has a different purpose and risk profile. Fixed ALPR cameras capture vehicle and plate information; body-worn cameras create officer-perspective recordings and feed a digital-evidence workflow; drones are intended to provide remote aerial response; and Peregrine connects investigative searches and analytics across departmental data sources.

Council authorization and vendor descriptions establish approved capabilities and contract ceilings—not current deployment, policy compliance, accuracy, effectiveness, or public-safety outcomes. Those distinctions remain explicit throughout this dossier.

Evidence rule: Meeting transcripts remain internal research inputs used to verify actions and locate timestamps. Public source links in this dossier lead only to videos and documents.
Detailed technology records

Decisions, capabilities, costs and evidence

Briefing-card format · source-linked

ALPRFlock automated license plate readers
Council actionApproved citywide right-of-way authority in 2023 and a two-year subscription for 36 additional cameras in 2024.
Latest actionApproved 5–0
Authorization$225,900 / two years

Verified history: A 2023 staff report says Beaumont first entered a Flock data-sharing arrangement on July 29, 2020 for equipment in public right-of-way within the Sundance HOA. Council approved a ten-year citywide encroachment agreement on May 2, 2023. On August 20, 2024, staff reported 11 operating cameras and requested 36 additions at entrances, exits, crime-associated areas, and other strategic locations.

Key points
  • Eleven existing cameras plus 36 authorized additions implies 47, but the reviewed record does not confirm that every unit was installed or remains active.
  • Staff described searches and alerts involving suspect vehicles, burglaries, and stolen vehicles.
  • The cameras photograph vehicles and plates; staff said they were not used to cite an unidentified driver for traffic conduct.
  • The 2023 encroachment agreement authorized placement in public rights-of-way but did not establish the final installed inventory.
Data, policy and oversight
  • The live Flock transparency portal reports a 30-day retention period.
  • Beaumont Police Policy 465 says ALPR data downloaded to the server should be stored for a minimum of one year.
  • Policy 465 addresses authorized use, individual accounts, logging, audits, sharing requests, retention, and public release.
  • No published access-log audit, sharing register, error-rate report, complaint findings, or complete current inventory has been added.
Fiscal record

The verified 2024 ceiling is $225,900 for a two-year subscription covering 36 additional cameras. The original Sundance cost, cost of the 11 earlier cameras, invoices, actual expenditures, installation count, and successor or renewal agreement remain unverified.

What to watch
  • Reconciliation of the 30-day portal disclosure and one-year policy language.
  • Current camera locations, operational status, users, outside recipients, and direct network sharing.
  • Alerts, false alerts, useful leads, recoveries, arrests, complaints, misuse findings, and cost per useful outcome.

Supporting documents and video

Full meeting transcripts are retained internally for verification and timestamp work; they are not public source links.

BWCAxon body-worn cameras and evidence services
Council actionApproved a five-year, $1,005,901.89 service agreement with Axon Enterprises and authorized the City Manager to execute it.
ActionApproved 5–0
Authorization$1,005,901.89 / five years

Verified history: Council considered the five-year Axon technology agreement on December 2, 2025 as Agenda Item J.4. Staff reported that the existing Wrap Technologies contract would expire in June 2026 and that the department tested Axon, Wrap, and Motorola systems between August and October 2025. The presentation framed the action as a combined camera, evidence-management, and software-services decision rather than a camera-only purchase.

Included capabilities
  • Body-worn cameras with hardware upgrades every 2.5 years, as represented in the staff report.
  • Evidence.com digital evidence management, which staff said the Riverside County District Attorney would require for criminal filings beginning in 2026.
  • AI-assisted report drafts, automated transcription, translation in more than 100 languages, and redaction assistance.
  • Axon Standards personnel-investigation and performance-data tools.
  • Officers remain responsible for reviewing generated reports for accuracy.
Fiscal record

The staff report states a total five-year authorization of $1,005,901.89: $9,352.35 in year one from the Supplemental Law Enforcement Service Account, followed by $199,309.91 annually in years 2026–2030 from the General Fund. Staff projected approximately $20,000 in annual outside-transcription savings. These are authorization and forecast figures; invoices and actual expenditures remain unverified.

Published policy controls
  • Policy 450 says officers should activate before specified enforcement and investigative contacts when safe and practical, then continue through completion of the event.
  • Officers are directed to test cameras before service and upload files through a docking station at least daily.
  • System access is described as logged, auditable, and limited by right-to-know and need-to-know; supervisors may not search recordings solely for unrelated violations without the Chief's consent.
  • The Support Services Lieutenant is designated as BWC Administrator with responsibilities for users, training, system evaluation, policy review, security, retention, and release.

Version boundary: the currently linked manual is dated September 12, 2023 and still identifies Intrinsec Storage. It predates the Axon/Evidence.com authorization and does not establish the controls currently configured in Axon.

Policy and accountability questions
  • Has Policy 450 been revised for Axon, Evidence.com, AI-assisted report drafting, translation, and redaction?
  • What exact retention schedule applies to each recording category and generated text product?
  • How are automated transcripts, translations, report drafts, and redactions tested for accuracy and corrected?
  • What do access audits, activation reviews, complaints, public-record requests, prosecutions, and case outcomes show?
Records still needed

Executed agreement and quote, current Axon-specific policy, deployed inventory, retention schedule, access and audit reports, complaint findings, AI and redaction performance, invoices, equipment-loss records, and measures of evidentiary value.

Supporting documents and policy

December 2, 2025 · Agenda Item J.4 · Council action, five-year ceiling, funding schedule, and represented capabilities verified from the staff report and meeting record.

DFRDrone-as-First-Responder program
Council actionApproved a separate three-year, $900,000 agreement with Flock Safety for a Drone-as-First-Responder program.
ActionApproved 5–0
Authorization$900,000 / three years

Verified history: Council approved the program on April 7, 2026 as Agenda Item J.9. The staff report says Beaumont's patrol-car-based UAS program began in 2017 and distinguishes it from the fixed-dock first-responder model. Although Flock also supplies fixed ALPR cameras, the drone program is a separate operational system with distinct contracts, deployment decisions, privacy effects, records, and performance measures.

What the authorization establishes
  • The three-year agreement covers four Flock Aerodrome systems, docking stations, radar integration, software, training, implementation support, maintenance, and a mid-contract equipment refresh.
  • The proposed docking locations were the City Hall and Fire Station 106 roofs.
  • The staff report says flight logs would be automatically recorded and redacted flight data posted on the Police Department website.
  • Approval does not by itself prove the launch date, current coverage, installed inventory, flight volume, public-log publication, or response outcomes.
Published UAS policy and prior inventory
  • Policy 612 requires constitutional, privacy, and FAA compliance; written deployment authorization; trained operators; mission documentation; maintenance records; evidence integrity; and retention under the City's schedule.
  • It prohibits random surveillance, targeting based solely on protected or perceived characteristics, harassment, discrimination, personal use, and weaponization.
  • The March 2025 specialized-equipment report listed four DJI Mavic 3 drones costing $20,154.84 and two DJI Matrice 300 drones costing $30,398, all funded through SLESA, with estimated annual maintenance of $2,548.
  • That six-aircraft inventory predates the four-system Flock DFR authorization and does not establish which earlier aircraft remain active or how the two programs now relate.

Version boundary: the published manual is dated September 12, 2023. It governs UAS generally but predates autonomous fixed-dock response, radar integration, remote piloting, and the promised public flight-log workflow.

Operations and privacy questions
  • Which calls qualify for launch, who pilots or supervises flights, and when can personnel view a live feed?
  • Were both proposed docking sites installed, and what are the actual coverage and exclusion areas?
  • What FAA authority, airspace restrictions, weather limits, safety reporting, and incident procedures apply?
  • What video, telemetry, flight-log, and dispatch data is retained, searched, shared, redacted, or released?
  • Has Policy 612 been revised specifically for autonomous dispatch, remote piloting, radar, and DFR operations?
Fiscal and staffing record

The schedule is $200,000 in year one and $350,000 in each of years two and three. Staff also estimated $24,000 for electrical and Ethernet work and $10,000 for a pilot workstation. The report proposed replacing one vacant Police Sergeant position, costed at $336,695 annually, with three Community Service Officers costed at $293,445, projecting $43,250 in annual salary savings. These are authorization and proposal figures, not verified expenditures, installations, hires, or savings.

Records still needed

Current DFR-specific policy, executed contract and exhibits, deployment and acceptance records, installed aircraft and dock inventory, FAA approvals, published flight logs, call categories, live-access rules, retention and sharing policy, infrastructure invoices, staffing actions, incident reports, complaints, maintenance records, and verified outcomes.

Supporting documents and policy

April 7, 2026 · Agenda Item J.9 · Council action, contract schedule, proposed sites, staffing plan, and discussion segment verified from the staff report and meeting record.

DATAPeregrine investigative platform
Council actionApproved a three-year, $204,000 Peregrine agreement after removing the item from consent for public discussion.
ActionApproved 5–0
Authorization$204,000 / three years

Verified history: Council considered the Police Department Peregrine software agreement on August 4, 2026 as Agenda Item G.14. The item was pulled from consent for discussion. Police Chief Comeau described a platform consolidating searches across approximately twelve law-enforcement databases, providing automated crime analytics, and supporting a future Drone-as-First-Responder workflow.

Verified scope and represented capabilities
  • The order form names Sun Ridge RIMS CAD and RMS, legacy Mark43 CAD and RMS, and Axon body-worn-camera and Evidence.com data as initial integrations.
  • The annual subscription includes unlimited department users, implementation, configuration, initial integrations, data modeling and cleansing, onboarding, introductory training, and web and mobile access.
  • Represented tools include search, mapping, link and network analysis, reporting, dashboards, and CJIS-compliant file storage and sharing.
  • The staff package represents role-based access, single sign-on, multifactor authentication, City ownership and standard-format export of customer data, and granular sharing permissions.
  • Technology-related efficiency and future staffing claims were discussed, but have not yet been independently measured.
Contract chronology requiring explanation

The agenda package contains an order form signed by the City Manager on May 28, 2026 with a June 1, 2026 effective date, while Council considered and approved the agreement on August 4, 2026. The public record reviewed here does not explain the authority or sequence behind those dates. The staff report says the first-year amount was already included in the FY 2025–26 budget, but budget inclusion is not necessarily the same as contract-execution authority.

Data-governance questions
  • Which fields are connected, and which records are excluded from each named source system?
  • What user roles, query justifications, approval controls, audit logs, alerts, and prohibited uses apply?
  • Which vendor personnel or outside agencies can access Beaumont data, and when is authorized sharing configured?
  • How are inaccurate, stale, duplicated, or misidentified records corrected before investigative use?
  • What usage analytics are retained by the vendor, and how are they separated from customer data?
Fiscal and outcome record

The initial term runs from June 1, 2026 through June 30, 2029 at $68,000 annually, totaling $204,000. Implementation, configuration, named initial integrations, onboarding, and introductory training are included; additional integrations or services may require a separate written scope and fees. Invoices and actual payments remain unverified, and authorization does not prove time saved, crimes cleared, errors prevented, or staff positions avoided.

Records still needed

Explanation and authority for the pre-approval signature and effective date; production data map; permissions; query and audit logs; retention and sharing rules; prohibited-use rules; accuracy controls; complaints; investigations; invoices; training records; additional-service charges; and measurable outcomes.

Supporting documents

August 4, 2026 · Agenda Item G.14 · Agreement scope, price, dates, and Council outcome verified from the agenda package and meeting record.

Cross-technology accountability

Questions every system must answer

01

What is deployed today?

What hardware, software, licenses, integrations, launch sites, accounts, and vendor services are active—and which authorizations were never fully implemented?

02

What data enters and leaves?

What each system collects, generates, imports, retains, exports, shares, or deletes; which policy controls each copy; and whether actual practice matches the rule.

03

Who can use it?

Which Beaumont users, supervisors, vendors, prosecutors, and outside agencies have access, and what approvals, training, justifications, and audit logs apply?

04

Is it accurate and effective?

What verified measures show useful leads, faster response, evidence value, errors, false alerts, unnecessary deployments, complaints, misuse, or no operational benefit?

05

What does it actually cost?

What Council authorized, what the City contracted for, what was invoiced and paid, what staff and infrastructure add, and what future renewals or replacements require.

06

How is the public protected?

What policies, warrants or legal process, prohibited uses, release rules, audits, complaint procedures, discipline, security controls, and public reporting create accountability?

Verified timeline

How Beaumont's police technology record developed

Authorization dates—not assumed deployment dates

Sundance arrangement

A 2023 City staff report says the City entered a Flock data-sharing agreement limited to public right-of-way within the Sundance HOA. The original agreement and authorization record are not yet in this evidence set.

ALPR use publicly acknowledged

The Police Department listed automated license plate readers among technologies used to improve efficiency and public safety.

Installation authority expands citywide

Council approved a ten-year encroachment agreement allowing Flock equipment in public rights-of-way throughout Beaumont. It passed with the consent calendar, 5–0, without substantive public discussion.

Official staff report →

Thirty-six-camera expansion approved

Staff reported 11 existing cameras and requested 36 additions at entrances, exits, and other strategic locations. Council approved the two-year, $225,900 subscription, 5–0.

Watch segment · 4:08:21–4:13:36 →

Five-year Axon ecosystem approved

Council approved body-worn cameras together with digital evidence management, transcription, translation, redaction assistance, equipment services, and related documentation tools.

3:06:16–3:18:30 →

Peregrine platform discussed and approved

Council removed the item from consent for discussion, then unanimously approved an investigative platform described as consolidating searches across approximately twelve databases and supporting analytics and future drone workflows.

1:13:54–1:17:50 →
Cost register

Known authorizations and financial gaps

Authorization is not expenditure

Flock fixed ALPR expansion$225,900

Two-year subscription authorized in 2024 for 36 additional cameras. Earlier costs, invoices, payments, and renewal remain incomplete.

Axon body-camera ecosystem$1,005,901.89

Five-year authorization: $9,352.35 in year one and $199,309.91 annually thereafter. Executed pricing, invoices, actual expenditures, and realized savings remain unverified.

Flock drone program$900,000

Three-year schedule of $200,000, $350,000, and $350,000, plus estimated $34,000 in infrastructure and workstation costs. Actual expenditures and staffing savings remain unverified.

Peregrine platform$204,000

Initial term through June 30, 2029 at $68,000 annually. Named initial integrations and onboarding are included; invoices, payments, and additional-service charges remain unverified.

Financial standard: Every dossier distinguishes Council authorization, executed contract value, invoice, payment, total operating cost, and renewal exposure. These figures are not interchangeable.
Council actions

What Beaumont authorized

DateTechnology actionVoteEffect and limit
July 29, 2020Sundance Flock data-sharing arrangementApproval record not locatedLater staff report describes limited right-of-way access; the original agreement and authority remain unverified.
May 2, 2023Ten-year citywide Flock encroachment agreement5–0, consentAuthorized placement in public rights-of-way; did not establish how many cameras were ultimately installed.
August 20, 2024Flock subscription for 36 additional cameras5–0Authorized $225,900 over two years; staff reported 11 existing cameras.
December 2, 2025Five-year Axon technology agreement5–0Authorized body cameras and associated evidence, transcription, translation, redaction, equipment, and documentation services.
April 7, 2026Flock Drone-as-First-Responder agreement5–0Authorized a separate three-year, $900,000 aerial-response program; approval does not prove deployment or results.
August 4, 2026Peregrine investigative software agreement5–0Approved after discussion; represented capabilities include cross-database search, analytics, and future drone-workflow support.
Documents and video evidence

Records supporting the dossier

Primary sources first

FLC-001 · Policy

Beaumont Police Policy 465

Published rules for collection, searches, training, access logging, audits, sharing, retention, and release.

Official City ALPR page ↗
FLC-002 · Current disclosure

Flock transparency portal

Vendor-hosted disclosure of the department's 30-day retention period, rolling usage statistics, and network-sharing information.

Open transparency portal ↗
FLC-003 · Staff report

Sundance history and citywide agreement

The 2023 staff report describes the 2020 Sundance arrangement and the requested ten-year citywide encroachment authority.

Open staff report in viewer →
FLC-004 · Staff report

May 2, 2023 meeting

Official staff report for the citywide public-right-of-way agreement.

Official staff report →
AXN-001 · Council record

December 2, 2025 Axon authorization

Staff report and bounded Council discussion supporting the five-year, $1,005,901.89 authorization and represented camera, evidence, and AI-assisted services.

Official staff report → · Video · 3:06:16–3:18:30 →
PER-001 · Agreement and Council record

August 4, 2026 Peregrine authorization

Agenda package, signed order form, and bounded Council discussion supporting the $204,000 initial term, named integrations, and unresolved signature chronology.

Verified meeting record → · Video · 1:13:54–1:17:50 →
POL-450 · Published policy

Body-worn-camera controls

The September 2023 manual addresses activation, uploads, access logging, review, release, administrator duties, and training, but still names the pre-Axon storage system.

Policy 450 · PDF ↗
POL-612 · Published policy

Unmanned aerial systems

The September 2023 manual establishes general privacy, authorization, training, documentation, maintenance, retention, and prohibited-use controls; DFR-specific revision remains unverified.

Policy 612 · PDF ↗
UAS-2025 · Annual inventory

Pre-DFR drone inventory

The March 2025 report lists four DJI Mavic 3 and two DJI Matrice 300 aircraft, their acquisition costs, authorized uses, training requirements, and estimated maintenance.

2025 specialized-equipment report · PDF ↗
Analysis

What the record means—and does not mean

Verified conflict

Two published retention descriptions need reconciliation

The Flock portal reports 30 days. Policy 465 says ALPR data downloaded to the server should be retained for at least one year. Both can be accurately reported, but neither explains whether there is a separate City copy, whether the policy is outdated, or how evidentiary exports are handled.

Chronology question

The Peregrine order form predates Council approval

The agenda package includes a City Manager signature dated May 28 and a June 1 effective date; Council approval occurred August 4. The reviewed record does not explain the authority or sequence. A budgeted first-year payment does not, by itself, resolve whether separate execution authority existed.

Inference

Forty-seven cameras is an implied—not confirmed—network size

Eleven reported existing cameras plus 36 approved additions equals 47. That arithmetic does not prove all approved units were installed, activated, or remain operational. A current inventory is needed.

Evidence gap

Policy requirements are not proof of compliance

The policy calls for individual logins, access records, regular audits, and reviewed sharing requests. Without logs, audit reports, sharing approvals, and complaint outcomes, the public cannot independently evaluate actual compliance.

Evidence gap

Anecdotes do not establish system-wide effectiveness

Police staff described examples involving burglaries, suspect vehicles, and stolen vehicles. Aggregate counts for alerts, false alerts, leads, recoveries, arrests, complaints, and cost per useful outcome have not been found in the reviewed record.

Frequently asked questions

Direct answers from the current record

What do the cameras collect?

Fixed cameras photograph passing vehicles and license plates. The resulting records can be searched by plate and reported vehicle characteristics and can generate alerts involving identified vehicles.

Are the cameras used to issue traffic tickets?

At the August 20, 2024 meeting, police staff said the cameras could not be used to cite drivers for conduct such as running stop signs because the image does not establish who was driving. That statement describes the represented practice at that meeting; it is not a binding restriction in the published ALPR policy.

Where are the cameras?

Staff said the additions were planned around entrances and exits, areas associated with crime, and other strategic locations. The reviewed record does not contain a complete, current, authoritative location and installation list.

Does an authorized search require reasonable suspicion or probable cause?

Policy 465 says reasonable suspicion or probable cause is not required before an authorized user searches ALPR data. The legal process required in a particular investigation depends on its facts and applicable law; the public record does not show how often warrants or subpoenas are used.

Can other agencies receive Beaumont data?

The policy allows sharing with law-enforcement and prosecutorial agencies for official purposes after a written request reviewed by the Administration Division Commander or designee. The reviewed source set does not contain the underlying recipient list, requests, approvals, or a complete description of direct network access.

Has the system been audited?

The policy says audits should occur regularly. The reviewed public record does not include published ALPR audit reports, access-log reviews, error-rate reporting, complaint findings, or disciplinary outcomes.

How effective is the system?

Officials have described successful examples, but the available public record does not provide enough aggregate data to calculate useful leads, arrests, recoveries, false alerts, or cost per successful outcome.

Primary sources

Public source register

Videos and documents only

  1. Beaumont Police Department, Policy 465: Official ALPR policy website ↗
  2. Flock Safety: Department transparency portal ↗ (live disclosure; values may change)
  3. City staff report: Flock encroachment staff report →, May 2, 2023
  4. Flock camera expansion: August 20, 2024 staff report · PDF → and bounded video segment →
  5. Body-worn cameras: December 2, 2025 staff report · PDF → and bounded video segment →
  6. Drone program: April 7, 2026 staff report · PDF → and bounded video segment →
  7. Peregrine platform: August 4, 2026 verified meeting record and documents → and bounded video segment →
Research completion

What remains to complete the public record

The decision history, known capabilities, Council actions, contract schedules, initial cost record, published BWC and UAS controls, prior drone inventory, oversight framework, and supporting public sources are now built. The remaining work depends primarily on current system-specific policies, audits, invoices, operational datasets, and implementation records not yet present in the repository.

75% research complete
  • All systemsCurrent inventories, invoices, renewal terms, current policies, user roles, retention, sharing, access logs, audits, complaints, and verified outcomes.
  • Flock ALPRThe 2020 agreement, retention reconciliation, installation status, sharing records, audits, and aggregate effectiveness data.
  • Body camerasExecuted agreement and quote, deployed inventory, an Axon-specific policy revision, exact retention schedule, AI and redaction performance, audits, complaints, invoices, and evidentiary outcomes.
  • DronesExecuted exhibits, installed docks and aircraft, FAA authority, a DFR-specific policy revision, published flight logs, live access, retention, staffing actions, incidents, complaints, invoices, and response outcomes.
  • PeregrineExplanation of the signature chronology, production data map, permissions, query logs, prohibited uses, accuracy controls, audits, complaints, invoices, and investigative outcomes.
  • InventoryIdentify and verify any other Beaumont PD operational technologies before declaring the dossier comprehensive.
  • Ongoing reviewClaim-by-claim verification and editorial review as new records become available.