How to Evaluate ESG & Sustainability Software

1. Confirm the reporting scope and version

Record which entities and reporting periods are in scope, which requirements apply and who confirms that assessment. The European Commission's reporting page connects CSRD with ESRS and records policy developments. Treat applicability, timing and the version supported by a vendor as explicit checks. Avoid carrying an old company-count estimate or deadline into a new procurement brief.

European Commission: Corporate sustainability reporting. EU reporting context and policy updates; confirm the rules relevant to your entity and period. Checked 20 September 2026.

2. Separate the workstreams in the proposal

Data collection, carbon accounting, materiality assessment and disclosure preparation can involve different modules and owners. Ask which are included, which require other tools and where evidence passes between them. EFRAG's implementation guidance addresses materiality, value-chain questions and datapoints for the ESRS adopted in 2023. Check the relevance of that edition to your reporting basis before using it to specify software.

EFRAG: ESRS implementation guidance. Non-authoritative implementation guidance; the linked project identifies the standards edition it addresses. Checked 20 September 2026.

3. Follow a value through its calculation

The GHG Protocol Scope 3 Standard provides a framework for corporate value-chain emissions accounting. For a proposed calculation module, ask the vendor to show the input, unit conversion, method, factor source and factor version behind a result. Record missing data, estimates and assumptions. Define your relevant value-chain categories instead of assuming the same emissions share for every organisation.

GHG Protocol: Corporate Value Chain (Scope 3) Standard. Corporate value-chain accounting context; no universal footprint percentage or endorsement of software. Checked 20 September 2026.

4. Demonstrate corrections and review access

Start with a source document, import its value, correct an error and review the resulting change. Ask how the system records the reason, owner and affected outputs. Test what a contributor, reviewer and external reviewer can each see or change. A dashboard total is insufficient evidence if the underlying calculation and supporting records cannot be inspected.

5. Confirm the deliverable and ongoing support

Specify the output you need, its reporting basis, language and format. If digital tagging is relevant, confirm the applicable requirement and the product's released support for that version. Test an actual export and its supporting evidence. Obtain written clarification of update entitlements, implementation work and responsibility for reviewing any output before it is issued.

6. Fix the inventory boundary before the demonstration

The GHG Protocol Corporate Standard sets out standardised approaches and principles for preparing an inventory of the seven greenhouse gases it covers, with emphasis on consistency and transparency. Write down which entities and facilities fall inside your inventory and on what basis, then ask the vendor to show where that boundary is held in the product. Ask what happens to earlier periods when a site is added or sold: are prior-year figures restated, or does the year-on-year line quietly stop being comparable? A demonstration that starts from a finished dashboard will not show this, so begin it from the boundary settings.

GHG Protocol: Corporate Accounting and Reporting Standard. The standard's own page. It does not endorse or assess any software product, and the boundary questions here are our proposal. Checked 3 October 2026.

7. Ask for both electricity methods on one record

The Scope 2 Guidance covers accounting for emissions from purchased electricity, steam, heat and cooling, and its page refers to eight quality criteria for the contractual instruments used in the market-based method. Take one sample electricity record and ask the vendor to produce a location-based figure and a market-based figure from it. Ask where a supplier contract or certificate is recorded, which criteria the user is asked to confirm, and whether the report states which method produced each number. A tool that supports one method may meet a narrow need; what matters is that you can tell which method any figure came from.

GHG Protocol: Scope 2 Guidance. Guidance on accounting for purchased energy, with the market-based method's quality criteria. The page does not say which software supports it. Checked 3 October 2026.

8. Check which framework version a template follows

A reporting template mirrors a framework as it stood when the template was written. The IFRS Foundation's page for IFRS S2, the climate-related disclosures standard, records that the ISSB issued amendments to its greenhouse gas emissions disclosures in December 2025, a reminder that the text behind a template can change after the template is built. For every framework the vendor lists, ask which published version the template follows, the date it was last updated and what the customer must do to receive an update. Record the answer next to the supported-versions line of the quote, and treat an answer of a framework name without a version as not yet answered.

IFRS Foundation: IFRS S2 Climate-related Disclosures. The standard's navigator page, used here only for the existence of a dated amendment. Whether IFRS S2 applies to an entity is a separate question for the reporting specialist. Checked 3 October 2026.