# Asset-Forfeiture Funding for Surveillance Procurement A procurement-pattern concept central to the investigation: **municipal/county law-enforcement agencies use asset-forfeiture proceeds to acquire surveillance technology outside the ordinary annual-budget process**. The visibility and authorization path varies. Conway's Council did vote by a separate ordinance, but only after the cameras had been cut from the annual budget and the contract had been signed; other corpus examples use different procedures. The record therefore supports a narrower pattern about surveillance purchasing outside the ordinary budget cycle, not a universal claim that elected appropriating bodies never vote. The Conway PD–Flock procurement is a documented instance. ## How it appears in the corpus The Conway procurement narrative, as the corpus reveals it ([[Morning - Procurement Pivot Thread]] + [[AR - Conway PD - Welcome to Flock! (3) - Flock Kickoff Slide Deck]]): 1. **Original plan: 2025 City budget line item.** Flock TSM Brittney Hall's 2024-12-12 email to Chief Harris asks for "budget approval confirmation on the Flock LPR cameras" — meaning the cameras were proposed as a city-budget item awaiting Council approval. 2. **Council cuts the line item.** Harris's 2024-12-13 reply: "The cameras were unexpectedly cut from the 2025 budget." The Council, in its budget-review role, declined to appropriate funds for the deployment. 3. **Pivot to asset forfeiture.** Same 2024-12-13 email: "However, I can still get them using our asset forfeiture funds. I just need to get approval at the first city council meeting in January, which I am confident I will get. On to plan B." 4. **Vendor designs around the appropriation-cycle risk.** Hall's 2024-12-16 email surfaces the contract's **non-appropriation clause**: "We have a non appropriation clause built into the contract that allows you out of contract if council denies it." The clause is a sales tool — agencies can commit prior to legislative authorization, with a contractual exit if denied. 5. **End-of-quarter discount.** Hall offers a $5,700 installation waiver explicitly contingent on year-end signature: "if we waive all of installation $5700, could you sign this month net 60 terms?" The discount appears on the executed Order Form. 6. **Vendor records the funding source on its own onboarding sheet.** [[AR - Conway PD - Welcome to Flock! (3) - Flock Kickoff Slide Deck]] Page 16: **"Funding Source: Asset forfeiture"** — Flock's own customer-kickoff template captures the funding-source decision in writing. 7. **The Council formally authorizes the spend — by ordinance, after the contract.** On January 14, 2025, the Conway City Council unanimously passed [[Ordinance O-25-09 — LPR Bid Waiver and Asset Forfeiture Appropriation|Ordinance O-25-09]] — twenty-seven days after Chief Harris signed the Flock contract on 2024-12-18. The ordinance waived competitive bidding on a sole-source theory ("Flock Safety is the only provider who can supply the LPR system in order to be in compliance with surrounding agencies"), authorized the $180,000 purchase, and appropriated $180,000 from the asset-forfeiture fund balance (250.000.4900) into the asset-forfeiture computer-equipment expense account (250-121-5930). The [[January 14 2025 Conway City Council Meeting|minutes]] record the motion, the second, and the 8-0 roll-call vote; no discussion is recorded. The [[Flock LPR Cameras Capital Request]] documents the original general-fund (001) ask that the ordinance rerouted into fund 250. 8. **The disbursements execute the appropriation.** [[Flock Payment Records — INV-56859 and INV-81961]]: $60,000 paid 2025-07-09 (Year 1, INV-56859) and $120,000 paid 2026-01-16 (Years 2 & 3, INV-81961), both drawn on G/L 250-121-5930. Total $180,000, matching the ordinance authorization. ## Stakeholders - **The agency** — controls the asset-forfeiture account; decides the spend. - **The vendor** — adapts contract structure to the funding cycle (non-appropriation clause + year-end discounts). - **The Council** — appropriates the city budget and, at Conway, later adopted a separate bid-waiver and asset-forfeiture appropriation after contract execution. - **The public** — receives less visibility when the procurement moves outside the annual budget cycle; a later ordinance may disclose authorization without supplying the underlying fund ledger or pre-purchase deliberation. ## Timeline - 2024-12-12 — Hall emails Harris asking for budget-approval confirmation. - 2024-12-13 — Harris replies: "cut from the 2025 budget … asset forfeiture funds … Plan B." - 2024-12-16 — Hall offers $5,700 install waiver + non-appropriation clause + net-60 terms. - 2024-12-16 — Burningham asks Hall for the MSA. - 2024-12-18 — Chief Harris executes the Flock contract via DocuSign ([[Contract to Legal Thread (Dec 2024 DocuSign)]]). - 2024-12-30 — Mayor's-Office Procurement Manager Tiffany Maddox and Chief of Staff Felicia Rogers approve the asset-forfeiture funding mechanism and the bid-waiver ordinance structure by email ([[2024-12 Maddox Rogers Bid-Waiver Signoff (Flock Cameras Thread)]]). - 2025-01-02 — Maddox advises CPD Assistant Celeste Phillips to strip "sole source" language from the draft ordinance text; the laundered "the only provider" phrasing replaces it ([[2025-01 Maddox Advises Strip Sole-Source Language (Ordinance for Review Thread)]]). - 2025-01-14 — Conway City Council passes [[Ordinance O-25-09 — LPR Bid Waiver and Asset Forfeiture Appropriation|Ordinance O-25-09]] 8-0, waiving competitive bid and appropriating $180,000 from asset-forfeiture fund balance 250.000.4900 into expense account 250-121-5930 ([[January 14 2025 Conway City Council Meeting]]). - 2025-01-22 / 23 — Project kickoff; Flock's customer template records "Funding Source: Asset forfeiture." - 2025-02-11 — O-25-09 recorded in Faulkner County official records (Doc Num L2025018532). - 2025-06-25 — Springbrook ERP workflow notification for PO `0000097136` (vendor 12100 Flock Safety, batch `62525.06.2025`, authored by Chief Harris) routes to Tiffany Maddox for purchasing approval ([[Springbrook PO Workflow Notifications and Flock Vendor Onboarding]]). - 2025-07-09 — City of Conway pays $60,000 (INV-56859, Year 1) from G/L 250-121-5930 ([[Flock Payment Records — INV-56859 and INV-81961]]). - 2025-12-16 — Flock invoice INV-81961 issued for "Year 2 & 3" at $120,000; no PO# on the invoice (consistent with non-city-procurement spend). - 2026-01-06 — Burningham forwards past-due notice to Celeste Phillips asking "Have they been paid?" — the actual funding-source disbursement remains opaque to the contract's named AP contact. Same day, Springbrook ERP workflow notification for PO `0000100151` (vendor 12100 Flock Safety, batch `29204.12.2025`, authored by Chief Harris) routes to Tiffany Maddox. - 2026-01-16 — City of Conway pays $120,000 (INV-81961, Years 2 & 3) from G/L 250-121-5930. - 2026-01-27 — The Asset Forfeiture Log records `Axon annual payment O-26-11` at `-$52,714.52`; the product and accounting type are not identified ([[Conway Asset Forfeiture Log 2023-2026]], p. 1). - 2026-07-22 — City Finance completes `FOIA-2026-205`, producing the forfeiture schedule, annual statements, two one-month cash trial balances, and duplicate Flock invoices ([[sources/city-of-conway/FOIA-2026-205/_overview|FOIA-2026-205 overview]]). ## Conway Finance production — inflows, additional technology, and accounting boundary The Finance production materially answers the earlier inflow-side gap at a source-category level. The schedule repeatedly names “Check from the 20th District” and “Wire from DEA,” plus a `$31,735.74` “USPS Check” and interest deposits ([[Conway Asset Forfeiture Log 2023-2026]], `Jan 2023 - Present Asset Forfeiture Accounting.pdf`, pp. 1-2, verbatim rows). The file does not supply the underlying seizure/case records or define every blank balance update, and no native spreadsheet or complete system-generated GL export was produced. The same schedule broadens the surveillance-funding finding beyond Flock: `7/25/2024 — Drone package from Skydio — -$57,962.71` and `1/27/2026 — Axon annual payment O-26-11 — -$52,714.52` appear on page 1. These rows establish schedule entries, not product models, invoices, payment dates, or accounting classifications ([[Conway Asset Forfeiture Log 2023-2026]], p. 1). > [!contradiction] The schedule and cash records use different dates for the Flock obligation > The schedule records `1/14/2025 — O-25-09 Flock Safety Cameras — -$180,000.00` (`Jan 2023 - Present Asset Forfeiture Accounting.pdf`, p. 1). The cash-account trial balances instead show `$60,000.00` and `$120,000.00` AP credits on July 9, 2025 and January 16, 2026, and the earlier vouchers identify those same-date amounts as the first and final Flock payments ([[Conway Flock Payment Trial Balances]], both p. 1; [[Flock Payment Records — INV-56859 and INV-81961]], `PO 97136.pdf` and `PO 00151.pdf`, p. 1). The records can coexist if the January schedule line is an appropriation, encumbrance, or reservation rather than cash, but the production does not define it. See [[T018 - Conway Asset Forfeiture Schedule vs Cash Ledger]]. ## Notes - The **specific Arkansas legal framework** for asset forfeiture (state statute, "equitable sharing" through DOJ, etc.) remains an open research question. State and federal forfeiture-fund rules differ substantially; the rules constrain what an Arkansas municipal agency can spend forfeiture proceeds on and what oversight is required. - The **broader policy critique** of asset-forfeiture funding for surveillance — that it perpetuates a "policing-for-profit" loop in which seizures fund surveillance which produces more seizures — is well-developed in ACLU, Brennan Center, and Heritage Foundation/Institute for Justice literature, which later research could draw on. - For the [[Conway Police Department]] specifically, the Council ordinance, meeting minutes, payment vouchers, source-category schedule, annual statements, and two payment-month trial balances are now in the record. `FOIA-2026-205` materially answers the inflow-source question but does not supply the native schedule, complete GL detail, or case-level provenance. The live accounting question is the classification of the schedule's January 14, 2025 full-value Flock entry ([[T018 - Conway Asset Forfeiture Schedule vs Cash Ledger]]). - This concept page applies to other Arkansas jurisdictions in the investigation as well. The pattern is not Conway-specific: asset-forfeiture authorization is a live question wherever a municipal ALPR purchase bypasses the appropriation. ## Little Rock — the recurring forfeiture pattern (CLR-2026-778) The [[sources/city-of-little-rock/CLR-2026-778/_overview|CLR-2026-778]] production documents the same asset-forfeiture-funding pattern at scale at [[Little Rock Police Department]] — not for a single ALPR procurement (as at Conway) but as a *recurring* funding mechanism across multiple distinct surveillance/investigative product lines: | Procurement | Resolution / Ordinance | Forfeiture account | Amount | |---|---|---|---| | **[[Fusus]] RTCC platform (2022)** | Resolution 15,763 (2022-09-06) | **Seized Funds Account No. 270529-G3514** | $128,937/yr × 3 years = $386,811 | | **Motorola Watchguard M500 (2025)** | (Resolution number in draft; Sourcewell #101223-MOT) | **State Asset Forfeiture Funding Account No. 110520-60200** ($103,996.80 of total) + Special Project Account #S52C520 LRPD Fencing Project surplus ($129,996.00) | $233,992.80 total | | **[[Utility Associates]] Rocket Modems (2025)** | Resolution 16,787 (2025-08-19) | **RTCC funding allocation 108529-S52C458** (an RTCC-designated account, partially overlapping with seized funds context) | $79,000/yr | | **[[i2 Group]] Analyst's Notebook + iBase (2024)** | Sole-source exemption #44 | "RTCC funding" (per Ty Tyrrell memo) | $11,916.36/yr | LRPD has at least two distinct asset-forfeiture-style funding streams in the corpus: 1. **Seized Funds Account No. 270529-G3514** — historical asset-forfeiture-proceeds account; used for the 2022 Fusus RTCC procurement. 2. **State Asset Forfeiture Funding Account No. 110520-60200** — newer/separate state-level forfeiture account; used for the 2025 Motorola M500 expansion. Plus an **RTCC funding allocation 108529-S52C458** that appears repeatedly across LRPD procurements (Utility, i2, parts of the connectivity cluster) — making "RTCC funding" itself a distinct line in the LRPD budget, separate from the asset-forfeiture accounts. The recurring pattern at Little Rock confirms the [[Conway Police Department]] observation: asset-forfeiture funding for surveillance procurement is **not a Conway-specific or one-off occurrence**; it is a repeating municipal pattern in Arkansas. The Little Rock data extends it to a metro-scale surveillance build-out funded across multiple forfeiture-pattern accounts. ## Open questions (LRPD-specific) - **The inflow side of the LRPD Seized Funds account (270529-G3514).** What seizures fund the Fusus procurement? The corpus does not document the seizure-source ledger — the same open question as Conway. - **State Asset Forfeiture vs. Seized Funds — the legal/regulatory distinction.** Both fund surveillance procurement at LRPD but appear to be separately administered. Whether the two accounts are governed by different Arkansas statutes (state-level civil asset forfeiture vs. local proceeds-of-seizure accounts) is a Tier-2 question outside the corpus. - **The "RTCC funding allocation" 108529-S52C458 as a forfeiture-account variant.** Whether this account is sourced from forfeiture proceeds, general fund, or a hybrid is not directly documented in the corpus. ## Pulaski County (PCSO) — a narrower funding record *Erratum, 2026-07-30: this section formerly described the Pulaski County Flock procurement as conclusively non-forfeiture and non-grant funded. PCSO Finance certified that its 2015-present search found no responsive asset-forfeiture authorization records, while the County routing form charges `3015-0400-3073` and leaves the Grants Administration signature field blank. Those records do not identify every upstream source feeding the account.* The [[pulaski-county-government/26-365/_overview|Pulaski County `#26-365`]] production documents a charged general-fund line rather than a named asset-forfeiture account: 1. **PCSO Finance's 2026-06-01 item-4 response** reports no responsive asset-forfeiture authorization records in its 2015-present search ([[2026-06 Pulaski County SO 26-808 Closed with No-Records on Items 2 and 4]]). That is a custodian-and-search-bounded finding. 2. **The County contract routing form charges `3015-0400-3073`**, identified in the source inventory as general fund ([[Pulaski County Flock Safety Term Contract Award (Contract 6764)]]). Its Grants Administration signature field is blank, but the form does not define the significance of a blank or identify every upstream funding source. The defensible contrast is documentary: Conway and LRPD records name forfeiture accounts, while the PCSO Flock records reviewed here do not. Additionally, PCSO's **pre-Flock Genetec ALPR system** ([[SkyCop Invoice 8381 — Pulaski County Genetec System]], 2021) was funded by **federal grant** — the DOJ Bureau of Justice Assistance Project Safe Neighborhoods Formula 18 (PSN18) award — not asset-forfeiture. See [[Federal Law Enforcement Grants for Surveillance Procurement]] for the contrasting federal-grant funding pattern. ### Why the Pulaski County counter-pattern matters The asset-forfeiture pattern at Conway PD and LRPD ([[Ordinance O-25-09 — LPR Bid Waiver and Asset Forfeiture Appropriation]] and the LRPD recurring-forfeiture procurements documented above) is one of three documented surveillance-procurement funding mechanisms in the Arkansas corpus: 1. **Asset-forfeiture funding** — Conway PD's Flock, LRPD's Fusus/Motorola/Utility/etc. 2. **Federal grant pass-through** — PCSO's pre-Flock Genetec system (PSN18 / [[US Department of Justice — Bureau of Justice Assistance|BJA]] / [[Arkansas Department of Finance and Administration — Office of Intergovernmental Services|DFA-IGS]]) 3. **General-fund charge line** — PCSO's Flock routing form (`3015-0400-3073`); LRPD's Flock procurement (Account 105225-63360) The asset-forfeiture pattern is therefore **not the only funding record in this corpus**. The records also document grant-funded and general-fund-charged procurements; the approval and upstream-source history must be established from each procurement's own records. *Observation, distinct from the record:* the Pulaski County counter-pattern suggests that smaller-volume surveillance procurements may be more likely to be general-fund-funded (because they fit within an existing budget line item without specific appropriation action), while larger-volume procurements may be more likely to require asset-forfeiture or grant-funding workarounds. PCSO's $36,900 Flock contract is small enough to fit within a general-fund line; Conway's $180,000 and LRPD's $690,000 may have triggered the workaround patterns.