California voluntary carbon market disclosures: a dated evidence guide
California's voluntary carbon market disclosures can be easier to understand when you separate three questions: what supports the offset project, what connects an offset to its purchaser's claim, and what supports the company's own emissions statement? These are related questions, but the same document will not necessarily answer all three.
This guide explains the three disclosure paths described as existing law in a California Senate Judiciary Committee analysis prepared for its July 2, 2024 hearing on AB2331. It then offers practical ways to organise the evidence. The analysis is a dated account of AB1305, not a current consolidated statute. This guide does not determine whether your business is covered, establish a reporting deadline or provide legal advice.
The practical aim is narrower: help a business reader identify the records behind a statement and prepare a clearer package for a current-law review. A well-organised file makes questions easier to answer. It does not make an unsupported claim true.
Start with the source and its limits
The committee document separates its description of existing law from the changes proposed by AB2331. That distinction matters. A proposal can explain what legislators hoped to clarify without establishing what a business was already required to do. This guide uses the existing-law discussion on pages 2, 5 and 6; it does not adopt the proposed timing, exclusions or verification treatment in the document's other sections.
The source describes sellers and marketers of voluntary carbon offsets, buyers or users making specified climate claims, and entities making specified company or product claims. These are useful organising categories, not a substitute for the precise legal tests. A business may need to examine more than one category. Simply calling itself a buyer, seller or manufacturer does not settle the applicability question.
Keep two tasks separate. First, document what the business actually says and does. Second, have the relevant legal requirements checked against those facts. That order produces a more useful review than asking someone to assess a vague statement such as “we use carbon credits.” Record the exact claim, the entity or product it describes, where it appears and the period it covers.
Sellers: connect project details to delivery and shortfall evidence
The Senate analysis describes seller and marketer disclosures about project details, validation or verification, accountability for shortfalls, and data and methods needed to reproduce the number of credits issued. Its discussion includes project location, timing, quantities, durability and the protocol used to estimate emissions benefits.
For an evidence file, translate that description into a practical question: can another reviewer locate the basis for each project statement? A project name alone is not a useful answer to a question about a calculation. A general registry homepage is not the same as the relevant project document. Identify the particular record, version and passage that support the statement being reviewed.
For example, if a project description refers to future removals, keep that statement separate from records about removals already measured. If a document discusses a storage commitment, do not silently convert it into a guarantee that storage will last indefinitely. Preserve the stated assumptions and limitations alongside the headline benefit.
Accountability also deserves its own place in the file. A description of the intended outcome and a description of what happens if that outcome falls short answer different questions. Our recommendation is to record both, with an unresolved-question field where the available documentation is incomplete. This is evidence-management advice, not an exhaustive statutory checklist.
Offset users: connect the credit to the claim
For offset buyers or users making specified claims, the dated analysis describes information about the seller and project, identification details, project type and location, the estimation protocol, and independent verification of data and claims. The point for a reader is to preserve the connection between the transaction record and the statement being made, rather than keeping the purchase documentation in isolation.
Start with the exact wording of the claim. Does it concern a product, a facility, business travel or the whole organisation? What period does it describe? Those are recommended review questions, not legal definitions supplied by this guide. They help reveal whether the supporting records address the same subject as the public statement.
Then locate the project and transaction records that the team intends to rely on. Note any mismatch rather than resolving it by assumption. A missing identifier, an unclear reporting period or a document that covers only part of the asserted activity should remain visible to the reviewer.
Finally, identify what any verification actually covers. A project-level assessment and an assessment of a company's emissions statement are not interchangeable evidence. A purchase record can help document a transaction; it does not, by itself, demonstrate that a broad carbon-neutrality claim is justified. Keep the question about the claim open until the relevant evidence has been examined.
Company and product claims: retain the basis and progress evidence
The third path in the committee's account concerns entities making specified climate claims. Its existing-law discussion addresses how a claim was determined to be accurate or accomplished, how interim progress is measured, and whether there is independent verification of the company's data and claims. That makes the statement itself a useful starting point for organising records.
A practical claim file should distinguish an achieved result from a future goal. Consider the difference between “we reduced emissions during the reporting period” and “we aim to reduce emissions.” The first calls for evidence about the result being described; the second calls for clear explanation of the goal and the basis for reporting progress. These examples illustrate review practice, not conclusions about statutory coverage.
Preserve the measurement boundary, comparison period and relevant methodological explanation. If the underlying method changes, record the change rather than presenting two unlike figures as directly comparable. If an assurance statement is used, note its scope and limitations instead of attaching a general “verified” label to the whole company.
This approach also helps distinguish missing evidence from an adverse finding. An unanswered question does not necessarily establish wrongdoing. It does mean that the editor or reviewer should not fill the gap with confident language. Identify the person responsible for resolving it and retain the decision with the claim's version history.
What the analysis says about public enforcement
The July 2024 analysis describes a civil penalty of up to $2,500 for each day information is unavailable or inaccurate, per violation, with a total not exceeding $500,000 as stated in that account. It identifies the Attorney General, district attorneys, county counsel and city attorneys as public prosecutors able to seek recovery through civil action.
These figures are a description of the dated source, not a calculation of a particular business's liability. They should not be presented as an automatic daily bill. Nor does this guide infer how the total would be allocated between companies, projects or claims. Those questions require the relevant law and facts, not arithmetic applied to a summary.
For an evidence team, the useful lesson is that availability and accuracy are separate concerns. A file may exist but fail to support the statement beside it. Conversely, a well-supported internal calculation may be difficult for a reviewer to locate. Our recommendation is to check both the substance of the evidence and the location of the intended disclosure. That recommendation does not replace a legal assessment of what must be disclosed.
Build an evidence matrix, then obtain a current-law check
The following fictional example illustrates an internal review aid. Cedar Example Co., its projects and record names are invented. The table is not a statutory form, a real company's disclosure or an indication of compliance.
| Evidence path | Record and owner | Version and scope | Open question and next check |
|---|---|---|---|
| Seller/project | Project P-01 description and shortfall plan; project lead | Draft 3, 1 November; estimates and delivery assumptions | Does the shortfall plan address the stated outcome? Locate the supporting passage. |
| Offset use and claim | Purchase file T-02 and claim C-01; procurement lead | Review copy, 2 November; one purchase and one proposed claim | Does the project identifier match? Reconcile the documents before review. |
| Company claim | Calculation M-03 and assurance scope A-01; reporting lead | Version 2, 3 November; defined activities and period | Does assurance cover the claim's full boundary? Refer the gap to the reviewer. |
Use a stable locator for each record, preserve the version examined and assign an owner to every unresolved question. Review the file when a claim or its supporting facts change; this is a suggested working practice, not an asserted legal update interval.
The result should be a package that distinguishes evidence, assumptions and decisions. Take that package into a current-law review before relying on it for a compliance decision. The three paths help organise the work; they do not certify the outcome.
