Across seventeen CPRA requests in this case audit, twelve were closed with affirmative completeness or no-records language, making any later-surfacing record responsive at closure a contradiction of the City's own closure words.
The City’s official closure of twelve public records requests as "complete" or containing "no records" creates a conflict with any records that may be discovered later. Under state law, these closures are formal determinations that the search is finished and all required documents have been produced. If a record is later produced that should have been in one of these closed requests, it would contradict the City's previous statements that the record did not exist or had already been provided. For instance, the City stated it had no records of photographs taken during a September 2025 walkthrough, yet property security footage shows an inspector taking photos on that day. These twelve closures were issued by three different officers over several months, establishing a formal baseline that the City claims is a full and complete production for this case.
This requester filed seventeen CPRA requests in the audit of Case 23-009185. Twelve were closed with affirmative completeness or no-records language in distinct formulations by three named Office of the City Clerk officers. Two were denied as wholly exempt; three of the four that appeared open at Stage 2 review have since closed with deficient or partial language; and the fourth — R.26-2206, filed for Bo Cosley's 09/16/2025 photographs — was closed June 4, 2026 with "The City does not have any records responsive to this request," a closure directly contradicted by the property's own security camera footage of Cosley taking photographs at the property on that date P.2 P.3 P.4 P.5 P.6 P.7 C28. The only clean native-file export the City produced went to three unrelated cases, not this one R.26-1863. The closure language is what makes the audit a trap rather than only a complaint: under the CPRA, closing a request as complete is an affirmative statement about the search and disclosure determination, not a neutral administrative act GC § 7922.530 GC § 7922.535 GC § 7922.540.
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 that the request expressly asked it not to send R.26-1965 M. 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.
Stated simply, when the City closes a public-records request with affirmative completeness or ‘no records’ language, it is making a determination on the record about the adequacy of its search and production. Over seven months the requester received eleven such closures tied to this case audit. Any later-produced record that fell within one of those closed scopes would therefore place the City in one of three positions: it claimed the record did not exist, claimed it had already been produced, or withheld it without the identification CPRA requires. That is why C47 carries the disproof slot for the deck's record-gap claims.
The CPRA requires an agency to produce disclosable records, issue a written determination within the statutory window, and identify the responsible official and basis when it denies or withholds records GC § 7922.530 GC § 7922.535 GC § 7922.540. Judicial enforcement lies under the writ statute GC § 7923.000. Closing a request as complete, or stating that no responsive record exists, is therefore an affirmative determination about the search.
Eleven requests in the Case 23-009185 audit were closed with completeness or no-records language. Each NextRequest thread time-stamps the closure statement and identifies the officer or closure message source.
| Request | Closed | Closing officer | Closure language | Scope closed |
|---|---|---|---|---|
| R.25-3549 | 11/07/2025 | Anna Sorensen | "All responsive records have been provided." | all Lovato Code Enforcement records 01/01/2020-09/19/2025, narrowed to Aug-Sep 2025 caseload |
| R.25-4711 | 12/29/2025 | Jena Swafford | "All responsive records associated ... have been released." | produced 09/02/2025 Lovato email; see C48 |
| R.26-39 | 01/06/2026 | Jena Swafford | "The City does not have any records that are responsive to your request." | proof/correction of the 09/11/2025 email-log statement |
| R.26-71 | 03/26/2026 | Mindy Cuppy | "All responsive records have been provided." | 2025 Lovato note/log export, all cases |
| R.26-1060 | 04/08/2026 | Mindy Cuppy | "All responsive records ... have been released ..." | 2025 Code Enforcement personnel/officer roster |
| R.26-1061 | 03/25/2026 | Mindy Cuppy | "... collected all documents that appear to be responsive ... This closes your public record request." | Nov-Dec 2025 note exports for five named officers |
| R.26-1265 | 04/02/2026 | Mindy Cuppy | "All responsive records have been provided." | citywide B31/B59 violation-code Notice-and-Order search, past five years |
| R.26-1549 | 04/20/2026 | Mindy Cuppy | "... collected all documents that appear to be responsive ... This closes your public record request." | April 2026 case-file production |
| R.26-1963 | 05/18/2026 | Mindy Cuppy | "The City does not have any records responsive to this request. All records were provided under 26-1549." | per-entry CitizenServe metadata plus attached communications |
| R.26-1964 | 05/18/2026 | Mindy Cuppy | same back-reference to R.26-1549 | case-level audit trail plus related communications |
| R.26-1965 | 05/22/2026 | Mindy Cuppy | "All responsive records have been provided." | searchable native export, answered with the 631-page flattened PDF M |
| R.26-2206 | 06/04/2026 | Unknown | "The City does not have any records responsive to this request." | Bo Cosley's 09/16/2025 photographs at 4880 T Street — CONTRADICTED BY CCTV P.2–P.7 C28 |
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 GC § 7922.540.
R.26-1986, R.26-1987, R.26-2204, and R.26-2206 appeared open in the Stage 2 local captures. All four have since closed. R.26-1986 closed June 11, 2026 — referred to the city portal (deficient; no Haynie declaration). R.26-1987 closed June 11, 2026 — produced 5 pages covering only 1 of 11 requested requests, confirming internal coordination records exist while leaving 10 requests unaddressed. R.26-2204 closed June 12, 2026 — denied under GC 7927.705 (blanket exempt, narrowed metadata-only refiling). R.26-2206 closed June 4, 2026 — "The City does not have any records responsive to this request" (photographs of 4880 T Street by Bo Cosley on 09/16/2025). The R.26-2206 closure is the strongest post-Stage-2 development in the completeness-trap record: the City certified no photographs exist; the property's CCTV recorded Cosley taking them C28 P.2–P.7. R.26-2206's closure language has been added to the closure table above and to the twelve-closure count. R.26-1863 is used only for the limited point that comparator case-file extracts exist and the public request ID is known; the portal-thread capture was unresolved in Stage 2 and remains unresolved.
A written City retraction identifying previously withheld or undisclosed records would itself be evidence of non-compliance during the closed period. There is no version of "we were wrong, here is the record" that rescues the earlier completeness statement.
Twelve times, across three named officers and several fixed phrasings, the City told this requester the audit of Case 23-009185 was answered in full or that no responsive record existed R.25-3549 R.25-4711 R.26-39 R.26-71 R.26-1060 R.26-1061 R.26-1265 R.26-1549 R.26-1963 R.26-1964 R.26-1965 R.26-2206. The twelfth — R.26-2206 — is the most consequential: the City certified no photographs of the 09/16/2025 walkthrough exist, while the property's own cameras recorded the Principal Building Inspector taking them C28. Those statements are not neutral. Under the CPRA, a closure is a determination about a search and production GC § 7922.530 GC § 7922.535, and the City's identification duties attach when it denies or withholds records GC § 7922.540.
Anticipated City defense: 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.
Answer: That response narrows the claim but does not defeat it. C47 does not say every later record contradicts every closure. It says that a record responsive to one closed scope, existing at the time of that closure, cannot be squared with the City's own completeness or no-records statement for that scope. The case-file-specific closures and back-reference denials are squarely about this case. That is the anchor every record-gap card cites: if the City later produces a record that should have been in a closed scope, the City's own closure words become the contradiction.
---