The Index Pointer and the Unanswered Custodian Question

Case 23-009185 | Card 42 | 4880 T Street, Sacramento CA 95819

In Request R.26-71, the City answered a note-text export request by pointing to a file from an earlier request, never retracted that answer, and closed the request without answering a February 3, 2026 custodian question. The request sought a raw 2025 note/log export authored by Paul, with case ID and note text as minimum fields R.26-71. The next day, January 9, 2026, the City replied that the records "have already been released to the public" and pointed to "25-3549.pdf," a file from a different request R.26-71 R.25-3549. The requester responded in writing that the cited file was a case-list/index with summary fields, not the underlying note entries requested R.26-71. The later notices, productions, and closure neither retracted the "already produced" answer nor explained why the pointer had been treated as responsive.

The custodian question arose because the request sought the subject inspector's own records. On February 3, 2026, the requester asked whether Paul had been asked to search for, select, review, or control production of responsive records, and whether a disinterested custodian was handling production with supervision R.26-71. From that question through the March 26 closure, about fifty-one days later, the portal thread carried the delay-notice sequence, the note-text export, and the closure, none of which answered who controlled the production R.26-71 GC.7922.535. Card 40 addresses the seventy-seven-day delay and the comparator disparity on this same request; this card addresses the unretracted index pointer and the unanswered custodian question.

IN PLAIN TERMS

The owner asked for the actual note text from one inspector's 2025 records. The City pointed to an older file, which the requester identified as an index — a list of cases, not the note entries requested. Because the records were the inspector's own work, the requester also asked whether Paul was involved in searching, selecting, reviewing, or controlling the production, and whether a neutral custodian was handling it. The public portal shows the question was raised in writing on February 3 and was still unanswered when the City closed the request on March 26.

RECORD CHAIN

  1. The rule — duty to assist and a timely determination. 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.
  2. The request and the "already produced" reply. Request R.26-71 defined the records by structure — "General Notes," "General Information," "Case Notes," narrative entries — with case ID and note text as minimum fields 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.
  3. The owner's correction. 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.
  4. The owner's correction and the first delay notice arrived the same day; the pointer was never retracted. On January 20, 2026, the portal thread carried both the first two-week delay notice, citing GC.7922.535(c)(2) volume of materials, and the requester's correction of the City's "already produced" reply, which by then had stood for roughly eleven days. The later notices and closure did not acknowledge or correct the January 9 pointer R.26-71.
  5. The conflict-of-interest question. On February 3, 2026, in this request for the subject inspector's own records, the requester asked on the public portal whether Paul had been asked to search for, select, review, or control production of responsive records, and whether production and review were being handled by a disinterested custodian with appropriate supervision R.26-71.
  6. The later notices did not address the question. The City posted later portal notices on the request R.26-71 GC.7922.535; none mentioned the disinterested-custodian question.
  7. Production and closure without an answer. The City released the Accela case export (Anna Sorensen, March 25, 2026), then released the March 26 note-text export (Mindy Cuppy), then closed the request with "All responsive records have been provided" R.26-71. The closing notice does not state who handled the production and does not answer the February 3 disinterested-custodian question.

"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 portal thread shows two different record references: "25-3549.pdf," which the requester described as a case-list/index released months earlier in R.25-3549, and the note-text export released later in this request. The City later produced the note-text export within this request; the January 9 pointer had not resolved it R.26-71 R.25-3549.

FULL CIRCLE

The sequence appears on the City's own portal R.26-71. The City answered the request as "already produced" by pointing to a file the requester identified as a case-list/index, not the requested note text R.26-71 R.25-3549. After the requester asked on February 3 whether the subject of the records was controlling the search, selection, review, or production, the City closed the request on March 26 without answering that question R.26-71.

The expected response is that the "already produced" reply was a good-faith pointer to an existing Paul-related production, and that the CPRA does not require the City to describe every internal production step. On the first point, the request described the records in specific terms — note text, case ID, system export R.26-71. The owner wrote that a case-list index did not contain the requested note text, and the City later released the note-text export in this same request; the January 9 pointer had not resolved it R.26-71.

On the second point, the custodian question was narrower than a demand for internal workflow. It asked whether the subject of the records had any role in controlling access to them, and whether a disinterested custodian was handling production with supervision R.26-71. The record shows an "already produced" answer pointing to a file identified as an index, never retracted, and a closure without any answer to the February 3 disinterested-custodian question.

APPLICABLE LAW

SOURCE CITATIONS USED BY THIS CARD

CARD REFERENCES