# Sherwood ALPR Permitting and Operational Status Sherwood's records do not support one deployment date or one permit status for its 15-site Flock inventory. They support a stage-by-stage matrix: some sites have issued TCD and District permits; some were removed from ARDOT review because they are outside state right-of-way; some remain application-only or unmatched; and the completion/inspection record contains unresolved chronology and attachment anomalies. Separately, the February 11 stop proves operational use before the Department's March 24 successor-policy and “final system” date. ## Evidence ### Current inventory and ARDOT coverage are different things Sherwood listed 15 current camera positions on July 8, 2026 ([[Sherwood Flock Camera Locations]], paragraphs 5-19). ARDOT's CSV contains only four Sherwood point rows — P1871 twice, P1888, and P1915 — and omits P1855 ([[Statewide Traffic Control Devices Export]], `TrafficControlDevices.csv`, lines 192-193, 237, 267). The CSV's status, inspection, and comment fields are blank. It is a broad traffic-control-device export, not a demonstrably complete ALPR index. ### Exact locations require version-aware crosswalking Tier-1 engineering and permit records supply exact points for eleven of the fifteen current-inventory corridors. The complete table and every located variant appear in [[Sherwood Flock Camera Locations]] and the cross-agency register [[Arkansas ALPR Camera Coordinates and Directional Nomenclature]]. Four rules control the synthesis: - Sites 1, 2, 3, 5, and 9-15 have produced plan or engineering points; sites 4, 6, 7, and 8 do not. - The ARDOT drawings restore westbound nomenclature for site 5 (West Maryland) and site 10 (Wildwood), which the July inventory did not state. - Wildwood and Warden/Saltgrass have materially different earlier/revised/candidate coordinates. Warden was later moved outside ARDOT right-of-way, so no produced point is promoted to a confirmed current as-built coordinate. - Case-261931 historical Highway 107 #07, `34.89850692, -92.17196590` in the later drawing, is at log mile 11.419 and is not P1915/current site 15, `34.880610, -92.182052`, at log mile 9.941. The statewide CSV's Sherwood points are close to, but not identical with, the engineering-plan coordinates. That is an evidentiary version difference, not license to average the pairs or silently choose a new “true” point. ### Permit approval is not installation or acceptance - P1871: TCD issued April 30, 2025; SP-06-2025-0017 dated May 12; City completion form dated June 11; no produced final inspection/acceptance; later February 2026 start-work notice for two devices ([[Sherwood Highway 107 Permit P1871]]). - P1888: TCD issued June 16, 2025; SP-06-2025-0028 dated July 14; City completion form dated August 20; no produced final inspection/acceptance ([[Sherwood Kiehl Avenue Permit P1888]]). - P1915: TCD issued September 9, 2025; SP-06-2025-0042 dated October 6; CO1 approved January 13, 2026; completion field blank ([[Sherwood Highway 107 Permit P1915]]). - P1855: TCD form dated March 10, 2025 but still in a pending-Mayor packet; ARDOT later said the work had been completed without an approved special permit and needed retrospective documentation ([[Sherwood Landers Warden and Wildwood Applications]], `Emails.pdf`, p. 5). The local City is the permittee; Flock is the contractor/installation and bond party. ARDOT's terms say permits are requested by and issued to the local City Mayor or County Judge, while the special-permit packet records Flock's bond ([[Sherwood Highway 107 Permit P1915]], `1105497_-_Signed_docs.pdf`, p. 2; `SP-06-2025-0042_City_of_Sherwood.pdf`, p. 4). ### Non-ARDOT sites remain operationally relevant Trammel and West Maryland were marked “Remove, Not on ARDOT HWY” in case 261931 ([[Sherwood Multi-Site Application Case 261931]], pp. 7-8). Warden/Saltgrass was moved outside ARDOT right-of-way, and Wildwood was closed out as City jurisdiction ([[Sherwood Landers Warden and Wildwood Applications]]). Those dispositions mean ARDOT permitting does not apply; they do not prove the devices were never installed. Conversely, their presence on Sherwood's July inventory does not establish an installation date or City permit. ### Operation and policy have independent chronologies The February 11, 2026 stop establishes that Sherwood was receiving and acting on Flock alerts before March 24 ([[Sherwood Incident and CAD Records]], incident report p. 4). Policy 11.08.00 became effective March 24 and requires physical-plate verification, ACIC/NCIC confirmation, outcome marking, activity logs, and annual audits ([[Sherwood ALPR Policy 11.08.00]], pp. 3-4). Sherwood's completion correspondence describes March 24 as the date the “final” system was installed; “final” does not mean first operational use and does not identify a specific device. ### PD-2026-520 did not close the operational-record gaps Items 1 and 2 remained awaiting confirmation immediately before closure and were not answered by the five policy PDFs. Item 3 received only a statement that the Department does not maintain a configuration-file report; item 4 is partial because the successor ALPR policy was not in effect and completeness across the requested policy subparts was not confirmed; item 5 is a custodian-specific statement that the prior Captain Edwards email is the only written review record ([[PD-2026-520 Request Coverage and Custodian Statements]]). ## Caveats - No final inspection or notice of final acceptance was produced for P1871 or P1888. P1915's completion date is blank. - [[T009 - Sherwood ALPR Completion and Installation Chronology]] remains open; no inference is made about why the dates and attachment labels conflict. - The CSV is not used to infer statewide completeness, installation status, or operational status. - The ARDOT production does not identify which camera generated the February 11 alert. - An exact plan point does not, without an as-built survey or activation record, establish that the camera was installed at that exact point or remains there today. - A custodian-specific no-records statement is not broadened into a claim that no record exists in another account, system, or custodian's possession. ## Open questions - Produce the February 11 alert record and related Flock activity/audit records, or a category-specific no-records response identifying systems and custodians searched. - Produce existing-form sharing/configuration records or clarify that none exists across the relevant Department and vendor systems. - Obtain site-specific activation, installation, final-inspection, and final-acceptance records for P1855, P1871, P1888, and P1915. - Obtain City permits for municipal-right-of-way sites and reconcile the unmatched current-inventory locations. - Explain the P1871 completion/start-work sequence and the SP-0017/P1915 attachment mismatch.