A carbon-credit invoice, a project report and a company emissions statement belong in the same review conversation, but they answer different questions. Treating them as interchangeable can leave a disclosure file looking complete while its central claim remains unexplained.

This article offers a practical workflow for organising an AB1305 evidence file. Its legal background is deliberately dated: the California Senate Judiciary Committee's July 2, 2024 analysis of AB2331, which separately describes existing AB1305 provisions and proposed changes. It is not a verification of today's statute, an applicability determination or a reporting calendar.

The workflow is an editorial recommendation. It helps a team show what it knows, what a document actually supports and what still needs review. It neither establishes legal compliance nor validates a carbon-neutrality claim.

Begin with the statement, not the folder

Before collecting another report, write down the exact statement under review. Preserve its wording, intended audience, location, subject and reporting period. A proposed product claim and a statement about an organisation's operations should not share an evidence file merely because both contain the words “carbon neutral.”

Create a claim record that can survive changes in staff and documents. Give it an internal identifier and record which version is being reviewed. If the statement changes, retain the earlier version with an explanation of what changed. This is a recommended recordkeeping practice, not a claim that AB1305 prescribes a particular identifier or filing system.

Next, describe the activities behind the statement in ordinary language. Is the business discussing an offset project it markets, credits it has purchased, or its own emissions performance? Is it describing a completed result or a future objective? A short factual description is more useful than assigning a legal label before anyone has examined the underlying activity.

Keep marketing language and technical evidence side by side. That makes it easier to spot when a headline reaches further than the report on which it relies.

Sort the evidence into three paths

The Senate analysis's existing-law discussion provides a useful organising framework. It describes project and accountability disclosures for sellers or marketers, project and transaction-related information for offset users making specified claims, and substantiation of company or product claims. The table below translates that dated account into review questions. It is not an exhaustive statement of legal requirements.

Path described in the analysisPractical review questionUseful evidence category
Seller or marketerWhat supports the stated project benefit and the response to a shortfall?Project description, protocol, calculations and accountability documentation
Offset buyer or user making a claimWhich project and transaction does the team connect to this statement?Seller and project identifiers, project details and verification information
Entity making a company or product claimHow was the statement supported, and how is progress measured?Claim methodology, measurement records and verification scope

Do not force every business into just one row. The categories are a way to separate questions, not a ruling on whether a reader falls within California's jurisdiction. Equally, do not assume that a credit purchase answers all questions about a company's emissions statement. Follow the evidence needed for the actual claim.

Make record locations precise enough to use

A list of report titles is a starting point, not a finished evidence file. For each statement, identify the particular version and passage, table or calculation the reviewer should examine. A document that discusses a project generally may not contain the calculation supporting a specific quantity.

The committee's seller discussion includes project information, verification, accountability if projected benefits are not achieved, and data and methods needed to reproduce issued credits. A practical file should therefore distinguish the project narrative from the numerical basis and from the shortfall response. Combining all three under one label makes it harder to see what is missing.

For a buyer's file, preserve the relationship between the seller, project identifier, supporting project documents and proposed claim. If records use different names, explain the correspondence rather than asking the reader to infer it. If a document cannot be located, mark that issue explicitly.

The recommendation is traceability, not volume. Twenty loosely related attachments can be less useful than a small, clearly mapped set. Avoid adding documents merely to make the file appear substantial. Every attachment should answer a question or disclose an important limitation.

Read verification scope before using a verification label

The dated Senate account discusses whether independent verification exists for relevant project attributes or company data and claims. It does not justify treating every form of verification as the same assurance about every statement.

For review purposes, ask what was examined, which period and activities were covered, and what limitations the verifier recorded. Keep the answer beside the claim. An assessment of project attributes should not quietly become an endorsement of the purchaser's whole business. An assurance statement concerning selected data should not be described as covering data outside its stated scope.

Also separate verification from the underlying calculation. A reviewer may need to understand both the method used and the work performed by an independent party. If either is unclear, avoid a broad “verified” badge as a substitute for explanation.

This is particularly important when the public language changes after the evidence was prepared. A broader claim may require a fresh assessment of whether the existing records still address it. That is a recommended review trigger, not an asserted statutory schedule.

Keep uncertainty visible through the handoff

An evidence file should allow a reviewer to distinguish a supported statement from an assumption and an unresolved question. Use those as separate statuses. A document's presence alone should not automatically move a claim to “supported.”

For each open issue, identify an owner and the next action. “Needs checking” is too vague to hand over. “Reporting lead to reconcile the claim's period with the calculation's period” tells the next person what to do. Preserve the outcome of that check alongside the file version reviewed.

For a fictional example, imagine a team finds that its proposed statement covers all operations, while the attached calculation covers only selected facilities. The practical response is to make the mismatch visible and return the wording and evidence for review. It is not to assume the excluded facilities are immaterial or to label the statement unlawful without examining the facts.

This discipline keeps the guide useful without pretending that an editorial workflow can resolve legal applicability, scientific quality or liability. Those are distinct assessments, and the evidence file should help the relevant reviewer perform them.

Understand the dated enforcement account without inventing a liability estimate

The July 2024 analysis describes a civil penalty of up to $2,500 per day for each violation, for days when information is unavailable or inaccurate, with a total not exceeding $500,000 as described in the source. It identifies civil recovery by the Attorney General, district attorneys, county counsel or city attorneys.

That is not an automatic invoice or a prediction about a particular company. This article does not allocate the stated total between projects, entities or claims. It also does not use proposed changes discussed elsewhere in the committee document as enacted obligations.

The practical implication for a review workflow is to examine accuracy and availability separately. Confirm that the selected evidence supports the intended wording, then check that the planned disclosure points readers to the intended information. Where the answer is uncertain, retain the question for the appropriate current-law review rather than replacing it with an unsupported conclusion.

Deliver a review package, not a compliance badge

A useful final handoff contains the exact proposed statement, its evidence map, the relevant record versions, the scope of any verification and a short list of unresolved questions. Name the decision still required instead of implying that assembling the package has settled it.

Keep the dated legal background separate from the team's own working practices. This article intentionally does not state precise territorial exclusions, an initial posting deadline or an annual statutory update obligation. Those matters require an appropriate current source and assessment before the team relies on them.

The immediate next step is manageable: choose one real statement, identify the evidence path or paths it raises, and map each substantive assertion to a specific record. Remove duplication, flag unsupported extensions and send the resulting package for review. A clearer evidence file will not guarantee a favourable conclusion, but it will make the basis for that conclusion easier to understand.