The case file’s March 26, 2026 “ADDITIONAL COMPLAINT” carries no intake-file pointer, where its January 2026 sibling routes to a numbered complaint file.
When a city logs a neighbor complaint, the cleanest paper trail includes some kind of traceable intake record — a ticket, a form, or a pointer to a separate complaint file — so the person being complained about can later check who said what, and when. Govt Code §7920.000 This city case file has three such “additional complaint” entries. One January 2026 entry points to its own numbered complaint file, so it can be traced; M038 M011 the other two — a January 9 entry and the March 26 one — point to nothing. The March 26, 2026 one — the one that calls the resident a “37 year old homeless man” who is “terrorizing the neighborhood” — points to nothing: no ticket, no companion file number, no intake record at all. M040 It names the inspector who logged it and the date, but not a routed source the owner could pull and test. M040 The same thing happened at the very start of this case: the original complaint’s intake ticket was left out of the city’s first records release and only turned up after the owner’s representative pushed back in writing and caught the gap. M001 Card 34 So the same missing-intake pattern shows up at both ends of the file — and here it stands out because the city’s own January entry shows exactly the kind of pointer the March entry is missing. M038 M011
Bottom line: the city’s file carries a damaging March 2026 “complaint” with no traceable intake record behind it — while a near-identical January entry in the same file does point to one, which is exactly what the March entry should have done.The City’s produced case file carries a note-log entry labeled “ADDITIONAL COMPLAINT” dated 03/26/2026, M040 repeated as a memo entry on the same record. M011 The same file holds a second “ADDITIONAL COMPLAINT” entry dated 01/27/2026 M038 M011 — and that earlier entry routes to a numbered intake file: “See FILE #: 26-003747.” The 03/26/2026 entry carries no such pointer: no companion file number, no 311 ticket, no intake date distinct from the narrative date, no routing receipt, and no source document the narrative paraphrases. M040 M011 The originating complaint at the front of this case is the same shape of gap — the City’s 03/20/2023 “Date/Time Opened” export filter dropped the originating 311 ticket until the requester challenged the cutoff in writing. Card 34 The City’s production-completeness posture is anchored at Card 47.
The entry is not blank-author content. The note records its author — the inspector of record — and its date. M040 What it does not carry is the intake record a “complaint received” generates: where the 01/27/2026 sibling points to a separate complaint file the owner could request and test, the 03/26/2026 narrative stands alone. M038 M040
The label “ADDITIONAL COMPLAINT” on the 03/26/2026 entry characterizes it as a complaint received — the kind of content a routed intake record sits downstream of. M040 Govt Code §7920.000
The file holds three “ADDITIONAL COMPLAINT” entries: 01/09/2026 (Paul Lovato, “Additional complaint called in states”) M038 M011; 01/27/2026 (Doug Pierson) M038 M011; and 03/26/2026 (Paul Lovato) M040. Of the three, only the 01/27/2026 entry routes to a numbered complaint file — “See FILE #: 26-003747.” The 03/26/2026 entry carries no companion file number, no 311 ticket, and no routing entry anywhere in the production. M040 M011
A named author — the inspector of record — a date, and a caller narrative whose caller identity is withheld under the City’s complainant exemption. M040 The owner can read the characterization — that the resident is “A 37 YEAR OLD HOMELESS MAN … TERRORIZING THE NEIGHBORHOOD” — but cannot date, attribute, or trace it to a routed intake the way the 01/27/2026 entry permits. M038 M011
A prejudicial complaint narrative sits in the produced file with no paired intake record the owner can date, attribute, or test — the front-of-case pattern, repeated late in the file, and visible against the City’s own 01/27/2026 entry that does carry a file pointer. M040 M038 M011 That the City’s production-completeness posture makes a missing intake record a contradiction only sharpens the point. Card 47 R.26-1549 R.26-1965
The City produced a block labeled “ADDITIONAL COMPLAINT,” dated it 03/26/2026, and framed it as a complaint received M040 — but produced no routed intake record alongside it that the owner could pull and test. The City’s own file shows what such a pointer looks like when it exists: the 01/27/2026 “ADDITIONAL COMPLAINT” entry points to complaint file 26-003747 M038 M011 — the one of the file’s three “ADDITIONAL COMPLAINT” entries that routes to a separate file. The 03/26/2026 entry has no such pointer. M040 M011 The originating complaint at the front of this case had its intake ticket filtered out of the City’s first export and surfaced only when the requester caught the cutoff; Card 34 the 03/26/2026 entry never had a paired, routed intake record in the file to begin with. The same intake-record gap appears at both ends of the production. Govt Code §7920.000 R.26-1965