The policy promised supervisory review.
The agency produced no audit.
We document the gap.
Verified retention citations.
Rule-anchored records requests.
Named stall patterns, countered.
Sharing rosters mapped.
Adversarial review before you file.
For Residents, Reporters, and Counsel.
For the Side Without the Cameras.
Must Exist documents. You own every filing decision. Counsel owns every legal conclusion. That division of responsibility is the engagement.
Built From Three Decades of Public Records Practice
Then From What the Agencies Wrote Back
MUST EXIST™ RULE-ANCHORED
LICENSE PLATE READER RECORDS REQUESTS
AND PRODUCTION AUDITS
Police agencies buy plate camera networks through procurement processes that generate paperwork, then govern them with written policies promising supervisory review, authorized access, and defined search reasons. The searches log themselves, by the thousand. The audits the policy promises often go unrun, the sharing configuration goes unreviewed, and almost nobody asks to see either. Must Exist converts that gap into records: the governing use policy, the query audit trail, the sharing roster, the contract and its amendments, and the agency's own retention citations, packaged for residents facing a renewal vote, the commissioners who have to cast one, reporters working the story, and defense counsel who need the production organized.
Every request is anchored to a written rule the agency adopted, never to a record a requester wishes existed. Every statutory citation is grounded in primary source text or left visibly bracketed on the page. Every draft runs an adversarial review before it is filed. The method is built on filed Chapter 119 requests and what came back, including a production that surfaced a suppression feature two prior no-records determinations had said did not exist.
The rule earns the request. The request never outruns the rule.
MUST EXIST™ RULE-ANCHORED
PLATE READER RECORDS REQUESTS
AND PRODUCTION AUDITS
The plate reader accountability project
I am not a lawyer. Nothing here is legal advice. This is process guidance and template language, and records law varies by state and by facts. If your situation turns on your own circumstances, talk to a lawyer in your state.
Your police department runs cameras that photograph every car that drives past. Not speeders. Every car. Yours, several times a day, on the way to work and back.
Somewhere your agency wrote a policy for those cameras. Who may run a search. What reason they have to enter. How often a supervisor reviews the logs. Which outside agencies may reach your city's cameras.
That policy is a public record in most states. So is the paper it should have generated.
Get the rule they wrote. Then ask for the paper that rule should have produced.
That is the entire method, and it does not require you to win an argument about the Constitution.
Why call it Must Exist?
Because every request starts with the same sentence.
If this decision was made the way the policy says, the following records must exist.
You are not guessing what an agency has. You are reading the rule it wrote for itself, working out what paper that rule generates when it is followed, and asking for that paper by name.
One honest limit, up front, because the other side will raise it. A record is not required to exist just because you would find it useful. The strength of a Must Exist request comes from anchoring it to a written rule, a contract term, or a statute that actually creates the obligation. If you cannot point at the rule, you do not have a request yet. You have a hunch, and the agency will tell you so.
That constraint is a feature. A request built on a real rule cannot be waved off as fishing.
What are the three documents?
- The use policy. The general order, SOP, or directive governing plate camera use. This is the rule, and it comes first because everything else gets measured against it.
- The query audit log. Who searched, when, from what account, at what agency, and what reason they entered. Native electronic format, with personal identifying information removed.
- The sharing roster. Which outside agencies and networks your agency's system is configured to share with. This is the least requested document in the whole field and often the most useful. It tells you who else has been inside your city's cameras, and it tells you which neighboring agency to ask when yours goes quiet.
Now compare. What the policy promises, next to what the logs show, next to who actually had access. Every useful finding in this field lives in one of those gaps.
What happens when you file?
Three outcomes. Each one leaves you holding a document.
- The policy and the paper match. The agency runs a real process and can show its work. Say so publicly, by name. That costs you nothing, and it is why the next agency answers you.
- The paper does not match the policy. A policy that promises quarterly supervisory audits, next to an agency that cannot produce one audit, is a failure measured against the agency's own written standard. Not a theory. Their standard.
- The agency certifies no responsive records. A written certification is itself a document you can publish next to the search volume and the policy language. It is not proof of misconduct, and this page will not tell you it is. It is a record, in writing, that a council member can read out loud.
What filing guarantees you is a documented record. Not an outcome, and not a policy change.
What about warrants?
You will see this question framed everywhere as how many of those searches had a warrant. Be careful with it.
No court has held that a routine plate camera query requires a warrant. An agency that answers "we do not require judicial authorization for standard plate searches" has given you a lawful policy disclosure, not a confession. Treating that answer as misconduct is how a records project gets dismissed at the podium, and it deserves to be.
The version that works is narrower. Where the agency's own policy, its contract, or a state statute says a category of search requires judicial authorization or supervisory approval, ask for the records showing that authorization happened. Now you are measuring the agency against a standard it accepted, and the answer means something either way.
We never ask for anyone's plate
We do not request plate numbers, vehicle photographs, owner records, investigative targets, or informants. We say so inside the request, in writing, before the agency reaches for it.
Read your state's exemption carefully, because it is usually wider than people assume. Florida's section 316.0777(3) is the example I know best. It makes confidential both images and data containing or providing personal identifying information, and personal identifying information in data generated from those images. That is not a rule about one column labeled plate. It reaches free-text fields, linked identifiers, and anything that lets someone reconstruct who a search was about.
So the method aims at what those statutes are written around: the contract, the purchase order, the use policy, the sharing configuration, and the process facts inside an audit record. Whether a specific field survives that exemption depends on what is in it, and the agency has to tell you which exemption it claims and produce the segregable remainder.
What did the Supreme Court actually decide?
On June 29, 2026, the Supreme Court decided Chatrie v. United States, No. 25-112. By six to three, in an opinion by Justice Kagan, the Court held that police conduct a Fourth Amendment search when they obtain a person's stored cell phone location history, because you keep a reasonable expectation of privacy in the record of your own movements even when a company holds it. The Court vacated and remanded, leaving the validity of the warrant itself to the lower courts. It also held that pulling only a limited window from that database is still a search.
Does that make plate readers illegal? No.
Chatrie was a phone location case. It never mentioned license plate readers, and no court has held that a plate camera query is automatically a search requiring a warrant.
The case pointing the other way is real. In Schmidt v. City of Norfolk, Chief Judge Mark Davis of the Eastern District of Virginia ruled on January 27, 2026 that Norfolk's network of roughly 176 cameras, holding data for 21 days, was not an unconstitutional search. His reasoning was that this particular network did not yet paint a full enough picture of a person's life, and he warned in the same opinion that a larger one might. The plaintiffs, represented by the Institute for Justice, are appealing to the Fourth Circuit as No. 26-1227, with the Cato Institute supporting.
The law is unsettled and moving. Anyone selling you certainty about this is selling something.
Which is exactly why the method does not depend on it. A records request asks whether an agency followed the rule it wrote. That question has an answer today, in every state, regardless of what the Fourth Circuit does.
Why file now instead of later?
In November 2025, a Washington judge ruled that plate camera data are public records under that state's Public Records Act. Cities across the state switched cameras off rather than comply. Then, on March 30, 2026, Governor Bob Ferguson signed Senate Bill 6002, which among other things exempted the data from public disclosure.
One court said the records were public. The legislature then said they were not.
That is one available endgame. When records law becomes inconvenient, the fight moves from the custodian's desk to the statehouse. File while your door is open, and watch your own legislature. Lobbying on disclosure rules is itself a story, and lobbying filings are public records too.
Has this worked anywhere?
Cities have been canceling plate camera contracts since 2025.
In a growing number of those cases, the sequence was the same. Residents obtained the query logs. The logs showed searches by agencies the city had not authorized under its own policy or contract. The contract died at a public meeting.
Residents got the paper first. The politics followed it.
You will not be inventing the sequence.
Start here
The method is free, under a Creative Commons Attribution license. Attribution is the only string.
- [Get the request builder and the operator kit →]([PRODUCT URL])
- [Have me run the campaign with you →]([SERVICE URL])
- Read the case files on Substack →
Stop tweeting at the surveillance state. Start filing against it.
FAQs
Do I need to be a lawyer?
No. You need to be able to read a form and keep a calendar.
Do I need to say why I want the records?
Florida's public records law does not require a statement of purpose or any showing that your interest is legitimate. Other states differ. Check the statute you are filing under.
What if the agency has no written policy at all?
That is a finding, and a clean one. An agency running a surveillance network with no governing policy has told you in writing that nobody set the rules. Several states require a written policy by statute, so check yours before you assume the absence is merely embarrassing.
Will this get the cameras removed?
Maybe, and I will not promise it. Some cities canceled after residents pulled these records. Plenty did not. Filing gets you a record, not an outcome.
Is any of this a lawsuit?
No. I do not sue the government. I file its paperwork and let the record do the arguing. If your records fight ever needs a courtroom, that is a decision for a lawyer in your state.
What does it cost?
Nothing to start. Fees vary by state and by request. Florida caps duplication charges and allows a special service charge when a request requires extensive information technology or clerical work, so a narrow request is cheaper than a broad one for reasons built into the statute.
Is this legal advice?
No. Process guidance and template language. Talk to a lawyer in your state where legal interpretation is required.








