Skip to main content

CalRecycle reporting

CalRecycle annual report software for SB 1383 jurisdictions

The CalRecycle annual report is due August 1 each year and covers the entire previous calendar year. For most jurisdictions the reporting itself is not the hard part — the hard part is that the underlying data lives in eight places, arrives from haulers in whatever format they prefer, and has to be reconciled every summer under deadline.

CityGreen Connect collects that data as it is generated, so the annual report assembles from work already done rather than a six-week reconstruction.

A no-obligation assessment of where your programs stand.

What the annual report covers

Jurisdictions report on the implementation of their programs across the full span of SB 1383 obligations. That includes organic waste collection, contamination monitoring, waivers and exemptions, education and outreach, hauler oversight, edible food recovery, procurement, CALGreen and Model Water Efficient Landscape Ordinance compliance, capacity planning, and compliance monitoring and enforcement.

The reporting period is the prior calendar year: the report due August 1 covers January 1 through December 31 of the year before. That gap is a trap — the data you need was generated up to nineteen months earlier, by staff who may no longer be in the role.

Reference: 14 CCR § 18994.2

The hauler data problem

Almost every jurisdiction hits the same wall: the tonnage numbers that drive the report come from haulers, and haulers report on their own terms. Quarterly submissions arrive as spreadsheets with different column names each time. A hauler serving four cities sends one file covering all of them. Facility names are spelled three ways. Someone on staff spends weeks turning that into numbers that add up.

This is also where reporting errors are most expensive, because a tonnage figure that was wrong in the source data is wrong in the annual report, and stays wrong in the record.

Connect flips the direction of the flow. Haulers submit through structured forms tied to your jurisdiction — collected tons, customer compliance, education and outreach distribution, and construction and demolition projects — so the data arrives already attributed, already validated, and already separated by jurisdiction even when the hauler serves several.

From submitted tonnage to a finished report

Once hauler data is in, reporting becomes a matter of reading it rather than assembling it. Connect provides the report views jurisdictions actually need at reporting time:

  • Collected tons — overall tonnage, plus breakdowns by hauler and by receiving facility.
  • Customer compliance — which accounts are subscribed and compliant, and which are not.
  • Route reviews — contamination monitoring activity and findings across the year.
  • Construction and demolition — C&D projects and non-compliant C&D projects tracked separately.
  • Education and outreach — what was distributed, to whom, and in what volume.

Reporting and the Implementation Record are the same work

It is worth saying plainly, because jurisdictions often staff them as two separate efforts: the annual report and the Implementation Record draw on the same underlying evidence. Inspections, route reviews, education campaigns, waivers, and procurement all feed both.

When those records are captured once, in one place, the annual report stops being an event. The numbers are already there in August because they were filed in March, and the record that supports them is already assembled if CalRecycle follows up.

Built by people who have filed these reports

CityGreen Consulting has guided California jurisdictions through waste-management compliance since 1991, including compliance and financial auditing of waste haulers. Connect is the platform built out of that practice — the reporting views exist because the consultants using them needed them for real filings, not because a product team guessed at the workflow.

Common questions

When is the SB 1383 annual report due?

August 1 each year, covering the entire previous calendar year (14 CCR § 18994.2). The report due August 1 covers January 1 through December 31 of the prior year.

Our hauler serves several cities in one file. Does that work?

Yes — and it is one of the specific problems the platform is built to handle. Hauler submissions are attributed to the correct jurisdiction, so a shared hauler’s tonnage does not get merged across the cities it serves.

Can we import the tonnage history we already have?

Yes. Historical program data is brought into Connect during onboarding, so year-over-year comparisons survive the move instead of starting from zero.

Does the platform file the report for us?

Connect assembles and organizes the data behind the report. Submission remains yours — though CityGreen Consulting works with many jurisdictions on the filing itself as a consulting engagement.

Keep reading

Let's develop your program.

CityGreen Consulting has guided many California governments to full State compliance. We'd be happy to assess where you stand and recommend next steps.

A no-obligation assessment of where your programs stand.