SB 1383 inspection software for the field and the office

What jurisdictions are required to inspect

SB 1383 makes jurisdictions the front-line regulator, not just the service provider. The inspection obligations run across several programs at once:

• Commercial edible food generators — jurisdictions were required to inspect Tier 1 and Tier 2 commercial edible food generators on or before January 1, 2024, at a rate sufficient to determine compliance — including whether each generator holds a current contract or written agreement with a food recovery organization.
• Contamination monitoring — route reviews and waste evaluations to assess container contamination, with findings recorded over time and follow-up for accounts that keep failing.
• Regulated entity compliance — verifying that businesses and multifamily properties actually subscribe to and use the organic waste collection service they are required to have.
• Complaint investigation — investigating complaints of alleged violations, which may require an inspection, route review, or compliance review to resolve.

Reference: 14 CCR §§ 18995.1, 18995.3

The part that goes wrong is the paperwork, not the inspection

Inspectors are generally good at inspecting. What breaks down is everything after: a finding written on a paper form, photographed on a phone, or typed into a personal spreadsheet, then re-entered at the office days later — if it gets re-entered at all.

By the time a compliance review arrives, the jurisdiction can describe its inspection program but cannot evidence it. The inspections happened. The record showing they happened, at what rate, with what findings, and with what follow-up, does not exist in a form anyone can produce.

The second failure is the broken chain. A notice of violation that cannot be traced back to the inspection that prompted it — or forward to whatever resolved it — is a weak record even when every individual document exists.

Field to office, without the double entry

Connect gives inspectors a mobile inspection flow built for a phone in a parking lot: the generator is already there, the form matches the inspection type, photos attach to the finding, and the record syncs to the office tracker. Nobody re-keys anything, which is what makes the record complete rather than merely intended.

• Guided inspection forms — the form follows the inspection type, so field staff capture what the regulation expects rather than what fits on a clipboard.
• Photos attached to findings — contamination evidence lands on the record it belongs to, not in a camera roll.
• Live office tracker — the office sees findings as they are filed, not at the end of the week.
• Case history end to end — complaint, inspection, enforcement, and resolution stay linked as one case you can produce on demand.

Enforcement that produces a defensible record

Enforcement is where jurisdictions are most exposed, because an escalation ladder only holds up if each rung is documented. Connect tracks notices of violation alongside the inspection that triggered them, the generator they were issued to, and the follow-up that closed them — with dates attached to each step.

Route reviews get the same treatment. Contamination findings accumulate against the account rather than living in isolated quarterly files, so a pattern of repeat contamination is visible as a pattern, which is exactly what makes escalation defensible.

Complaints come in through the front door

Residents report problems whether or not you have a system for it. Connect includes a public complaint form for your jurisdiction, so a resident report arrives as a tracked case with a timestamp instead of a voicemail. From there it follows the same chain as any other case — investigated, inspected if warranted, resolved, and recorded.

That matters for compliance as well as service: investigation of complaints and alleged violations is its own Implementation Record category, and complaint records are among the easiest evidence to lose.