Case 23-009185 • 4880 T Street, Sacramento CA • Card 31 of 55

The Inspector Supplied the Applicant’s Permit-Scope Wording, and the City’s Own Permit Export Later Classified That Work as Residential Housing-Minor, With Plans Not Required

Risk: HIGH Punch: 9 / 10

1 — Header

The inspector supplied the applicant’s permit-scope wording, and the City’s own permit export later classified that work as Residential Housing-Minor, with plans not required.

In plain terms

When a building official tells a property owner to get a permit, the owner is supposed to describe the work in their own words on the application. SCC §8.100.190 Here, a city inspector emailed the applicant the exact wording to put in the “scope of work” box — including the line “Remove all Illegal construction in/at garage” — R.25-3549 and that same wording then became the official scope on the permit the city issued, so the city’s own permit record now carries the inspector’s phrasing about the work. M010 The detail that makes this matter only surfaced once the records were pulled: the city’s own permit list files the like-for-like/minor-repair portion under a routine category — “Residential Housing-Minor” — and marks it “Plans not required.” R.25-3549 That sits in tension with how the case began, when the city’s served order had called the building “substandard and/or dangerous.” M122–M124 HSC §17980 To be fair to the city’s side: its “plans not required” tier is tied to the “like for like” minor-repair part of the job, and its own file shows Planning getting pulled in the moment the owner wanted to expand the work — a different siding around the fireplace, added square footage at the garage. M010 M011–M012 So this is not a clean either/or. But the narrower point still holds: the city treated the like-for-like minor-repair portion as routine and plans-exempt at the very time its served order was still using broad “substandard and/or dangerous” language — M125 SCC §8.100.190 a contradiction the record only makes visible because the owner’s side forced the records out through public-records requests. R.26-1965

Bottom line: the inspector supplied the applicant’s permit wording, that wording became the city’s public permit record, and the city’s own permit-system export then files the like-for-like/minor-repair portion under a routine, plans-exempt record type (“Residential Housing-Minor”) — a narrower administrative register than the broad “substandard and/or dangerous” framing the case started with.
Source Citations (7)
  • M010Permit ledger for RES-2524445; scope matching Lovato’s supplied wording; “(Plans not required)”; VIOLATIONS table with B45, SCC §8.96.110(L), “Added square footage at detached garage to be permitted.” M010.pdf
  • M011–M012Successor permit RES-2603471; same record type and scope; siding inspection approved 04/02/2026; Planning-involvement note once scope expanded beyond like-for-like. M011–M012.pdf
  • M122–M124Served Notice and Order boilerplate invoking Chapters 8.96 and/or 8.100 and HSC §17980/§17985; broad “substandard and/or dangerous” framing. M122–M124.pdf
  • M125Served Correction List with B59, SCC §8.100.190, “Permits Required” placeholder; no specific permit category named. M125.pdf
  • R.25-3549Nov 2025 CPRA production; hosts Lovato email supplying permit scope wording and Block_Permit_List_Apr2_2026.csv classifying RES-2524445 and RES-2603471 as Residential Housing-Minor, “(Plans not required).” NextRequest
  • R.26-1549Apr 2026 CPRA production; closed as complete. NextRequest
  • R.26-1965May 2026 searchable CitizenServe case file, 631 pages. Provenance source for M-page citations; Lovato permit-scope email not in M production, separately produced via R.25-3549. NextRequest