The Same-Afternoon Portal Split

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

Two messages went through the same portal channel on the same closed request on the same afternoon; the City turned one into a new request within two hours and gave the other no entry at all. Both were sent through the message function on Request 25-3549 [R.25-3549.1], which the City had closed on November 7, 2025 with "All responsive records have been provided." [R.25-3549.1] At 12:02pm on December 29, 2025 [R.25-3549.1] the requester set two City productions of the same case file side by side — "The City has produced two materially different PDFs for the same case record:" [R.25-3549.1] — asked for six named records about how they were generated, wrote "Silence or substitution will not be treated as a response." [R.25-3549.1], and ended "Please treat this as a continuation of my existing CPRA request." [R.25-3549.1] (Card 47 carries the two productions.) At 1:46pm [R.25-3549.1] he asked the City to verify one case-log entry: the 09/11/2025 note that the inspector had "replied back to the email stating: Chris, Thank you for reaching out to the City of Sacramento" [R.25-3549.1] (Card 28).

The 1:46pm words became Request 25-4711 [R.25-4711.3], "Entered on behalf of requester:" [R.25-4711.3], "Request received via web" [R.25-4711.3], 3:44pm [R.25-4711.3]. A Clerk's Outlook print of the inspector's 09/02/2025 email is stamped 12/29/25, 3:25 PM [E3]; "Document(s) released" [R.25-4711.3] at 4:22pm [R.25-4711.3] (the release notice, Jena Swafford, 4:22:47 PM [R.25-4711.2]); closed at 4:23pm [R.25-4711.3]: "All responsive records associated with this public records request have been released and this public records request is now closed." [R.25-4711.3] The 12:02pm message: the City's timeline for Request 25-3549, as captured for this deck, shows no staff entry of any kind after November 7, 2025, 8:05am [R.25-3549.1] — not for it, and not for the January 6, 2026 message [R.25-3549.1] that asked "Why was the first message ignored?" [R.25-3549.1] That January 6 message is the last entry the capture holds [R.25-3549.1]; the capture carries no date of its own, so the live page for Request 25-3549 [R.25-3549] is linked here as the place any later entry would sit. The Act sets the City's response clock [GC.7922.535] and its duty to help a requester [GC.7922.600]; Card 4 is the completeness baseline (what the file the City produced means, and does not mean).

What became of the six-item message of December 29, 2025, 12:02pm — when the message sent through the same channel on the same closed request at 1:46pm was a tracked request by 3:44pm, a released document by 4:22pm, and closed by 4:23pm [R.25-4711.3], the requester asked on January 6 [R.25-3549.1] why the first had drawn nothing, and the City's own timeline for Request 25-3549, as captured, ends with that January 6 message [R.25-3549.1] and shows no staff entry of any kind after November 7, 2025 [R.25-3549.1]?

IN PLAIN TERMS

On one afternoon the requester sent two messages the same way, through the message box on a request the City had already closed. The second, about one email, became a new request within two hours [R.25-4711.3], got a document by 4:22pm and was closed by 4:23pm. The first, which laid two different versions of the same case file side by side and asked six questions about how they were made, got nothing [R.25-3549.1] — no reply, no number, no entry. When the requester asked in January why, nothing again [R.25-3549.1] — that January message is the last thing on the timeline as captured. The question for the City: what became of the first message?

RECORD CHAIN

  1. November 7, 2025 — the request the messages went to was closed. Request 25-3549 [R.25-3549.1]: "All responsive records have been provided." [R.25-3549.1], 8:05am.
  2. December 29, 2025, 12:02pm — the six-item message. "The City has produced two materially different PDFs for the same case record:" [R.25-3549.1] — 586 pages / 1.62 GB against 590 pages / 50.02 MB, different producers — then six numbered records, "For each item below, please either produce the record as a separate file or explicitly state that the record is not being produced" [R.25-3549.1], and "Please treat this as a continuation of my existing CPRA request." [R.25-3549.1]
  3. December 29, 2025, 1:46pm — the one-email message. "I am writing to request verification of an email communication referenced in the official case record." [R.25-3549.1] — the 09/11/2025 note; "I did not receive any such email, nor did I send an email to which this would have been a reply." [R.25-3549.1]
  4. December 29, 2025, 3:25pm – 4:23pm — the second message becomes Request 25-4711. Outlook print, "Jena R. Swafford", 12/29/25, 3:25 PM [E3]; Request opened, "Request received via web", 3:44pm [R.25-4711.3]; "Re_ 4880 T Street Jackie's House - 25-3549.pdf" [R.25-4711.3] released 4:22pm (notice [R.25-4711.2]); closed 4:23pm. Card 46 carries what that one email shows about the search.
  5. January 6, 2026, 11:38am — the question, and the timeline after it. "Only the later message was acted on (it was converted into Request #25-4711 and I received email notifications)." [R.25-3549.1] "Why was the first message ignored?" [R.25-3549.1] The 25-3549 timeline after November 7, 2025, 8:05am, as captured: three requester messages and no staff entry [R.25-3549.1]; the January 6 message is the capture's last entry [R.25-3549.1].

FULL CIRCLE

The City's first available answer is the requester's own line: he asked that the 12:02pm message be treated as "a continuation of my existing CPRA request" [R.25-3549.1], so it stayed on the existing request rather than opening a new one.

The existing request had been closed for seven weeks. A continuation of a closed request goes nowhere unless the City reopens it, opens a new one, or says which; the City did none of the three — while the 1:46pm message, sent through the identical channel to the identical closed request, was a new request by 3:44pm.

The City's second available answer is that the November 7 closure covered Request 25-3549's own scope and says nothing about the two case-file productions the message compared.

Agreed, and the card says nothing else: the closure is where the message was sent, not what it questioned. What has no entry is the message itself, its six items, and the January 6 question about it.

The City's third available answer is that the capture is undated, so a staff entry made after it would not show.

The capture's last entry is the requester's January 6, 2026, 11:38am [R.25-3549.1] message, which itself records that the 12:02pm message had drawn "no email notifications, acknowledgment, tracking number, or any communication at all" [R.25-3549.1]; a staff entry made after that date would sit on the live page for Request 25-3549 [R.25-3549], which this card links.

What would defeat this card is a staff entry on the 25-3549 timeline after November 7, 2025, 8:05am, or a request number opened from the 12:02pm message. The timeline as captured [R.25-3549.1], ending with the January 6, 2026 message, holds neither, and the live page [R.25-3549] is where either would appear. Card 4 is the completeness baseline (what the file the City produced means, and does not mean).

APPLICABLE LAW

SOURCE CITATIONS USED BY THIS CARD

CARD REFERENCES