California Enacts Landmark Climate Disclosure Bills SB 253 & 261

California just did the regulatory equivalent of walking into a room, clapping once, and saying: “Alright everyonenumbers on the table.” With two headline-grabbing lawsSB 253 and SB 261the state is pushing large companies to disclose (1) their greenhouse gas emissions and (2) their climate-related financial risks. If your business is big enough and “doing business in California,” you may soon be reporting climate data with the kind of seriousness usually reserved for taxes and caffeine intake.

This article breaks down what the bills require, who’s covered, what the timelines look like, what’s happening with implementation, and how to prepare without turning your finance team into full-time carbon philosophers.

Quick Overview: What SB 253 and SB 261 Do

• SB 253 (Climate Corporate Data Accountability Act) requires qualifying companies to publicly disclose Scope 1, Scope 2, and eventually Scope 3 greenhouse gas (GHG) emissions, plus obtain third-party assurance.
• SB 261 (Climate-Related Financial Risk Act) requires qualifying companies to publish a climate-related financial risk report and describe measures adopted to reduce and adapt to those risks.
• Both laws focus on large entities “doing business in California”even if headquarters are somewhere elsebecause California has always been a bit of an overachiever.

Why These Bills Are a Big Deal

SB 253 and SB 261 are widely viewed as “landmark” because they don’t just nudge companies toward voluntary ESG storytelling. They require standardized, recurring disclosuresmoving climate data from the “nice-to-have” marketing shelf to the “auditor might ask about it” shelf.

The practical impact is bigger than California’s borders. Many large companies operate nationally with integrated supply chains, shared financial reporting systems, and one set of public disclosures. That means a California requirement can quickly become a de facto national reporting baselineespecially when suppliers, customers, and lenders start asking, “So… what’s your number?”

SB 253 Explained: The Corporate Emissions Disclosure Law

Who Must Comply

SB 253 applies to “reporting entities” with total annual revenues over $1 billion that do business in California. The law captures many public and private companies, and it generally doesn’t matter where you’re incorporated as long as you meet the thresholds and California nexus.

What Must Be Disclosed: Scope 1, Scope 2, and Scope 3

SB 253 requires annual public reporting of:

• Scope 1 emissions: Direct emissions from sources you own or control (think company vehicles, onsite fuel combustion).
• Scope 2 emissions: Indirect emissions from purchased energy (electricity, steam, heating/cooling).
• Scope 3 emissions: Other indirect emissions across the value chainoften the biggest category and the biggest headache (supplier emissions, business travel, product use, shipping, and more).

Scope 3 is where the real plot twist lives: you may need data from suppliers and partners who don’t know their own emissions yet. (If you’ve ever chased someone for a missing invoice, imagine doing it with carbon data across 14 categories.)

How Emissions Are Measured

SB 253 reporting is designed to align with established emissions accounting approaches commonly used in corporate reporting (often referencing GHG Protocol-style concepts such as organizational boundaries, operational control, emission factors, and verification practices). The goal is comparabilityso disclosures don’t turn into a creative writing contest called “My Carbon Footprint, But Make It Vague.”

Assurance: Yes, Someone Else Has to Check Your Math

SB 253 includes third-party assurance requirements that phase in over time. In plain English: you don’t just publish emissions numbersyou also bring in independent assurance providers to validate them. Expect internal controls, documentation, and audit trails to matter more than ever.

Where the Data Goes

The disclosures are submitted through a state-administered program (supported by a reporting organization selected by the California Air Resources Board). The key point: these disclosures are meant to be publicly accessible, not tucked away in a “please don’t click” PDF.

Penalties and Fees

SB 253 authorizes administrative penalties for noncompliance and also funds implementation through fees assessed on covered entities. Translation: if you’re covered, budgeting for compliance is not optionallike insurance, but with spreadsheets instead of commercials.

SB 261 Explained: The Climate-Related Financial Risk Disclosure Law

Who Must Comply

SB 261 applies to covered entities with annual revenues over $500 million that do business in California. This threshold is lower than SB 253, so SB 261 pulls in a wider set of companiesmany of which may not have mature climate reporting programs today.

What Must Be Published: A Climate-Related Financial Risk Report

SB 261 requires a biennial climate-related financial risk report that describes:

• Climate-related financial risks the company faces (physical and transition risks).
• Measures adopted to reduce and adapt to those risks.
• Use of a recognized disclosure framework (often discussed in practice as TCFD-aligned or equivalent approaches).

“Physical risk” can include extreme weather impacts, supply chain disruption, water stress, wildfire exposure, or heat-related operational issues. “Transition risk” can include policy changes, market shifts, carbon pricing exposure, litigation risk, reputational risk, or technology disruption. In other words: climate risk is business risk, with a weather app and a balance sheet in the same group chat.

Where It Must Appear

The report must be publicly available (commonly via the company’s website) and submitted through the state’s process. The public aspect matters: your climate risk story is no longer just for investorsit’s for customers, employees, journalists, NGOs, and that one competitor who definitely “isn’t looking” (they are).

Penalties

SB 261 allows administrative penalties for failure to publish the required report. Enforcement also considers whether an entity made good-faith efforts to comply.

What’s Happening Now: Implementation, Timelines, and Reality

CARB’s Role

The California Air Resources Board (CARB) is the main agency charged with implementing these programsdefining key terms, setting fee structures, establishing reporting mechanics, and determining practical deadlines.

A Key Reporting Deadline for SB 253

CARB has approved an initial regulation that sets a first-year reporting deadline for SB 253 of August 10, 2026, with first-year reporting focused on Scope 1 and Scope 2 emissions. That’s an important anchor date for planning internal timelines, assurance provider availability, and data readiness.

SB 261 Enforcement Status

SB 261 has faced legal challenges, and CARB has indicated that SB 261 reporting is currently voluntary under a court order. Practically, many companies are still preparing, because (a) requirements may return on a revised timeline and (b) climate risk disclosure capability is increasingly demanded by lenders, investors, customers, and global regulations.

Good-Faith Compliance and the “Start With What You Have” Approach

CARB has signaled that early reporting cycles emphasize good-faith compliance, acknowledging that some companies need time to build new data collection and reporting processes. That does not mean “wing it.” It means: document your assumptions, show your work, and demonstrate a clear plan for improving completeness and accuracy.

Real-World Examples: What These Disclosures Look Like in Practice

Example 1: A National Retailer

A retailer with stores across the U.S. may have relatively straightforward Scope 1 (fleet fuel) and Scope 2 (electricity), but Scope 3 dominatesmanufacturing of products, upstream shipping, packaging, and customer product use. SB 253 pushes the company to standardize supplier data requests, choose emission factor libraries, and build a repeatable methodology that survives third-party assurance.

Example 2: A Software Company

A software company might have small Scope 1, moderate Scope 2 (data centers, offices), but significant Scope 3 tied to cloud services, purchased hardware, business travel, and employee commuting. SB 261 then forces leadership to connect climate issues to financial outcomes: data center resilience, energy price volatility, and customer procurement requirements.

Example 3: A Manufacturer

Manufacturers may face material physical risks (heat stress, water availability, wildfire disruptions) and transition risks (carbon-intensive inputs, regulatory shifts, low-carbon product competition). A strong SB 261 report often includes scenario thinking, governance structures, and concrete mitigation actionsnot just “we care deeply” and a stock photo of a leaf.

How to Prepare: A Practical Compliance Roadmap

1) Confirm Coverage (Don’t Guess)

• Calculate revenue thresholds using the definitions that apply to the California programs.
• Evaluate whether you “do business in California” under the applicable standard.
• Identify subsidiaries and consolidated entities that may be included.

2) Build a Cross-Functional Reporting Team

Climate disclosure is not a “sustainability team only” project. You’ll likely need Finance, Legal, Procurement, Operations, Risk, Internal Audit, and IT. If you don’t involve Finance early, you may end up with a beautiful emissions report and zero confidence it can survive assurance.

3) Choose Methodologies and Set Boundaries

• Define organizational boundaries (equity share vs. control approaches) and keep them consistent year-over-year.
• Decide how you’ll handle estimation, data gaps, and materiality thresholds for Scope 3 categories.
• Create a methodology memo you can hand to an assurance provider without anyone crying.

4) Build the Data Pipeline

You can’t report what you can’t collect. Set up systems to pull energy, fuel, travel, procurement, logistics, and supplier data in a repeatable way. The end goal is not “a heroic spreadsheet.” The end goal is a process you can repeat annually without sacrificing weekends.

5) Engage Suppliers (Scope 3 Starts Here)

For many companies, supplier engagement is the long pole in the tent. Start now: segment suppliers by spend and emissions intensity, provide templates, align data requests with widely used standards, and plan for a multi-year maturity curve. Expect to use a mix of primary data and modeled estimates at first.

6) Prepare for Assurance Like It’s a Financial Audit (Because It’s Heading That Way)

Assurance providers will want evidence: invoices, meter data, contracts, emission factors, calculation logic, controls, approvals, and governance. Do a “mock assurance” run internally before you pay someone else to find the gaps.

7) Draft the SB 261 Narrative With Finance-Grade Specificity

A helpful climate risk report typically covers governance, risk identification, material impacts, scenario thinking, risk management processes, metrics and targets, and the actions underway. Avoid generic statements. Use concrete examples: supply chain concentration, facility exposure, insurance costs, capex plans, and product strategy changes.

Common Pitfalls (And How to Avoid Them)

• Waiting for “perfect guidance”: Start with what’s known, document assumptions, and iterate.
• Treating Scope 3 like a side quest: For many businesses, it’s the main storyline.
• Overpromising in narratives: Make sure claims match data and governance reality.
• Ignoring internal controls: Assurance will expose weak processes fast.
• One-off reporting: Build a repeatable annual cycle with clear owners and timelines.

What This Means Strategically (Beyond Compliance)

Yes, SB 253 and SB 261 are disclosure laws. But disclosures change behavior. Once emissions and climate risk become trackable and comparable, they influence procurement, financing, pricing, product design, site selection, and M&A. Companies that treat this as a strategic capabilitynot just a compliance tasktend to move faster, disclose better, and find efficiency opportunities along the way.

Conclusion: Don’t PanicBut Do Start

California’s SB 253 and SB 261 push large companies toward climate transparency with real reporting mechanics, defined thresholds, and public disclosures. SB 253 makes emissions reporting more standardized and assurance-ready. SB 261 makes climate risk a board-level financial discussion rather than a footnote.

The smartest move is to treat 2026 as a readiness milestone: confirm applicability, build your reporting engine, pressure-test your numbers, and create a climate risk narrative that can hold up under scrutiny. Do it well, and you’re not just complying with Californiayou’re building credibility in a world that increasingly asks, “Show me the data.”

Experiences From the Trenches: What Preparing for SB 253 & 261 Actually Feels Like

If you’ve never tried to collect emissions data across a modern company, let me paint you a picture. It starts with optimism. You make a neat project plan. You schedule a kickoff call. Someone says, “How hard can it be? We already have our utility bills.” This is the corporate equivalent of saying, “I’ll just have one chip” at a party.

Week one is mostly vocabulary. People discover that “Scope 1” is not a new streaming service, “Scope 2” is not a sequel, and “Scope 3” is not a conspiracy theoryalthough it sometimes feels like one. The facilities team has data, but it’s in three portals, two PDFs, and one invoice that only exists as a photo someone took in 2019. Procurement has supplier lists, but categories are labeled things like “Miscellaneous – Do Not Touch.” Finance wants consistency. Legal wants defensibility. Sustainability wants accuracy. IT wants to know why everyone suddenly cares about spreadsheets.

Then comes supplier outreach. You send a friendly email: “Hi! Can you share product-level emissions data for the past year?” Some suppliers respond instantly (bless them). Others reply with questions that reveal they thought “carbon accounting” was something only trees did. A few will send numbers that are clearly “vibes-based”rounded to the nearest million, suspiciously identical across multiple categories, or delivered in a PowerPoint slide titled “Our Commitment,” featuring precisely zero actual commitments. You learn to build a tiered approach: prioritize the biggest suppliers, accept modeled data where needed, and document assumptions like your future audit depends on it (because it might).

Meanwhile, SB 261 work feels like writing a story where the villain is uncertainty. Risk teams ask for probabilities. Climate risk often answers with ranges. Your operations leaders start mapping facilities against flood, heat, and wildfire exposure. Someone notices a key supplier sits in a region with increasing extreme weather events. The CFO asks, “Could this affect margins?” and suddenly the room gets quiet in a very productive way. The best SB 261 narratives don’t try to predict the future perfectlythey show governance, scenario thinking, and concrete actions: diversifying suppliers, hardening sites, adjusting insurance strategies, changing product mix, or improving energy resilience.

The most surprising experience for many teams is how quickly this becomes a systems project. To report annually (and withstand assurance), you need repeatability: data owners, cut-off dates, change controls, versioning, and a paper trail. “We can do it in a spreadsheet” works exactly onceusually the year you discover your spreadsheet has 17 tabs named “FINAL_v6_REALLYFINAL.” Eventually, you build a reporting calendar the same way you do financial close: collect, validate, reconcile, approve, disclose.

And here’s the good news: once the machine is built, it gets easier. The second year is less chaos and more refinement. Supplier data improves. Estimation shrinks. Governance matures. And the company starts seeing strategic value: emissions hotspots reveal efficiency opportunities; risk mapping supports smarter capex; cleaner disclosures strengthen trust with customers, investors, and employees. It’s still workbut it becomes the kind of work that makes your business sharper.