Climate and ESG disclosures are no longer something you can just “tack on” at the end of the process. In fact, for most organizations, the real risk isn’t just a single inaccurate sentence–it is the lack of a consistent, repeatable governance process that keeps disclosures and sustainability claims aligned, supportable, and ready for real-world scrutiny. Whether it’s customers, lenders, insurers, regulators, auditors or your board, each will expect these disclosures are made with a clear, consistent and defensible governance process to ensure accuracy.

As the climate and ESG disclosure and reporting season approaches, it is not too early to prepare. That’s why I am posting a practical 90-day checklist to help you get your annual report, ESG report, sustainability web pages, customer questionnaires, and climate-related statements audit-ready. Use this checklist as a start on the path toward disclosures that are not just compliant, but also robust enough to stand up to the credibility demands of all your stakeholders. What would you add or change? Happy New Year.

Why Disclosure Readiness is a Governance and Controls Issue

Organizations get into trouble (or into expensive rework) for predictable reasons:

• No decision rights: Everyone edits; no one owns the final approval.
• Inconsistent boundaries: Different teams describe different footprints (operations vs. supply chain, market vs location-based electricity, “net zero” scope, etc.).
• Claims without substantiation: Statements are made without a clean evidence file.
• No retention discipline: Key data, assumptions and approvals aren’t preserved.
• No escalation triggers: There is no “stop publish” rule when high-risk language appears.

The solution is not a longer disclaimer statement. It is the presence of an efficient and scalable governance system that produces accurate, defensible, consistent output.

A 90-Day Disclosure Readiness Checklist

1. Assign decision rights (Who is Responsible, Accountable Consulted and Informed, RACI) and create a single point of accountability for final approval. Document who does what and in what order.

• Responsible: Who drafts content, collects inputs and maintains the evidence file?
• Accountable: Who owns the final statement and approves publication?
• Consulted: Who in finance, legal, operations, climate/ESG, marketing/comms, risk, HR has reviewed?
• Informed: Which board/committee, executive sponsor, business unit leaders have reviewed?

Deliverable: Create a one-page RACI that explicitly states who can approve publication and who can pause it.

Best Practice: Name a Disclosure Owner and a Claims Owner. If that is one person for both, fine–just be explicit.

2. Build a disclosure and claims inventory (document where statements and claims actually live).

Most organizations underestimate how many “disclosure surfaces” they have. Create an inventory of every channel where climate/ESG statements appear, including:

• Corporate website (sustainability pages, product pages, FAQs)
• Customer RFPs and supplier questionnaires
• Sales decks, capability statements, and marketing collateral
• Annual report//ESG report/investor decks
• Press releases, awards submissions, public speeches
• Social posts and executive quotes
• Internal policies that may be shared externally (procurement, climate commitments)

Deliverable: An inventory spreadsheet or database with URL/file location, owner, last updated dates, and approval status.

3. Create a claims taxonomy (categorize what you are actually saying)

Common categories:

• Target/commitment claims: “net zero by 2040,” “science-based targets”
• Attribute claims: “100% renewable,” “carbon neutral,” “low carbon”
• Comparative claims: “reduced emissions,” “more efficient than. . “
• Product-level claims; labels, packaging, “sustainable materials”
• Process claims: “we offset,” “we procure RECs,” “we use verified credits”
• Foward-looking claims: plans, roadmaps, anticipated impacts

Deliverable: A claims register listing each claim, category, channel, owner and risk rating (low/medium/high)

4. Build the substantiation file or database (your “defensibility binder”)

For each high-visibility claim, create a substantiation packet that answers:

• What exactly is the claim? (final proposed wording)
• What is the boundary? (which operations/products/time period)
• What method is used? (approach, assumptions, key definitions)
• What evidence supports it? (data sources, invoices, calculations, contracts, policies)
• What limitations exist? (material exclusions, uncertainty, dependencies)
• Who reviewed and approved it? (names, dates, version history)

Deliverable: A standardized substantiation template (one-page summary plus attachments) that can be produced quickly if challenged.

Tip: Don’t aim for perfection. Aim for traceability. Ensure a reasonable review can follow how you got there.

5. Align the language pack (consistency across teams and channels)

Create a controlled set of “approved phrases” and “avoid phrases” so marketing, sustainability and finance aren’t inventing their own versions.

Include:

• Approved definitions (e.g. what “renewable” means in your context)
• Approved references to instruments/approaches you used (without over-claiming)
• Standard boundary language (where applicable)
• Standard qualifiers for forward-looking statements
• Examples of acceptable vs. unacceptable phrasing for common claims

Deliverable: A short “Disclosure and Claims Language Pack” that becomes the default reference.

6. Establish the workflow (review cadence plus escalation triggers)

A defensible workflow includes:

• Drafting Source of Truth: one controlled document repository
• Review Sequence: subject matter -> legal/governance -> executive board as needed
• Red Flag Escalation: certain claim types require enhanced review
• Stop-Publish Rule: if substantiation is incomplete, the claim doesn’t publish
• Version Control: track changes and approval timestamps

Deliverable: A one-page SOP and a simple checklist used before anything goes live.

7. Record retention and audit trail (the part people often skip)

Retention should cover:

• Underlying data inputs and key assumptions
• Evidence documents (contracts, invoices, certificates, policies)
• Draft versions and approvals
• Final published versions (screenshots/PDFs)
• Change history and who authorized changes

Deliverable A simple trigger list that causes the claim register and substantiation file to be revisited.

A Practical 90-Day Timeline (so this doesn’t become a perpetual project)

Days 1-15: Governance Foundation

• Assign RACI and owners
• Build your inventory of disclosure surfaces
• Create a first-pass claims register

Days 16-45: Substantiation and language discipline

• Build substantiation packets for high-risk/high-visibility claims
• Create the language pack (approved and avoid phrases)
• Set your workflow and escalation rules

Day 46-75: Drafting and internal alignment

• Draft/revise content using controlled language
• Run cross-functional review
• Confirm boundaries, definitions, and evidence completeness

Day 76-90: Final approvals and retention

• Finalize approval trail
• Create final “as-published” archive
• Document lessons learned and update the process

When You Should Seek Help

Consider outside counsel support if:

• You are making high visibility “net-zero,” “carbon neutral,” or product level claims
• Your disclosures will be used in financing, underwriting, or major customer and contracting
• Multiple business units or brands are publishing statements
• You have limited substantiation and need to build a defensibility file quickly
• You are inside a 30-day window and need a triage plan

Next Steps

If you want more information about flat-fee services for Quick Start or Climate Disclosure Readiness and Claims Governance, please Contact Us. We will work with you to evaluate which flat-fee services most appropriate for your situation.