Disclosure focus
This disclosure is about keeping a regular, two-year reporting cycle in place and being able to show that the organisation is actually meeting it. In practice, the focus is on whether the organisation has a repeatable process for preparing and updating the required climate-related information on time, rather than treating it as a one-off exercise.
The practical question is how broadly the reporting approach is applied across the business. Organisations should think about whether the information covers the parts of the group or operations that are relevant to the disclosure, not just a single flagship site or a narrow pilot area. The aim is to show a consistent, organisation-wide reporting rhythm that can be maintained over time.
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-REPORTING-TIMELINE sub-elements (LRA working checklist)
State whether reporting is required every two years.
Note whether the rule is currently being enforced.
Specify which reporting period is in scope.
Record the legal deadline for the first report.
Enter the date the report was submitted.
Indicate whether the submission was made voluntarily.
How to prepare it
1Confirm whether this filing is on the two-year reporting rhythm and note the organisation’s current position on enforcement, so the timeline basis is clear before you start drafting.
2Set the reporting period you are covering and identify the first date the law expects for this report, using the same period consistently across the pack.
3Gather the source records that support the timeline entries, including internal approvals, filing logs, and any dated evidence that shows when the report was prepared and sent.
4Prepare the final timeline details in plain language: the period covered, the first statutory due date, the actual submission date, and whether the filing was made as a voluntary action.
5Record any exclusions, assumptions, or changes in status that affect the timeline, and explain why they were applied so the evidence trail is easy to follow.
6Check the completed disclosure against the official source before release, making sure the dates, status statements, and reporting-cycle description still match the latest authoritative guidance.
Request the data
Request the reporting timeline and filing status details
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Are we on a biennial filing track for this reporting cycle, and what is the current status of the filing, deadline, and any voluntary submission record?
Use your organisation’s own labels first, then map them to the reporting timeline fields. For example, if your team talks about filing windows, submission tracking, or regulatory notices, use those terms in the request and only translate them into the disclosure fields when you compile the evidence. This is a possible LRA training template; adapt it to your organisation and check the source material before sign-off.
Weak request
Please provide the SB 261 reporting timeline evidence and enforcement status for the disclosure.
Why it fails: It uses framework language that may not match how the business tracks filings, and it does not tell the owner which internal record to pull, which dates matter, or how to distinguish a planned filing from a voluntary submission. That makes it harder to answer quickly and consistently.
Better request
Please send the filing calendar entry, legal tracker extract, or board-approved note for [reporting cycle] covering [entity/group], showing whether this cycle is on a biennial filing track, the current filing status, the first-filing deadline used, the submission date, and whether any filing was made voluntarily. Include the source, last-updated date, and any short status note.
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 how you defined each field, including whether the filing was treated as required or voluntary, which reporting period was used, and how the deadline and submission date were captured from the source records.
Context note
Explain that these figures describe the filing position for the period in question, showing both the legal timing expectation and the organisation’s actual submission outcome.
Fluctuation statement
If the filing date moved relative to the deadline or the reporting period changed, note the operational or timing reasons behind that shift and whether the submission remained required or was made voluntarily.
Content index entry
SB261-REPORTING-TIMELINE Biennial reporting timeline and enforcement status — [location / page] / [notes]
Download Centre
Preparation tools & forms
Professional preparation tools for SB261-REPORTING-TIMELINE — 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
The information is presented without a date or as-at point.The scope or boundary of the statement is left undefined.Key terms are used inconsistently across the report.Material changes since the previous period are not disclosed.Assertions are made without supporting detail or a source record.Boilerplate is used that does not actually answer what is asked.
Common gaps
Mistakes to avoid when collecting the data
Ask the right owner
The request goes to a policy lead or legal contact instead of the team that actually tracks filing dates, so the answer comes back in framework language rather than the organisation’s own terms.
Set the boundary first
People start collecting dates and status without agreeing which entity, business unit, or filing population is in scope, so later evidence cannot be tied back to one clear boundary.
Use one time basis
One team uses the calendar year, another uses the reporting cycle, and the resulting dates cannot be compared because they were not gathered on the same basis.
Keep the original labels
Source files are copied into a summary sheet and the original field names, notes, and file titles are lost, making it hard to trace where each date or status came from.
Do not merge unlike groups
Voluntary filings and any other submission population are rolled together even though they need separate tracking, so the final dataset hides differences that matter.
Capture the evidence trail
The team records the answer but not the supporting file name, date pulled, or system reference, so no one can show how the figure was checked later.
Record the sign-off path
The data is passed along by email without a named reviewer or approval step, leaving no clear trail of who confirmed the reporting cycle, deadline, or status.
Check the timing against the filing date
The first-deadline date is entered from memory or a stale calendar note instead of the source used at the time, so the submission date and deadline no longer line up.
Separate current status from planned status
A draft view of whether the filing is voluntary is mixed with the live position, so the record no longer shows the organisation’s present status clearly.
Where judgement is often needed
Choosing the reporting cycle after a group change
If acquisitions, disposals or restructurings change the business perimeter, fix one cut-off basis for the cycle covered, explain which entities were included or left out, and keep the same basis for the dates you report.
Handling different country calendars and filing clocks
Where local reporting calendars differ, use one organisation-wide date basis for the cycle and submission date, then note any country-level timing differences that affected the filing plan.
Deciding whether a borderline entity is in scope
For entities near the edge of coverage, apply the same internal test consistently, state the judgement used, and disclose any exclusions or inclusions that were not obvious.
Setting the first deadline when the law changes mid-cycle
If the first filing date is affected by a change in status or an update to the legal position, document the date you used, why it was chosen, and whether the filing was made on a voluntary basis.
Using actual dates versus planned dates
Report the date the submission was actually sent rather than the planned date, and explain any gap between the two if the filing was delayed or brought forward.
Mixing measured records with estimates
When exact records are not available for a timing field or status field, use the best supportable estimate, label it clearly, and explain the source and method behind it.
Rounding dates or status descriptions
Do not round away meaningful timing detail; if you simplify a date or status label for presentation, keep the underlying record available and explain the presentation choice.
Protecting sensitive filing information through grouping
If disclosing the cycle or enforcement position could expose sensitive internal information, aggregate only as far as needed, say what has been grouped, and keep the explanation clear enough for review.
Examples
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
Illustrative (synthetic) example — Utilities
We have chosen to report on a two-year basis, and the current position is that the rule is being applied as written. Our reporting window runs from 1 January 2024 to 31 December 2025, and we submitted on 15 June 2025 against the first filing date of 30 June 2025. - The filing was made voluntarily, before any enforcement action was taken. - This example is for practitioner illustration only and is not legal advice.
This example shows how a company might describe the timing of a first filing under a biennial approach, including whether it filed before enforcement activity began.
Illustrative (synthetic) example — Consumer goods
Our group also reports every two years, and we understand the rule to be in force for our filing. The period we covered was 1 July 2023 to 30 June 2025, with the first due date set at 30 June 2025 and our submission completed on 28 June 2025. - We treated the filing as voluntary because it was sent before any enforcement step. - This is an illustrative narrative for training purposes only.
This example gives a second, different sector view of the same timing disclosure, showing a voluntary submission made just before the first due date.
How companies report SB261-REPORTING-TIMELINE in practice
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.
Owens Corning
Building Products · United States · 2024
Owens Corning’s 2024 Sustainability Report specifies the reporting cycle as January 1, 2024 to December 31, 2024, indicating the timeframe covered by the assessment (p.383). The report includes an assurance statement confirming management’s responsibility for the report’s preparation and content (p.381). However, there is no evidence found regarding the statutory first deadline, submission date, voluntary submission status, or biennial reporting requirements under SB261.
Host Hotels & Resorts, Inc.
Real Estate · United States · 2025
Host Hotels & Resorts, Inc.'s 2025 Corporate Responsibility Report includes a GRI content index covering the period from January 1, 2024, to December 31, 2024, indicating a defined reporting cycle (p.62). The report references various ESG-related appendices and disclosures, such as TCFD references (p.57) and performance tables (p.53), but does not provide specific information on the SB261 reporting timeline requirements like biennial reporting, statutory deadlines, or submission dates. Notably, there is no evidence in the report regarding the current enforcement status or voluntary submission status for SB261 disclosures.
Republic Services
Solid Waste Management Utilities · United States · 2024
Republic Services’ 2024 Sustainability Report includes information on its environmental health and safety (EHS) program, which covers environmental compliance and employee health and safety goals such as incident reduction and safety amplification (p.6). The report also highlights efforts to improve worker safety through equipment upgrades, like the transition to automated side-load trucks and new recycling carts, reducing manual waste handling (p.10). However, there is no evidence in the report regarding the SB261 reporting timeline, enforcement status, submission dates, or voluntary submission status.
✓ 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-REPORTING-TIMELINE?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 preparer is updating the filing tracker for a company that has already sent one climate report and is now planning the next one. The team is unsure whether to treat the filing as part of a repeating two-year cycle or as a one-off update.
QShould the tracker show that this disclosure follows a repeating two-year reporting pattern, and what cycle should be recorded?
Reveal model answer →Hide answer ↑Yes. The preparer should mark that the disclosure sits on a two-year rhythm and record the specific reporting period being covered, so the timeline is clear and can be checked against the evidence file.
Why this matters · Always link the filing to the correct reporting period and show whether the process repeats every two years.
A draft pack shows a submission date, but the legal team has not yet confirmed whether the law is currently being enforced for this company’s filing route. The preparer is about to finalise the disclosure anyway.
QCan the disclosure be signed off without a current enforcement status, or does that status need to be captured first?
Reveal model answer →Hide answer ↑The status needs to be captured before sign-off. The disclosure is not complete if the team has not stated the present enforcement position, because that is one of the core data points supporting the timeline entry.
Why this matters · Do not treat the enforcement position as optional; it belongs in the disclosure record alongside the dates.
A company missed its expected first filing date in the prior year and is now preparing a late submission. The preparer has the actual send date, but the draft does not yet show the statutory first deadline that the team was working to.
QShould the disclosure include both the deadline that applied and the date the report was actually sent?
Reveal model answer →Hide answer ↑Yes. The preparer should show the deadline that governed the first filing and the actual submission date, even if the report went in late, so the timing can be assessed against the evidence.
Why this matters · Keep both the target date and the real submission date in view; the comparison matters.
A sustainability manager wants to describe the filing as voluntary because the company chose to publish early, even though the team is also tracking the legal timetable and enforcement position. The draft currently mixes those ideas into one sentence.
QHow should the preparer separate the voluntary aspect from the legal timeline so the disclosure stays clear?
Reveal model answer →Hide answer ↑The preparer should record the voluntary submission status as its own item and keep it distinct from the reporting cycle, deadline, submission date, and enforcement status. That way, the reader can see whether the filing was made by choice while still understanding the legal timing context.
Why this matters · Separate the voluntary label from the statutory timing fields so each point is easy to verify.
Framework references
Related framework references
How this disclosure maps across the major reporting frameworks.
California
SB261-REPORTING-TIMELINE
within California SB 261: Climate-Related Financial Risk Act
Open official source →Related & explore
Covered entity applicability → Guide ✓Climate-related financial risk disclosure → Guide ✓Implementation fee and administration →TCFD or equivalent framework alignment → Guide ✓Reporting gaps and completion plan →Measures to reduce and adapt to climate-related financial risk → Guide ✓Show all 6 related disclosures →
FAQ
Questions this page answers
SB261-REPORTING-TIMELINE: what data do I need to gather before I start the disclosure draft?+−
The page says to prepare six datapoints: reporting frequency, enforcement position, covered reporting period, first filing deadline, filed on date, and whether the filing is voluntary. It also gives a step-by-step preparation section, so you can use that as the starting point for collecting and checking the inputs.
How do I use the SB261-REPORTING-TIMELINE page to set the reporting period and filing date correctly?+−
Use the datapoints list to capture the covered reporting period, first filing deadline and filed-on date in one place. The page is designed to help you turn those dates into a draft disclosure rather than leaving them scattered across emails or source files.
What should I include in the evidence pack for SB261-REPORTING-TIMELINE assurance readiness?+−
The page includes an evidence pack with five items for assurance readiness, alongside six assurance claims to verify. Use those sections together so each claim has a clear claim, risk and evidence trail before review.
How do I use the six assurance claims on the SB261-REPORTING-TIMELINE page in practice?+−
Treat the six claims as a checklist for what needs to be verified, then link each one to the relevant risk and evidence. That helps you spot gaps early and build a cleaner assurance file.
What are the common mistakes on the SB261-REPORTING-TIMELINE page that I should avoid?+−
The page lists common reporting gaps and mistakes so you can check for missing dates, unclear ownership, or incomplete support before drafting. Use that section as a pre-submission quality check.
How do I use the SB261-REPORTING-TIMELINE workbook download to prepare the disclosure?+−
The Download Centre includes a Prep & Assurance workbook in .xlsx format, which is intended to support preparation and assurance readiness. Use it to organise the required datapoints, evidence and draft content before you finalise the disclosure.
What is the printable Library Card PDF for SB261-REPORTING-TIMELINE used for?+−
The Download Centre also provides a printable Library Card in PDF format. It is there as a practical companion to the page content, so you can keep the key points and preparation steps to hand while drafting.
Can I use the synthetic example disclosure on SB261-REPORTING-TIMELINE as a template for my own draft?+−
Yes, but only as a synthetic illustration. The page says the examples are illustrative, and the quantitative table is there to show how the disclosure can be structured rather than to provide real company data.
How do I turn the SB261-REPORTING-TIMELINE page into a first draft disclosure?+−
Use the draft-output section, which includes visualisation ideas, narrative starters and a content-index line. That gives you a practical way to move from collected data to a readable draft.
Is the data I collect for SB261-REPORTING-TIMELINE reusable for ESRS E1 climate reporting?+−
The page notes ESRS E1 (Climate Change) as the closest correspondence, so the data may be reusable across both contexts. It does not say the requirements are identical, so you should still check the other framework separately.
Who should own the SB261-REPORTING-TIMELINE disclosure process in my organisation?+−
The page is aimed at sustainability and ESG managers, HR or data owners, and assurance reviewers, so ownership should sit with the person coordinating those inputs and checks. Use the step-by-step preparation section to assign tasks and keep the evidence pack aligned.
More questions this page can help with
SB261-REPORTING-TIMELINE checklist for sustainability manager: what should I do first?SB261-REPORTING-TIMELINE data points list for filing deadline and filed-on dateHow to complete the SB261-REPORTING-TIMELINE evidence pack for assuranceSB261-REPORTING-TIMELINE common reporting gaps and how to avoid themHow to use the SB261-REPORTING-TIMELINE Prep & Assurance workbookSB261-REPORTING-TIMELINE synthetic example disclosure table explainedSB261-REPORTING-TIMELINE draft narrative starters and content index lineSB261-REPORTING-TIMELINE reporting frequency and enforcement position: what do I capture?SB261-REPORTING-TIMELINE assurance claims claim risk evidence mappingSB261-REPORTING-TIMELINE voluntary filing flag: how should I record it?SB261-REPORTING-TIMELINE from company reports table: how do I use real examples?SB261-REPORTING-TIMELINE ESRS E1 reusable data question
How this library is built
312 published reports indexed
63171 pages with page-level citations
247 practitioner guides
Free · LRA Community
Get your SB261-REPORTING-TIMELINE 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 →