Disclosure focus
This disclosure is about whether your organisation falls within the scope of the California climate-risk reporting requirement. In practice, it asks you to determine if you are a covered entity and, if so, to explain the climate-related risks and governance matters that are relevant to the business as a whole, rather than only to a single site or flagship location.
The practical focus is on the organisation’s overall exposure and management approach across its operations, assets, and activities that matter to the reporting boundary. That means looking beyond headline facilities to the parts of the business that could materially affect climate risk, resilience, and oversight, so the report reflects the full covered entity rather than a narrow operational snapshot.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official CARB source.
Before you start
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Preparation
Key datapoints to prepare
＋ Show SB261-APPLICABILITY sub-elements (LRA working checklist)
State the organisation’s annual revenue or gross receipts.
Identify the legal form of the business entity.
Confirm whether the business operates in California.
Record whether any exemption applies.
Indicate whether the insurance-entity exclusion applies.
Say whether the report is prepared at parent level on a consolidated basis.
Confirm whether revenue is above $500 million.
Indicate whether the entity is based in the United States.
How to prepare it
1Confirm the reporting perimeter first: identify the legal entity or group you are assessing, note the business form, and record whether the reporting is being prepared at parent level or for a standalone entity.
2Check whether the organisation is in scope by testing the California nexus and the U.S. base, then capture a clear yes/no conclusion with the supporting source documents.
3Measure the relevant turnover figure for the period used in the assessment, using the same basis consistently, and keep the working papers that show how the number was derived.
4Assess the threshold condition against the revenue figure and record the result, together with the evidence used to support the calculation and any assumptions applied.
5Review whether any exclusion or exemption applies, including any insurance-related carve-out, and document the reason for the conclusion plus any changes from prior assessments.
6Before finalising, compare the completed assessment with the official source material to make sure the scope, figures, and exemption conclusions still align with the latest wording and any updates.
Request the data
Request the entity and revenue evidence
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Do we sit within the scope test for this California reporting obligation, based on our entity type, California activity, revenue level, and any exclusion or consolidation position?
Use your organisation’s own terms first, then map them to the reporting fields. For example, ask for the group structure, legal entity type, turnover or gross receipts, California trading footprint, any insurance-related exclusion position, and whether the figure is held at parent or local level.
Weak request
Please confirm whether we are covered and send the SB 261 applicability evidence.
Why it fails: This uses framework language that may not match how the business tracks the information, and it does not specify the exact evidence needed to test the scope position. It also leaves out the source, basis, period, and ownership details needed to trace the answer back to records.
Better request
Please send the evidence pack for [entity] and [period] covering: the revenue or gross receipts figure used for the scope review, the California business activity check, the legal form, any insurance-related exclusion position, and whether the figure is held at parent or entity level. Include the source system or file, the basis used, and the name of the person who can confirm the position.
Industry examples
Draft your disclosure
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Method note
State the basis used to decide whether the entity is in scope, including how revenue was measured, how California activity and U.S. location were assessed, whether the report was prepared at parent level, and how any exemption or insurer exclusion was applied.
Context note
Explain that the figures are being used to determine whether the business falls within the reporting population, rather than to describe performance, and note which recorded facts support the final applicability conclusion.
Fluctuation statement
If the applicability result changes from one period to the next, point to the specific driver, such as a revenue movement across the threshold, a change in business presence, a different consolidation basis, or a revised exemption assessment.
Content index entry
SB261-APPLICABILITY Covered entity applicability — [location / page] / [notes]
Download Centre
Preparation tools & forms
Professional preparation tools for SB261-APPLICABILITY — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.
Free · Community members
Assurance readiness
For each claim, check the evidence
Evidence pack to prepare
Common reporting gaps
Figures are stated without the supporting narrative, or narrative without figures.Scope is inconsistent between the text and the numbers.The reporting boundary is left undefined.Material changes since the previous period are not disclosed.Estimates and measured values are not distinguished.Source records for the figures are not identified.
Common gaps
Mistakes to avoid when collecting the data
Wrong owner asked
Teams often ask the sustainability lead for legal form, revenue, or US presence when those facts sit with finance, tax, legal entity management, or the parent-company reporting team.
Framework language used too early
People ask for answers in disclosure terms instead of the organisation’s own records, which makes source teams translate rather than simply confirm the underlying fact.
Scope not fixed
The data pull starts before everyone agrees which legal entity, group perimeter, or reporting population is in scope, so the figures and status checks do not line up.
Wrong period basis
Collectors mix a current snapshot with a prior-year revenue basis or another timing point, so the applicability check is built on mismatched dates.
Counting bases mixed
One team uses standalone entity figures while another uses group-level numbers, which can make the revenue test and the entity status check point to different populations.
Source labels lost
Original file names, system tags, or ledger labels are stripped away, so later reviewers cannot trace where each revenue or entity-status value came from.
Separate populations merged
Insurance-related entities, parent-level reporting units, and operating subsidiaries are blended into one file even though they should be checked separately.
Evidence trail incomplete
The pack contains the answer but not the supporting extract, date stamp, or reviewer sign-off, so no one can show how the applicability call was reached.
Where judgement is often needed
Group boundary after a buy-in or sale
Set the reporting perimeter using the business structure in place for the reporting period, and explain any material change caused by an acquisition, disposal or similar transaction.
Which revenue figure to use when records differ
Choose one clearly defined revenue basis, apply it consistently, and disclose the source and timing if internal and external figures do not match exactly.
Cross-border legal form and local labels
Map overseas legal forms to your own entity description in a way that is consistent and explain any judgement where local naming does not align neatly with the California test.
Operations that sit close to the California line
Decide whether the organisation is in scope based on how it actually trades or operates in California, and state the practical basis used where the position is not clear-cut.
Parent-level reporting versus entity-by-entity review
If the group can be assessed at parent level, use that approach consistently; if not, explain why a different boundary was used and how the conclusion was reached.
Insurance-related exclusion where activities are mixed
Where the organisation has both insurance and non-insurance activities, explain how you separated them and how you decided whether the exclusion applies to the relevant part of the business.
Estimated figures where measured data are not available
Use estimates only where direct figures are not yet available, describe the method and assumptions, and flag any areas where the result could change once better data arrive.
Rounding and threshold proximity
State the exact or rounded figure used for the threshold test, and disclose any rounding approach where the result sits close to the cut-off.
Privacy limits on sharing supporting detail
If data protection rules prevent full disclosure of underlying records, provide the highest level of aggregation that still supports the conclusion and explain the limitation.
Examples
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
Illustrative (synthetic) example — Utilities
We would say our group is a UK-incorporated parent filing on a consolidated basis, with our California activity captured through a U.S. subsidiary. Our latest annual turnover is **$620 million**, so the revenue threshold is met; we do business in California (**Y**), we are not using an insurance-company carve-out (**N**), and we are not claiming any other exemption (**N**). - Legal form: corporation - Parent-level reporting: **Y** - U.S.-based entity: **Y**
This example shows how a reporter can describe the applicability check in plain language while still covering the key status points. It is synthetic and internally consistent.
Illustrative (synthetic) example — Consumer goods
We are a non-U.S. limited liability company that reports at the parent level, and our California sales activity means we do business in the state (**Y**). Our annual receipts are **$480 million**, so we do **not** clear the revenue threshold (**N**); we also do not rely on an insurance-only exclusion (**N**) and we are not otherwise exempt (**N**). - Legal form: limited liability company - Parent-level reporting: **Y** - U.S.-based entity: **N**
This example shows a different fact pattern where the revenue threshold is not met, while the other applicability indicators are still stated clearly. It is synthetic and internally consistent.
How companies report SB261-APPLICABILITY in practice
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.
Sands China Ltd.
Hotels, Restaurants, Leisure, Tourism Services · Macao · 2025
Sands China Ltd.'s 2025 ESG Report identifies California, Utah, Singapore, and Macao as significant locations of operation where the company owns property (p.49). However, the report does not provide quotable evidence regarding annual revenue, exemption status, insurance exclusion, legal form, parent consolidation availability, revenue threshold, or US-based entity status. This leaves several key applicability criteria unclear or unaddressed in the report.
Ingersoll Rand Inc.
Electrical Equipment and Machinery · United States · 2024
Ingersoll Rand Inc.'s 2024 Sustainability Report provides some related context on exemption status, noting risk categories such as Green (low risk), Yellow (medium risk), and Red (high risk), but does not clearly disclose the exemption status itself (p.61). The report includes references to revenue and acquisitions (p.5, p.75) and discusses material issues related to labor and employee matters (p.55-56), but it does not provide explicit information on SB261 applicability criteria such as annual revenue, business category, legal form, or insurance exclusions. Overall, key datapoints required for SB261 applicability are largely missing or unclear in this report.
CSX Corporation
Ground Transportation — Railroads · United States · 2024
CSX Corporation's 2024 Sustainability Report includes discussion of climate-related risk assessment integrated with their enterprise risk management program, as noted on page 48. The report also outlines alignment with the United Nations Sustainable Development Goals, specifically SDG 3 on health and well-being, on page 4. However, there is no quotable evidence regarding the applicability of SB261 disclosures, such as annual revenue, business category, exemption status, or legal form, found anywhere in the report.
✓ LRA AI Assistant · Human-in-the-loop
Ask Study Studio AI assistant about this disclosure
Get practical answers for your reporting context. Your first two answers are free — join LRA Community for free to continue without a limit.
TryHow do I prepare SB261-APPLICABILITY?What data do I need to collect?Where can I see a real-report example?What mistakes should I avoid?
2 free answers
Check your understanding
Scenarios to work through
A group has a US-incorporated parent with several operating subsidiaries. The parent prepares a single set of group accounts, and one subsidiary sells into California through local distributors.
QShould the preparer assess the parent group as a whole, or treat the California-facing subsidiary on its own for this applicability check?
Reveal model answer →Hide answer ↑Use the entity that will be reporting, then decide whether the group can be looked at at parent level. If the parent is the reporting unit and group reporting is available, the preparer should test the parent-led position rather than isolating one subsidiary. The California activity still matters for the 'does business in California' point, but it does not by itself change which legal entity is being assessed.
Why this matters · Start with the reporting perimeter, then test California activity and group reporting position against that perimeter.
A company is organised as a limited liability company and had annual gross receipts of 520 million currency units in the latest year. It has no staff or office in California, but it ships products there through third parties.
QDoes the absence of a California office mean the business can stop the applicability assessment?
Reveal model answer →Hide answer ↑No. The preparer still needs to check whether the business is active in California in some way and whether the revenue level is above the threshold. A lack of premises or employees in the state does not, on its own, end the assessment if the business still reaches the market there.
Why this matters · Physical presence is only one part of the picture; California market activity and revenue both need to be considered.
A financial services group has a regulated insurance subsidiary with 610 million currency units of annual revenue. The rest of the group is a non-insurance trading business, and the insurance arm is the only part with California customers.
QShould the preparer treat the insurance subsidiary as excluded, or include it in the covered-entity review because the wider group is above the revenue threshold?
Reveal model answer →Hide answer ↑The preparer should first identify whether the insurance-related exclusion applies to that entity. If it does, that subsidiary is not treated the same way as the rest of the group for this check, even if the wider group is large and active in California. The decision turns on the entity’s own status, not just the group’s size.
Why this matters · Check whether a specific exclusion applies to the entity before relying on group revenue alone.
A multinational has a US parent and a non-US holding company above it. The non-US parent owns the US operating company, which has 505 million currency units of annual revenue and sells into California.
QWhich entity should the preparer test for this applicability screen: the non-US holding company, the US operating company, or both?
Reveal model answer →Hide answer ↑The preparer should test the entity that sits within the reporting scope and is actually being assessed for this disclosure. If the US operating company is the relevant reporting entity, its own legal form, revenue, California activity, and any exclusion status need to be checked. The non-US holding company is only part of the analysis if it is itself the reporting entity or if the reporting approach is at parent level.
Why this matters · Match the assessment to the actual reporting entity, then apply the revenue, California activity, legal form, and exclusion checks to that entity.
Framework references
Related framework references
How this disclosure maps across the major reporting frameworks.
California
SB261-APPLICABILITY
within California SB 261: Climate-Related Financial Risk Act
Open official source →Related & explore
Climate-related financial risk disclosure → Guide ✓Implementation fee and administration →TCFD or equivalent framework alignment → Guide ✓Reporting gaps and completion plan →Biennial reporting timeline and enforcement status → Guide ✓Measures to reduce and adapt to climate-related financial risk → Guide ✓Show all 6 related disclosures →
FAQ
Questions this page answers
How do I use the SB261-APPLICABILITY page to work out whether my organisation should prepare a California SB 261 climate-related financial risk disclosure?+−
Start with the plain-language explainer and the datapoints to prepare, then use the step-by-step preparation section to organise the information you already hold. The page is designed to help you turn those inputs into a draft and an evidence pack, rather than to act as an official source.
What data do I need to gather for SB261-APPLICABILITY before I start drafting?+−
The page says to prepare annual turnover, California trading presence, exemption position, insurance carve-out, entity legal type, parent-level reporting, revenue threshold test, and US domicile status. Use those items as your collection checklist so you can build the disclosure from a complete set of inputs.
How should I set scope and methodology for the SB261-APPLICABILITY disclosure using this page?+−
Use the step-by-step 'how to prepare' section to decide which entity or group is in scope and to line up the datapoints that support that decision. The page also flags parent-level reporting and exemption position, which are useful anchors when you document your approach.
Who should own the SB261-APPLICABILITY data collection and drafting work?+−
The page is set up for a sustainability or ESG manager, HR or data owner, or an assurance reviewer to use together, so ownership should sit with the person coordinating those inputs. In practice, assign each datapoint and each assurance claim to a named owner so the evidence pack can be completed on time.
What should I put in the evidence pack for SB261-APPLICABILITY to be assurance-ready?+−
The page includes an evidence pack with five items and a separate set of six assurance claims to verify. Use those together so each claim is backed by a clear claim, risk and evidence trail before you finalise the draft.
What are the common mistakes people make when preparing the SB261-APPLICABILITY disclosure?+−
The page has a section on common reporting gaps and mistakes, which is there to help you spot weak points before review. Use it as a pre-submission check so you can correct missing data, unclear scope or unsupported statements early.
How do I use the Prep & Assurance workbook for SB261-APPLICABILITY?+−
The Download Centre includes a Prep & Assurance workbook in .xlsx format, which is intended to help you organise the preparation and assurance steps. Use it alongside the page’s datapoints, assurance claims and evidence pack so your draft and support files stay aligned.
What can I do with the printable Library Card PDF for SB261-APPLICABILITY?+−
The Download Centre also provides a printable Library Card in PDF format, which is useful as a quick reference while you are collecting data or checking the draft. It can help you keep the key preparation points and assurance items in view without reopening the full page.
Are the synthetic example disclosures on the SB261-APPLICABILITY page useful for building my own draft?+−
Yes — the page includes synthetic illustrative example disclosures, including a quantitative table, to show how the information can be presented. Treat them as examples only and adapt the structure to your own data, making sure any figures you use are internally consistent.
Can I reuse data prepared for ESRS E1 (Climate Change) for SB261-APPLICABILITY?+−
The page says ESRS E1 (Climate Change) is the closest correspondence, so some of the same underlying data may be reusable. Do not assume the disclosures are identical; use the page to see where your existing climate data can support the California disclosure.
More questions this page can help with
SB261-APPLICABILITY checklist for annual turnover, California trading presence and US domicile statusHow to document exemption position for SB261-APPLICABILITY in a working paperSB261-APPLICABILITY parent-level reporting: what evidence should I keepHow to build an assurance evidence pack for SB261-APPLICABILITYWhat are the six assurance claims to verify on the SB261-APPLICABILITY pageHow to use the SB261-APPLICABILITY workbook and printable Library CardSB261-APPLICABILITY common reporting gaps and mistakes to avoidHow to turn SB261-APPLICABILITY data into a draft disclosureSB261-APPLICABILITY synthetic example disclosure table and narrative startersESRS E1 climate data reuse for SB261-APPLICABILITYHow to assign ownership for SB261-APPLICABILITY data collectionWhat does the SB261-APPLICABILITY plain-language explainer cover
How this library is built
312 published reports indexed
63171 pages with page-level citations
247 practitioner guides
Free · LRA Community
Get your SB261-APPLICABILITY tools — free
Your preparation tools are free for LRA Community members and students. Register once (it's free) and your download starts right away — plus the Disclosure Library, templates and the LRA AI-assistant.
✓
You're in — your download is starting
Your file is downloading now. Your Community Cabinet — with the Disclosure Library, templates and the LRA AI-assistant — is ready too.
Open your Cabinet →