Red flags & open questions

Each flag is graded by strength of evidence. Flags marked "open question" are interpretive — read the source documents and judge for yourself.

Last updated

Grading legend strongest documents directly support the concern · supported documented but with nuance · open question the corpus raises it but doesn't answer it · documented gap something the corpus shows is missing
#1

Procurement record absent from corpus

supported
The 6/13/2025 grant application identifies Flock by name and references "preliminary planning with Flock Safety" (Grant p.6) — months before competitive procurement could have occurred. The Standard Contract checkbox is "Department Procurement" (815 CMR 2.00) — not a Statewide Contract (Grant p.22).

The application represents "The Town of Ayer will be adhering to the procurement process as dictated by the Commonwealth of Massachusetts" (Grant p.6). No RFR, RFP, competing-vendor quotes, or sole-source justification appear in this corpus.

Caveat: 815 CMR 2.00 permits a range of procurement methods including department-led; the absence of competing-bid documentation here does not, by itself, prove a violation.
#2

Pre-award vendor engagement

supported
Per Gill's 11/25/2025 email, APD "began engaging with Flock Safety" "approximately one year" earlier — i.e., late 2024 per Gill's own retrospective wording (Email p.1). No contemporaneous late-2024 record about Flock engagement appears in this corpus. OGR's 10/6/2025 award email warns: "Grant related costs incurred prior to your official start date will not be authorized for reimbursement" (Grant p.19).

No reimbursement issue actually arises — the Order Form was signed 10/29/2025, after Stanton's 10/24/2025 countersignature. But the long pre-award vendor relationship is consistent with the "vendor was already chosen" pattern.
#3

Goods/quantities changed between grant and contract

strongest
Application proposed 5 ALPRs + 3 live cams (Grant p.6). Contract delivered 5 LPRs + 2 PTZ Video + 1 Solar LPR/Video bundle + Traffic Analytics (Order p.2). The bundle effectively adds a 6th LPR-capable device.

OGR required a "revised budget reflecting the exact award amount" (Grant p.18). That revised budget does not appear in this corpus.
#4

Contract auto-renewal vs. one-year grant

strongest
Grant covers exactly one year ($25K, ends 8/31/2026). Order Form has 12-month initial + 36-month auto-renewal term, renewing unless cancelled with 30 days' notice (Order p.2, p.13). Without invoking the §11.15 non-appropriation termination (Order p.19), Year 2+ obligations fall on the Town's general fund.
#5

No reimbursement evidence in corpus

documented gap
Chief Gill certified non-supplant (Grant p.3). The Town paid the full invoice from CASH-UNRES (unrestricted cash) on 12/18/2025 (Order p.21).

Paying first from unrestricted cash is the normal mechanic of a reimbursement grant — the Town pays Flock, then bills OGR for the $25K. That is not, on its face, supplanting. However, no reimbursement request, drawdown, or receipt appears anywhere in this corpus, so it cannot be confirmed from these records that the grant was ever drawn down. If this corpus represents a complete PRR production about Flock spending, that absence is itself notable.
#6

PO# missing from all transactions

strongest
All three documents — Order Form (Order p.6), Invoice (Order p.20), and Town accounting screen (Order p.21) — show an empty PO Number field. Whether a Town-side purchase order exists outside this corpus is unknown.
#7

Sharing setting vs. contract licensing — the strongest concern

strongest
The administrative setting: as of 4/30/2026 the platform is MA-only — 47 in-state, 0 out-of-state, 0 federal (Sharing p.1). This is consistent with Gill's 11/17/2025 instruction to the implementation team.

However, the contract Ayer signed still grants Flock:
  • A "limited, non-exclusive, royalty-free, irrevocable, worldwide license to use the Customer Data" — Order §4.1 (Order p.11)
  • Authority to "access, use, preserve and/or disclose the Customer Data to law enforcement authorities, government officials, and/or third parties" on a good-faith belief of necessity — Order §5.3 (Order p.12)
  • A perpetual license to share data with third parties whenever the Customer requests an integration — Order §4.4 (Order p.11)
Both the MCOPA legal advisory (Email p.13) and the ACLU letter (Email p.7, p.10) explicitly warn that contract language may supersede user-selected restrictive sharing settings. Both recommend amending contracts.

The corpus contains no evidence of any contract amendment by APD or the Town of Ayer.
#8

Does APD Policy 336 even apply to these cameras?

open question
Policy 336.1 says it "only applies to overt, marked public safety video surveillance systems operated by the Department" and "does not apply to mobile audio/video systems, covert audio/video systems, or any other image-capturing devices" (APD-Pol p.3).

Whether Flock's pole-mounted PTZ Condors and Solar LPR/Video bundle qualify as "overt, marked" within Policy 336's meaning is a fact question this corpus does not answer. Policy 336.4.1 requires a video-access log; Policy 336.7 requires an annual review by the Chief. Neither log nor review appears in this corpus.
#9

These records were not proactively published

strongest
Both Gill→Pontbriand internal emails (Email p.1, p.3) were collected and released only in response to a public records request. Neither the Town of Ayer nor APD has published its Flock contract, the related grant award, or its ALPR policy on a town webpage. The only path the public has to these records is to file a PRR — which the public records law requires the Town to respond to within 10 business days.
#10

Document orientation / scan handling

documented
All 5 PDFs were exported with 270° rotation flags on every page. Grant Packet pp.12–15 (budget worksheet) and Order Form p.21 (Town payment screen) are also native landscape. Data is intact but readability depends on the viewer. The document viewers on this site auto-correct orientation.
#11

APD policy adoption date is not in the corpus

open question
Policy 426 footer says "Copyright Lexipol, LLC 2026/04/27" (APD-Pol p.1). That is the manual's print/publication date — Lexipol re-prints the entire manual with the current date — and is not necessarily the date Policy 426 was adopted by APD. The corpus does not establish when Policy 426 was actually adopted.

A separate question is whether prior versions exist and when Policy 426 was first adopted relative to camera installation in Q1 2026.
#12

Public statement vs. documented funding source (NERAC vs Byrne JAG)

strongest
At the April 21, 2026 Select Board meeting, Chief Gill stated on the record that the Flock cameras were funded "through a grant through the NERAC grant system." NERAC is the Northeast Homeland Security Regional Advisory Council, which distributes DHS/FEMA Homeland Security Grant Program (HSGP) funds.

The corpus shows a fundamentally different funding source: the U.S. Department of Justice — Bureau of Justice Assistance — Edward J. Byrne Memorial Justice Assistance Grant (CFDA 16.738, federal award #15PBJA22GG00645JAGX, administered by MA OGR; Grant p.18, p.20, p.22).

Byrne JAG and HSGP are different federal programs (DOJ vs DHS) with different purposes and different oversight pathways. No NERAC project request, council meeting record, or HSGP grant award appears in this corpus. Either (a) Gill misstated the funding source publicly, (b) NERAC funded a separate purchase not in this corpus, or (c) both grants exist and a follow-up PRR to MAPC / EOPSS-OGR is needed to find the second. See Select Board fact-check #1.
#13

"Flock doesn't tell us who's driving" framing vs. Flock's own product marketing

strongest
On the record April 21, 2026, Chief Gill said: "What Flock doesn't do is tell us who's driving cars. It doesn't tell us about anything about a person that's in the cars. Doesn't tell us who owns them."

Flock's own product marketing for the LPR product line directly contradicts this framing. The company advertises Vehicle Signature® and Flock FreeForm™ as features that capture "more detail … no plate required" — make, model, color, roof racks, bumper stickers, decals, and vehicle damage — and produce "actionable evidence." Flock's Convoy Analysis feature explicitly maps which vehicles travel together to identify associations between drivers. Flock's Nova platform supplements ALPR reads with data-broker and public-records information to track individuals without a warrant (404 Media reporting, May 2025).

A camera that reads only plates and lets officers run them through NCIC/RMV gets the registered owner's name instantly. The "doesn't tell us who's driving" distinction obscures the operational reality. See Select Board fact-check #6 for Flock's own marketing image.
#14

Ayer PD on the Flock network long before cameras "came up"

supported
Gill stated on April 21 that the cameras had been up "approximately three or four weeks" (i.e., ~late March 2026). The Order Form was signed 10/29/2025 and the Town paid in full on 12/18/2025 — a ~5-month gap between signing and physical install. Flock onboards agencies into the nationwide data-sharing network at contract signing, not at camera activation. Ayer PD already appears on the data-sharing partner lists of other agencies' Flock transparency portals (Waltham, Woonsocket RI, Newtown CT, Simsbury CT, Putnam CT, East Hampton Village NY, Boardman Township OH).

The implication: Ayer's data-sharing configuration may have been set by Flock months before APD completed training or established its written policy. Cambridge terminated its Flock contract for this kind of unilateral action by the company.

What is NOT in this corpus