The City produced 283 words of paperwork per day for 1,156 days on placeholder violations, a volume pattern that warrants supervisory review because the underlying findings stayed generic.
The City of Sacramento generated more than 327,000 words of administrative paperwork against a single property over three years without ever identifying a specific violation. While the file grew by an average of 283 words every day, the assigned inspector authored only about 1.3 words of that daily volume, with the remainder consisting of automated templates and form letters. During this period, the City refused three written requests to provide specific details about the alleged property defects and never updated its original order to name them. Even without specific findings, the City issued 19 penalty orders under a generic catch-all provision and eventually doubled the penalty rate to $2,000 per cycle. By the time an inspector first recorded a description of the actual property conditions, the City had already charged $31,230 and placed a cloud on the property’s title. This sequence shows a large volume of administrative consequences being generated before the City specified what the owner was required to fix.
Between March 17, 2023 and May 16, 2026, the City generated 327,569 words of administrative paperwork across 1,190 pages against this single property: 283 words per day for 1,156 consecutive days. The assigned inspector personally authored 1,521 of those words, or about 1.3 words of the 283-word daily average (derived from the May reference production M). The rest is templates, fee-cycle automation, hearing-scheduling form letters, copied 311 narrative, pasted third-party correspondence, and boilerplate. The full denominator is locked in C54 and supported there by internal quantitative reports INTERNAL.C54.31 INTERNAL.C54.30 INTERNAL.C54.ForensicOCR.
This card places the paperwork volume against the case dates. It does not prove motive. It shows that the case generated major administrative consequences while the Notice and Order was never amended to name a specific violation. Across the same period, the first on-property condition description is dated the day of the compelled backyard inspection M035 C54, every penalty order cites the same catch-all noncompliance provision SCC § 1.28.010 M146 C12, and the penalty rate doubled in the same window as the attorney-routed permit demand M585 C10 C27.
Stated simply, the City built a large file against one property over three years and two months, but the substance did not keep pace with the volume. Almost none of the daily word count was inspector-authored; most was form paperwork and automated or copied text. Meanwhile, the City never amended the original order to say exactly what the violations were, even after the owner's side asked for specifics. By the time the City first set foot on the property, it had already charged $31,230 and left a cloud on title, all on violations it had not specified C09 C13 C14 M035.
C54 carries the denominator: 327,569 words, 1,190 pages, and 1,156 days, for 283 words per day. It also carries the inspector-authorship figure: 1,521 inspector-authored words, or about 1.3 words per day, supported by the internal wordcount, authorship, and OCR reports INTERNAL.C54.31 INTERNAL.C54.30 INTERNAL.C54.ForensicOCR.
Every penalty order cites the same generic catch-all provision without naming what was found or where. The first penalty-order exemplar is M146, and the templated-penalty pattern is proved in C12 SCC § 1.28.010.
The supervisor-branded penalty block appears on all 19 produced administrative penalty orders as part of a 24-cycle run, each on the same catch-all; the rate doubled to $2,000 per cycle in fall 2025 M585 C10 C12. The inspector supplied permit-application scope language C31, looped the supervisor, recorded complaints to City Council, a Councilman's office, the Mayor's office, and the Police Chief in an owner-facing email C52, and the permit demand was routed through the owner's attorney before a long-time contractor walked off C27 C32.
The denominator is 283 words per day for 1,156 days, with about 1.3 daily words authored by the inspector C54 INTERNAL.C54.31 INTERNAL.C54.30 INTERNAL.C54.ForensicOCR. This card places that volume against the record's own dates and shows why a supervisor should not treat the file as routine without checking the predicate. The demand for specifics was followed by neighbor-yard photographs and a move from preliminary notice to formal order C05 C07; the penalty rate doubled in the window of the attorney-routed permit demand M585 C27; supervisor loops and complaints-to-officials email appear at contested steps C52; and the cost landed before access through $31,230 in charges (documented across C09, C13, and C14), a title cloud, a lost contractor, and an attorney-routed scope change C13 C14 C32 C27.
The strongest City response is that this volume is ordinary output for a multi-year enforcement process the owner could have ended by abating violations or appealing the order; correlation with owner actions reflects the procedural calendar; and the fee total reflects continued noncompliance. That response assumes the City had given the owner an identifiable violation to abate or appeal. Across the period reviewed, the City refused three written demands for specifics and never amended the order to name the violation C07 C29. The volume is not the legal violation by itself. The review problem is the scale of process generated on a predicate that stayed generic.
Personnel: Paul Lovato · Bo Cosley · Jacqueline M. Baritell
---