CollectionFlock Surveillance Collection

Contract and Board Approval

What the Board packet and executed Flock agreement establish about approval, cost, term, and procurement.

Verified from public record
Amador Transparency Project, “Contract and Board Approval,” Flock Surveillance Collection, updated August 10, 2026.

July–August 2026 deployment update

The expanded July production adds pre-contract sales, MOU, mapping, funding, policy, and deployment records. An email newly produced August 10 says that two locations were still left to install on July 27, 2026 and describes a right-of-way permitting issue.

Transcript update

February 2025 consent-calendar process now documented

The newly archived meeting transcript shows a public-comment period expressly limited to non-agenda matters, followed by agenda approval and the immediate 5–0 consent-calendar vote. No separate consent-item comment invitation appears in the transcript. At the August 11, 2026 meeting, Chairman Patrick Crew later said the Board probably should not have had the program on consent. This raises a public-comment compliance question but is not presented as a final legal conclusion.

Read the Board meeting/process review

Executive summary

The Board of Supervisors agenda item for February 25, 2025 recommended approval of a contract with Flock Safety and authorization for Captain Jeremy Martin and county officials to negotiate final terms. The packet is marked “Approved Unanimous.”

Public record Board agenda item report

Page 1 identifies the meeting date, recommendation, and approval notation.

Open source record

Contract dates and term

The order form lists a 24-month initial term and 24-month renewal terms. The county signature is dated March 3, 2025; Flock’s signature is dated March 5; and the approval-as-to-form line is dated March 7.

Public record Executed contract signatures

Contract page 5 contains signatures and dates.

Open source record

Pricing

LineAmountRecord language
Subtotal, Year 1$45,500Includes professional-services implementation charges.
Annual recurring subtotal$40,000Listed on the order form and billing schedule.
Estimated tax$0As shown on the order form.
Contract total$85,500Stated total for the 24-month initial term.

Procurement method

The Board packet includes an exception-to-competitive-bid disclosure. The form marks “Sole Source” and identifies an estimated total cost of $85,500. The justification cites Flock’s integrated platform, transparency portal, camera system, vehicle-fingerprint features, and partnerships.

Public record Sole-source disclosure

Pages 10–11 contain the exception request and justification.

Open source record

Equipment and services

The February 2025 Sheriff’s Office proposal described a quote for eight cameras. Later deployment records in the July 2026 production refer to a ten-location project, while the installation sheet contains eight dated entries. The July 27 email newly produced in August helps explain that difference by stating that two locations were still left to install at that time.

The later email does not identify those two sites or establish their eventual installation status. The archive therefore distinguishes the Board-era eight-camera proposal from the later ten-location deployment record rather than treating the numbers as interchangeable.

Funding statement

The proposal says the first year would be fully funded through Sheriff’s Office grant funding and partnerships, with no impact to the general fund, and that future grant funding would be pursued.

Record limitation

The archive does not yet include invoices, purchase orders, grant award documents, or later renewal records. The contract amount therefore does not by itself establish the final amount paid from each funding source.

Revision history
  1. Added the later ten-location deployment context and the newly produced July 27 email stating that two locations remained to be installed.
  2. Standardized evidence labels and added print, permanent-link, citation, and revision-history tools.

View project-wide corrections and revision history.