Across seventeen CPRA requests in this case audit, eleven were closed with affirmative completeness language — making any record responsive at closure and surfacing later a contradiction of the City’s own closure words.
When you ask a city for public records, the law treats the city’s act of closing your request as an official statement: it is the city saying, on the record, that it searched and gave you everything it has on that subject. Govt Code §7922.530 Govt Code §7922.535 Over about seven months this property owner’s representative filed eleven separate records requests tied to one code-enforcement case, and the city closed every one of them with some version of “you have it all” — and in one instance, twenty-two minutes after the request came in, the city answered that the records do not exist at all. R.26-39 Think of each closure like a signed receipt that says “paid in full.” The catch is simple: if a document that should have answered one of those requests turns up later, the city already swore on its receipt that the document either did not exist, was already handed over, or — and this it never admitted — was being held back. There is no clean way out: even a later letter saying “we were wrong, here it is” only proves the earlier receipt was inaccurate. Govt Code §7922.540 A few of the eleven requests reached past this one case — the inspector’s whole year of notes, a roster of officers, a citywide search by violation code — and those are described as exactly that, so no one can say the case is being overstated. The detail that only surfaced because the owner’s representative kept filing and comparing the city’s own portal threads is that the city plainly can hand over a searchable, native file when it wants to: it did exactly that for three other people’s cases in a single day. R.26-1863
Bottom line: the city closed eleven records requests in this audit by stating it had given everything — so any record that existed then but appears now is, by the city’s own words, one it said was gone, already sent, or quietly held back, and that is why every “where is the missing record” claim in this case points back here.This requester filed seventeen CPRA requests in the audit of Case 23-009185. Eleven were closed with affirmative completeness or no-records language in distinct formulations by three named Office of the City Clerk officers. Govt Code §7922.530 Govt Code §7922.535 Govt Code §7922.540 One more was denied as wholly exempt, four remain open in the latest local captures reviewed for this pass, and the only clean native-file export the City produced in response went to three unrelated cases — not this one. R.26-1863 The closure language is what makes the audit a trap: under the CPRA, closing a request as complete is an affirmative determination about the search and disclosure, not a neutral administrative act. Govt Code §7922.530
The case-file-specific closures are the strongest. The first full-case production was closed “All responsive records have been provided.” R.25-3549 A follow-up asking whether one logged email was ever sent to the requester was closed twenty-two minutes after filing with “the City does not have any records that are responsive to your request.” R.26-39 The most recent searchable-export request was closed “All responsive records have been provided,” even though the City released the same flattened 631-page PDF the request expressly asked it not to send. R.26-1965 Two further requests for system metadata and the case-level audit trail were closed by back-reference: “all records were provided under” the April case-file production. R.26-1963 R.26-1964
Eleven times, three named officers, several fixed phrasings — and the only version of “we were wrong” that would disprove any of these closures would itself confirm the failure it admits. Card 48
The CPRA requires an agency to produce disclosable records, Govt Code §7922.530 issue a written determination within the statutory window, Govt Code §7922.535 and identify the responsible official and basis when it denies or withholds records. Govt Code §7922.540 Judicial enforcement lies under the writ statute. Govt Code §7923.000 Closing a request as complete, or stating that no responsive record exists, is therefore an affirmative determination about the search.
The eleven closures and their verbatim language, in chronological order:
A record that should have answered one of the eleven closed scopes, but appears only after closure, is by the City’s own posture one of three things: a record the City said did not exist, a record the City said was already supplied, or a record withheld without the identification the statute requires. Govt Code §7922.540 Each reading is a documented CPRA failure on the closed request.
The strongest single closure: on R.26-39 the City closed twenty-two minutes after filing — received 12:08 PM, denied and closed 12:30 PM — with “the City does not have any records that are responsive to your request.” That phrasing claims the records do not exist at all. R.26-39 The searchable-export closure answered with the thing it ruled out: Request R.26-1965 asked for a native, searchable case-file export and stated “please do not send a flattened PDF, a print report, screenshots, scanned pages, or a stack of images.” The City closed it “All responsive records have been provided” and released the 631-page print-rendered PDF. R.26-1965 The City can produce a native export — it did, for other cases: on Request R.26-1863 the same office produced complete case-file exports for three unrelated cases and closed the request in roughly one day. R.26-1863
A written City retraction of any closure — identifying records previously withheld or undisclosed — would itself be evidence of CPRA non-compliance during the closed period. Govt Code §7922.540 There is no version of “we were wrong, here is the record” that rescues the earlier completeness statement. That is why this card carries the disproof slot for every record-gap claim in the audit.
Eleven times, across three named officers and several fixed phrasings, the City told this requester the audit of Case 23-009185 was answered in full — once stating, in twenty-two minutes, that no responsive record exists at all. R.26-39 R.25-3549 R.25-4711 R.26-71 R.26-1549 R.26-1963 R.26-1964 R.26-1965 Those statements are not neutral: under the CPRA a closure is a determination about a search and production, Govt Code §7922.530 Govt Code §7922.535 and the City’s identification duties attach when it denies or withholds records. Govt Code §7922.540 An inadequate or contradictory CPRA response is judicially enforceable. Govt Code §7923.000
The strongest City response is that CPRA completeness is per-request, not global; a later-created or out-of-scope record can be produced later without contradicting any closure; and several scopes are not limited to this one case. That response narrows the claim but does not defeat it. A record responsive to any one closed scope that existed at the time of closure and surfaced only later is a CPRA failure on that request — and the case-file-specific closures and back-reference denials are squarely about this case. R.26-1549 R.26-1963 R.26-1964 R.26-1965 The “we cannot export it that way” defense to the searchable-export closure is foreclosed by the City’s own R.26-1863 production of native case-file exports for three other cases in a day. R.26-1863 Govt Code §7922.570