The Missing Representative Records

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

The City's file names the records the owner's representative sent it, and does not contain them. Its activity log records three inbound contacts from the representative in 2023: an April 4, 2023 email [M024], quoted inside an inspection note; an August 23, 2023 appeal and pictures [M025], "Uploaded copy of documents received to the documents tab" [M025]; and a September 27, 2023 phone call [M025] about the refused appeal. Its documents index lists the second by name and size: "Appeal and Pictures" [M014], 6.045045 MB, 08/23/2023. The file the City produced holds the note, the summary, and the index row — and not the email, the packet, or a call record — and the City closed the request behind it with "All responsive records have been provided." [R.26-1965.1]

A fourth contact is in the City's own email and nowhere in its file: on May 3, 2023 the Building Division front counter wrote the inspector, copying the representative, "This customer stopped by without an appointment. He has questions about the case. Could you please follow up with him." [E14] — and the log goes from 04/24/2023 to 05/19/2023 [M002] with no entry for it. What the City called the August packet, and refused, is Card 3 (a monitoring-fee appeal, for no fee); the City produced one representative-side thread in usable form under a different request (E3, Card 46). The same pattern repeats in 2025: a 09/11/2025 entry [M036] quotes the representative's September 2, 2025 email in-line, and the index lists its attachment at "95 KB" [M022] — the attachment is not in the produced pages either.

Where is the 6 MB "Appeal and Pictures" the City's own log says it uploaded on August 23, 2023 — when its own documents index lists it by name, size, and date [M014], its own note says "Uploaded copy of documents received to the documents tab" [M025], it closed the case-file request with "All responsive records have been provided" [R.26-1965.1], and the file it produced holds only the staff summary?

IN PLAIN TERMS

The City's file says the owner's representative sent it an email, an appeal with pictures, and a phone call — and it holds staff notes about each, not the records themselves. The City's own index lists the appeal packet by name and size [M014]; its own note says it was uploaded [M025]; it closed the file as complete [R.26-1965.1]. A 2025 email from the same representative is kept the same way: quoted inside a log entry [M036], its attachment indexed [M022] and not reproduced. A May 2023 visit to the City's counter is in a City email [E14] and in no log entry at all. The question for the City: where is the appeal packet you say you uploaded?

RECORD CHAIN

  1. April 4, 2023 — an email, kept only as a quotation inside a log line. The entry opens, "I received an e-mil [sic] about this property stating: Good morning" [M024] and continues with the representative's message quoted inside the log line. The email is preserved only as the log's in-line quotation; the produced Case File [R.26-1965] holds no standalone copy of the email with headers.
  2. August 23, 2023 — an appeal packet with pictures, "uploaded". The entry states, "Received an appeal and pictures from" [M025] the representative, whom the City's note describes as the "'friend/helper' of the Property Owner" [M025], and then, "Uploaded copy of documents received to the documents tab" [M025].
  3. August 23, 2023 — indexed at 6 MB, not reproduced. The City's own documents-tab index lists "Merge Document ... 08/23/2023 Appeal and Pictures ... 6.045045 MB" [M014]. The underlying 6 MB appeal-and-pictures content is not reproduced as document pages anywhere in the produced Case File [R.26-1965], which the City closed as complete [R.26-1965.1].
  4. September 27, 2023 — a phone call, kept only as a staff summary. The entry states, "Received a call" [M025] from the representative — the City's note calls him "friend of po" [M025] — "very upset that he received a denial for the Mon fee appeal that he submitted" [M025]. The produced Case File [R.26-1965] carries only the staff summary of the call.
  5. September 11, 2025 — a second email kept in-line, its attachment indexed and not reproduced. The entry opens, in the City's words, "I received an email from property owners handyman along with a document. Document has been uploaded to documents and email states:" [M036] and then quotes the representative's September 2, 2025 email through to its close; the same page carries the inspector's reply, the one the E3 thread [E3] shows sent 9/2/2025. The documents-tab index lists the attachment as "Document from handy man" [M022], 09/11/2025, at "95 KB" [M022]. The file the City produced under Request 26-1965 (closed with all responsive records provided [R.26-1965.1]) holds the log quotation and the index row, and no page of the 95 KB attachment.
  6. December 29, 2025 — a representative-side thread produced under a different request. Its Request 25-4711 response included the thread "Re: 4880 T Street Jackie's House" [E3] in usable form; the portal record for that request [R.25-4711.3] shows the release.
  7. May 22, 2026 — the City's own pages identify the missing records. The case log names the April email [M024], the August appeal and pictures [M025], and the September call [M025]; the August 23 entry [M025] states the documents were uploaded; and the production's own index lists the upload [M014]. The underlying records appear nowhere in the produced Case File [R.26-1965], which the City closed as complete [R.26-1965.1].

FULL CIRCLE

The City's first available answer is that activity-log entries are summaries by design, that inbound records sit in another system, and that the August note shows the appeal was received and handled.

The City's own determination closes it. The request behind the file asked for the case data "including case fields, entries, notes, documents, photos, attachments, communications, correspondence, and metadata" [R.26-1965.1], and the City closed it with "All responsive records have been provided." [R.26-1965.1] For the packet the record goes further: the note says uploaded, the index — itself a page of the produced file — lists the upload by name, size, and date, and the pages are not there. Either the upload exists and was not produced, or the City's own log and index name a file its system does not hold.

The City's second available answer is that the August packet was handled: it was refused as a monitoring-fee appeal for no fee.

That is what the City called it (Card 3). What was filed is the 6 MB the City has not produced; its own label is all the file holds.

What would defeat this card is the "Appeal and Pictures" upload of 08/23/2023 itself, produced — which would show the closed-as-complete determination was untrue — or a City page stating that the index row and the upload note were in error. The file the City closed with "All responsive records have been provided." [R.26-1965.1] holds neither. 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