Disclosure focus
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.
Prepare
What to collect before drafting
Tick each field as the evidence lands. Owners are the teams that usually hold the source files.
-
Reporting frequency
Legal / Sustainability reportingWhether this filing is due every two years or not, based on the organisation’s current reporting obligation.
Evidence Legal/compliance tracker, reporting calendar, or statutory assessment note showing the current filing cadence.
Watch for Frequency set against the wrong statutory basis, so an annual cycle is treated as biennial or vice versa.
-
Enforcement position
Legal / ComplianceThe present status of how the requirement is being enforced, using the latest official position the organisation is relying on.
Evidence Regulatory update log, legal memo, or counsel note recording the current enforcement view and date checked.
Watch for Current enforcement position not refreshed, so the team relies on an outdated status after the regulator’s position has changed.
-
Covered reporting period
Sustainability reporting / FinanceThe time span the report is meant to cover, with clear start and end dates for the cycle being reported.
Evidence Reporting calendar, policy note, or board paper stating the period covered for this filing.
Watch for Reporting window mis-set, so the filing covers the wrong period or mixes a full cycle with a partial one.
-
First filing deadline
Legal / ComplianceThe date by which the first report must be filed under the statute, as currently interpreted for the organisation.
Evidence Statutory tracker, legal advice, or compliance calendar showing the first due date and basis for it.
Watch for First deadline calculated from the wrong trigger date, so the filing date slips against the statutory timetable.
-
Filed on date
Sustainability reporting / LegalThe actual date the report was submitted, as recorded by the filing process or portal confirmation.
Evidence Submission receipt, portal confirmation, or email acknowledgement showing the date and time sent.
Watch for Submission date taken from draft approval or internal sign-off instead of the portal receipt, so the recorded date is wrong.
-
Voluntary filing flag
Legal / Sustainability reportingWhether the report was submitted voluntarily rather than because it was due under the current obligation.
Evidence Filing decision note, legal assessment, or submission record showing the voluntary status at the time of filing.
Watch for Voluntary status not aligned to the filing decision, so an optional submission is recorded as mandatory or the other way round.
Before you start
- Have you confirmed whether this sits on a two-year reporting rhythm for your organisation, or not?
- Which reporting period are you using for this entry, and does it match the cycle you are covering?
- Can you point to a source for the first due date and the date you actually submitted?
- Is the current position one of active enforcement, paused enforcement, or another status you can evidence?
- If the filing was made without a legal obligation, have you clearly marked it as voluntary?
How to prepare it
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.
Formal email template
Subject: Request for filing timeline and status evidence for [reporting cycle]\n\nDear [name/team],\n\nPlease could you share the evidence we need for the [reporting cycle] filing timeline and status check for [entity/group]? We are looking for the internal record that shows:\n- whether this reporting cycle is on a biennial track\n- the current filing status\n- the deadline used for the first filing in scope\n- the submission date, if already sent\n- whether any submission was made on a voluntary basis\n\nPlease include the source record, the date it was last updated, and any note that explains the status. If the information sits in a tracker, board paper, legal memo, or filing calendar, a copy or extract is fine.\n\nThis is a possible LRA training template; please adapt it to your organisation’s own terms and check the source material before sign-off.\n\nMany thanks,\n[preparer name]
Short Teams / Slack version
Hi [name/team] — could you send over the filing tracker / legal note / calendar entry for [reporting cycle] covering [entity/group]? We need the record showing whether this is on a biennial track, the current filing status, the first-filing deadline used, the submission date, and whether anything was filed voluntarily. Please add the source and last-updated date. Thanks.
Industry examples
Financial services
Context. A regulated group tracks climate-related filings through Legal and Company Secretariat, with deadlines logged in a compliance calendar.
Adapted request. Please share the compliance calendar entry and any supporting note for [reporting cycle] covering [entity/group], showing whether this filing cycle is on a biennial track, the current filing status, the first-filing deadline used, the submission date, and whether any filing was made voluntarily.
Example response. Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
Manufacturing
Context. A group with multiple subsidiaries keeps filing status in a central legal register managed by Company Secretariat.
Adapted request. Please provide the legal register entry for [reporting cycle] covering [entity/group], including the filing track, current status, first deadline, submission date, and any voluntary submission note. If the register uses different labels, keep those labels and add a short mapping note.
Example response. Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
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
Download preparation tools for SB261-REPORTING-TIMELINE with free verified email access for 24 hours. Source-report links remain public.
Check
For each claim, check the evidence
I have checked whether this entity is in scope for the California climate-risk filing and whether the reporting obligation applies to it.
Risk Assurance will test whether the in-scope assessment is correct and supported by the legal-entity analysis, because an incorrect yes/no conclusion would make the whole disclosure misleading.
Evidence to check Entity scoping memo; legal-entity register; applicability assessment against the cited California provisions; internal sign-off showing why the entity is or is not covered.
I have used the current enforcement position to describe the regulatory consequence of not publishing, or of publishing something that is not adequate.
Risk The assurer may probe whether the statement overstates, understates, or misstates the regulator’s present powers, or whether it is based on outdated legal review.
Evidence to check Latest legal review or counsel note; source materials on the regulator’s current penalty powers; version control showing the date the enforcement position was last checked; approval record for the wording used.
I have identified the reporting period that the disclosed timetable relates to and matched it to the correct cycle.
Risk The main risk is that the period described is the wrong one, overlaps the wrong year, or is inconsistent with the entity’s reporting calendar.
Evidence to check Reporting calendar; board or management paper confirming the period selected; cross-reference to the period used in the disclosure pack; evidence that the same cycle is used consistently across the report.
I have stated the first required date and the repeating pattern in a way that matches the statute and our internal timetable.
Risk The assurer will check whether the date and cadence are accurate and whether the disclosure has accidentally shifted the timing or implied a different sequence.
Evidence to check Statutory interpretation note; compliance calendar; draft-to-final change log; sign-off from legal, compliance, or reporting owners confirming the timing statement.
I have recorded the date the report was made public or filed, and that date is supported by the publication trail.
Risk Assurance will test whether the date is real, complete, and aligned with the actual release or filing event, rather than a planned or draft date.
Evidence to check Website publication record; filing receipt or submission confirmation; timestamped email or portal evidence; archive copy of the final version with the same date.
I have explained the route we used to meet the requirement where we did not use a direct statutory filing route, and the method is consistent with the chosen compliance approach.
Risk The assurer may ask whether the method described truly satisfies the obligation, whether it was approved in advance, and whether the disclosure is describing the same route that was actually used.
Evidence to check Compliance strategy paper; legal advice on the chosen route; records of any voluntary or equivalent submission; evidence that the method used matches the one described in the disclosure.
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.
Where drafts go wrong
Mistakes to avoid and where judgement is needed
The left column is what preparers get wrong while collecting; the right column is where you will have to make and explain a judgement.
Mistakes to avoid
- Ask the right ownerThe 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 firstPeople 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 basisOne 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 labelsSource 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 groupsVoluntary 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 trailThe 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 pathThe 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 dateThe 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 statusA 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.
Judgement needed
- Choosing the reporting cycle after a group changeIf 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 clocksWhere 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 scopeFor 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-cycleIf 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 datesReport 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 estimatesWhen 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 descriptionsDo 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 groupingIf 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
How it reads on the page
Synthetic, written by LRA — not from a company report, not text from any standard.
Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
SB 261 enforcement is paused pending appeal. The law has not been cancelled. Record the current court and CARB position separately from the statutory biennial reporting cycle. Early publication alone does not make reporting voluntary.
Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
SB 261 enforcement is paused pending appeal. The law has not been cancelled. Record the current court and CARB position separately from the statutory biennial reporting cycle. Early publication alone does not make reporting voluntary.
Quality ladder
- Basic
I filed on 2025-06-30.
- Better
Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
- Best
Illustrative planning record: reporting period, statutory timing, current enforcement position, publication date and legal basis for treating publication as voluntary. Publish after the stated reporting period ends. Early publication alone does not establish voluntary status.
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.
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.
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.
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.
Real reports
How 3 companies report it
Examples of full and partial reporting practice. These are evidence-led reviews, not exact disclosure templates to copy.
Owens Corning
Host Hotels & Resorts, Inc.
Republic Services
| Field | Owens Corning | Host Hotels & Resorts, Inc. | Republic Services |
|---|---|---|---|
| Reporting frequency | Not found | Not found | Not found |
| Enforcement position | Not found | Not found | Not found |
| Covered reporting period | Not found | Not found | Not found |
| First filing deadline | Not found | Not found | Not found |
| Filed on date | Not found | Not found | Not found |
| Voluntary filing flag | Not found | Not found | Not found |
Ask the Knowledge Hub AI Assistant about this disclosure
Get practical answers for your reporting context.
Check your text
Paste one or two paragraphs. The fragment is used for this check only and is not stored in your conversation.
Peer comparison uses examples on this card, not prevalence in the report corpus.
Advice, not assurance
Framework references
Relevant California requirements and related disclosures
California
SB261-REPORTING-TIMELINE
within California SB 261: Climate-Related Financial Risk Act
Related & explore
More in California SB 261 →Browse full catalogue →Search all disclosures →
FAQ
Questions this page answers
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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