Public records requests

City tracking 238-2025 · broad Flock request

Filed about October 16, 2025. Public Request: MuckRock Flock Request. The request sought Flock-related communications, contracts, procurement documents, hot-list names, agencies shared with or from, private-site agreements, and right-of-way installation permits, among other items.

The City issued a fee estimate of $81.87 (October 2025). After payment, document access was provided in November 2025. The production package on file in this archive includes:

• Resolution packets as produced: RES-0022-2023 and RES-0087-2025
• 2024-162 Flock OS 911 PDF
• ROW permit PDF (52399)
• Flock Safety correspondence PDF
• Exchange mailbox exports (Outlook .pst files). Not published on this site.

Resolutions for 2023 and October 2025 also appear in the City’s public council document systems and on this site’s Library page. That package is not the evaluation-category answer set under 211-2026 and does not include Organization or Network audit CSV exports of the kind requested under 166-2026.

Findings from the mailbox export

The production included multi-GB Exchange mailbox exports. Selected items from that publicly produced mail and its attachments:
Public request: MuckRock 238-2025 / 194981.

Pilot metrics intent (February 2023)

On February 6, 2023, early in the public pilot, Sgt. Brandon Claxton emailed patrol, detectives, and dispatch lists that the cameras were a pilot to be evaluated after a couple of months using officer feedback and analytics from Flock, prepared for Command Staff. He asked officers to email him when Flock solved a case or produced leads, and to mark in-product Apprehended or Not Apprehended so administrators could pull benefit reports.

Records retention discussion (March–April 2023)

Before the multi-year services contract, city mail under subject Flock Safety Contract and Records Retention opened the retention question. Deputy City Clerk / Records Manager Julia Porter cited schedule POL 011 and 30-day retention for police audio/video, recommended adding video disposition to monthly Council disposition lists, and asked to meet on process. Holly Grant (Records Unit / Custodian) wrote that Records does not handle audio/video retention but would attend so the unit could answer questions. Chief Bob Muenz named Capt. Rapp (and possibly Sgt. Claxton) as contacts and said scope was expected to include Flock plus facility/body/vehicle video.

Early sites vs multi-year scale

Mailbox planning files include a camera-location CSV for Blue Springs MO PD listing 24 named sites (intersection labels in planning materials). Local coverage in early 2023 also described a roughly two-dozen camera pilot. Post-pilot commercial quotes and Resolution 22-2023 order-form language run to about 51 Falcon-class units plus Flex gear and about $148,350 per year. Later portal and expansion figures are higher; do not mix source counts.

Library: Resolution 22-2023 · 2023 post-pilot quote · ROW permit 52399.

Success tracking brief (February 2024)

Among city email produced under this request is a vendor “Account Review” with the Police Department’s Flock liaison. The calendar agenda listed long-term goals, usage and adoption stats, and discuss success tracking. The follow-up message attached a Flock slide deck labeled for Blue Springs MO PD (title page dated February 20, 2024).

One slide in that deck describes an in-product outcome log and a CSV download of user-entered results, pitched to show council and the community return on the Flock partnership. Fields listed include case number, number of arrests, disposition, crimes, property recovered, approximate value, and notes.

Full deck: Account Review PDF (Library).

FlockOS 911 competitive bid waiver (September 2024)

The same production includes a City of Blue Springs Request for Competitive Bid Waiver for supplier Flock Group Inc.. The form is signed and finance-cleared September 25, 2024. City mail under subject FlockOS 911 AIF attaches that form with Flock’s sole-source letter and related contracting files.

On the form, checked reasons include items sold through the manufacturer only with “no other comparable unit available,” and “Other reason; sole source letter attached.” The written explanation is: “FlockOS 911 is a sole source product from Flock Group Inc.” For how the price was shown to be fair, the form checks Other and answers “See above.”

Library: bid-waiver form · Flock sole-source letter · related production 2024-162 Flock OS 911 packet.

Share surface (network notices, not audit exports)

The mailbox includes a large set of automated vendor notices that other agencies have shared Flock cameras with Blue Springs (about 100 unique agency names in the extract, many of them Missouri agencies). Names in production include Raymore, Gladstone, and county sheriffs’ offices, plus out-of-state agencies. Separate digests list pending share requests aiming at Blue Springs cameras with proposed Search and Hot List permissions that a local admin must accept or reject. In August 2025, vendor staff sent an education message on sharing, search, and audits (opt-in models and radius sharing examples). That is product education, not a settings export for this City.

Library: LEA · Free Form · 2023 quote · 2025 quote · DFR impact prep. Related Council path: Resolution 108-2025.

City tracking 166-2026 · Organization and Network audits

Filed about June 2, 2026. Public Request: MuckRock ALPR audit. The request sought Flock Insights Organization Audit and Network Audit data from January 1, 2025, forward (machine-readable if available), plus network-share settings.

On June 4, 2026, Custodian of Police Records Holly Grant closed the request with no fee. The letter states that the Police Department does not have any records responsive regarding Flock Safety; that Flock’s subscription is responsible for collection, storage, maintenance, and retention; that information that may be responsive can be accessed through the Flock transparency portal; and that records older than 30 days will not be available under Flock’s stated deletion policy.

On September 14, 2026, Chief Bob Muenz told KCTV5 the department runs bi-weekly audits reported to him. On September 16 he told KCTV5 the department does not need to change its policies after the Governor’s license-plate-reader order. The Police Department later posted on Facebook that it is already in compliance with those standards. This dock remains closed with no records responsive. City-held findings from those reviews, and the search logs that order describes, are not in this production. Press kit.

City tracking 211-2026 · evaluation, outcomes, and policies

Three online Public Records Request forms (about July 9–10, 2026) were acknowledged together under tracking number 211-2026 and routed to Police Administration. Substantive answer from Custodian of Police Records Holly Grant, August 4, 2026. Closed with no fee assessed. Category tables below summarize that City answer. Empty categories use the City’s wording: No Preexisting documents.

Materials presented to or relied on by Council (2025 and later)

Performance and use (2023 to present)

Policies and governance

City tracking 248-2026 · expansion emails (open)

Filed August 4, 2026 (separate online form from the 211-2026 set). Seeks emails and related records discussing a recommendation to expand the Flock agreement during 2025, including Resolution 87-2025 (October expansion) and Resolution 108-2025 (December Safe City path).

On August 6, 2026 the City Clerk issued a fee estimate of $109.47. The letter’s original IT keyword set was brand-name searches for Flock Safety. It invited confirmation or alternatives and described a production target around August 21, 2026 if payment arrived promptly.

Later that day the requester replied before payment: keep the purpose but sharpen keywords to Safe City, the 2025 resolution identifiers, Freeform, DFR, RTCC, and Flock paired with expansion or approval language, so hits favor decision mail over every vendor brand mention. A revised fee estimate and timeline were requested.

On August 7, 2026 the Clerk accepted those search terms, said IT estimated staff time cut in half, and issued a revised fee of $54.74. The August 21 close-of-business target stayed the same. No payment confirmation or production packet is on file yet.

Council agendas, minutes, resolutions, and ordinances remain available in the City’s document systems. Mirrored copies (Google Drive): Library. Live hubs: eCode360 Blue Springs and Agenda Center.

Flock transparency portal (where City answers pointed)

Under tracking number 211-2026, several policy topics were answered by linking a site run by Flock Safety. Under tracking number 166-2026, the close letter also pointed to that portal. Live page: transparency.flocksafety.com/blue-springs-mo-pd. Numbers below are from a browser capture of that page on August 27, 2026 (rolling 30-day windows).

On the police department site, the menu item “Flock Safety” also opens this same portal: www.bluespringsgov.com/2704/Flock-Safety. If these activity metrics and Success Stories are treated as the only concrete wins on file, see Outcomes. Retention context and Supreme Court location-privacy cases: Location privacy.

Location privacy (Carpenter & Chatrie)

Carpenter and Chatrie are phone-location holdings. They do not ban Flock.

In Carpenter v. United States (2018), the Supreme Court held that obtaining seven or more days of historical cell-site location information from a phone company is generally a Fourth Amendment search requiring a warrant. People have a reasonable expectation of privacy in the record of their physical movements. The Court did not decide that shorter windows are automatically exempt.

In Chatrie v. United States (June 29, 2026), the Court held that police conduct a Fourth Amendment search when they acquire a person’s Google Location History (including through a geofence warrant). It rejected the idea that a short time window automatically escapes that rule, and remanded on whether that warrant met probable cause and particularity.

Those holdings concern phone location records held by carriers or tech companies, not automated license-plate readers. Plate or vehicle hits plus time and place across a network can still assemble a retrospective movement map.

How long a vendor stores data is a policy choice. The issue in these cases is when government access to a detailed movement record is a search.

In August 2026, Flock announced a recommended default retention of seven days (down from 30), with longer hold via Evidence Mode / case numbers, and said existing customers keep their current periods. Flock’s public reason was operational (most no-full-plate searches within a week). That is not an admission that it chose seven days because of Carpenter. The Blue Springs city-referred portal still listed 30-day retention on the August 27, 2026 capture. A vendor default announcement is not a City ordinance rewrite.

Opinions (PDF): Carpenter · Chatrie. Flock announcement: company blog. Reporter brief: Press kit.

Blue Springs Police Department Policies

Public order 41.3 / §41.3.9 covers readers in department vehicles, not a named fixed Flock/Safe City network SOP. Under 211-2026, fixed-network policy questions were answered with the Flock portal URL. That answer did not include a separate city SOP packet for those topics.

Portal success stories and RTCC text are not multi-year independent evaluations. Under 211-2026, compliance reviews and “oversight of the Flock Safety system” were No Preexisting documents.