The City of Sacramento has a written process for what happens after somebody reports a code complaint. It is printed on the notice the City mails to the property owner, as a flow chart headed “Inspection and Notice Process”. The first step costs nothing. The owner gets twenty-one days to fix the problem voluntarily. A Code Liaison can close the case without an officer ever being assigned. An inspection has to confirm that a violation exists. Only then does a Notice and Order issue, and only at that point does any money attach.
The City mailed that notice, with that flow chart, to 4880 T Street on January 29, 2026. It did not use that route on this case in March 2023. This page sets the two side by side. It is not an argument about why. It is what the City's own documents say the route is, and what the City's own file says happened instead.
The five steps, as the City prints them
From the Notice of Alleged Violation packet mailed to this property on January 29, 2026 — page 3, section 5, “Inspection and Notice Process” (N1).
Complaint reported to the City of Sacramento → NOTICE OF ALLEGED VIOLATION SENT TO PROPERTY OWNER → Timeline allocated to correct violation(s) — 21 DAYS → Violation(s) NOT Corrected? → INITIAL INSPECTION · Violation confirmed · Notice and Order issued → Notice and Order sent to property owner. Notice and Order, Monitoring, Title Report and Termination fees and Admin. Penalties assessed against the property. Violation(s) Corrected? → Case closed. No fees are due.
| Step | What the City's own document says it is | On Case 23-009185 |
|---|---|---|
| 1 | Notice of Alleged Violation. Mailed to property owner and to tenant/occupant. The packet's own fee schedule lists it as “Courtesy notice, not required — No fee.” | Never sent |
| 2 | Twenty-one days to correct. “You are responsible for correcting such violations within 21 days of the date noted above.” “The city is requesting you voluntarily comply and correct the violation(s).” | Never given |
| 3 | Code Liaison. A named phone number and email on the face of the notice. “A Code Enforcement officer may only respond if the Code Liaison is unable to resolve your case.” | Never involved |
| 4 | Initial inspection. Every branch of the flow chart passes through it. The Notice and Order issues only from the branch marked “Violation confirmed.” | Never done |
| 5 | Notice and Order. The first step that costs anything: Notice & Order $730.00, Code Compliance Monitoring Fee $340.00, appeal processing $560.00. | Issued first |
The packet also explains the notice in plain terms: “A Notice of Alleged Violation is a courtesy notice … A follow-up date for property inspection by the Code Enforcement Officer will be scheduled to determine if compliance was achieved if the case cannot be closed by the Code Liaison.” And on what happens if it isn't fixed: “If the violation(s) are not corrected at the time the Code Enforcement Officer conducts a follow-up inspection, he/she shall issue a Notice and Order, Administrative Penalty, and/or Criminal Citation to the property owner.” (N1, page 7.)
The same address, on that route, in 2026
On January 29, 2026 the City opened case 26‑003780 at 4880 T Street on a noise complaint and mailed a Notice of Alleged Violation from the Neighborhood Code Compliance Division — addressed to Jackie Baritell Trust, served by first class mail on both property owner and tenant/occupant, boxes 21 and 29 checked: “Noise: Mechanical device” and “Other: 8.68.060 Exterior noise standards.” Twenty-one days. Code Liaison contact printed on it. No fee. (N1, page 1.)
That notice is the reason this page exists. It is the City demonstrating, at this property, that the route is real and that it applies here.
Case 23-009185, March and April 2023
Every entry is from the City's own 311 export or its own case file.
| Date | What the City's record shows | Source |
|---|---|---|
| Mar 17, 2023 11:41 a.m. | 311 ticket 230317‑1609966, filed on the web. Service type Code Enforcement; sub-service type Work Without a Permit. The narrative describes a garage addition and, at greater length, noise at night and in the early morning. | R.25-3549.3 · Card 41 |
| Mar 18, 2023 | Case opened in the City's case system. Type: Work Without Permit. Categories: Substandard Building. No City employee has yet visited the property. | M001 |
| Mar 20, 2023 12:00 p.m. | First site visit. The inspector's note: “from the front of the dwelling there looks to be no work going on … A buster preliminary letter will be requested. With a card left at the door, and a preliminary letter, I will see if anyone gets ahold of me.” | M024 |
| Mar 21, 2023 | A Housing and Dangerous Buildings preliminary letter issues, giving ten business days to make contact and naming a $1,075.00 enforcement fee if contact is not made. Its attached Correction List reads “B31: Other” and “B59: 8.100.190 — Permits Required.” | M117 · M118 · Card 2 |
| Apr 4, 2023 | The owner's representative writes to the inspector at 8:52 a.m., inside the letter's window. The inspector reproduces that email in his own case note and replies the same morning. | M024 · Card 6 |
| Apr 7, 2023 | Case note: “Since there was no reply back to e-mail, I contacted the complaining party to find out if the work can be viewed from their property.” | M024 |
| Apr 11, 2023 7:00 a.m. | Case note: “Due to lack of contact from the Owner and failure to obtain an HDB permit I issued the Notice and Order, I also ordered a Cloud be placed on the title and a Title report be done.” | M024 · Card 6 |
| Apr 12, 2023 | Notice and Order to Repair or Demolish. Its Correction List carries the same two codes and the sentence “Neither interior nor exterior has been completely inspected.” | M124 · M125 · Card 2 |
Twenty-six days from the complaint to the Notice and Order. The Neighborhood Code track that the 2026 notice runs on — Title 8.04 of the Sacramento City Code — does not appear anywhere in the 631 pages of the case file the City produced for this case. Neither 311 ticket number appears in it either, and neither does the date March 17, 2023.
The first 311 search began after the complaint
When the case file was asked for, the City's first 311 export carried its own filter in its header: “Date Field: Date/Time Opened equals Custom (3/20/2023 to 10/30/2025).” The complaint that opened the case was filed March 17. Scoped that way, the search could not return it. A corrected export, run after the requester named the ticket number, contains it. Both are hosted: R.25-3549.2 and R.25-3549.3. Card 41 sets out what each one shows.
What the code requires either way
The published route is City practice. These are the provisions that apply regardless of which track a case is on.
| Provision | What it requires |
|---|---|
| SCC 8.100.700 | Proceedings commence only where the building official “has inspected or caused to be inspected” the building and “has found and determined” that it is substandard. |
| SCC 8.100.720(A)(2) | The Notice and Order must contain a brief and concise description of the conditions found to render the building substandard. Card 1 |
| SCC 1.28.010(C)(3) | Where the violation pertains to building, plumbing, electrical, structural or zoning provisions, “the responsible party shall be provided a reasonable period of time to correct the violation prior to imposition of the administrative penalty,” except where there is an immediate danger to health or safety. |
What this page does not say
- It does not say the City was required to send a Notice of Alleged Violation on this case. Nothing in Chapter 8.96 or Chapter 8.100 requires one, and the City's own fee schedule calls it “not required.”
- It does not say the case was routed to Housing and Dangerous Buildings for any particular reason. No document produced in this case states a reason, and none is asserted here.
- It does not say the March 20 filter on the first 311 export was deliberate. That date is also the first entry in the case file, and the record does not distinguish between the two explanations.
- It does not treat any case note, photograph or later production as the basis of the April 12, 2023 Notice and Order. That order states no basis. The material produced years afterward under the Public Records Act cannot supply one, and is not offered here as though it could.
Sources on this page: the Notice of Alleged Violation packet mailed to 4880 T Street on January 29, 2026 for case 26-003780, seven pages, hosted as N1; pages of the May 2026 case-file production (R.26-1965.2) cited as M-numbers; and the two Sac311 exports released on Request 25-3549. The agenda language quoted on the hearing pages of this site comes from the City's own published Code Compliance Hearing agenda for February 11, 2026, at cityofsacramento.gov. Where a finding on this page is developed further, the card that carries it is linked in line.