The Index Pointer and the Unanswered Custodian Question
The City gave two written answers to the same request for one inspector's 2025 case notes, seventy-six days apart, and both cannot be right. Request 26-71 [R.26-71.1] asked, on January 8, 2026, for a raw export of Paul Lovato's 2025 notes with two fields, "Case number / case ID" [R.26-71.1] and "Note text (message/body)" [R.26-71.1]. The next morning the City wrote: "The record(s) you are seeking have already been released to the public as part of a prior City of Sacramento public records request." [R.26-71.1] and pointed to "25-3549.pdf" [R.26-71.1] from an earlier request. The requester answered the same day that "The document 25-3549.pdf is a case list/index (case numbers with summary fields)." [R.26-71.1] and "A single narrative field per case is not responsive to this request." [R.26-71.1] On March 26, 2026 the City released "PRA 26-71 - Paul Lovato Case Notes.xlsx" [R.26-71.1] as the responsive record and, one minute later, closed the request: "All responsive records have been provided." [R.26-71.1] (Card 40 carries the seventy-seven days in between.)
Because the notes were the inspector's own, the requester asked on January 20, 2026 — after the City had "already attempted to sidestep this request by pointing me to 25-3549.pdf" [R.26-71.1] — for the City to "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" [R.26-71.1]. The thread [R.26-71.1] carries the City's five extension notices, a March 18 message that "we will need to individually pull each case and redact it" [R.26-71.1], two releases, and the closure — and no answer to that question. The law asks the City to help a requester identify the records (Government Code 7922.600 [GC.7922.600]) and to say within ten days whether it holds them (7922.535(a) [GC.7922.535]).
Which of the City's two written answers on Request 26-71 described the record — January 9, 2026 [R.26-71.1], that the inspector's 2025 case notes "have already been released to the public" in a file from an earlier request, or March 26, 2026 [R.26-71.1], when it released "PRA 26-71 - Paul Lovato Case Notes.xlsx" as the responsive record and closed the request on it — when the requester had asked on January 20 [R.26-71.1] whether the inspector himself was searching and selecting those notes, and the thread carries no answer?
IN PLAIN TERMS
The requester asked for one inspector's 2025 case notes — the note text itself. The City's first answer, the next morning, was that those records had already been released [R.26-71.1] in a file from an older request; the requester wrote back that the file was a list of cases, not the notes [R.26-71.1]. Because the notes were the inspector's own, he also asked whether the inspector was the one searching and selecting them [R.26-71.1]. Seventy-six days later the City released the notes [R.26-71.1] under this request and closed it on them. Nothing on the thread takes the first answer back, and nothing on it answers the second question. The question for the City: which of its two written answers described the record?
RECORD CHAIN
- January 8, 2026 — the request: two fields. "Please produce the raw system export of all "General Notes," "General Information," "Case Notes," narrative entries, or similar note/log records entered/authored by Inspector Paul Lovato during calendar year 2025" [R.26-71.1]; minimum fields "Case number / case ID" [R.26-71.1] and "Note text (message/body)" [R.26-71.1]; "System export preferred." [R.26-71.1]
- January 9, 2026, 8:38am — "already been released". "The record(s) you are seeking have already been released to the public as part of a prior City of Sacramento public records request." [R.26-71.1] "The case number / case ID can be found in request 25-3549 in the document titled "25-3549.pdf" under the documents tab." [R.26-71.1] At 11:24am the requester: "The document 25-3549.pdf is a case list/index (case numbers with summary fields)." [R.26-71.1] "A single narrative field per case is not responsive to this request." [R.26-71.1]
- January 20, 2026, 2:45pm — the custodian question. After the first extension notice that morning: "Because this request seeks note/log entries authored by Inspector Paul Lovato, any delay influenced by him or made for his benefit would be improper and would directly undermine the integrity of this process." [R.26-71.1] "Please confirm. Whether Paul Lovato has been asked to search for, select, review, or control production of records responsive to this request" [R.26-71.1].
- January 20 – March 17, 2026 — five notices, no answer to either point. Each notice: "additional time is necessary to properly respond to your request due to the volume of materials" [R.26-71.1] (Card 40). None mentions 25-3549.pdf, the January 9 answer, or who was searching.
- March 18 – 26, 2026 — the City produces the notes itself. March 18: a case list, with "Please be advised that we will need to individually pull each case and redact it which will take time to complete." [R.26-71.1] March 25: "Accela Inspections & Parcel Conditions PLovato CY2025.xlsx" [R.26-71.1]. March 26, 3:26pm: "PRA 26-71 - Paul Lovato Case Notes.xlsx" [R.26-71.1], signed Mindy Cuppy, City Clerk [R.26-71.1]; 3:27pm: "All responsive records have been provided." [R.26-71.1] Nothing on the thread withdraws the January 9 answer or names who pulled the notes.
FULL CIRCLE
The City's first available answer is that January 9 was a pointer: the case IDs were in 25-3549.pdf, the note text came March 26, and nothing requires a notice withdrawing the earlier message.
The January 9 sentence is not a pointer to one field. It says "The record(s) you are seeking have already been released to the public" [R.26-71.1] — the records sought, in a request whose first line asked for the note text. The City's own March 26 release is the page that shows those records had not been released: it produced them, under this request number, as the responsive record, and closed on them.
The City's second available answer is that the Public Records Act does not require it to describe every internal production step, including who searched.
The card asserts no such rule. It records that the question was asked on the thread on January 20, in a request for the subject inspector's own notes, and that the City's ten later entries [R.26-71.1] — five notices, a message that staff "will need to individually pull each case" [R.26-71.1], two releases, a closure — answer it nowhere.
What would defeat this card is a page showing the 2025 note text released to the public before January 9, 2026, or a City message on the thread saying who searched for and selected the notes. The thread [R.26-71.1] holds neither; the City closed it with "All responsive records have been provided." [R.26-71.1] Card 4 is the completeness baseline (what the file the City produced means, and does not mean).
APPLICABLE LAW
- GC.7922.535: CPRA determination-within-ten-days requirement; extensions permitted only for unusual circumstances, each capped at no more than 14 days per notice (GC.7922.535(b)).
- GC.7922.600: CPRA duty-to-assist obligation; agency must assist requester in identifying responsive records.
- GC.7922.500: CPRA non-obstruction rule; the CPRA may not be used to delay or obstruct inspection or copying.
SOURCE CITATIONS USED BY THIS CARD
- R.26-71.1 — verbatim capture of the NextRequest 26-71 page (requester contact details redacted): the January 8, 2026 request; the January 9, 8:38am "already been released" message and the 11:24am reply; the January 20, 2:45pm custodian question; the five extension notices; the March 18, 25 and 26 releases; the March 26, 3:27pm closure "All responsive records have been provided."
- R.26-71 — the live portal page for Request 26-71.
- R.25-3549.1 — Request 25-3549 portal thread and closure record, the earlier request whose "25-3549.pdf" the City pointed to on January 9, 2026.