This page is built from documents anyone can open: a leaked vendor guide whose full text is public, the signed Axon contract Durham published with its council agenda, emails released under Asheville’s records requests, the videos and agendas of the council meetings cited, and the research of an allied group, credited and linked where used. It documents the path a camera proposal travels on its way to a WNC council vote. The purpose is practical: each link in the path is a decision a community can see coming, and the closing section lists the specific asks that put each one on a public agenda.

One framing fact belongs up front. The proposals in this record reached councils through vendor sales calls and routine agenda placement; the public records do not show a resident petition or public outcry asking for any of them. The departments in this record are the vendors’ customers, sold to with the same materials as everyone else, and several of the officials quoted below are the ones who surfaced the problems.

The script

In August 2026, 404 Media published a leaked internal Flock Safety guide, dubbed the Flockbook, that coaches police departments on presenting and defending plate reader systems to city councils, paired with a May 2026 Flock webinar titled “How to Speak to City Councils: Meeting the Moment with Confidence.” The full text is public, and Flock’s guide for presenting to councils lays it beside Asheville’s record. The guide advises departments to prepare “a carefully scripted presentation” for opponents who “come prepared.”

The dates limit what the leak can show: it published in August, so it proves nothing about what any official said before that. What it gives residents is the ability to read the vendor’s coaching before the next presentation; Hendersonville’s council hears a Flock presentation from its police chief on Sept 3, and the coaching document for exactly that setting is now public. The messaging layer is also growing a level above the vendors: Hendersonville Police Chief Blair Myhand said in mid-August that he is working with the International Association of Chiefs of Police on resources to help departments communicate with their communities about this technology, expected by year end. A chief seeking better communication tools is engagement, and it is recorded here as that; the development worth tracking is that the communication materials for this technology are increasingly produced nationally rather than locally. On September 3 the chief told his council the rest (timestamped in the meeting record): he sits on the IACP executive board, chairs its working group of about a dozen chiefs writing a model plate reader policy and public communication tools, and has been asked to moderate a panel with Flock’s chief executive in October. In Hendersonville, the vendor’s script, the association’s model policy, and the presentation to council share an author, by his own description.

The money

The purchase money often arrives from outside the town too. Nationally, the researchers at Southerners Against Surveillance Systems & Infrastructure document how federal Department of Homeland Security grant programs, principally the State Homeland Security Grant Program and the Urban Area Security Initiative, fund vendor surveillance products into local policing. Their project on DHS, Flock, and Fusus is worth reading in full; the research is theirs, so this page links it rather than repeating it.

Asheville’s version is on the timeline: a congressman signed the formal request for $1.14 million in federal RTIC funding in May 2024, with a one-sentence written justification, before council knew of the arrangement; the money arrived in February 2026 at more than double the first request; the federal conditions attached were published after acceptance. By the time local debate began, the money had been requested, doubled, and accepted, and the argument that carried the first council vote was that the center already existed.

The purchase route

The contract commonly arrives through cooperative purchasing, a national contract an agency buys through without running its own competitive bid. Durham bought its Axon system through Sourcewell contract No. 101223-AXN, incorporated by reference into the signed agreement. That signed copy also answers a question towns should ask about the route: where the cooperative contract and Axon’s own master terms conflict, the contract says Axon’s terms govern.

Whether Asheville or Brevard purchased through a cooperative is not in the public record; the purchasing vehicle is named on each purchase Quote, and neither Quote has been posted. Both facts are answerable by the town that holds the paper.

The venue

Two patterns appear in the meeting record. Asheville’s first RTIC money passed in March 2025 on the consent agenda, the portion reserved for routine, undebated business (2025-03-25 City Council). The substantive briefing came at an April 2026 work session where the presenters were sales representatives from Axon and Flock alongside the interim chief, with no public comment taken; the vendors’ statements that day on data ownership differed from their own contract terms read into the record (2026-04-28 Work Session). The baseline underneath both: a sitting councilmember first learned her city had been running plate readers from the press (2025-03-07 Agenda Briefing).

The vote, then the contract

The dates carry this section.

  • May 7, 2026: five days before the vote, City Manager D.K. Wesley confirmed on the record that the Axon agreement “does not exist yet… B2 will give me authorization to further negotiate and finalize that contract with Axon.”
  • May 12, 2026: council authorized the seven-and-a-half-year commitment, with no final text in existence for members or residents to read.
  • July 16, 2026: nine weeks after the vote, APD’s business manager emailed Axon’s representative: “Legal has finished reviewing the combine contract and we are ready for your review and signature!” The reply: “Let me get this routed for signature now!” (The released emails are on The RTIC Policy; the exclamation points are the emails’ own.)

Residents who negotiate contracts professionally described the position to council before the vote; one summary from the podium: “You can’t negotiate against Skynet” (The People Who Showed Up).

The terms

The signed Durham contract shows what the paper provides for once the sequence completes: payment obligations are non-cancelable; hardware delivered below list price is billed at the difference on early exit; renewal is priced below replacement at each decision point. Durham received $1,060,333 of hardware at a net price of zero dollars under those terms. Brevard’s offer of three no-charge cameras sits under the same clause structure, which is why the Brevard read asks for the exit cost in dollars before the Sept 8 vote.

The vendor swap

When a community ends one vendor’s contract, the record shows the channel delivering the next vendor for the same function. Interim Chief Stepp’s August 14 memo to Asheville’s council states APD is “not pursuing a full transition away from Flock” while “expanding and integrating Axon’s automated license plate reader capabilities,” operational by February 2027. Denver declined a new Flock contract, removed about 110 cameras, and contracted with Axon for 50 (Communities that ended or limited camera contracts). Brevard’s county sheriff runs Flock and the city is being offered Axon; whether one led to the other is not established, and this page does not claim it.

The asks

Each link above converts into a specific, answerable request with a named owner, and none of them is an anti-camera ask:

  1. Post the purchase Quote before the vote (the council or manager holds it): the Quote carries the price, the term, the quantities, and the purchasing vehicle.
  2. Name the purchasing vehicle (same owner): a cooperative contract number can be read before signing, conflict clause included.
  3. Pair any vendor presentation with an independent expert, with public comment (the body setting the agenda).
  4. Read the exit clause aloud with a dollar figure (the attorney reviewing the contract): what does leaving in year two cost?

Brevard has already met more of this standard than any town in this record: its draft policy and master terms are posted, its information session (Sept 1) came before the council date (Sept 8), when the chief withdrew the request, and the remaining item from the list above is the Quote. The documents, read clause by clause: Transylvania County. The vendor script: Flock’s guide for presenting to councils. The contract form nationally: What Axon Contracts Do. The full local sequence: Timeline.

Corrections welcome; this page is meant to be checked.