Part 2: Lawton’s Digital Guardrails — City Details Oversight for Facial Recognition and Surveillance Technology

Lawton, Okla.– In Part 1, the Lawton Town Crier examined Lawton’s expanding public safety technology ecosystem, including automated license plate readers, facial recognition technology, and broader policy questions surrounding surveillance governance. In this follow-up, the City of Lawton provides detailed responses regarding oversight, access controls, system integration, and transparency. Missed Part 1? Read our initial investigation into Lawton’s expanding public safety technology ecosystem here.


Part Two: A Closer Look at the City’s Stated Guardrails

In Part 1, the Lawton Town Crier examined Lawton’s expanding public safety technology ecosystem, including automated license plate readers, facial recognition technology, grant funding, and broader governance questions surrounding surveillance infrastructure.

This follow-up takes a closer look at the City’s own stated guardrails—how officials say access is restricted, what oversight mechanisms are intended to exist, how the technology is reportedly structured operationally, and what accountability questions remain.


Who Has Access?

One of the central questions raised in the original reporting involved who may ultimately access surveillance-related technologies.

Public planning materials referenced broader municipal departments within larger modernization initiatives, prompting questions about whether surveillance capabilities could eventually extend beyond traditional law enforcement functions.

City Manager John Ratliff says current access is tightly restricted.

“Departments outside of law enforcement do not have access to the City’s Flock Safety system or facial recognition technology software. At this time, there are no plans to expand access beyond authorized law enforcement personnel.”

He also emphasized the rationale for that restriction.

“Due to the sensitive nature of the information collected through license plate reader technology, access is intentionally limited to ensure compliance with policy requirements and appropriate use standards.”

That response draws a distinction between broader planning concepts and present-day operational reality.

Still, one question remains open:

If expanded access is not contemplated, why are broader non-law-enforcement departments reflected in larger planning frameworks at all?


What Technology Is Actually Connected?

Public concern often centers not just on what technologies exist—but whether they connect.

Can automated vehicle tracking integrate with facial recognition?

Can police systems share data automatically?

Is the city building a unified digital surveillance platform?

Ratliff acknowledged limited interoperability between certain public safety systems.

“Regarding systems integration and transparency, certain public safety systems are capable of limited integration in order to improve operational efficiency for responding officers.”

He offered one example:

“For example, certain CAD-related information may interface with other authorized law enforcement platforms used during emergency response operations.”

But he drew a specific line around facial recognition software.

“However, the facial recognition technology software itself will remain a standalone system and will not directly integrate across all City platforms.”

That clarification narrows the scope of operational integration.

At least under the City’s current stated framework.


Flock’s Current Operational Scope

The City also addressed questions regarding Flock Safety’s broader capabilities.

Ratliff noted that while Flock offers additional traffic-related tools, Lawton is not currently using them.

“While Flock does offer additional tools related to traffic analytics, the City does not currently utilize or subscribe to those services and has no plans to do so.”

That statement is important.

Public discussion about surveillance technology often assumes deployment of full vendor capability.

The City says that is not the case here.


The Budget Changed

The original reporting noted that public records reflected a grant award of $13,612, while later cost discussions suggested higher figures.

Ratliff provided clarification.

“Regarding budgeting and sustainability, the City initially received a grant award of $13,612 based on the original quoted cost of the facial recognition software.”

He said vendor pricing later changed.

“Due to delays in grant processing and subsequent pricing changes from the vendor, the updated cost increased.”

According to Ratliff, the City negotiated a reduced first-year cost.

“Following discussions with the company, the City was able to negotiate a reduced first-year cost of approximately $20,000.”

He also indicated future vendor evaluation remains underway.

“The City is currently evaluating additional vendors and comparable software solutions to ensure cost effectiveness moving forward.”

That provides substantially more budgeting context than was publicly available during the initial reporting.


Oversight and Accountability

Perhaps the most significant new detail involves oversight.

Who ensures facial recognition technology is used appropriately?

Ratliff pointed to a formal governance structure.

“In regard to oversight and accountability, the City’s Facial Recognition Technology (FRT) Policy requires the designation of an FRT Coordinator.”

That individual will have compliance responsibilities.

“The FRT Coordinator will oversee compliance with the policy, including procedures governing the use of the technology and auditing requirements.”

Potential misuse, he said, would be formally reviewed.

“Any potential misuse or policy violations would be reviewed through the appropriate supervisory and internal review processes, including involvement from Internal Affairs when necessary.”

That response materially expands the public understanding of the City’s stated accountability model.

But practical implementation questions remain:

  • Who is the designated FRT Coordinator?
  • Has that appointment already occurred?
  • How often are audits conducted?
  • What data is included in audit review?
  • Are audit logs retained?
  • Will audit findings be public?
  • How many authorized users exist?

These are natural follow-up accountability questions.


Transparency Without a Dedicated Portal

The City also addressed whether it intends to proactively publish usage data or oversight reporting.

The answer was no.

“At this time, the City is not planning to establish a centralized transparency portal specific to these technologies.”

Instead, the City says transparency will continue through existing mechanisms.

“The City remains committed to transparency through its existing processes, including public information requests, media engagement, and established public information practices.”

That means public oversight remains primarily reactive rather than proactively published.


The Bigger Picture

Part 1 focused on infrastructure, policy adoption, and the broader technology environment.

Part 2 focuses on the City’s explanation of current governance.

Taken together, both perspectives matter.

The first documents the technology environment.

The second explains how city leadership says those systems are currently constrained.

The larger public policy question remains unchanged:

How are evolving public safety technologies governed in practice?

Lawton’s response provides several notable assurances:

  • law enforcement-only access
  • no current expansion beyond authorized users
  • standalone facial recognition deployment
  • designated oversight through an FRT Coordinator
  • audit and supervisory review mechanisms
  • Internal Affairs involvement for potential misuse
  • continued transparency through existing records processes

Those statements provide important context.

As with any governance framework, the next public accountability question becomes documentation, implementation, and auditability.

That remains an ongoing reporting area.


Transparency & Reporting Methodology

This report is based on written responses provided by City Manager John Ratliff to questions submitted by the Lawton Town Crier as part of its reporting on Lawton’s public safety technology systems.

Part 1 focused primarily on infrastructure, public policy, and broader governance questions reflected in planning documents, City Council materials, and previously obtained public records.

This follow-up focuses more specifically on the City’s stated operational guardrails, oversight framework, and official explanations regarding implementation.