Method: This site distinguishes contracted capability from confirmed deployment, and distinguishes internal police policy from city ordinance and state law. A product appearing in a contract does not prove Mt. Juliet has enabled it. “No ALPR mentioned” does not prove ALPR was absent.
Current ALPR location/direction entries73Not necessarily distinct physical cameras
Original 2019 proposed locations37Public RFP announcement
Confirmed / implementing technology categories4Other products are contracted or announced but not yet verified deployed
10-year Safe City payment schedule$6.92MPublic contract; cover-page discrepancy remains flagged
PUBLIC VERIFIABILITY

Provisional transparency score

This score measures how easily a resident can independently verify scope, spending, rules, sharing, audits, outcomes and governance. It does not score legality, police integrity, crime reduction, or whether the technology should exist.

55/100

System inventory & scope

8 / 15
Partial

Public: Current ALPR location/direction list; DFR page; police acknowledges city-wide LPR and camera networks.

Gap: No consolidated product-by-product deployment inventory; no authoritative physical ALPR camera count; Condor/Raven/mobile/integration quantities are not publicly enumerated.

Improve: Publish annual inventory by product, physical device count, location, ownership, activation date and funding source.

Primary source

Spending & procurement

11 / 15
Good but incomplete

Public: Major Flock contract, payment schedule and Board approval records are public.

Gap: No single actual-spending/invoice ledger; original Rekor procurement/transition is incomplete in one place; public Flock order form contains a corrected/uncorrected total discrepancy.

Improve: Publish invoices, amendments, grants and cumulative actual spend in one annual technology report.

Primary source

Rules & legal documents

15 / 20
Good but fragmented

Public: City ordinance, current ALPR general order, state-law references and contract are publicly accessible.

Gap: Prior policy versions/redlines are not presented together; broader Safe City products do not have one consolidated governance framework comparable to the ALPR policy.

Improve: Publish policy history/redlines and technology-specific policies for video integration, acoustic sensors, AI search, drones and other Safe City features.

Primary source

Access & data-sharing transparency

8 / 15
Partial

Public: MJPD describes sharing standards and publishes an access-agreement/transparency area.

Gap: No aggregate outside-agency query counts; no public inventory of integrated private/public video feeds; actual FlockOS network sharing and outside-jurisdiction video settings are not disclosed.

Improve: Publish sharing configuration, connected-feed inventory, agencies with access by data type, request/query counts and revocations.

Primary source

Audit & compliance publication

5 / 20
Major verification gap

Public: Current policy contains detailed audit/logging requirements and says administrators audit every 30 days.

Gap: No recurring public monthly audit results or completed annual ALPR report was located in this review; the public cannot see audit sample size, exceptions, unauthorized use or corrective action.

Improve: Publish monthly aggregate audit metrics plus the annual report already contemplated by policy; add periodic independent audit.

Primary source

Use & outcome reporting

6 / 10
Partial

Public: MJPD publishes successful-interception examples and frequent public-safety announcements.

Gap: Success examples are agency-selected and do not provide a denominator for all alerts, searches, stops, false alerts or no-action outcomes.

Improve: Publish total alerts/searches/stops, verified hits, no-action outcomes, false/incorrect alerts, investigations assisted and disposition metrics.

Primary source

Public governance & change control

2 / 5
Limited

Public: Major contracts and Board votes are public records.

Gap: Product-level activation can occur under a broad Safe City agreement; major items have sometimes had little recorded public discussion; no clear public impact-review trigger for adding a new surveillance/data capability.

Improve: Require Board/public notice for major new data types, integrations, retention changes, AI features or sharing expansions and publish impact assessments.

Primary source
Why show the math? A transparency grade can become advocacy disguised as measurement. Every point here is visible and editable. If new audit reports, inventories or spending records are published, the score should rise.
SAFE CITY TECHNOLOGY INVENTORY

What Mt. Juliet has, has announced, or has the ability to use

Products are categorized by evidence status so a contract feature is never presented as a confirmed local deployment.

Confirmed deployed / implementingPublicly announcedContracted capability
Product / systemCategoryEvidence statusQuantityWhat it doesDataRetentionThird-party integrationOutside-agency capabilityActual Mt. Juliet sharingSource
Flock Safety LPR (formerly Falcon)
Do not equate 73 public entries with 73 distinct physical Falcons until device inventory is obtained.
License plate recognitionConfirmed deployed
Confirmed local deployment
73 public location/direction entries; exact physical unit count unknownCaptures plate/vehicle images and supports hot-list alerts, historical searches and vehicle-description searches.Images, license plates, vehicle characteristics, date/time/locationMJPD current policy: 21 days unless tied to an active investigation/case; 2025 order form states 30 days.FlockOS supports community network access and broader LPR network sharing.Contract includes state/nationwide plate lookup and direct-access requests to other law-enforcement devices.MJPD publishes agencies with access agreements; exact query volume and network configuration are not public on the city page.Open
Flock Safety Video Camera PTZ (formerly Condor)
MJPD separately advertises a city-wide camera network, but that does not establish that every fixed camera is a Condor.
Live / recorded videoContracted capability; deployment quantity not verified
Product is in city Flock contract; exact deployment not verified
UnknownLive-streamed pan/tilt/zoom video with edge storage and VMS.Live and recorded videoContract describes 30 days of edge storage.Can appear with other video sources in FlockOS.FlockOS contract feature set includes access to live/recorded video outside agency jurisdiction when enabled/shared.Which Mt. Juliet Condor feeds, if any, are shared outside MJPD has not been publicly verified.Open
City-wide fixed camera network
Keep this inventory separate from ALPR so a park video camera is not accidentally counted as a Falcon.
Live / recorded videoPublicly announced; device inventory not published
MJPD recruiting page confirms a “City-Wide Camera Network”; product models/locations incomplete
UnknownFixed public-safety video cameras across the city, including cameras observed/referenced at public facilities and parks.VideoVaries by system; not established here.Potentially integrable into FlockOS if connected through Flock video integration products.Unknown for Mt. Juliet configuration.Not publicly verified.Open
Flock Safety Gunshot Detection (formerly Raven)
Do not call every observed “listening device” a Raven without model/location confirmation.
Acoustic detectionContracted capability; local activation not verified
Included in Mt. Juliet Flock contract; deployment not independently confirmed
Unknown; contract licenses by coverage area, not unit countDetects acoustic signatures associated with gunfire and generates location-based alerts.Acoustic sensor eventsNot established from the local order form excerpt.FlockOS contract describes unified LPR, video and audio alerts.Platform-level sharing/integration capabilities exist; local Raven-sharing configuration not verified.Unknown.Open
Acoustic car-crash detection
Track separately from Raven gunshot detection unless the city confirms they use the same hardware.
Acoustic detectionPublicly announced as Safe City technology
Public announcement; exact hardware/product configuration needs verification
UnknownAcoustic detection associated with crash-response technology, as described by MJPD in its Safe City/Flock911 announcement.Acoustic event detectionUnknownPart of broader Safe City ecosystem as publicly described.Unknown.Unknown.Open
Video Integration Gateway 2.0 (formerly Wing)
This is the product most relevant to the question of tying city/local cameras into Flock.
Third-party camera integrationContracted capability; activation not verified
Capability explicitly in contract; local enablement/sharing unknown
UnknownConnects existing third-party cameras/video systems to the Flock platform; local order form describes a 16-stream gateway with 16TB storage and 8-channel AI capability.Third-party live/recorded videoContract description states 30 days of storage for the gateway product.Yes — core purpose is integrating non-Flock/public/private video feeds.The same contracted FlockOS feature set says agencies can view shared live/recorded footage from neighboring agencies, schools, traffic cameras and third-party feeds.No public evidence located establishing which Mt. Juliet integrated feeds are actually available to outside agencies.Open
Community Network / private-camera partnerships
A records request should ask for registered/integrated camera counts, MOUs, sharing settings and outside-agency access rules.
Public-private integrationProgram capability publicly described; exact connected inventory unknown
Current MJPD page + Flock contract capability
UnknownAllows private Flock customers/partners to share footage or, under contracted FlockOS features, allows law enforcement to request access to privately owned Flock LPR feeds.Private LPR/video feeds when owners opt in/shareDepends on source system and agreement.Yes.Potentially, depending on the owner’s sharing settings and law-enforcement network configuration.MJPD says private customers cannot access law-enforcement data; exact downstream access to private feeds by outside agencies has not been publicly established.Open
Flock Mobile Security Trailer
Needs serial/model/site confirmation before adding a local quantity.
Mobile video / deterrenceContracted capability; local Flock trailer deployment not verified
Included in contract; do not equate every MJPD surveillance tower with this product
UnknownMobile trailer with deterrence light, two PTZ cameras, 360-degree multisensor camera and audio talk-down.Video / audio talk-downNot established separately in local contract description.Integrated with Flock platform.Depends on sharing configuration.Unknown.Open
FlockOS Premium
The existence of a feature in FlockOS does not prove MJPD has enabled it.
Operations / data platformContracted
Included in contract
Agency software platformCentral operational interface combining LPR, video, audio, maps, alerts, audits and integrations.Aggregates data from connected systemsDepends on underlying data source/product.Yes — contract lists public/private video, CAD, AVL, body-camera location and other integrations.Yes at platform capability level, including law-enforcement network access and outside-jurisdiction video where enabled.Mt. Juliet-specific settings are not fully public.Open
Flock Nova — Customer Data / OSINT
This is broader than ALPR and should have its own governance/records questions.
Data integration / intelligenceContracted capability; usage not verified
Included in contract
Software subscription capabilityCentralizes agency CAD/RMS/digital evidence data and, separately, offers open-source intelligence/shared inter-agency data.Agency records, dispatch, digital evidence, OSINT and shared dataNot established in local order-form description.Yes.Shared inter-agency data is part of the described capability.Specific Mt. Juliet datasets and connections not publicly verified.Open
FreeForm AI search
Publicly verify whether enabled, who can use it, what query justifications are required, and whether its searches appear in audit logs.
AI / investigative searchContracted capability; activation not verified
Included in contract
Software add-on capabilityNatural-language search across LPR images and video footage from FreeForm-enabled devices.Searches LPR images/video metadata and imageryUnderlying source retention applies.Can search enabled data sources in the platform.Depends on data available to the user/account.Unknown.Open
Flock911
This is not an ALPR camera, but it demonstrates that the Safe City platform now extends well beyond plate readers.
911 / real-time responseConfirmed deployed
MJPD publicly announced deployment after testing
Agency-wide software integration; exact user count unknownDelivers live 911 call information into FlockOS to provide real-time context to responding personnel.911 call audio/context/location informationNot established here.Integrates 911/CAD context into FlockOS.Not established for Mt. Juliet.Unknown.Open
Flock Aerodome Drone as First Responder
City page says active-incident use, not random patrol, and promises a public flight transparency portal once launched.
Drone / aerial videoConfirmed implementation/testing
Confirmed local DFR program
2 strategically placed drone docks; city DFR page describes two operational coverage locationsDispatches drones to active calls and transmits live aerial video to responders/command staff.Live aerial video, telemetry, flight logsPer DFR policy/portal; exact local retention should be tracked separately.FlockOS contract integrates drone live video/GPS.Assistance to other public-safety agencies is described; live feed sharing specifics should be verified.Not fully documented on public page.Open
Flock Aerodome DFR Radar
The Flock drone contract also references radar and radio-frequency sensor data as Flock Drone IP.
Radar / airspace sensingConfirmed implementation/testing
Confirmed on city DFR page
1 radar described as providing citywide coverageDetect-and-avoid / airspace monitoring supporting beyond-visual-line-of-sight drone operations.Radar and airspace sensor dataNot established on public program page.Integrated with DFR platform.Not relevant/unknown.Unknown.Open
Traffic Analytics
This retention is for aggregate analytics and should not be confused with individual ALPR plate-read retention.
Traffic analyticsContracted capability; activation not verified
Included in contract
Software capabilityAggregates vehicle counts in 15-minute bins and supports breakdowns by class, state and make.Aggregate vehicle-count analyticsContract says aggregate counts may be hosted up to 5 years.Part of Flock platform.Unknown.Unknown.Open
Third-party camera question: Mt. Juliet’s Flock contract explicitly includes a video-integration gateway and FlockOS features for integrated public/private cameras and outside-jurisdiction video sharing. That proves the capability exists. It does not tell us which Mt. Juliet feeds are connected, whether they are shared externally, or which agencies can see them. Those are records/configuration questions the site tracks as unresolved.
WHO CAN CHANGE THE RULES?

State law, city ordinance, contract, police policy and public statements are not the same

The ordering below is about durability and external constraint, not a complete legal hierarchy. Federal/constitutional law can also control. This is a transparency framework, not legal advice.

State law

Tennessee ALPR retention limit — T.C.A. § 55-10-302

External legal constraintMJPD change alone: No

Main protection: Government-captured plate data may not generally be stored more than 90 days unless part of an ongoing investigation, with additional destruction rules.

How it changes: Requires state legislative/legal change, subject to controlling federal/constitutional law.

If violated: Binding law; legal consequences are determined through applicable civil/criminal/judicial processes, not merely department discipline.

MJPD chooses a stricter 21-day limit by policy; city ordinance is stricter than state maximum at 30 days. State law is an external floor/ceiling applicable to the city; it does not prevent Mt. Juliet from adopting stronger local restrictions where lawful.

Read source
State law

Tennessee confidentiality of captured ALPR data

External legal constraintMJPD change alone: No

Main protection: Restricts public inspection of captured plate data.

How it changes: State legislative change. Public Chapter 672 (2026) removed the scheduled sunset of this confidentiality provision.

If violated: Captured plate data is treated as confidential and not open for general public inspection under the public-records statute.

Limits what citizens can obtain directly, which makes aggregate audit/public reporting more important for external verification. The confidentiality rule protects plate data but also limits public ability to independently inspect individual reads.

Read source
City ordinance

Mt. Juliet Ordinance 2019-40

Local law adopted by elected boardMJPD change alone: No

Main protection: 30-day city retention cap (subject to investigation exception), no unmanned traffic enforcement, restrictions on non-governmental disclosure, and public listing of automatically shared governmental agencies.

How it changes: Board action is required to amend/repeal an ordinance.

If violated: City law rather than an internal police procedure.

More durable than a police general order, but it does not contain all of the detailed audit/query controls in the current police policy. The ordinance preamble expressly contemplated privacy and abuse risks when the city adopted ALPR rules in 2019.

Read source
City contract

Flock Safety Safe City order form / agreement

Contractual obligation / purchased capabilityMJPD change alone: Generally no for material contract terms

Main protection: Defines purchased products, services and some retention/product terms; the 2025 order form states a 30-day retention period.

How it changes: Contract amendment/renewal and whatever city approvals are legally or administratively required.

If violated: Creates contractual rights/obligations between the parties; not the same thing as a public criminal or civil statute governing officers.

Current MJPD ALPR policy says 21 days; the actual configured setting should be verified and the contract/policy difference reconciled. The contract is also important because it reveals capabilities not obvious from the Guardian Shield ALPR webpage.

Read source
Police policy / General Order

MJPD General Order 10D.6 — Automated License Plate Recognition Program

Internal departmental ruleMJPD change alone: The department can amend the general order through its policy process; it is expressly “subject to amendment.”

Main protection: 21-day retention, individual accounts, legitimate-purpose/query justification, case/call information, audit logging, 30-day administrator audits, monthly records and annual reporting requirements.

How it changes: Departmental policy amendment; current document directs readers to PowerDMS for the most recent version.

If violated: The policy expressly says violations of the General Order form the basis for departmental administrative sanctions; violations of law are handled separately in a judicial setting.

Detailed safeguards are useful, but they are less externally durable than ordinance/state law and require public audit results to verify operation. This is why the site separates “strong policy on paper” from “binding external rule” and from proof that the control is actually operating.

Read source
Public webpage / statement

Guardian Shield public facts, safeguards and transparency claims

Public representationMJPD change alone: Generally yes as website content/communications

Main protection: States 21-day retention, trained/authorized access, logging/auditing, controlled data sharing, no current federal sharing and other privacy assurances.

How it changes: Administrative website update; no ordinance vote required.

If violated: Useful evidence of what the department represents to residents, but not itself a substitute for law, ordinance, contract, or policy.

The site can compare each statement with published records and mark what remains independently unverifiable. Public claims should be preserved with dates because webpage language can change.

Read source
ALPR INVENTORY

How many plate-reader cameras are there, really?

The current city webpage contains 73 active location/direction entries. This site deliberately does not call that 73 physical cameras until the city’s device inventory is obtained.

#Public location entryDirectionStatusPhysical camera/groupLast verifiedSource
1E Division St WB @ Golden Bear GtwyWBActive on city webpageUnknown2026-08-06City list
2East Division St @ Ramp to Golden Bear Gtwy SBSBActive on city webpageUnknown2026-08-06City list
3Pleasant Grove Rd @ Triple Crowne Pkwy - EBEBActive on city webpageUnknown2026-08-06City list
4Pleasant Grove Rd @ Triple Crowne Pkwy - WBWBActive on city webpageUnknown2026-08-06City list
5Lebanon Rd @ Pin Oak Dr EBEBActive on city webpageUnknown2026-08-06City list
6Providence Pkwy @ S Mount Juliet Rd - EBEBActive on city webpageUnknown2026-08-06City list
7S Mount Juliet Rd @ Crossings Circle - EBEBActive on city webpageUnknown2026-08-06City list
8S Mount Juliet Rd @ Providence Way/Belinda – EBEBActive on city webpageUnknown2026-08-06City list
9Pleasant Grove Rd @ Old Pleasant Grove Rd - EBEBActive on city webpageUnknown2026-08-06City list
10Old Lebanon Dirt Rd @ Cobbleston Landing EBEBActive on city webpageUnknown2026-08-06City list
11Central Pike WB @ Walton's Grove Subdivision / WestboundWBActive on city webpageUnknown2026-08-06City list
12South Mt. Juliet Rd SB @ Central Pike / South BoundSBActive on city webpageUnknown2026-08-06City list
13Central Pike EB @ Mt JulietEBActive on city webpageUnknown2026-08-06City list
14Central Pike NB @ Adams LaneNBActive on city webpageUnknown2026-08-06City list
15North Mt. Juliet Rd NB @ Pleasant Grove / NorthboundNBActive on city webpageUnknown2026-08-06City list
16North Mt. Juliet Rd. SB @ Pleasant Grove / South BoundSBActive on city webpageUnknown2026-08-06City list
17Central Pk EB from S MJ RdEBActive on city webpageUnknown2026-08-06City list
18North Mt. Juliet Rd. SB @ Hwy 70 / South BoundSBActive on city webpageUnknown2026-08-06City list
19Hwy 70 EB @ North Mt. Juliet Rd. / EastboundEBActive on city webpageUnknown2026-08-06City list
20Hwy 70 WB @ North Mt. Juliet Rd / West BoundWBActive on city webpageUnknown2026-08-06City list
21Robinson Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
22Mundy Park - InboundInboundActive on city webpageUnknown2026-08-06City list
23Beckwith Rd @ Wilfong Pkwy - SBSBActive on city webpageUnknown2026-08-06City list
24Grace Road- Bradshaw Farms Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
25Mt. Juliet Soccer Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
26Ethan Page Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
27Cedar Creek Greenway - InboundInboundActive on city webpageUnknown2026-08-06City list
28Belinda Pkwy EB @ Providence Trail - EBEBActive on city webpageUnknown2026-08-06City list
29South Rutland Rd @ Baird Farms Construction Entrance - NBEntranceActive on city webpageUnknown2026-08-06City list
30Providence Pkwy @ Central Pike - WBWBActive on city webpageUnknown2026-08-06City list
31N Mt Juliet Rd @ Division St - NBNBActive on city webpageUnknown2026-08-06City list
32Nonaville Rd SB @ Saundersville Rd - SBSBActive on city webpageUnknown2026-08-06City list
33South Green Hill NB @ West Division St - NBNBActive on city webpageUnknown2026-08-06City list
34Lebanon Rd @ Terrace Hill Rd WBWBActive on city webpageUnknown2026-08-06City list
35Lebanon Rd E of Curd Rd EBEBActive on city webpageUnknown2026-08-06City list
36Old Lebanon Dirt Rd @ N Mt Juliet Rd - WBWBActive on city webpageUnknown2026-08-06City list
37Providence Way @ S Mount Juliet Rd - WBWBActive on city webpageUnknown2026-08-06City list
38N Mount Juliet Rd @ E Division St - WBWBActive on city webpageUnknown2026-08-06City list
39Old Lebanon Dirt Rd @ N Mt Juliet Rd - EBEBActive on city webpageUnknown2026-08-06City list
40Old Lebanon Dirt Rd @ Davidson County Line - WBWBActive on city webpageUnknown2026-08-06City list
41Golden Bear Gtwy @ Vanner Rd - NBNBActive on city webpageUnknown2026-08-06City list
42Charlie Daniels Park - InboundInboundActive on city webpageUnknown2026-08-06City list
43Golden Bear Gtwy @ Hwy 70 - SBSBActive on city webpageUnknown2026-08-06City list
44West Division St @ Davidson County Line - WBWBActive on city webpageUnknown2026-08-06City list
45Del Web Blvd @ S Rutland Rd - ExitExitActive on city webpageUnknown2026-08-06City list
46Providence Pkwy @ Central Pike - EBEBActive on city webpageUnknown2026-08-06City list
47Del Web Blvd @ S Rutland Rd - EntranceEntranceActive on city webpageUnknown2026-08-06City list
48Old Pleasant Grove Rd @ Pleasant Grove Pl - EBEBActive on city webpageUnknown2026-08-06City list
49Pleasant Grove Rd @ WalMart - EBEBActive on city webpageUnknown2026-08-06City list
50Providence Pkwy @ Providence Trl - WBWBActive on city webpageUnknown2026-08-06City list
51S Rutland Rd @ Beckwith Rd - WBWBActive on city webpageUnknown2026-08-06City list
52Golden Bear Gateway @ Vanner Rd - SBSBActive on city webpageUnknown2026-08-06City list
53Lebanon Rd @ Nonaville Rd - EBEBActive on city webpageUnknown2026-08-06City list
54Belinda Pkwy @ Providence Trl - WBWBActive on city webpageUnknown2026-08-06City list
55Leesa Ann Ln @ Darrington Way - WBWBActive on city webpageUnknown2026-08-06City list
56Old Lebanon Dirt Rd @ Kelsey Glen Dr - EBEBActive on city webpageUnknown2026-08-06City list
57Pleasant Grove Rd @ Old Pleasant Grove Rd - WBWBActive on city webpageUnknown2026-08-06City list
58Golden Bear Gateway @ I 40 On Ramp - SB (Covers WB Ramp)WBActive on city webpageUnknown2026-08-06City list
59Belinda Pkwy EB @ I-40 Ramp - EBEBActive on city webpageUnknown2026-08-06City list
60Beckwith Rd @ Summit Blvd - NBNBActive on city webpageUnknown2026-08-06City list
61Golden Bear Gtwy @ Beckwith Rd - NBNBActive on city webpageUnknown2026-08-06City list
62North Mt. Juliet Rd. NB @ I-40 / NorthboundNBActive on city webpageUnknown2026-08-06City list
63I-40 On-Ramps @ North Mt. Juliet Rd / WestboundWBActive on city webpageUnknown2026-08-06City list
64North Mt. Juliet Rd SB @ Division St. / South BoundSBActive on city webpageUnknown2026-08-06City list
65Hwy 70 WB @ Davidson County Line / WestboundWBActive on city webpageUnknown2026-08-06City list
66Hwy 70 EB @ Davidson County Line / EastboundEBActive on city webpageUnknown2026-08-06City list
67Pleasant Grove Rd @ WalMart - WBWBActive on city webpageUnknown2026-08-06City list
68South Mt. Juliet Rd. @ I-40 / Southbound on Mt. Juliet Rd @ I-40SBActive on city webpageUnknown2026-08-06City list
69South Mt. Juliet Rd NB @ Central Pike / North BoundNBActive on city webpageUnknown2026-08-06City list
70South Mt. Juliet Rd. @ I-40 / I-40 Eastbound On-RampEBActive on city webpageUnknown2026-08-06City list
71Lebanon Rd @ S Greenhill Rd EBEBActive on city webpageUnknown2026-08-06City list
72Lebanon Rd @ S Greenhill Rd SBSBActive on city webpageUnknown2026-08-06City list
73Lebanon Rd @ Sunset Dr - WBWBActive on city webpageUnknown2026-08-06City list
PUBLIC SPENDING

Contracts, invoices and commitments

Track actual spending, annual costs and long-term commitments separately.

2025-07-01Flock Safety

Safe City Year 1 invoice schedule

$185,000

Year 1

First scheduled invoice under the expanded agreement.

View source
2025-06-09Flock Safety

Modified 10-year Safe City agreement

$6,920,300

10-year payment schedule

The order form contains a separate cover-page total of $6,950,300; this discrepancy should be reconciled.

View source
2020-01-08Rekor Systems

Original Guardian Shield ALPR service

$89,000

Approximate annual cost announced during selection

MJPD described cost as near $89,000 per year pending final negotiations.

View source
2019-07-01Not selected

Initial ALPR program funding

$100,000

FY 2019–20

MJPD later reported that $100,000 had been allocated for the fiscal year.

View source
DECISIONS, VOTES & PUBLIC PARTICIPATION

Guardian Shield / Safe City timeline

Implementation, vendor changes, votes, policy amendments, network growth and whether citizen comment was located.

FY 2019–20 (beginning July 2019)

City funding set aside and vendor evaluation begins

Budget / planningVote record not yet locatedVerified public statement; underlying vote needed

MJPD later reported that the city had allocated $100,000 for the fiscal year and that police and IT personnel began evaluating ALPR technology.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Ordinance process followed in August–September 2019.

Source
August 26, 2019

ALPR privacy ordinance receives first reading

Law / ordinanceIndividual roll call not yet locatedVerified date; roll call missing

Ordinance 2019-40 received its first reading. It was designed to limit ALPR uses and provide public transparency.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Proposed restrictions included retention limits, no unmanned traffic enforcement, restrictions on nongovernmental disclosure, and publication of automatically shared governmental agencies.

Source
September 9, 2019

Ordinance 2019-40 adopted

Law / ordinancePassed; individual roll call not yet locatedVerified passage; roll call missing

The Board gave final passage to the city's ALPR ordinance, which was signed by then-Mayor Ed Hagerty.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day city retention ceiling, no automated traffic enforcement, no sale/provision to nongovernmental entities except as authorized by law, and website listing of agencies receiving automatic sharing.

Source
November 27, 2019

RFP released after roughly 60-day single-site pilot

Procurement / pilotAdministrative procurement stepVerified

The city released a request for proposals after testing one ALPR site for about 60 days. MJPD identified 37 proposed fixed-camera locations.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day internal retention was described, although state law allowed up to 90 days.

Source
January 8, 2020

Rekor selected as original Guardian Shield vendor

Vendor selectionCouncil authorization / contract vote not yet linkedVerified announcement; approval packet needed

After testing and review, the city and MJPD announced Rekor Systems as the selected ALPR vendor.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Images described as retained for 30 days.

Source
February 24, 2020

MJPD ALPR policy issued

Policy / oversightAdministrative policy; no council vote identifiedIssue date verified; original version missing

General Order 10D.6 lists an original issue date of February 24, 2020. The currently posted copy was later amended and now references Flock.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The current copy contains access, justification, logging, auditing, retention, sharing, and public-reporting rules; those provisions cannot all be assumed to have existed unchanged in 2020.

Source
April 1, 2020

Guardian Shield begins operation

ImplementationNo separate launch vote identifiedVerified

MJPD later identified April 1, 2020 as the start of the Guardian Shield program.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day retention was publicly described at launch.

Source
February 25, 2021

MJPD announces 100 successful interceptions

Performance reportNo voteVerified

MJPD reported that Guardian Shield had surpassed 100 successful interceptions since its April 2020 start.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Operational-success reporting; no audit or misuse statistics were included in this announcement.

Source
November 2024 — exact meeting date pending

Initial Flock authorization referenced as Resolution 67-2024

Vendor transitionResolution passed; exact roll call not yet verifiedPartially verified; official vote record needed

Later city records identify Resolution 67-2024 as an earlier authorization for the transition to Flock. A November 2024 report also described commissioners approving a Flock contract.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Later March 2025 records call Flock the new LPR vendor and describe approvals for transition.

Source
March 24, 2025

Board unanimously approves continued Flock LPR transition

Council vote5–0, unanimousVerified roll call

Resolution 31-2025 authorized the mayor to sign an agreement with Flock for the license-plate-reader program.

Yes: Art Giles; Bill Trivett; James Maness; Jennifer Milele; Scott Hefner

No: None recorded

Citizen comments: No citizen comments recorded in the reviewed meeting minutes.

Written comments: Not determined.

Agreement and transition documents were attached to the agenda item.

Source
June 9, 2025

Board approves modified 10-year Safe City agreement

Council vote / expansion5–0, unanimousVerified roll call and contract

Resolution 50-2025 authorized a modified Flock agreement that consolidated services and expanded the platform beyond ALPR.

Yes: Art Giles; Bill Trivett; James Maness; Jennifer Milele; Scott Hefner

No: None recorded

Citizen comments: Many citizens spoke on other topics; no Flock/ALPR comment was identified in the recorded citizen-comment summaries.

Written comments: Minutes note citizen/business emails were distributed to commissioners, but topics were not identified as Flock-related.

The order form lists a 30-day retention period. The current MJPD policy states 21 days, creating a contract-policy point that should be reconciled publicly.

Source
July 1, 2025

Billing and installation period begins under expanded agreement

Contract implementationAuthorized through Resolution 50-2025Verified contract term

The order form scheduled the first $185,000 invoice for July 1, 2025 and prohibited installation before that date.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Contracted products and actual deployed products should be tracked separately.

Source
February 4, 2026

MJPD announces Flock911 and Safe City upgrades

Technology expansionNo separate vote identified in the announcementVerified

MJPD announced Flock911, which delivers real-time 911 information to officers, and stated that its Flock Safe City designation provides ongoing automatic upgrades to the wider Flock suite.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The website timeline should distinguish council-approved contract authority from later administrative activation of individual products.

Source
June 15, 2026

MJPD ALPR policy amended

Policy / oversightAdministrative policy; no council vote identifiedVerified amendment date; redline missing

The currently posted General Order 10D.6 is marked amended June 15, 2026.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Current policy calls for 30-day system audits, monthly records, annual public reporting, and 21-day retention.

Source
August 6, 2026 snapshot

Public location list has grown from 37 proposed entries to 73 active entries

Network growthExpansion votes by location not yet tracedVerified current list; physical-camera count requires clarification

The current Guardian Shield page lists 73 active ALPR location/direction entries, compared with 37 proposed locations in November 2019.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The current policy requires annual reporting of camera totals, but the historical expansion path is not evident from one consolidated public timeline.

Source
PUBLIC USE LOG

When MJPD says Guardian Shield mattered

Catalog police releases, Facebook posts, news articles and records with a precise description of ALPR’s role.

ALPR triggeredALPR assistedHistorical searchExplicitly not ALPRNo ALPR mentionedUnclear
2026-05-31MJPD Guardian Shield spreadsheet

Missing-person vehicle alert led officers to vehicle and wanted passenger

ALPR triggered officer response

Result: Missing person located and welfare checked; passenger with warrants transported to jail.

What the source says: MJPD says Flock cameras alerted officers to the missing-person vehicle.

Entered from MJPD public successful-interceptions spreadsheet; underlying case report not yet reviewed.

Open source
2026-04-30MJPD Guardian Shield spreadsheet

Investigative hotlist alert used to locate fleeing suspect

ALPR triggered officer response

Result: Vehicle stopped; suspect detained and transported to Wilson County Jail.

What the source says: A locally created investigative alert in Flock triggered the response.

Useful example of a locally created investigative alert rather than an automatic stolen-vehicle hit.

Open source
2026-02-11MJPD Guardian Shield spreadsheet

Investigative alert connected to counterfeit-money investigation

ALPR triggered officer response

Result: Wanted suspect detained; other passengers also arrested for separate warrants/drug charges.

What the source says: MJPD says Flock generated an alert from a locally added investigative entry.

Underlying incident report not yet reviewed.

Open source
2025-01-30MJPD Guardian Shield spreadsheet

Stolen Chrysler alert preceded attempted stop and later arrests

ALPR triggered officer response

Result: MJPD attempted a stop; vehicle fled; surrounding agencies later located it and two people were arrested.

What the source says: MJPD says Guardian Shield alerted officers to the stolen car entering Mt. Juliet.

Shows an ALPR alert beginning a multi-agency response even when MJPD did not complete the initial stop.

Open source
CLAIMS VS. EVIDENCE

What the city says—and what would verify it

The goal is not to assume a claim is false. It is to identify the records that would demonstrate the safeguard is operating as described.

Retention

“Images not used for an investigation are generally retained no more than 21 days.”

Official claim only

Current public Guardian Shield page states 21 days; city ordinance allows up to 30 days.

Useful verification: Current configured retention setting, exception logs, and counts of records preserved beyond the standard period.
Official source
Auditing

“Every search is logged and subject to supervisory review and regular audits.”

Needs independent verification

Policy/public page describes logging and audits; aggregate audit results are needed to verify scope, frequency, findings, and follow-up.

Useful verification: Monthly audit reports, audit methodology, number of queries reviewed, exceptions, and corrective actions.
Official source
Access

“Only trained and authorized personnel may access the ALPR system.”

Needs independent verification

Public policy states restricted access. Current counts of users by role are not shown on the public page.

Useful verification: Authorized-user count by role, access reviews, account deactivations, and training completion in aggregate.
Official source
Tracking

“The system does not continuously track people.”

Statement requires context

Individual cameras create point-in-time vehicle observations. Practical movement reconstruction depends on network density, retained history, search features, and shared cameras.

Useful verification: Exact physical camera count, historical search capabilities, partner/private-camera access, and external network access.
Official source
Data sharing

“Information is shared only with authorized government agencies for legitimate law-enforcement purposes and required documentation.”

Needs independent verification

City publishes agencies with access agreements; aggregate access frequency and outside-agency query counts are not on the public page.

Useful verification: Outside-agency query counts, approvals/revocations, audit findings, and sharing changes by agency in aggregate.
Official source
Search justification

“Officers must have a documented investigative reason and, when required, reasonable suspicion to search the system.”

Needs independent verification

The policy states the requirement. Audit results can show whether case/call numbers and reasons are actually present and valid.

Useful verification: Aggregate number of queries missing/using invalid case references or requiring corrective follow-up.
Official source

Audit data

Awaiting records

No aggregate audit report has been entered yet.

SOURCE LIBRARY

Documents behind the site

Policies, ordinances, contracts, invoices, minutes, posts, reporting, laws and open-records responses.

DateTypeTitlePublisherSummaryLink
2019-09-09OrdinanceOrdinance 2019-40 — ALPR regulationMt. Juliet Board of CommissionersCity ordinance addressing retention, automated traffic enforcement, disclosure, and automatic sharing.Open
2026-06-15Police policyMJPD General Order 10D.6 — Automated License Plate Recognition ProgramMt. Juliet Police DepartmentCurrent amended policy covering use, query justification, audit trail, retention, audits, sharing, and reporting.Open
2025-06-09ContractFlock Safe City order formMt. Juliet / Flock SafetyTen-year Safe City agreement and payment schedule.Open
2025-06-09Meeting minutesBoard minutes — Resolution 50-2025Mt. Juliet Board of CommissionersPublished minutes showing unanimous approval of modified Flock Safe City agreement.Open
2025-06-02ContractFlock Safety Safe City order form — product and feature descriptionsCity of Mt. Juliet / Flock SafetyLists Falcon LPR, Condor PTZ, Raven gunshot detection, mobile trailers, FlockOS/Nova/FreeForm, video integration/Wing, Flock911, traffic analytics, DFR drones/radar and network/video-integration capabilities.Open
2026-08-06City webpageMJPD Drone as a First Responder program pageMt. Juliet Police DepartmentPublic program details including implementation/testing status, two strategically placed drone docks, one radar with citywide coverage and promised flight transparency portal.Open
2026-08-06City webpageMJPD recruiting page — Safe City, city-wide LPR and camera networksMt. Juliet Police DepartmentMJPD publicly describes an advanced Flock Safe City program, funded DFR program, city-wide LPR network and city-wide camera network.Open
2026-04-07State lawTennessee Public Chapter 672 / SB1879 — ALPR captured-data confidentiality sunset removedTennessee General AssemblyRemoves the scheduled sunset of the Tennessee public-records confidentiality provision for captured ALPR data.Open

Methodology

This is an independent public-source transparency project, not an official city website. It catalogs what Mt. Juliet and other sources publicly state, the records supporting those statements, and gaps where additional documentation would be useful.

Evidence discipline: “contracted capability” is not “deployed”; “city-listed ALPR location” is not automatically one physical camera; and “police policy” is not the same as a city ordinance or state statute. The transparency score measures public verifiability only.

Use-log limitation: a curated list of posts is not a statistical sample of all police stops or arrests. Do not calculate the percentage of arrests caused by ALPR unless a complete official denominator is obtained.