Your city how-to

How to end a surveillance contract in your city, step by step.

A working kit. What to request, how to read it, how to handle a records office that stalls, what to say at the podium so it produces a document, how to end the contract through the budget, and how to put permanent rules on the ballot.

Fill in the brackets.

Every name, statute number and contract clause number from the city this came from has been removed. What is left is the method. Where you see a bracket, put your own city's fact in it.

[CITY][STATE][VENDOR][PLATFORM NAME][RECORDS CONTACT][CLERK][CITY ATTORNEY][CHIEF][YOUR NAME][ADDRESS][PHONE][EMAIL][PUBLIC RECORDS ACT CITATION][RESPONSE DEADLINE][CONTRACT DATE][ANNUAL AMOUNT][TOTAL AMOUNT][SECTION NUMBER]

Get the documents

Do this on day one. Do not attend a meeting, post anything, or talk to a council member until you have read the three documents below. Everything else here depends on having them.

1

Identify the three documents you need.

The order form

The itemized list of what the city bought: camera counts and types, software modules, gateways that connect other cameras, analytics packages, search tools, any data-fusion or real-time crime center platform, and the price by year. It is usually more than plate readers.

The master services agreement, or the vendor's terms and conditions

The contract that governs the data. In many vendor agreements the order form incorporates a set of terms by reference, sometimes by a web link, and the terms at that link may have changed since the city signed. You need the version in effect on the signature date.

The council packet, agenda and minutes for the approval vote

Plus the recording of any committee meeting that heard it first. Read the agenda wording. Read the resolution's recitals, the “whereas” clauses. Recitals often mention a trial period, a negotiated discount, or crimes solved, and each of those implies records that exist somewhere.
2

Look in these places first, in this order. Give it one day.

Method 1. The city's website

Search for the vendor's name, “license plate,” “camera,” “agreement,” and the approval year. Look under the council or clerk pages for agendas, packets and minutes. Many cities post full packets as PDFs with the contract attached.

Method 2. The city's meeting portal or video channel

Cities use hosted portals that hold packets and recordings for years. Open the meeting on the approval date and the committee meeting before it. Download the packet PDF and the video.

Method 3. The clerk's office

Call or visit. Ask for the packet for the meeting on [DATE] and the executed agreement with [VENDOR]. Clerks often hand these over on request without a formal filing. If they do, get the executed copy with signatures, not the draft that went in the packet.

Method 4. Other cities

Vendors use standardized contracts. Search for “[VENDOR] master services agreement” plus “pdf” and the names of nearby cities. A neighboring city's posted contract shows you the structure and the section numbers to expect, and it may show what another city negotiated out.

Method 5. The vendor's own website

Save a dated copy of the currently posted terms and any “data ownership” or “plain English” explainer page, with the URL and date visible. These change without notice. A saved copy proves what was there.
3

If any of the three is not in your hands by the end of that day, send a records request for it the same day.

Do not wait for the clerk to get back to you. Do not wait for a meeting. Use the short letter below. It starts the statutory clock, and everything the records office does after that is on the record.

Day-one request

To: [RECORDS CONTACT], City of [CITY]
cc: [CLERK], City Clerk; [CITY ATTORNEY], City Attorney
Subject: [STATE] public records request: [VENDOR] agreement, order form, and approval packet (Items 1 through 5)
Date: [DATE]
Under [PUBLIC RECORDS ACT CITATION], I request copies of the following public records. I am a resident of [STATE]. Please provide electronic copies by email or download link where the records exist in electronic form.
1. The fully executed agreement between the City and [VENDOR], including every order form, exhibit, addendum, and amendment, with every signature, name, title, date, and purchase-order number, and any electronic-signature certificate of completion.
2. Every document incorporated into that agreement by reference (terms and conditions, implementation guide, information-security addendum, third-party terms, product-specific terms, state-specific terms), in the version in effect on the date the City signed.
3. The agenda, packet, staff report, resolution or ordinance, and minutes for every council or committee meeting at which the agreement was presented, discussed, or approved.
4. The audio or video recording of each of those meetings.
5. The invoice(s) and payment record(s) for the agreement to date, and the date of first installation or first camera validation.
If the City has no responsive record for a numbered item, please say so in writing for that item. I understand a response is due within [RESPONSE DEADLINE] under [CITATION]. Please contact me at [PHONE] or [EMAIL] if any part of this request is unclear; I would rather narrow the scope than have an item denied as overbroad. Thank you.
Respectfully,
[YOUR NAME] · [ADDRESS] · [PHONE] · [EMAIL]
4

While you wait, work with what you have.

Read whatever you found in Step 2. If you have a recording, transcribe it yourself and time-stamp every statement by the vendor's representative and by the police chief. That transcript will be the most quoted document in your campaign. Start the tracking log (Chapter 11) with this first request as row one.
5

When the executed agreement arrives, check it before you rely on it.

Confirm it has signatures, dates and a purchase-order number. Confirm the billing terms match the invoice. If what arrives is an unsigned draft with a blank signature page, log it as partial and put the executed copy at the top of your follow-up letter (Chapter 8).

Read the contract: the clause checklist

Vendor surveillance contracts share a structure. Go through your city's agreement with this list. For each item, write down the section number and copy the exact sentence into a file. You will use those section numbers in every request and every council question.

Find the data ownership and license clause.

Look for a sentence saying the city “owns” the data, followed by a grant to the vendor of a license to use it. Write down every adjective on the license: irrevocable, perpetual, worldwide, royalty-free. Ownership with an irrevocable, perpetual, worldwide license attached is not what an official means when they say “we own the data.”

Find the anonymized or derived data clause.

Look for a right to anonymize customer data and use or distribute the result, and for the words machine learning, train, improve the services, or other offerings. Look for a definition of the vendor's own property that includes derivative works, outputs, models, or results generated by or through the services. This is the clause under which residents' movement data becomes the vendor's product.

Find the third-party recipient clause.

Look for what happens when the city connects an integration partner or shares with another agency, and whether the recipient may retain data longer than the city's own retention period. Look for any “shall not” that binds the recipient. Often there is none. Write that down too.

Find the vendor-disclosure clause.

Look for language allowing the vendor to disclose footage to “law enforcement authorities, government officials, and/or third parties” on a “good faith belief” that disclosure is “reasonably necessary.” Note whether the city gets notice.

Find the hosting and subcontractor clause.

Look for permission to use third parties to host or deliver the service. You will later ask which company, which region, and whether any of it sits outside the country.

Find the retention and deletion clause.

Write down the retention period and whether deletion is “rolling.” Note whether deletion applies to originals only and whether the city must download anything it wants to keep.

Find the hardware ownership clause.

Note who owns the cameras and whether the city may move them.

Find the survival clause.

Look for the list of sections that survive termination. Check whether the data license section is on it. If the license is perpetual but the section does not survive, flag it for the attorney. If it does survive, the city's exit does not end the vendor's rights.

Find the liability cap and the dispute forum.

Note the cap, often twelve months of fees, the exclusions for consequential damages and data loss, the governing state's law, and any mandatory arbitration. A city that agreed to another state's law and binding arbitration has agreed to something worth a written council question.

Find the non-appropriation clause.

Copy it word for word, including any timing condition such as “at the end of the applicable fiscal year” and any notice period. This clause is the exit. Chapter 14 is built around it.

Find the list of documents incorporated by reference.

Note every one that lives at a vendor-controlled web address and any sentence allowing the vendor to modify them. Ask the city to produce each as of the signature date.

Find the term, renewal, and non-renewal notice.

Note the initial term, whether it auto-renews, and how many days before the term ends the city must give notice. Calendar that date the moment you learn the start date of the term.

Find the permitted-purpose definition.

If it is broader than law enforcement, for example “prevention of commercial harm,” note it.

Look up your state's law

You do not need to become a lawyer. Find the provisions below, copy their exact words into a file, and note the year of the most recent amendment. Use the official code or the legislature's act PDFs. Do not rely on a commercial legal site alone.

Look up your public records act.

Find the response deadline, three working days in some states, ten in others, “reasonable time” in some. Find the rule on segregating exempt from non-exempt material. Find whether records held by a private vendor performing a public function are still public records; many states say yes by statute or by court decision. Find what a denial must contain. Find the appeal route and its timeline, whether a citizen who wins in court recovers attorney's fees, and the penalty for a negligent violation. Find the exemption most likely to be cited against you, usually an open-investigation exemption, and its exact limits.

Look up your state's license plate reader statute, if there is one.

Find the list of purposes for which a government entity may collect or use captured plate data. Find any sentence saying data shall not be used or shared for any other purpose. Find the retention cap. Find the definition of captured plate data and whether it includes data derived from the system; if it does, anonymized output is still covered. Find any prohibition on selling, trading or exchanging the data. Find any periodic reporting or audit requirement. Find any private right of action and its damages, and any attorney general enforcement provision. Note who the statute allows to hold or process the data and whether a vendor is among them.

Look up your audio recording and wiretap law.

If the order form includes cameras capable of capturing audio, the consent rules matter.

Look up any statute on automated traffic enforcement.

Some states prohibit it and require that device data not tied to a citation or investigation not be retained.

Look up your open meetings act.

Find the requirement to record meetings, how long the recording must be kept, and whether the city must post video. Most states do not require posting.

Look up your municipal budget statute.

Find the fiscal year, the date by which the mayor or manager must submit the budget, the date by which the governing body must adopt it, and the governing body's power to amend or revise the budget after adoption. You need these for Chapter 14.

Look up your local initiative and referendum rules.

Find whether the ballot title must be certified by a clerk or other official before any signature is collected. Find the signature count formula. Find the filing window before an election. Find whether initiated measures may go only to regular elections or also to special elections. Find the rules for a referendum on an ordinance the council has just passed, especially the number of days after passage. Find the canvasser requirements. Find any requirement to circulate the certified text verbatim. You need these for Chapter 16.

Look up council referral.

Some states let a council refer a proposed or adopted ordinance to the voters by its own vote, with no signatures. Find the vote threshold and the election timing.

Look up the tampering-with-public-records statute.

You will cite it once, in a preservation request, in a non-accusatory sentence.

Look up one or two court decisions.

On the vendor-custody question and the definition of a public record. Cite them by name and reporter, and only after reading them.

Write records requests that get answered

Most records offices are not malicious. They are busy, they triage, and they answer the requests that are easiest to answer and hardest to refuse. Write yours to be both.

Write one letter per subject.

Do not ask for all records relating to surveillance. That request gets denied as unreasonably burdensome, the denial goes in a file with your name on it, and it buries the eight narrow requests that would have been answered.

Send each letter as its own email on the same day.

Each starts its own response clock. A denial of one does not stall the rest. Letter the letters A, B, C and number the items inside them A1, A2, so that every later reference is unambiguous.

Tie every item to a quoted line.

Quote the contract section or the statute the item rests on, in the letter itself. An item that begins “Section [X] of the agreement provides that the vendor may [quoted words]. Please produce any record showing whether...” is difficult to call vague.

Ask for a specimen first.

Before asking for a full audit log, ask for one complete example record with every field the system populates. A specimen is narrow and low-burden, and it reveals what the system captures. Then ask for the full picture in the next item.

Ask for what the system already generates.

If the platform has an export, report or audit function, producing it is retrieval, not the creation of a new record. Say so in the letter.

State in writing that a written “no such record exists” is an acceptable answer.

Then every item produces a document either way.

Offer to narrow.

End with a sentence saying you would rather narrow the scope than have an item denied as overbroad. It is true, and it removes the excuse.

Copy the clerk and the city attorney.

On every request, and the chief if the records belong to the police department. Copying the attorney produces more careful responses.

Ask for electronic copies by email or download link.

Offer to pay the actual cost of physical media if that is easier for them.

Keep the tone of a person who expects to be answered.

No threats, no invented deadlines, no “I will be forced to.” The statute's deadline is the deadline. Cite it once.

The standing-requests block

Paste this block, adjusted to your state's citations, at the end of every request. It answers the four most common ways a records office narrows or refuses a request before anyone has to argue about it.

Standing requests that apply to every item above

If a record exists in the [PLATFORM NAME] platform or with any vendor rather than on a City server, it is still a public record. [CITE YOUR STATE'S DEFINITION OF A PUBLIC RECORD, AND ANY STATUTE OR DECISION APPLYING THE ACT TO RECORDS HELD BY A PRIVATE PARTY PERFORMING A PUBLIC FUNCTION]. Please obtain the records from the vendor rather than treating vendor custody as a denial.

Running an existing export, report, or audit-log function in a system the City already licenses is retrieval, not the creation of a record. I am not asking the City to compile information; I am asking it to produce what the system already generates.

[CITE YOUR STATE'S SEGREGABILITY PROVISION] provides that a request may not be denied because exempt information is commingled with non-exempt information, and that any reasonably segregable portion must be provided after the exempt information is removed. If any record is withheld in whole or in part, please identify the specific record, the specific exemption relied on, and release the segregable remainder.

If any item is withheld under [CITE THE OPEN-INVESTIGATION EXEMPTION], please state which item, and confirm whether an investigation is in fact open as to that record.

If the City has no responsive record for a numbered item, please say so in writing for that item. A written “no such record exists” is a complete and acceptable answer, and it is the answer I am asking for where that is the case.

I understand a response is due within [RESPONSE DEADLINE] under [CITATION]. If any item needs longer, please tell me which item and give the date the record will be available.

What to request: fourteen categories

Send one letter per category. The items under each are starting points; cut what does not apply and quote your own contract where the item refers to a clause.

Send categories A, B and C in the first wave, D through H in the second, and the rest in the third.

The executed contract and procurement

Request the fully executed order form and agreement with every signature, date and purchase-order number, and the e-signature certificate if one exists. Request every document incorporated by reference, as of the signature date. Request any request for proposals, bid solicitation, bid tabulation, sole-source justification, or competitive-bidding waiver. Request the city attorney's review of the agreement before execution. Request any record of which contract sections were explained to the council before the vote.

The pre-approval record

Request all drafts of the agenda item wording, the single highest-value item, because it shows who chose the words the public saw. Request all communications between any city official and the vendor before the vote, including pricing, scope, and the negotiation from list price to contract price. Request records of any trial or pilot period recited in the resolution: dates, equipment, agreements, evaluations, and the specific cases claimed. Request calendar entries, invitations and notes for every meeting, demonstration, lunch or site visit with the vendor. Request any individual briefing of a council member outside a public meeting. Request any non-disclosure, demonstration or evaluation agreement predating the vote.

The inventory

Request an itemized list of every camera and every integrated stream: identifier, device type, physical location, owner, installation date, which analytics are enabled on it, and the council action or budget line that authorized it, with “no council action identified” stated where that is the case. For every gateway that connects outside cameras, request its location, the number of streams connected, and each stream's owner. Request a reconciliation of any different camera counts stated by officials in different documents. Request any agreement with a private host of a camera. Request every right-of-way or highway permit for a device.

The audit logs

Request the organization audit log, complete export, from first system access to the date of the request: every search by every user, with user, date and time, search type, reason entered, case number, and devices searched. Request the same log filtered to every vehicle-attribute or plain-language search. Request the network audit: every search of the city's cameras by any outside agency. Request the outbound record: every search by a city user of any other agency's cameras. Request every search the system flagged as anomalous, and who cleared the flag, when, and why. Request every person who has held administrator rights, including vendor accounts. Request the current configuration of required fields and every change to it since account creation.

Anonymized or derived data and machine learning

Quote the clause. Request the named standard the vendor applies when it anonymizes data; a specimen or data dictionary showing which fields survive; any audit or attestation of the process; every communication in which the city asked what anonymized data consists of or whether its data trains models, and the vendor's replies; any record showing whether the city's data has in fact been used to train models; any opt-out request and its answer; any legal review of whether the clause is consistent with your state's “any other purpose” limit; and the city's position on whether derived data remains captured plate data under the statute.

Cloud hosting, subprocessors, and security

Request the name of the cloud provider; the region and whether it is a government cloud; whether data is stored, replicated or accessible outside the country; any criminal-justice information security addendum or certification; any state criminal-information-center vendor agreement; any security assessment or vendor risk review; any breach or security-incident notice; every account with access to the city's data, including vendor employees; how the city classifies vendor-hosted data under its retention schedule; and what happens to the data on termination.

Sharing settings

Request the current data-sharing and network-membership settings, every change to them since the account was created with dates and approvers, and the count of searches by outside agencies in the last ninety days.

Policies

Request every written policy, general order or procedure governing each component. If the only policy is titled “license plate readers,” ask in writing whether any policy governs the video cameras, the plain-language search tool, the live-911 video feature, and the data-fusion platform. State that a written “no policy exists” is a complete answer.

Statutory reporting and audits

If your state requires periodic statistical compilations or audits, request every one since the system went live, or a written statement identifying the periods not compiled. Send a parallel request to the state agency that is supposed to receive them.

Effectiveness

Request the list of cases in which the system was used, by case number and outcome; any record of a false hit, a wrong-vehicle stop, or a misuse complaint; and any analysis of a locally hosted alternative. If officials have said it has already proven its value, this letter fetches the proof or its absence.

Payment and grants

Request the invoices, the payment record with the fund and budget line, the date of first camera installation and validation, which starts the contract term, and every grant application or communication in which the vendor's products are named, including any pending application for drones or expansion.

Vendor communications materials and relations

Request every training or webinar on public communications or responding to criticism that any official was invited to or attended, with dates and names. Request every talking-points document, question-and-answer document, objection-handling guide, chief-to-council guide, template statement, or communications toolkit received from the vendor. Request all drafts of any public statement by the chief or mayor about the system and any record showing whether a city statement quotes a vendor-provided document. Request hospitality and event records: conference invitations, discount codes, lunches, travel, and who paid. Request any engagement of a lobbying firm concerning the system. Request meeting-platform recordings or automated summaries of vendor meetings transmitted to city accounts.

Your own data

If your state's statute gives a registered owner a right to their own captured plate data, request every detection of your plate, every search that returned it, any hot-list placement, any plain-language search that named you, and any sharing of your record outside the department. Decide with your attorney before putting a plate number or home address into a public filing.

The retention schedule and meeting recordings

Request the city's adopted records retention schedule; its email and text-message retention settings; any bulk deletion or purge since a set date; any preservation instruction issued to any vendor. If a posted meeting video is ever removed or replaced, request the timeline of who removed it and who directed it, every camera angle and audio channel from the meeting, and any written policy on editing posted recordings. If there is a pattern, request the instances, not the files, to keep the request narrow.

Template: a records request letter

Use this shape for every category letter. Replace the bracketed items. Keep the specimen item first.

Category request

To: [RECORDS CONTACT], City of [CITY]

cc: [CLERK], City Clerk; [CITY ATTORNEY], City Attorney; [CHIEF], Chief of Police

Subject: [STATE] public records request: [subject of this letter] (Items [A1] through [A8])

Date: [DATE]

Under [PUBLIC RECORDS ACT CITATION], I request copies of the following public records. I am a resident of [STATE]. Please provide electronic copies by email or download link where the records exist in electronic form.

This request concerns Section [SECTION NUMBER] of the [VENDOR] agreement in the [MEETING DATE] council packet, which provides:

“[QUOTE THE CLAUSE EXACTLY]”

I am asking for the records that show what that provision means in practice and what the City did to verify it.

SPECIMEN FIRST

1. [One complete example record, with every field the system populates, redacted as necessary. State that you are asking for one so that the item is narrow.]

THEN THE FULL PICTURE

2. [Item tied to the quoted clause.]

3. [Item tied to the quoted clause.]

4. [Communications in which the City asked the vendor about this, and the vendor's answers.]

5. [Any legal review, memorandum, or opinion addressing it.]

6. [The City's written position, or a statement that no record exists.]

[PASTE THE STANDING-REQUESTS BLOCK FROM CHAPTER 5]

Please contact me at [PHONE] or [EMAIL] if any part of this request is unclear. I would rather narrow the scope than have an item denied as overbroad. Thank you.

Respectfully,

[YOUR NAME]

[ADDRESS] · [PHONE] · [EMAIL]

Template: the follow-up letter when they stall, skip items, or deny without saying why

Send this letter the working day after a deadline passes, or the day a production arrives that does not match what you asked for. It stops a records office from managing you with partial productions, because it does the office's job for it: it acknowledges what came in, itemizes what did not, names the specific defects, and asks for nothing the statute does not already require. It is polite. It says in writing that you are not treating the delay as bad faith. Once sent, it is a dated document showing exactly what was owed on exactly what date.

Use it when any of these happens

The deadline passes with nothing.
Productions arrive with no cover letter saying which request they answer.
A numbered production has gaps.
One custodian's records start months after everyone else's.
The “contract” produced is an unsigned draft.
A one-page denial cites an exemption without identifying the request, the records, or the exemption's application.

Status and itemized list

To: [RECORDS CONTACT]

cc: [CLERK]; [CITY ATTORNEY]; [CHIEF]

Subject: [STATE] public records: status of my [DATE] requests, itemized list of records not yet received (Items 1 through [N])

Date: [DATE]

Dear [RECORDS CONTACT]:

Thank you for the records the City has produced to date. This letter does three things. It acknowledges what I have received, it provides an itemized list of the records requested on [DATE] that have not yet been received, and it identifies [two] deficiencies that need correction. Under [CITATION], responses to the [DATE] requests were due by [DUE DATE]. I am not treating the delay as bad faith; I am asking that the outstanding items now be completed, and this list is intended to make that easy.

Received to date, with thanks: [list each production by date and description, in neutral terms].

So that the record is orderly, one housekeeping request first:

1. For each production delivered to date, an itemized statement identifying which of my lettered requests and which numbered items that production responds to, and whether the production for that item is complete or partial. If any production was intended as complete for a given custodian, please say so in writing for that custodian.

Records requested [DATE] and not yet received, itemized:

2. The executed agreement. The agreement produced is an unsigned draft dated [DATE] with a blank signature page. Please produce the fully executed order form and agreement, including every signature, name, title, date, and purchase-order number, and the e-signature certificate of completion if one exists. If no fully executed copy exists in the City's possession, please state that in writing.

3. The production gap. Documents numbered [70] and [101 through 120] of the [DATE] production are missing. Please produce them, or state in writing why each was withheld, citing the specific exemption, and release any segregable portion.

4. [CUSTODIAN]'s records, [MONTH] through [MONTH]. My request covered communications from [START DATE] forward for all custodians. The production from [CUSTODIAN]'s mailbox begins [DATE]. Records produced from other custodians show responsive correspondence to and from [CUSTODIAN] throughout [PERIOD]. Please produce [CUSTODIAN]'s responsive records for that period.

5. [Letter X, item Y]. [One sentence restating the item.] Not received.

6. [Letter X, item Z]. [One sentence.] Not received.

7. The [DATE] denial letter. The one-page response citing “[QUOTED EXEMPTION LANGUAGE]” does not identify which request it responds to, the records withheld, or how the exemption applies to them. Please identify the request and items it was intended to answer; identify each record withheld; state whether [an investigation] is in fact open as to each; and produce the segregable remainder as [CITATION] requires.

A written “no such record exists” is a complete and acceptable answer for any numbered item, and where that is the case it is the answer I am asking for. My [DATE] request concerning [OTHER SUBJECT] remains pending on its own clock and is not superseded by this letter.

[PASTE THE STANDING-REQUESTS BLOCK]

Respectfully,

[YOUR NAME] · [ADDRESS] · [PHONE] · [EMAIL]

Three habits make this letter answerable only by producing records

Reference every earlier letter and item by its number.
Quote the office's own words back when describing a defect.
Never argue the merits of an exemption by email. State what the statute requires a denial to contain, and put the rest in the file for the appeal.

How to respond to a “no such record” or a refusal

Every response the records office sends, including silence, is one of seven types.

Identify the type, log it, and make the matching move. Do not argue by email. Do not send the whole request again.

1

Log it as received the day it arrives.

A denial, a “no such record,” and a non-answer are all logged as received, with the date and a one-line description. Silence past the deadline is logged as “overdue, nothing received” on the day after the deadline.
2

Identify which of the seven types you are holding.

1

Type 1: silence past the deadline.

Send the follow-up letter (Chapter 8) the next working day. Cite the deadline once. Itemize what is owed. Do not call, and do not send a second email asking whether they got the first one; the follow-up letter does that on the record.

2

Type 2: a partial production with no cover letter.

Send the follow-up letter with the housekeeping item first: map each production to a lettered request and numbered item, and state whether each is complete. Then list the gaps by number.

3

Type 3: a blanket denial citing an exemption without identifying the request, the records, or the application.

Reply in one paragraph: identify the request and items the denial is meant to answer; identify each record withheld; state whether the exemption's condition, for example an open investigation, is in fact met as to each record; and release the segregable remainder as [CITATION] requires. Quote the segregability provision. That reply is item 7 in the Chapter 8 template. If the denial targets a request made under a separate statutory right, for example your own plate data under a plate reader statute, say so and ask for the city's position on that statute directly.

4

Type 4: “the vendor holds it, we do not.”

Reply with the vendor-custody paragraph from the standing-requests block: cite your state's definition of a public record and the statute or decision applying the act to records held by a private party performing a public function, and ask the city to obtain the record from the vendor. Add: “If the City's position is that it has no contractual ability to obtain this record from its own vendor, please state that in writing.” Either answer is an exhibit.

5

Type 5: “this would require creating a record” or “we do not compile that.”

If the platform has an export or report function, reply that running an existing function is retrieval, and ask whether the City's position is that no export of the field exists. If the request truly asked for a compilation, narrow it: ask for the underlying records, or for a specimen, or for the fields the system already holds.

6

Type 6: “overbroad” or “unduly burdensome.”

Narrow it the same day, in writing, and thank them. Cut the date range in half, ask for one custodian, or ask for the specimen first. Keep the original item number so the record shows the same request narrowed, not abandoned. An offer to narrow that they refuse is worth more than a broad request they deny.

7

Type 7: a written “no such record exists.”

Do not argue. Say thank you in writing, log it, and file it as an exhibit. Then use it.
3

Decide whether to appeal.

Look up the appeal route you found in Chapter 3. In many states a requester may go to court on a short timeline and, if they substantially prevail, recover attorney's fees. Appeal only with your tracking log, the request, the response and your follow-up letter in hand, and only after talking to an attorney. A single clean denial of a narrow, well-quoted item is a better appeal than a pile of broad ones.
4

Use the negative.

For several categories, a written “no such record” is more useful than a document, because it is short, it is in writing, and it is hard to walk back. Write the finding in one sentence, with the item number and the date of the response, and put it in your exhibit index and your council one-pager.

What each negative proves

No record of the vendor's anonymization standard, no field list, no audit, and no correspondence asking about it.

The city granted a perpetual machine-learning license over residents' data and never asked what was in it.

The city cannot say which company hosts the data, in which region, or which vendor employees can reach it.

“We control our data” describes nothing in the contract.

The only policy covers plate readers.

Nothing governs the video cameras, the plain-language search tool, or the fusion platform, in the city's own words.

No record exists of the data-license sections being explained to the council before the vote.

The council approved a perpetual license without being told it was there. Put that sentence at the top of the non-appropriation one-pager.

The required statistical reports were never compiled.

Check your statute. Some tie non-compliance to the exclusion of evidence.

A vendor tells you its obligations run to its customer and it cannot act on your preservation request.

Route the request through the city as the contracting party, and keep the vendor's letter.

Template: a records preservation request

Send this in the first week, separately from any records request. It asks for nothing to be produced; it asks that material continue to exist. Vendor platforms delete on rolling cycles, often thirty days. Email systems purge on schedules. Text messages roll off phones. Building cameras overwrite. All of it without anyone deciding anything. A preservation request is the one letter that can legitimately cover the whole city.

Send a second, shorter notice directly to the vendor, asking it to suspend rolling deletion for the categories you name. Expect the vendor to answer that its obligations run to its customer. Keep that answer and route the request through the city.

Notice to preserve records

To: the Mayor; the City Attorney; the City Clerk; each member of the City Council; the Chief of Police; the Director of Information Technology; the records contact

Subject: Notice to preserve records: [VENDOR] agreement and related systems

Date: [DATE]

I am a resident of [CITY]. I have pending requests under [PUBLIC RECORDS ACT] concerning the City's [VENDOR] agreement and related systems, and I have submitted written questions to the Council on the same subject. I am writing to ask the City to preserve the records described below, and not to destroy, delete, overwrite, or allow the automatic expiration of any of them, until my pending requests are resolved.

I am asking for preservation, not production. The requests are separate and are already with the records contact. This letter asks only that the material continue to exist.

Two provisions bear on this and I set them out so that we are working from the same text rather than anyone's characterization of it. [CITE THE TAMPERING-WITH-PUBLIC-RECORDS STATUTE, QUOTING ITS OPERATIVE WORDS.] [CITE THE PENALTY PROVISION OF THE PUBLIC RECORDS ACT.] I raise these because most record loss is not anybody's decision. Retention rules run on their own. A preservation notice exists so that the systems get suspended before that happens, and so that no employee is later put in the position of explaining a routine deletion that no one thought about.

Records to be preserved, from [START DATE] through the resolution of my pending requests: (1) all records concerning the [VENDOR] agreement and every product named on the order form, including contracts, amendments, order forms, quotes, invoices, payments, configuration records, and correspondence; (2) all search, query, access, and audit logs for the platform, in their entirety; (3) all emails, text messages, direct messages, voicemails, notes, and calendar entries of [LIST OF OFFICIALS] concerning the agreement, my records requests, or my written questions, including on personal devices and accounts where the communication concerns City business; (4) all recordings of council and committee meetings and all video from cameras inside or on City buildings from [DATE] forward; (5) the City's records retention schedule, retention settings, and any deletion or purge activity affecting the categories above.

What preservation requires in practice: suspend automatic deletion and retention-based purging for the mailboxes and systems named; direct the affected officials in writing not to delete responsive material; direct [VENDOR] in writing to preserve the City's data and suspend rolling deletion as to the categories above; preserve backups covering the period rather than allowing them to rotate; and confirm to me in writing that this notice was received and circulated, and to whom.

This letter is not an accusation. I have no information that anyone has destroyed or intends to destroy anything. I am asking for a hold because the systems delete on their own, because my requests are pending, and because a hold costs the City little and protects everyone. I am glad to narrow any category the City finds unworkable.

Respectfully,

[YOUR NAME] · [ADDRESS] · [PHONE] · [EMAIL]

Keep the tracking log

Keep one file. Update it the same day anything is sent or received. It is the source of truth for “did we ask that yet.” Without it you will send near-duplicate requests, lose track of which productions answered which items, and the records office will not correct you.

Set up these columns.

Letter or set; item count; date sent; response due, calculated from your statute, counting working days and skipping holidays; date received; what was received, in one line; status, meaning done, partial, overdue, denied, or not yet sent.

Follow these rules.

Log a denial or a written “no such record” as received. Write a separate dated summary for every production: what was in it, item by item, quoted, and what it does not answer. Never let status live only in an email thread. When a response arrives with no cover letter, make the first line of your summary “no cover letter; does not identify which request it answers,” and make that item 1 of the next follow-up.

Keep an exhibit index alongside it.

Number every document you may ever quote: contract sections, transcript excerpts with time stamps, official statements with dates, records responses by item number. When you write a council question or a one-pager, cite exhibits by number. It keeps you from quoting from memory.

Build the statements-versus-contract table

1

Collect every public statement an official has made about the system.

The chief's letter or press statement, the mayor's replies to residents, remarks from the dais, social-media posts, and answers given at committee. Date each one and keep a copy with the source visible.
2

Build a two-column table.

Left column: the statement, quoted, with date and source. Right column: the contract clause on the same subject, quoted, with section number. Put “we own the data” next to the license grant with its four adjectives. Put “it deletes after thirty days” next to the derived-data clause and the third-party retention clause. Put “nobody outside the department can search it” next to the sharing clause and the network audit log. Put “it's just license plates” next to the order form's list of video cameras, gateways and search tools. Put “there is no AI” next to the plain-language search module on the order form.
3

Turn each row into a written question.

The form is always the same: “The [DATE] statement says [quote]. Section [X] of the agreement says [quote]. Please state in writing which one describes the City's rights.” Ask it at the podium and hand it to the clerk in writing the same night.
4

Watch for the forwarded letter.

If an official answers residents by forwarding the chief's public letter, check whether that letter mentions the data-license sections. It usually does not. The podium line is: “The letter describes how the department uses it. Section [X] describes what the vendor keeps. Which one is the contract?”
5

Check whether the statements came from the vendor.

If category L (Chapter 6) returns a vendor-supplied question-and-answer document, compare it to the chief's statement and the mayor's replies. If they paraphrase it, the record shows the city's public position was written by the vendor. State that with the two documents side by side and no adjectives.

Take it to the council

1

Learn the calendar.

When the council meets, when committees meet, when agendas post, often the Friday before, how long public comment is, and whether comment is limited to agenda items. Most councils take citizen comment under advisement, which means heard, no obligation, no record of a decision. That is normal. You create the record yourself.
2

Write your submission before the meeting and hand it to the clerk the same night.

Number the questions. Ask that it be entered into the record. Minutes summarize: “a resident spoke about cameras.” A written submission does not. It exists as a document, anyone can request it, and if the council later says nobody raised the point, the paper says otherwise.
3

Ask for a motion with a deliverable and a date.

Keep two phrases out of every ask. “Take under advisement” is the council's own phrase for doing nothing, and asking for it hands them the language to deny you with. “Investigate” is not a parliamentary action; there is no such motion, so there is no output, no date, and nowhere for it to land. Ask instead for a specific motion, and read it word for word so a member can repeat it.
4

Never say “I move” from the podium.

Only a seated member can move. Say: “I am asking any member of this council to make the following motion,” then read it. Put the motion on an index card and get it into a member's hands before the meeting, or give it to the clerk with a request that it reach a sponsor. A motion someone is physically holding gets made. A motion they would have to reconstruct from memory after public comment usually does not.
5

Make the written-opinion motion your first ask.

This motion ends nothing and commits no member to any vote. A member voting against it is voting against knowing what the contract says. It produces a dated legal opinion naming the deadline, which is a public record, an exhibit, and a calendar entry. If the defund later fails, the record shows the council was told the date in writing.

“I move to direct the City Attorney to provide the Council a written opinion on the City's rights under Section [NON-APPROPRIATION SECTION] of the [VENDOR] agreement, including the latest date on which notice may be given for termination effective at the end of a fiscal year, and whether any penalty or early-termination charge would apply.”

If you are being timed

“I'm asking a member of this council to move to direct the City Attorney to answer three questions in writing: what Section [X] of the [VENDOR] agreement requires, the last date notice can be given for termination at the end of a fiscal year, and whether any penalty applies. That's the whole request.”
6

Offer the referral as the fallback.

Lower cost for a member and harder to vote against. Never ask for a referral without a report-back date. An open-ended referral is where items go to be forgotten.

“I'm asking a member to move to refer the [VENDOR] agreement, and specifically the City's rights under Section [X], to the [PUBLIC SAFETY] Committee, with a report back to the Council by its second meeting in [MONTH].”
7

Keep three more motions on cards.

Sever the vendor line from the budget ordinance for a separate vote, because buried in a budget it passes on a voice vote and severed it has to be owned. Take the vote by roll call, so there are names for the record. Defer action pending the attorney's written opinion.
8
Ask six questions, each tied to a section number.
1. Section [X] grants the vendor an irrevocable, perpetual, worldwide license. Under what provision can the City revoke it?
2. Section [X] lets the vendor use anonymized data to train machine-learning models and for other products, permanently. Did the City ask what “anonymized” means, and is there a record of the answer?
3. Section [X] allows the vendor to disclose footage on its own good-faith belief. Does the City receive notice, and has it ever?
4. The order form includes video cameras, gateways for outside cameras, plain-language search across video, and a data-fusion platform. Which written policy governs each of those? If none, please say so in writing.
5. Which company hosts the data, in which region, and has the City seen that company's contract?
6. Section [X] allows termination on non-appropriation at no penalty. What is the last date notice can be given for termination at the end of this fiscal year?
9

Give each council member one page.

Quote the non-appropriation clause. Quote the chief's own written deference line if the records contain one; “happy to do whatever the Council thinks best” appears in many records. State the count of resident comments and emails. List the nearby cities that have already exited. End with “your constituents, your exit.” No adjectives.
10

Give them the exit.

Members who voted yes need a way to vote no without saying they were wrong. Say it for them: the public was never told, the council was told some things the contract does not support, and the contract has a no-penalty exit the vendor itself wrote.

End the contract by non-appropriation

It needs no court, no ballot, no findings, and no proof of anything.

Most vendor agreements with municipalities contain a non-appropriation clause, because municipal budgets are annual by law and the vendor knows it. The clause typically says that if funds are not appropriated for a future fiscal year, the customer may terminate, on some number of days' written notice, without penalty. This is the exit. A council may decline to fund a contract for any reason or none.

1

Read the clause word for word.

Some versions allow termination on thirty days' notice at any time. Others allow termination only “at the end of the applicable fiscal year upon thirty days' written notice,” which is two conditions: the notice period and the termination date. The difference decides whether your city exits this year or next.
2

Line it up with your budget statute.

If your fiscal year is the calendar year and the clause requires termination at fiscal year end with thirty days' notice, notice must be in the vendor's hands by roughly December 1 for termination on December 31. Now look at when your council adopts the budget. In many cities the finance committee meets in late November and the council adopts in December or January. If so, the budget vote happens after the notice deadline has passed. Miss it and the earliest exit is the following December 31: one more year of cameras and one more annual payment.
3

Do not wait for the budget vote. Get Motion A made in the month before the notice deadline.

It is a resolution, not a budget amendment. Give the sponsor's staff the recitals: the agreement's date and amounts; Section [X] quoted verbatim; the budget statute's fiscal year and the governing body's power to revise; that termination under Section [X] carries no penalty; that timely notice is required for termination at fiscal year end.

“I move the adoption of a resolution stating that the City Council does not intend to appropriate funds for the [VENDOR] agreement in the fiscal year beginning [DATE], and directing the Mayor to deliver written notice of non-appropriation to [VENDOR] under Section [X] of that agreement not later than [DATE], so that termination is effective at the end of the current fiscal year.”
4

Get Motion B made at budget adoption.

The confirming act. If your statute allows adoption as late as February, that extra time does not extend the notice deadline. Do not let anyone use the later adoption date to argue there is no rush.

“I move to amend the proposed [YEAR] budget by striking the appropriation of [ANNUAL AMOUNT] for the [VENDOR] agreement from the Police Department budget.”
5

If there is no majority yet, use the fallbacks.

The written-opinion motion, the severance motion, the roll-call motion and the deferral motion (Chapter 13) each cost a member less than a defund vote and each produces something usable.
6

Prepare the answers to the objections.

“We signed a multi-year contract, we can't cancel.”

Section [X] is in the contract the City signed. Read it aloud.

“There will be a penalty.”

Ask which provision, in writing.

“This would prejudice a creditor.”

Declining to appropriate for a future year is the exact act the clause contemplates. A vendor that bargained for a non-appropriation remedy is not prejudiced when it is used. Ask the city attorney to address it in writing.

“This is a public safety decision, not a budget decision.”

The council appropriates, which makes it a budget decision by definition. And a local-control ordinance keeps hot-list alerts. The question is who controls the data.

“The chief wants it.”

Quote the chief's own deference line if the records contain one.
7

Calendar the non-renewal date too.

Separately from non-appropriation, the agreement has an initial term that runs from a start event, often first camera validation, and auto-renews unless notice is given some number of days before the term ends. The moment a records response gives you the start date, calculate the term end and the notice deadline, and put both on a calendar with a reminder.
8

Collect the precedent.

Find every city in your state and region that has ended, suspended or declined to renew a contract with the same vendor in the last year, and how they did it: council vote, administrative decision, non-renewal. Request their council minutes and termination letters. A council that can say “we would be joining five named cities, not going first” votes differently from one that thinks it is alone.

Write the ordinance

A non-appropriation vote ends one contract. It does not stop the next one.

The permanent fix is a local ordinance that governs all surveillance technology, whoever the vendor is.

1

Decide what the ordinance requires.

It bans nothing. Before any surveillance technology is acquired or deployed, it requires: governing-body approval in an open meeting after public notice that names the technology plainly; a published written use policy covering purpose, access, retention, sharing and audit; annual public reporting; and periodic audits. It requires that data collected by city systems reside on city-controlled servers or under contract terms that prohibit vendor use, distribution or model training beyond providing the service. It preserves hot-list alerts for stolen vehicles and missing persons. It gives residents a way to object.
2

Draft it with an attorney.

Have the attorney check preemption, meaning whether state law reserves the subject; the definitions, so that “surveillance technology” is broad enough to cover video, audio, analytics and data-fusion platforms rather than just plate readers; and the enforcement section.
3

Write the one-sentence answer for “so you want to ban all cameras.”

“No. The ordinance requires approval, written rules, and audits. If a majority wants cameras under those rules, that is the outcome, decided in the open.”
4

Choose the route.

There are three: a council member sponsors it and a majority passes it, any month, no election; the council refers it to the voters by its own vote, if your state allows that, with no signatures; or residents put it on the ballot by petition. Chapter 16 covers all three.

Get it on the ballot

There are three ways to put the ordinance in front of voters, and a fourth to block an expansion. Do the state-law lookups in Chapter 3 before choosing one. Every deadline below is set by your state's law, and several of them cannot be recovered once missed.

Route A

Council sponsor, no election

The fastest route. It needs no signatures and exists whenever a majority can be found.

Recruit one council member to sponsor the ordinance. Use the one-pager from Chapter 13 and the records findings from Chapter 9.
Give the sponsor a clean draft reviewed by your attorney and a one-paragraph summary.
Ask for a first reading date in writing.
Fill the room at each reading with residents who each say one sentence.

Route B

Council referral, no signatures

A simple-majority referral of a proposed ordinance is an easier vote to recruit than passage.

Look up whether your state lets the council refer a proposed or adopted ordinance to the voters by its own vote, the vote threshold (majority or two-thirds), the deadline after adoption if any, and whether the referred question may go to a special election or only a regular one.
Ask the county clerk and the city attorney, in writing, what document the city files, with whom, and by what date to reach a given election. Ask whether the deadline differs between a proposed and an adopted ordinance.
Offer the referral to hesitant members as the middle path: “I'm not banning anything; I'm letting the voters decide.”

Route C

Citizen initiative, signatures

Look up the rules and write them on one page. The signature formula, often a percentage of the vote in the last mayoral election, so get the exact number from the clerk in writing. The filing window, often sixty to ninety days before the election. Whether initiated measures may go only to regular elections. Whether the ballot title must be certified before circulation. Who certifies in a city that lies in two counties. The canvasser requirements. Any verbatim-circulation rule. Any requirement to file the measure with the city clerk as well as the county clerk.
Draft three things with your attorney: the full text of the ordinance, the ballot title (the summary voters see), and the popular name (the short label). The ballot title is what gets challenged. Write it plainly, cover every material effect, and avoid adjectives.
Submit for certification before collecting a single signature, if your state requires it. Send the submission to the certifying official by the method the handbook specifies, get a stamped or emailed receipt, and calendar the official's review period. If the official rejects or edits the title, revise and resubmit; do not circulate the old version. Signatures collected before certification may be void.
Build the petition part. Include the certified ballot title, popular name and full text, verbatim, on every part. Include the signer fields your state requires: printed name, signature, address, date of birth or voter registration information, date. Include the canvasser's verification or affidavit block. If your city lies in two counties, prepare separate parts for each county's signers. Have the clerk look at a blank part before printing, and get the answer in writing.
Recruit and train canvassers. Give each one a one-page rules sheet: who may sign (registered voters of the city only), one county per part, no changes to the text, how to fill the verification, and what to say when asked what the measure does (read the ballot title; do not paraphrase). If your state registers or restricts paid canvassers, comply or use volunteers only.
Collect at least 125 to 150 percent of the required number. Some signers will not be registered, will live outside the city, or will sign twice. Check parts against the voter rolls weekly and retire canvassers whose parts fail.
File on time, in person, and get a receipt. File with the official your state names, before the deadline, with a cover letter listing the number of parts and signatures. Keep copies of every part.
Track the sufficiency determination. The clerk verifies signatures within a set period. Learn whether your state gives a cure period to collect more if you fall short, and how long. If a special council meeting is needed to certify the question to the election commission before ballot printing, request it in writing the day you file.
Watch the ballot deadlines. The election commission prints ballots weeks before the election, and absentee ballots go out earlier. Get the print date from the county in writing and work backward.
Campaign on the documents. The contract quotes, the records findings and the precedent list are the campaign. Use Chapter 18 for the objections.

Route D

Referendum on the next expansion

Vendors sell expansions: drones, more cameras, a fusion platform, a new network. Any new council approval usually opens a short window, often thirty days, for a referendum petition, and a referendum, unlike an initiative, may go to a special election in some states.

Watch every agenda posting, every week, for anything naming the vendor, drones, grants for surveillance equipment, or “safety products.”
Pre-draft the referendum petition now, with the attorney, so it is ready the day the item appears.
If your state requires certification, submit it the day the council approves the item, because the window starts at approval and certification takes days.
Collect and file within the window, following Steps 4 through 9 of Route C.
A filed referendum petition usually suspends the ordinance until the vote. Ask the city attorney to confirm that in writing.

Use the other lanes

You cannot open an investigation. You can preserve evidence, request records, build a record, and refer specific findings to the bodies that have investigative power. Each has a narrow door.

File an attorney general complaint when the records confirm use beyond the statute.

If your state's plate reader statute gives the attorney general enforcement authority, and some route it through the consumer protection act, a written complaint costs nothing and needs no lawyer. It creates an official record even if it is declined. File it on the day the records confirm that data was used or shared beyond the statute's permitted purposes: the machine-learning clause plus the “any other purpose” limit plus a “derived from” definition is the usual core. Attach the contract sections, the transcript excerpts and the records responses. Because vendor contracts are standardized, one attorney general action reaches every city in the state at once.

Ask a legislator to request an attorney general opinion.

In many states a legislator can request a formal opinion on a question of law, such as whether a perpetual vendor license to train models on captured plate data is compatible with the statute. It costs nothing, and the answer is official and can be quoted at any podium. Recruit the legislator in the months before the session.

Send a one-page brief to a state legislator before the next session.

Ask for: data on government-controlled servers; no vendor license to use, distribute or train models on captured data; an extension of the statutory definition from plate conversion to person and vehicle analytics and video; governing-body approval and a published use policy before deployment; and reporting duties with consequences. Find the legislators who already asked about vendor access at a committee hearing or rule review, and start with them.

File rulemaking comments.

If state agencies are writing plate reader rules under a recent act, the public-comment windows cost nothing and put your contract excerpts into an official docket where sympathetic legislators self-identify.

Pitch counsel and allied organizations with five sentences.

If your state provides a private right of action with liquidated damages, a suit is a decision for an attorney, with your own-plate records as the standing evidence. National civil-liberties organizations and public-interest law firms have taken these cases. Send the meeting footage and the contract with the pitch. Do not cite court decisions in public threads; keep them in a counsel's corner file for the attorney.

Refer to the legislative auditor or state auditor only with a documented procurement irregularity.

A purchase without required competitive bidding, or payments not matching an approved contract. Never on suspicion.

Refer to a prosecutor only with evidence that a specific record was destroyed by a specific person after they knew it was requested.

This is why the preservation letter matters. It creates the knowledge element if anything is destroyed later.

Keep an incident log if the city's attention turns toward you.

If enforcement activity at your home or business begins after you file requests or speak publicly, keep a same-day table: date and time, department and person, what happened, whether it was routine, what you did publicly in the prior thirty days, and what proof you have. Record what was said, not what you concluded. Do not confront the line employee. Give the log to your attorney, not to the council, and keep it separate from the surveillance file so that the weaker claim never drags down the stronger one.

Answer the common objections

Answer for the readers, not the arguer. One reply, then out.

“You use technology, you're a hypocrite.”

I signed terms of service for my internet. Nobody in this city signed one for these cameras. The council agenda is the only terms of service residents get; that is why we are on it.

“Your phone already tracks you.”

Everything my phone collects, I agreed to somewhere and can turn off or quit. There is no settings menu for a camera network on public streets.

“Stores film you already.”

A store camera watches one lot and answers to a company you can boycott. This is one networked system, searchable by software, run for the government, following everyone across the whole city. Scattered cameras do not make a movement history. A network is built to.

“Nothing to hide, nothing to fear.”

I lock my doors and seal my mail. Privacy is normal. And you do not get to decide you have nothing to hide; whoever runs the search decides what counts.

“It's a public street.”

One glance in public is public. A permanent, searchable record of everywhere everyone drove, kept on a private company's servers, is something else. And we are not asking a court to settle that; the city can set rules for its own tools.

“It solves crimes.”

Nothing on the table takes a tool away. The measure requires approval, written rules and audits. If the system works, the city can show the numbers, and it can work under rules. We have asked for the numbers in writing.

“Take the cameras down and crime goes up.”

If the deterrence numbers exist, the city can publish them. The burden of proof sits with whoever is spending public money.

“The chief says the city controls the data.”

Good. Then it will be easy to confirm in writing. When an official makes a claim about a contract, the contract is the answer sheet.

“It deletes after thirty days.”

Deleted from where? What about copies shared before day thirty? What does the vendor keep in any form? If the answer is “nothing and no one,” the city can say so in writing.

“It's just license plates.”

A plate is a person; it is registered to you, and reads joined across cameras become a movement history. And read what the city actually bought. It is on the public packet, and it is more than plate readers.

“The contract's signed, too late.”

City budgets are voted every year. Whether to fund any line next year is exactly what budget season is for, and the contract itself has a no-penalty exit for that case.

“Every city uses this.”

Dozens of cities have canceled or removed these systems since 2025. Pull the current count from a maintained tracker the day you use it, and link rather than assert.

“You're a handful of activists.”

The petition needs [NUMBER] verified voters of this city to reach the ballot, and then the whole city votes. You cannot get more local than that.

“You wrote this with AI.”

The quotes are from the city's own documents. Check the quotes, not the typist.

Follow the ninety-day checklist

Days 1 to 10

Get the three documents (Chapter 1); send the request the same day for any you cannot find. Build the clause checklist with section numbers and quotes. Look up the provisions in Chapter 3 from official sources. Learn the council calendar. Save dated copies of every vendor web page you may cite. Start the tracking log. Send the preservation request. Send the first three category letters (contract and procurement; pre-approval record; inventory), each as its own email.

Days 11 to 30

Send the second wave: audit logs, derived data, hosting and security, sharing settings, policies. Transcribe the committee and council recordings of the approval. Build the statements-versus-contract table. Attend the next council meeting with six numbered questions and a written submission for the clerk. Hand a member the written-opinion motion on an index card. Send the follow-up letter the day after the first deadline passes. Log every response and every non-response.

Days 31 to 60

Send the third wave: effectiveness, payment and grants, vendor communications, your own data, retention. Compile the precedent list of nearby cities that have exited and request their minutes. Draft the council-member one-pager. Identify the non-appropriation notice deadline against the budget calendar and put it on every ally's calendar. Draft the ordinance with an attorney. Look up the initiative and referendum rules and decide which route in Chapter 16 is realistic this cycle. Pre-draft the referendum petition for any expansion.

Days 61 to 90

Second council appearance with the reconciliation questions from the table. Recruit a sponsor for Motion A. Send a five-sentence pitch to one civil-liberties organization with the footage and the contract. If the records confirm use beyond the statute, file the attorney general complaint. Send a one-page brief to a state legislator. Update the log, the exhibit index and the one-pager. Keep watching the Friday agenda.

The posture

Read this chapter last, then read it again before every meeting, every email and every post. It is the rule that makes the rest of the kit work.

Quote documents. Do not characterize them.

A council will not respond to adjectives. It will respond, eventually, to its own contract read aloud next to its own public statements, with a written question attached. Every tool here is a way of getting words onto paper that someone official has to answer or refuse to answer. A refusal in writing is also a document. Over a few months the documents become a record that a council member can point to when voting to end the contract, that a reporter can quote, that an attorney general's office can act on, and that a court can read if it ever comes to that.

Be the resident asking the city about its own contract.

That is a position the city cannot comfortably attack. A person demanding everything from everyone, or a crusader, is a character the city knows how to handle. So, from the first email to the last podium appearance: you are not a litigant, you are not threatening anyone, you are asking for written answers, and you are keeping every one of them.

Never say “the cameras are illegal.”

Say what the contract says, say what the statute says, and ask how the two fit together.

Never argue “the council didn't know.”

Councils were usually told it was cloud-hosted, on the record, and they asked reasonable questions. Argue instead that the public was never told, because the agenda item said “safety products,” and that the council was told some things the contract does not support. Council members are people who were sold to. That framing gives them a way to change their vote without admitting fault, and you will need that.

Never threaten suit, and never use courtroom language from a podium.

It moves the argument onto ground where the city has staff and you do not.

Keep the subject on the contract and its rules.

Never individual officers.

Never cite a number, city, case or article you have not re-verified that day.

Statuses change monthly. A stale claim costs more credibility than it buys.

Never put the podium specifics in a public thread before the podium.

Contract, packet and statute quotes land once, in the right room, on the record. After that they can go anywhere.

Never chase a comment thread.

One clean reply for the readers, then out. The last word is worth nothing; the record is worth everything.

Never re-ask an official a question when their silence is worth more than their answer.

If you have asked a direct question in writing, how many signatures, what is the deadline, which provision, and received no reply, preserve the thread with timestamps visible and stop. Prompting them again repairs their record.

Never minimize the success stories.

When someone cites a case the cameras solved, condemn the crime, say the ordinance keeps hot-list alerts, and say the question is who controls the data.

Never put a family member's name, plate or address into a public filing.

Not without their consent and your attorney's view.

Never rely on memory.

Documents outrank recollection. If it is not in the tracking log or a dated file, it did not happen.

Never use sovereign-citizen framing, scripture at the podium, “viral,” or “the people demand.”

Each of them hands the city a character to argue with instead of a document to answer.

Have an attorney read anything before it is filed.

Whatever the clerk certifies is circulated verbatim.

Glossary

Order form: The itemized purchase: devices, software modules, and prices.
Master services agreement, or terms and conditions: The contract governing data, licenses, liability and termination, often incorporated by reference into the order form.
Non-appropriation clause: A clause allowing a public customer to terminate without penalty if the governing body does not appropriate funds for a future fiscal year.
Anonymized or de-identified data: Data the vendor says has been stripped of identifiers. Check the contract for what the vendor may do with it and whether your statute's definition of captured data includes data derived from the system.
Derivative works, outputs, models: Terms by which a vendor claims ownership of what it builds from customer data.
Gateway, or video integration device: Hardware that connects cameras the vendor did not install — a business's cameras, a school's, another department's — into the vendor's platform, often with analytics applied.
Plain-language or natural-language search: A software feature allowing a user to search plates and video by description, such as “landscaping truck” or “red sedan with roof rack,” rather than by plate number.
Data fusion or real-time crime center platform: Software that joins camera data with dispatch, records management and evidence systems into person and vehicle records.
Hot list: A list of plates that trigger an alert when read. A local-control ordinance typically preserves this function.
Organization audit and network audit: The vendor platform's logs of searches by the city's own users and by outside agencies, respectively. Usually exportable by an administrator.
Retention period: How long originals are kept before rolling deletion. It applies to originals in the vendor's portal, not to copies shared or derived before deletion.
Specimen: One complete example record, requested to reveal what fields a system captures without asking for volume.
Segregability: The rule that exempt material must be removed and the rest released, rather than the whole record withheld.
Take under advisement: A council's phrase for hearing a comment and doing nothing with it. Do not ask for it.
Ballot title and popular name: The summary voters read on the ballot and the short label for the measure. In some states both must be certified before signatures are collected.
Petition part: One physical petition sheet or booklet carrying the certified text and the signer and canvasser blocks. Parts are often required to be separated by county.
Sufficiency: The clerk's determination that a filed petition has enough valid signatures. Some states allow a cure period to add signatures.
Referendum versus initiative: A referendum asks voters to accept or reject something the council passed and often has a short window after passage. An initiative proposes a new measure. In some states initiatives go only to regular elections, while referenda may go to special elections.
Council referral: A council's vote to place a proposed or adopted ordinance before the voters without a petition.

This page is information and drafting support, not legal advice. Statutes, deadlines and vendor terms change. Verify everything against official sources on the day you use it, and have an attorney read anything before it is filed. Whatever the clerk certifies is circulated verbatim.

How to end a surveillance contract in your city, step by step.

Fill in the brackets.

Twenty-one chapters, in order.

Get the documents

Read the contract: the clause checklist

Look up your state's law

Write records requests that get answered

The standing-requests block

What to request: fourteen categories

The executed contract and procurement

The pre-approval record

The inventory

The audit logs

Anonymized or derived data and machine learning

Cloud hosting, subprocessors, and security

Sharing settings

Policies

Statutory reporting and audits

Effectiveness

Payment and grants

Vendor communications materials and relations

Your own data

The retention schedule and meeting recordings

Template: a records request letter

Template: the follow-up letter when they stall, skip items, or deny without saying why

Three habits make this letter answerable only by producing records

How to respond to a “no such record” or a refusal

What each negative proves

Template: a records preservation request

Keep the tracking log

Build the statements-versus-contract table

Take it to the council

End the contract by non-appropriation

Write the ordinance

Get it on the ballot

Council sponsor, no election

Council referral, no signatures

Citizen initiative, signatures

Referendum on the next expansion

Use the other lanes

Answer the common objections

Follow the ninety-day checklist

Days 1 to 10

Days 11 to 30

Days 31 to 60

Days 61 to 90

The posture

Glossary

Want email updates from us?