A Refusal Is Rarely the Final Word

Refusals aren’t random. Read enough of them and the same four claims come back — often stretched past what the statute they cite actually covers. Learn the pattern, and a “no” stops being the end of the road and becomes a step you know how to take.

“That record doesn’t exist.”

This is the most common response — and sometimes the most misleading. Agencies often say a record doesn’t exist because they haven’t generated it yet, even when the underlying data sits in the Flock system ready to export.

What the law says. Under N.C. Gen. Stat. § 132-6.1, electronically stored data is a public record. Records a vendor holds on the agency’s behalf remain the agency’s public records. Pulling an existing report from a database the agency controls isn’t creating a record — it’s producing one.

Your move. If you received anything in an earlier batch — a contract, a deployment notice, an invoice — those documents prove the system exists and is running. Cite them back. Ask specifically which items don’t exist, and why, and request an item-by-item accounting.

“That’s a security feature.”

N.C. Gen. Stat. § 132-6.1(c) protects passwords, system configurations, and hardware security settings. Agencies sometimes stretch it to cover audit logs — the records showing who searched the system, when, and why. That stretch doesn’t hold. An audit log is an accountability record: it shows how a public resource was used by public employees. It doesn’t reveal how to compromise the system.

Your move. Push back in writing. Point out that the exemption covers system security, not system use. Ask for the audit logs with any genuinely exempt fields redacted, and for a written explanation of each specific field withheld.

“Those are criminal investigation records.”

N.C. Gen. Stat. § 132-1.4 exempts records compiled in connection with investigating specific crimes. Agencies sometimes apply it to the entire Flock audit trail — every search ever run. That’s not what the exemption covers. A two-year log of every plate searched by every officer is an administrative record of how a surveillance system was operated. It is not a record compiled to investigate a specific crime.

Your move. Ask the agency to identify which specific records it’s withholding under this exemption, and why each one qualifies. If the agency’s own ALPR policy says audit logs exist for oversight and accountability — as many do — cite that policy back. An accountability record created under a department policy is administrative, not investigative.

A real example. The Durham Police Department has taken exactly this position — that its Flock usage logs “constitute a record of a criminal investigation … and are not public records.” (INDY Week) Taken to its logical end the claim is self-incriminating: if the entire log is a criminal investigation, the department is treating every driver it records as the subject of one. It’s the most common way an agency tries to hide who searched its cameras — and the argument to be ready for.

“We’ve fulfilled this request.”

Some agencies close a request before producing everything, citing § 132-6.2(e) — which says an agency need not create records that don’t exist. True as far as it goes. It does not authorize closing a request when responsive records do exist and simply haven’t been retrieved.

Your move. If the closure is premature, respond in writing. Identify each outstanding item, explain why you believe the record exists, and ask the agency to reopen and complete the request. Be specific — cite the documents already produced that prove the system is operational.

“We’ll get to it — eventually.”

Not every “no” sounds like one. Some agencies acknowledge the request politely, then park it — “we’re in our busy season,” “this will take two to three months.” An open-ended delay can be a refusal in slow motion.

What the law says. North Carolina requires a custodian to furnish public records “as promptly as possible” (N.C. Gen. Stat. § 132-6(a)). That’s a legal standard, not an aspiration, and a heavy workload doesn’t suspend it. North Carolina courts construe the Act liberally in favor of access, and where responsive records already exist and are readily accessible, an extended delay can amount to a constructive denial of the right of access. This matters most for ALPR records, because the core items — the Flock contract, policy, invoices, and the Organization & Network Audit — are discrete existing files or on-demand exports generated in a few clicks from the Flock Insights dashboard. A multi-month timeline for a one-click export is hard to justify.

Your move. Respond in writing. Acknowledge the workload, but ask for the readily available records on a short, specific timeline (say, ten business days) and the rest on a rolling basis. Ask the agency to name any single item it genuinely can’t produce promptly, and why. And ask for the name of the agency’s or town’s attorney — then copy counsel, so the government is on notice of its duty and of the remedies for unreasonable delay: an action to compel under § 132-9 (after the mediation the statute requires first), and reasonable attorneys’ fees for a requester who substantially prevails — fees a court may order paid personally by an official who knowingly violates the Act.

A real example. On July 10, 2026, the Kure Beach Police Department acknowledged our June 30 records request but said it would take “two to three months,” citing its busy season (read the response). We answered with a formal demand letter — a model you can adapt — explaining that an open-ended delay of that length is inconsistent with the “as promptly as possible” standard, citing the statutes and cases above, and demanding production within a reasonable time. See where it stands in the Records Hub.

Three habits that protect you

Keep it in writing. Every exchange is evidence. A polite, specific written reply that names the statute the agency is misapplying does more than a complaint — and it builds the record if you need to escalate.

Pin down what’s actually being withheld. Ask the agency, in writing, to identify each specific record it is withholding and the exemption it claims for each. An agency may withhold only what a specific statute exempts, and a one-line “no” makes that impossible to test. And if the real objection is that a record contains some confidential information, that is not grounds to withhold the whole thing: under N.C. Gen. Stat. § 132-6(c), the agency must separate the confidential from the nonconfidential, produce the rest, and bear the cost of that separation itself.

Preserve the data. If the agency is sitting on audit logs with short retention windows, say so — and ask, in writing, that they preserve all responsive records pending resolution. Put a date on it.

North Carolina’s two formal steps

First, mediation — N.C. Gen. Stat. § 7A-38.3E. The North Carolina Dispute Resolution Commission runs a low-cost process for public-records disputes. It isn’t merely an option: a court has jurisdiction over a records suit only after the requester has complied with the mediation statute (§ 132-9(a)). It’s faster than litigation and puts the agency on the record.

Then, Superior Court — N.C. Gen. Stat. § 132-9. A person denied access may seek a court order compelling disclosure, and such actions are set for immediate hearing. A requester who substantially prevails is entitled to recover reasonable attorneys’ fees (§ 132-9(c)) — and a court may order those fees paid personally by a public official who knowingly or intentionally violated the Act. This is the formal escalation; consult an attorney before proceeding.

Haven’t filed yet? Start with the DIY records-request guide and its copy-paste template. Want to read what others have already pried loose? That’s the Records Hub.

This page provides general information about North Carolina’s public-records process. It is not legal advice and does not create an attorney-client relationship. The application of these exemptions is fact-specific. If you’re considering formal action, consult a licensed North Carolina attorney.