The Unproduced Paul Email Category

RECORD CHAIN

1. The rule. Disclosable records are to be made promptly available [GC.7922.530] (Government Code 7922.530). City of San Jose v. Superior Court (2017) 2 Cal.5th 608: writings about public business by a public employee are public records whether held in an agency account or a personal one.
2. September 29 – November 7, 2025 — the request and its closure. "I am requesting all Code Enforcement records involving Inspector Paul Lavato from January 1, 2020 through September 19, 2025." [R.25-3549.1] — including "Emails, text messages, memos, or attachments he wrote or received about Code Enforcement cases." [R.25-3549.1] and "Communications between Code Enforcement management and Paul Lavato about inspections, enforcement decisions, or cases." [R.25-3549.1] Closed November 7, 2025, 8:05am: "The City has collected all documents that appear to be responsive to your request." [R.25-3549.1]; "All responsive records have been provided." [R.25-3549.1]
3. September 2 – 11, 2025 — the email, and the file's typed copy of it. "From Paul Lovato", "Date Tue 9/2/2025 2:43 PM", "Re: 4880 T Street Jackie's House" [E3], to two City staff and two owner-side addresses, answering a Cosley forward of the same afternoon, "Paul, who is this person? How is he involved?" [E3] (Card 28). The case file, 09/11/2025: "I replied back to the email stating: Chris, Thank you for reaching out to the city of Sacramento with your concerns of the property at 4880 T street." [M036] — the reply body in full, retyped into a note, with no sender, recipients, date or time; the same entry retypes the incoming message, "I believe you just came by and delivered the new Notice and Order packet." [M036] The note, not the email.
4. December 29, 2025 — a message on the closed request; a Clerk prints the email from her own Outlook; a new request number. 1:46pm, posted on closed Request 25-3549: "I am writing to request verification of an email communication referenced in the official case record." [R.25-3549.1] — asking for "The date and time the email was sent" [R.25-3549.1], "The sender email address" [R.25-3549.1], "The recipient email address(es)" [R.25-3549.1]. Then "12/29/25, 3:25 PM [E3] … Jena R. Swafford - Outlook" [E3]; Request 25-4711 opened 3:44pm [R.25-4711.3], "Re_ 4880 T Street Jackie's House - 25-3549.pdf" [R.25-4711.3] released 4:22pm, closed 4:23pm (Card 43, Card 46). The print predates the new request by nineteen minutes, and the filename itself carries the earlier request's number.
5. April 2023 – February 2026 — the rest of his case correspondence, held only on the owner's side. 04/04/2023 [E1.2], 04/05/2023 [E1.3] and 04/14/2023 [E1.5] emails from the inspector (the April 2023 packet [E1]); the 07/18/2025 email he wrote [S4]; the 08/20/2025 text sent to him [S3]; the 08/27/2025 email [S5]; the email of a Thursday in February 2026 [S6] dictating a permit scope (Card 35). None of them is in the case file the City produced in May 2026 under Request 26-1965 and closed 05/22/2026 with "All responsive records have been provided." [R.26-1965.1] — the later and larger production; the ones dated before September 19, 2025 fall inside the window of Request 25-3549.

FULL CIRCLE

The City's first available answer is that the words of the reply are already in the produced file: the 09/11/2025 note reads "I replied back to the email stating: Chris, Thank you for reaching out to the city of Sacramento with your concerns of the property at 4880 T street." [M036] and runs to the end of the reply.

The words are there; the record is not. The note carries no sender, no recipients, no date and no time — the fields the 1:46pm message asked for [R.25-3549.1] — and the City answered that message not by pointing to the note but by printing the native email and releasing it under Request 25-4711 [R.25-4711.3]. Request 25-3549 named "Emails, text messages, memos, or attachments he wrote or received" [R.25-3549.1], not notes about them.

The City's second available answer is its own sentence: it collected the documents that "appear to be responsive" [R.25-3549.1] — a statement about what its search found, not a warranty that nothing else existed.

Then the search is the question. The email was in a City mailbox, from the inspector's City address, dated inside the window, in the category the request spelled out; a Clerk found and printed it within two hours of a message asking whether it existed. A search of the inspector's City email for a request about the inspector's emails would have found it first.

The City's third available answer is that Request 25-3549 sought the inspector's records broadly, that the closure predates the December 29 print, and that the email surfaced on a later, narrower request.

The email did not come into existence on December 29; that is the day the City looked. Its header says when it existed and where: September 2, 2025, a City account [E3] — two months before "All responsive records have been provided." [R.25-3549.1]

What would defeat this card is a page carrying the September 2, 2025 email with its header inside the file the City produced in May 2026 under Request 26-1965 [R.26-1965.1] or the production listed on Request 25-3549 [R.25-3549.1], or a City statement of the mailboxes searched for Request 25-3549 that accounts for it. The May 2026 file holds the note and no such page; the closed request [R.25-3549.1] holds no such statement. Card 4 is the completeness baseline (what the file the City produced means, and does not mean).