The City closed the inspector's-notes request against an index holding no notes, and never answered the demand that he not control his own production.
The City of Sacramento closed a public records request for an inspector’s notes by pointing to an old index file that did not actually contain the requested information. After the property owner explained that the index only showed one-line summaries rather than the actual note text, the city did not retract its claim but instead issued a series of two-week delay notices. Because the records involved the inspector’s own work, the owner asked the city to confirm that a neutral person was handling the production rather than the inspector himself. The city sent four more delay notices over the next fifty-one days and eventually released the records, but it never answered the question about who controlled the search. This entire exchange was captured on the city’s public records portal, which shows that the integrity concern was raised in writing and left unaddressed through the final closure of the request.
Request R.26-71 asked for the raw 2025 note/log entries authored by Inspector Paul Lovato — minimum fields case ID and note text R.26-71. The day after the request opened, the City replied that the records "have already been released to the public" and pointed to "25-3549.pdf," a file released months earlier in a different request R.26-71 R.25-3549. Eleven days later the owner corrected the City in writing: that file is a case-list index showing one summary line per case, not the underlying note entries R.26-71. The City did not retract the "already produced" closure; it issued the first of a series of two-week extension notices R.26-71.
Then, in a request opened specifically for the subject inspector's own records, the owner posted a written conflict-of-interest demand — asking the City to confirm whether Lovato had been asked to search for, select, review, or control production of his own records, and that a disinterested custodian was handling it R.26-71. Across the next fifty-one days the City sent four further rolling delay notices R.26-71 GC § 7922.535, released the note-text export, and closed the request R.26-71 — never confirming, denying, or addressing who controlled the production. The seventy-seven-day delay and the comparator disparity on this same request are the subject of C35.
A property owner asked the city for one inspector's own 2025 notes — just the case numbers and what was written. The day after the request opened, the city said those records had "already been released" and pointed to an old file from a different request. But that old file was only an index — a one-line summary per case, not the actual notes — so it did not contain what was asked for. The owner had to write back and explain this; the city never took back its "already done" answer, it just started sending two-week delay notices. Because the records were the notes of the very inspector involved in the owner's own case, the owner then asked the city, in writing, a plain integrity question: was that inspector being kept away from pulling and approving his own records, with a neutral person handling it instead? Over the next fifty-one days the city sent four more delay notices and a form closing letter, and never answered that question. All of this is visible only because the exchange happened on the city's public records portal, which timestamps every message — the owner preserved that thread, and it is what shows the question was asked and left unanswered.
The City must reasonably assist a requester in identifying responsive records GC § 7922.600, make a determination within ten days GC § 7922.535, and may not use the CPRA to delay or obstruct inspection or copying GC § 7922.500.
Request R.26-71 defined the records by structure — "General Notes," "General Information," "Case Notes," narrative entries — with fields case ID plus note text R.26-71. The City replied that the records "have already been released … in request 25-3549 in the document titled '25-3549.pdf'" R.26-71 R.25-3549. That file shows *that* cases exist, not *what* was written in them.
The owner replied that 25-3549.pdf "is a case list/index … not the underlying 'General Notes / General Information / Case Notes' entries," and restated the request with explicit filter specifications R.26-71.
The City did not acknowledge or correct the prior "already produced" closure; it issued the first rolling delay notice R.26-71. The "already produced" reply had stood unretracted for roughly eleven days on a request that ran seventy-seven elapsed days.
On the public portal, in a request opened for the subject inspector's own records, the owner posted R.26-71: > "Please confirm. Whether Paul Lovato has been asked to search for, select, review, or control production of records responsive to this request, and that production and review is being handled by a disinterested custodian (not the subject of the request) with appropriate supervision."
The City answered with rolling extensions R.26-71 GC § 7922.535; none mentioned the disinterested-custodian question.
The City released the Accela case export (Anna Sorensen, March 25, 2026), then released "PRA 26-71 — Paul Lovato Case Notes.xlsx" (Mindy Cuppy, March 26, 2026), then closed the request with "All responsive records have been provided" R.26-71. The closing notice does not confirm, deny, or address who handled the production — pending since the February demand.
What the City's own record shows. The portal record R.26-71 carries the "already produced" message, the owner's correction, the first extension, the conflict-of-interest demand, four further delay notices, the productions, and the closure.
"The record(s) you are seeking have already been released to the public … The case number / case ID can be found in request 25-3549 in the document titled '25-3549.pdf' under the documents tab." — City of Sacramento, response to Request R.26-71, January 9, 2026 R.26-71
The two produced files belong to different record classes: "25-3549.pdf" (a case-list index released months earlier in R.25-3549) versus "PRA 26-71 — Paul Lovato Case Notes.xlsx" (the actual note-text export released seventy-seven days later in this request). The City's decision to produce both confirms they are distinct R.26-71 R.25-3549.
The owner's conflict-of-interest demand and the City's closing notice that does not mention, confirm, or deny it are both in the portal thread R.26-71.
Three actions are required, each grounded in the portal record for Request R.26-71:
A request for one inspector's own notes met two avoidable obstacles, both on the City's own portal R.26-71. First the City closed it as "already produced" against a case-list index that contained no note text, leaving the owner to re-argue an already-specified request before the City would treat it as open R.26-71. Then, when the owner asked in writing whether the subject of the records was controlling their own production, and named the specific concern — enforcement leverage from a delayed release — the City answered with four more delay notices and a form letter but never the question R.26-71. Whether or not Lovato touched the file, the City's silence across fifty-one days and five delay-notice opportunities, on a direct written integrity question, is the defect this card preserves R.26-71. The city closed a request for an inspector's own notes by pointing to a file that did not contain them, and when the owner asked in writing whether that inspector was kept from controlling his own production, the city sent more delay notices and a form letter but never answered.
Anticipated City defense: The "already produced" reply was a good-faith duty-to-assist pointer to an existing Lovato production, resolved once the owner clarified; and the CPRA does not require an agency to disclose its internal production workflow or the staff who searched, so the delay notices and closure complied GC § 7922.535.
Answer: Request R.26-71 described the records in precise terms — note text, case ID, system export R.26-71. A case-list index with one summary line per case does not contain "note text," and the City did not phrase its reply as a clarifying question or partial pointer — it phrased it as a closure ("have already been released") R.26-71. That is not duty-to-assist under GC § 7922.600; it left an already-specified request sitting against a non-responsive file. And the February demand was not a request for personnel information or internal workflow — it asked whether the subject of the records was controlling access to them, a question about the integrity of the CPRA process itself R.26-71. Silence on that question, across fifty-one days and five delay-notice opportunities, does not constitute a protected non-response under GC § 7922.500 and GC § 7922.600.
---