California’s climate-disclosure laws land on the sustainability team’s desk, but the work is a data-engineering programme. Firms that mistake the first for the second will report late, incomplete, and unassured numbers.
SB 253 and SB 261 read like reporting obligations. They are, in the sense that a filing eventually leaves the building. But the filing is the last five per cent. Everything before it is a data problem: identifying sources, wiring feeds out of systems that were never built to emit emissions data, engaging suppliers who owe you nothing, and standing up controls that will survive third-party assurance. If you scope this as a document your ESG lead writes each year, you will discover in the final weeks that the numbers do not exist in any queryable form. This is a build. It should be run as one.
What the two laws actually oblige you to produce
They are separate instruments with separate thresholds, and it is worth keeping them apart. SB 253, the Climate Corporate Data Accountability Act, applies to entities doing business in California with more than one billion US dollars in total annual revenue. It requires accounting and reporting of Scope 1, Scope 2 and eventually Scope 3 greenhouse-gas emissions, measured in line with the Greenhouse Gas Protocol. SB 261 applies at a lower threshold — more than 500 million dollars in total annual revenue — and requires a climate-related financial risk report describing the firm’s material physical and transition risks and what it is doing about them, anchored to the TCFD recommendations or an equivalent framework. Insurers are carved out of SB 261. “Doing business in California” is not a token nexus; it tracks the state’s tax-code test (Revenue and Taxation Code section 23101), including a California-sales threshold that sits a little above 750,000 dollars for 2025 and is inflation-adjusted.
Free · 4 minutes
When two of your systems disagree, do you know which one to believe?
Fourteen questions on ownership, lineage, and quality — the difference between a number on a dashboard and a number you could defend. Banded finding on screen, full sheet by email.
The California Air Resources Board adopted its initial implementing regulations in early 2026 and set the first SB 253 Scope 1 and 2 report for 10 August 2026, with the reporting year keyed to your fiscal year-end. CARB has signalled it will exercise enforcement discretion for that first cycle and will not require assurance on the initial submission. That is a grace period on the paperwork, not on the data. The measurement year is already behind you or running now.
Scope 1 and 2 you can solve; Scope 3 you cannot rush
Scope 1 and 2 are, mostly, an internal data-collection problem. Scope 1 is direct emissions — combustion in your own boilers, vehicles, refrigerant leakage. Scope 2 is purchased energy. The source data lives in fuel invoices, fleet-card records, utility bills and metering. It is scattered and inconsistently formatted, but it is yours, and with effort it can be pulled into a single accounting layer with emission factors applied consistently. Hard, but tractable, and tractable on the 2026 timeline.
Scope 3 is a different class of problem, and it is the one that sinks programmes started late. Scope 3 is your value chain — purchased goods and services, upstream transport, business travel, employee commuting, use of sold products. Most of that data is not yours. It sits with suppliers who have no contractual reason to give it to you in the format you need, on the cadence you need. You cannot buy your way out of this in the final quarter. Supplier engagement is a slow, relationship-driven process: identifying which suppliers matter by spend and emissions intensity, building a request they can actually answer, and having a defensible estimation method (spend-based or activity-based factors) for the long tail that will never respond. CARB has deferred the detailed Scope 3 requirements to further rulemaking, with reporting expected from 2027. Treat that as the deadline that governs your programme, because it is the one you cannot compress. The same value-chain data-plumbing challenge shows up wherever emissions carry a cost — it is the pattern behind the EU ETS and FuelEU emissions data pipeline in shipping, and the lesson is the same: the pipeline takes longer to build than anyone budgets for.
The vendor and integration layer is the real decision
Almost every firm at this scale buys a carbon-accounting or ESG-data platform rather than building one. That is usually the right call, but the platform is not the programme — it is one component that has to be fed. The decisions that matter are integration decisions: which systems of record feed it (ERP, procurement, travel, HR for commuting, facilities and utility feeds), whether those feeds are automated or a spreadsheet someone re-uploads each quarter, and where the emission-factor library comes from and how it is versioned. A platform populated by manual uploads is a manual process with a dashboard on top. It will not survive assurance and it will not scale to Scope 3. Model the integration work honestly before you sign, and evaluate vendors on how well they ingest your actual sources, not on the polish of the demo.
Sequencing the build against the dates
- Confirm which of the two laws catch you, at which threshold, and pin your reporting year to your fiscal calendar. The two have different scopes; a firm can be in both.
- Inventory Scope 1 and 2 sources and get them into one accounting layer with a versioned emission-factor set. This is the near-term deliverable.
- Start supplier engagement for Scope 3 now, prioritised by spend and emissions intensity, with an estimation fallback for non-responders. This is the long pole.
- Stand up the SB 261 climate-risk report as a governance artefact — physical and transition risks, owners, and the board’s line of sight — not a marketing document.
- Build the audit trail from day one: source-to-figure lineage, factor provenance, and change history. Assurance-readiness cannot be retrofitted.
Assurance is a design constraint, not a later stage
CARB is not requiring assurance on the first SB 253 cycle, but limited assurance over Scope 1 and 2 is scheduled to phase in from 2027, moving towards reasonable assurance around the end of the decade — dates worth confirming against the final regulation as the rulemaking settles. An auditor will ask to trace a headline figure back to source records and reproduce it. If your pipeline cannot show how each number was derived, which factor version applied, and who changed what, the assurance engagement becomes an archaeology exercise you pay for by the hour. The discipline is the same one that makes any regulated metric defensible — build the lineage in, the way an assurance-ready ESG data pipeline does, so the number and its evidence arrive together. The SB 261 risk report faces a softer but real version of the same test: a board that has signed it will be asked what it rests on, which is where board-level risk reporting that survives scrutiny earns its keep.
The litigation over these laws — a First Amendment challenge led by business groups — is live, and the enforcement posture on SB 261 in particular has shifted with court rulings, so verify the current status before you rely on any single deadline. But none of that changes the build. The data does not collect itself faster because a filing date moved. The firms that will report clean, assured numbers are the ones treating this as the data programme it is, starting from the sources and working towards the filing — not the other way round.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Free interactive tool
Interactive deadline calculator
Check which regulations apply to you and when
Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.
Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.
Full Governance by Sixteen Pillars
Govern your business. Prove your compliance.
A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.
See what's coming