Contractual opt-out
The order says Oak Point may opt out during the 60 days following implementation of the first Flock hardware. After that period, it says the City may not terminate and must pay invoices for the remainder of the term.
Contract and cost
The 180-day policy is not the only clock in the record
The available order, Council action, and invoice describe different obligations and time periods. A written implementation record is needed to show how they fit together.
Three different clocks
Policy review and contract exit are not the same thing
The Council's public action did not state that Flock had accepted a matching contractual exit date or that the cameras would be removed on day 181.
Council policy period
The July 22 motion approved the ALPR policy for 180 days. The separate camera motion did not say the devices must be removed or disabled at the end of that period.
Vendor term and renewal
The order states 12-month initial and renewal terms and provides for automatic renewal unless either party gives notice at least 30 days before the current term ends.
What Oak Point contracted for
A broader package than four ALPR cameras
These are contract facts. They do not prove that every listed device was installed or every feature was used.
Price and term
$50,000 annual recurring amount
Initial term: 12 months. Renewal term: 12 months. Data retention: 30 days.
Cameras
Eleven devices listed
Four license plate readers, two LTE pan-tilt-zoom video cameras, and five solar pan-tilt-zoom video cameras.
Software and services
More than hardware
FlockOS Starter, Enhanced LPR, and Traffic Analytics are listed in the order.
Side-by-side
Why the 180-day period still needs a written answer
The public discussion referred to a six-month trial, but the adopted actions did not place every part of the program on the same 180-day clock.
| Issue | July 22 Council action | June 2025 vendor order | What remains unclear |
|---|---|---|---|
| ALPR count | Two additional ALPRs, for a stated City total of four. | Four ALPR cameras listed. | Whether the July action was implemented under the existing order or another written agreement. |
| Product scope | The Police Chief confirmed items 6D, 6E, and 6F concerned ALPRs, not Condor/PTZ cameras. | Four ALPRs, two LTE PTZ cameras, five solar PTZ cameras, FlockOS Starter, Enhanced LPR, and Traffic Analytics. | The status and authorization of non-ALPR products. |
| Time period | The ALPR policy was approved for 180 days. | A 60-day post-implementation opt-out within a 12-month initial term, followed by a 12-month renewal term and subject to automatic-renewal language. | Whether Flock accepted any 180-day limitation and whether the contractual opt-out had already ended. |
| End of period | The camera motion did not state the cameras would be removed or disabled after 180 days. | The order describes renewal unless notice is given. | What happens to cameras, data access, and vendor services on day 181. |
Term dates and invoice
A signature date is not enough to calculate every deadline
The general order terms tie term commencement to product-dependent events, including installation and validation for hardware and execution for software. For a package containing multiple products, the earliest applicable start controls.
The reviewed records do not identify all of those dates, so the exact initial-term end, non-renewal deadline, and renewal status should not be calculated from the June 11 customer-signature date alone.
Flock later issued invoice INV-75091 for $50,000 on September 24, 2025, with an October 24 due date. That proves billing, not payment.
Records still needed
Complete the public cost record
The City should publish the payment record and fund, first validated installation date, operative term dates, any renewal or non-renewal notice, and any amendment implementing the July 22 action.