Commissioned Research
Top 10 Best Tcfd Reporting Software of 2026

GITNUXSOFTWARE REVIEW

Sustainability In Industry

Top 10 Best Tcfd Reporting Software of 2026

Compare tcfd reporting software options and how Watershed, Coolset, and Novata fit different sustainability reporting workflows and teams.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

This comparison is built for ESG analysts and operators mapping TCFD governance, strategy, risk, and metrics into report-ready disclosures. Readers weigh automation depth, data-model compatibility, and integration or API options so climate data collection and target tracking can feed consistent audit-ready outputs, with Greenly as one reference point for TCFD-aligned reporting workflows.

Watershed is the best choice for enterprise ESG teams needing scenario and emissions workflows tied to evidence, since it links workflow inputs and scenario outputs into export-ready disclosure artifacts with audit trails, whereas Coolset fits smaller teams that want TCFD-aligned drafts with section-level traceable review changes.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Watershed

Workflow-based evidence capture links calculation inputs and scenario outputs to export-ready disclosure artifacts.

Best for: Fits when ESG teams need scenario and emissions workflows tied to evidence with audit-ready exports.

2

Coolset

Editor pick

Evidence-linked review workflow that ties edits to specific disclosure sections and maintains a draft-level audit trail.

Best for: Fits when ESG teams need TCFD-aligned drafts with traceable workflow changes and repeatable inputs.

3

Novata

Editor pick

Workflow-driven TCFD narrative generation that links disclosure sections to versioned climate risk inputs.

Best for: Fits when ESG and risk teams need repeatable TCFD reporting with controlled review cycles.

Comparison Table

1
WatershedBest overall
enterprise
9.0/10
Overall
2
8.8/10
Overall
3
enterprise
8.7/10
Overall
4
enterprise
8.5/10
Overall
5
8.3/10
Overall
6
vertical specialist
7.8/10
Overall
7
7.6/10
Overall
8
API-first
7.3/10
Overall
9
vertical specialist
6.9/10
Overall
10
enterprise
6.5/10
Overall
#1

Watershed

enterprise

Watershed provides carbon accounting, climate data management, target tracking, and sustainability reporting.

9.0/10
Overall
Features9.0/10
Ease of Use9.0/10
Value9.0/10
Standout feature

Workflow-based evidence capture links calculation inputs and scenario outputs to export-ready disclosure artifacts.

Watershed is built for teams that must connect climate reporting workflows to verified business data and repeatable disclosure outputs. Its core strength is scenario and emissions workflow configuration through audit-friendly change tracking and structured reporting exports for climate frameworks.

Administrators can control contributor access and manage submission cycles while teams run calculations, evidence capture, and review steps in a single system. Watershed also supports automation needs via API access to reporting inputs and status updates across the climate reporting lifecycle.

Pros
  • +Audit trail logging ties edits to reporting outputs for climate disclosures
  • +API access supports automation of input loads and workflow state updates
  • +Scenario and emissions workflows stay in one review and submission flow
  • +RBAC-style contributor controls support governance for multi-user reporting cycles
Cons
  • –Configuration depth requires disciplined setup of calculation and evidence mapping
  • –Some climate modeling workflows need more external data wrangling before import
  • –Large reporting templates can become harder to maintain without strong template governance
  • –Scenario configuration can feel data-shape dependent when inputs vary by entity
Use scenarios
  • Energy data compliance teams

    Normalize utility data for recurring reports

    Traceable energy metrics

  • Sustainability procurement teams

    Update Scope 3 using supplier submissions

    Documented Scope 3 inventory

Show 2 more scenarios
  • ESG reporting and finance teams

    Assemble disclosures with calculation provenance

    Evidence-backed disclosure packages

    Teams capture evidence and calculation provenance to generate disclosure outputs aligned to climate frameworks.

  • Enterprise sustainability reporting teams

    Model entities and boundaries consistently

    Consistent entity rollups

    Organizations configure entities, operational boundaries, and source mappings to produce consistent rollups across reporting periods.

Best for: Fits when ESG teams need scenario and emissions workflows tied to evidence with audit-ready exports.

#2

Coolset

SMB

Coolset combines carbon accounting, ESG data collection, climate targets, and sustainability reporting.

8.8/10
Overall
Features8.8/10
Ease of Use8.7/10
Value8.9/10
Standout feature

Evidence-linked review workflow that ties edits to specific disclosure sections and maintains a draft-level audit trail.

Coolset is a climate and ESG reporting workflow tool built around structured inputs, configurable calculations, and controlled review cycles. It supports TCFD-aligned reporting by mapping disclosures to scenario narratives and risk statements, then organizing evidence collection to match those sections.

Coolset also focuses on audit trail logging for changes across drafts and data, which helps teams keep internal consistency during review and sign-off. Integration depth is driven by data import and connector-oriented ingestion paths, so climate outputs can flow from carbon accounting sources into reporting drafts.

Pros
  • +TCFD section mapping aligns narrative fields with reporting structure
  • +Change tracking captures edits across drafts for traceable reviewer workflow
  • +Configurable calculation and input staging reduces manual rework
  • +Connector-friendly ingestion supports keeping source data close to drafts
Cons
  • –Deep customization needs careful configuration of templates and fields
  • –Scope 3 coverage depends on accurate upstream category mapping and inputs
Use scenarios
  • Climate risk and sustainability teams

    Link scenarios to TCFD disclosure inputs

    Reviewable, linked assumptions

  • Sustainability operations teams

    Reuse workflows for recurring reporting

    Consistent reporting processes

Show 2 more scenarios
  • ESG reporting and communications teams

    Draft disclosures with traceable evidence

    Disclosure drafts with history

    Reporting teams connect disclosure content to source data, supporting documents, and internal review steps.

  • Carbon accounting managers

    Calculate consistent inventories across units

    Documented emissions inventory

    Teams collect operational activity data and run repeatable greenhouse gas calculations across facilities and business units.

Best for: Fits when ESG teams need TCFD-aligned drafts with traceable workflow changes and repeatable inputs.

#3

Novata

enterprise

ESG data platform for private markets with TCFD reporting framework.

8.7/10
Overall
Features8.7/10
Ease of Use8.6/10
Value8.8/10
Standout feature

Workflow-driven TCFD narrative generation that links disclosure sections to versioned climate risk inputs.

Novata’s workflow centers on producing consistent TCFD-aligned disclosures from versioned inputs, including risk assessment results and supporting assumptions. The tool fits organizations that already track emissions and climate metrics elsewhere and need a controlled path from those data points to published narratives. It also supports cross-functional coordination through review cycles so sustainability teams and risk owners can validate the same dataset.

A key tradeoff is that scenario modeling quality depends on the completeness of imported inputs and assumption definitions, so teams with fragmented data often spend time on data hygiene first. Novata works best when climate, finance, and risk owners agree on a baseline set of risk events, materiality boundaries, and metric definitions before automation ramps up. This setup reduces rework when assurance-ready exports and question-based disclosure content must stay consistent across iterations.

Pros
  • +TCFD disclosure workflows stay tied to controlled, reviewable inputs
  • +Automation reduces manual remapping between metrics and narrative sections
  • +Assumption handling supports repeatable scenario updates across cycles
  • +Integration options support pulling external climate and emissions datasets
Cons
  • –Scenario output quality depends on clean, well-scoped input assumptions
  • –Cross-team governance takes effort to keep definitions consistent
Use scenarios
  • ESG reporting teams

    Produce board-ready TCFD narratives

    Fewer inconsistencies across drafts

  • Climate risk analysts

    Update scenario-based risk metrics

    Faster iteration cycles

Show 1 more scenario
  • Enterprise governance teams

    Coordinate cross-functional review

    Lower review churn

    Manage approvals so risk owners and sustainability teams validate the same underlying climate results.

Best for: Fits when ESG and risk teams need repeatable TCFD reporting with controlled review cycles.

#4

Metrio

enterprise

Sustainability reporting software with TCFD framework templates.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Workflow linking scenario assumptions to TCFD disclosure outputs with traceable input changes.

Metrio’s TCFD execution flow ties climate scenario work to the disclosure outputs, which reduces the manual gap between assumptions and narrative sections. Its climate reporting data handling supports cross-year recalculation workflows and change tracking so auditors can follow how figures evolve across cycles. For teams coordinating multiple business units, the practical value is governance of inputs and outputs rather than only report assembly.

Pros
  • +TCFD workflows connect climate inputs directly to disclosure sections
  • +Change tracking supports audit trail logging across reporting updates
  • +Repeatable recalculation reduces inconsistency between iterations
  • +Exports target common assurance-ready documentation workflows
Cons
  • –Scenario setup requires careful input mapping to avoid rework
  • –Automation depth is limited if source systems lack consistent identifiers
  • –Some governance controls need deliberate admin configuration before scale
  • –Complex scope 3 category mapping can increase project timeline
Use scenarios
  • ESG reporting teams

    Run TCFD cycle with traceable changes

    Faster internal sign-off

  • Finance and FP&A partners

    Recalculate climate metrics across years

    Consistent year-over-year reporting

Show 2 more scenarios
  • Assurance and compliance owners

    Support evidence collection for filings

    Reduced evidence hunting

    Use audit trail logging to show how exported figures map to recorded inputs.

  • Data integration managers

    Automate emissions inputs from systems

    Higher calculation throughput

    Implement API connectors that feed emissions sources and maintain controlled updates.

Best for: Fits when ESG teams need controlled TCFD outputs with traceable calculation changes across cycles.

#5

Greenly

SMB

Carbon accounting platform with TCFD-aligned reporting features.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Traceable TCFD disclosure exports that preserve a link from reported figures to underlying calculation inputs and factor versions.

Greenly’s TCFD reporting flow is built around emissions inventory inputs and climate analysis outputs that can be packaged into disclosure-ready exports. The audit trail is designed to connect each reported figure back to the underlying activity inputs, assumptions, and factor versions. Configuration stays centralized, so repeated disclosures can reuse the same mapping and calculation logic across reporting periods.

Pros
  • +TCFD-aligned disclosure outputs link numbers to calculation inputs and assumptions
  • +Reusable calculation logic reduces rework across reporting cycles
  • +API supports automated imports for operational activity data sync
  • +Exports support assurance-oriented review workflows
Cons
  • –Scenario modeling sophistication is capped by the input detail available
  • –Some data mapping requires careful factor and activity normalization upfront
Use scenarios
  • ESG reporting teams

    Repeat TCFD reporting each cycle

    Faster report preparation

  • Sustainability data managers

    Automate activity data ingestion

    Lower reconciliation effort

Show 2 more scenarios
  • Finance and assurance liaisons

    Support assurance review trails

    Audit-ready review workflow

    Provides calculation traceability that connects outputs to inputs, assumptions, and factor versions.

  • Corporate climate analysts

    Package scenario narratives for disclosure

    Consistent disclosure narrative

    Aligns scenario-ready outputs into TCFD reporting sections for board and stakeholder use.

Best for: Fits when ESG teams need recurring TCFD outputs with traceable calculations and automation via API imports.

#6

Measurabl

vertical specialist

Measurabl collects real estate ESG data, calculates emissions, and produces portfolio sustainability reports.

7.8/10
Overall
Features7.8/10
Ease of Use7.7/10
Value7.9/10
Standout feature

Submission-grade audit trail that preserves calculation input history for each reporting output.

Measurabl is a climate and ESG reporting software used by real estate operators to manage emissions data, climate risk inputs, and reporting workflows. It is distinct for its focus on property-level measurement and an audit trail that ties calculation inputs to reporting outputs.

Pros
  • +Property-level emissions workflows match real estate reporting granularity.
  • +Audit trail links data inputs to calculation and reporting outputs.
  • +Emission factor library handling supports repeatable year-to-year updates.
  • +Automated exports reduce manual spreadsheet rework for disclosure packs.
Cons
  • –Requires disciplined configuration to keep required fields consistent.
  • –Climate risk modeling depth depends on how inputs are provided and mapped.
Use scenarios
  • Hotel sustainability teams

    Standardize property data collection and review

    Consistent property inputs

  • ESG reporting and sustainability teams

    Prepare recurring internal or external disclosures

    Standardized disclosure inputs

Show 2 more scenarios
  • Property operations teams

    Organize utility and meter records

    Building-level inputs

    Teams compile utility and energy data from multiple properties into consistent building-level inputs for analysis.

  • Central sustainability teams

    Route contributor approvals for portfolio reporting

    Reviewed traceable inputs

    Central teams route building data through contributor review and approval before portfolio-level reporting.

Best for: Fits when real estate ESG teams need audit-traceable emissions workflows with structured reporting outputs.

#7

Emitwise

SMB

Emitwise automates corporate carbon accounting and supplier emissions data collection.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Audit trail logging that links factor selections and calculation runs to the final disclosure numbers.

Emitwise collects emissions data and converts it into structured sustainability reporting outputs for TCFD-style climate disclosures. It supports workflows around GHG factor management, calculation runs, and audit trail logging so reviewers can trace source inputs to reported figures.

Pros
  • +Configuration-based reporting templates reduce manual mapping work for TCFD disclosures
  • +Audit trail logging ties calculation outputs back to input records and factor choices
  • +Emission factor library supports consistent factor governance across reporting periods
  • +Data ingestion workflows reduce reliance on spreadsheet consolidation for recurring updates
Cons
  • –Climate scenario and transition risk modeling coverage is narrower than dedicated risk workbenches
  • –Complex scope 3 category mapping needs careful setup and ongoing factor hygiene
  • –Extensibility via API can lag behind teams needing custom calculation logic
  • –Assurance-ready export fields may require post-processing for specific publication formats
Use scenarios
  • ESG reporting and finance teams

    Generate assurance-ready disclosure datasets

    Clarity on evidence

  • Net-zero program teams

    Maintain an ongoing emissions ledger

    Recurring emissions updates

Show 2 more scenarios
  • Industrial environmental compliance teams

    Apply data-quality checks to monitoring sources

    Consistent reporting outputs

    Teams connect measurement inputs with data-quality checks and produce compliance-oriented reporting views.

  • Sustainability and ESG teams

    Build period-based corporate inventories

    Repeatable inventories

    Teams construct recurring inventories from operational activity and asset data with consistent period-to-period calculations.

Best for: Fits when ESG teams need repeatable emissions calculations plus TCFD reporting outputs with strong traceability.

#8

ESG Book

API-first

ESG Book provides sustainability data, climate analytics, taxonomy mapping, and disclosure intelligence.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

TCFD pillar mapping remains linked to emissions and risk assumption records for traceable narrative reporting.

ESG Book supports TCFD-style climate reporting through structured scenario and risk inputs that map into report-ready disclosures. The workflow centers on importing entity data, linking emissions inputs to climate narratives, and maintaining change history for audit trails.

Pros
  • +TCFD pillar mapping stays attached to underlying climate inputs
  • +Draft workflows separate preparation from review and signoff steps
  • +Audit trail logging helps track assumption and figure changes
  • +Exports are structured for reuse in sustainability reporting workflows
Cons
  • –Scenario configuration requires careful setup to avoid inconsistent assumptions
  • –Scope 3 category mapping depth can require manual supplementation
Use scenarios
  • ESG reporting teams

    Draft TCFD disclosures from structured inputs

    Faster disclosure production cycles

  • Finance and FP&A analysts

    Align emissions assumptions with narratives

    Consistent assumptions across reports

Show 2 more scenarios
  • Internal audit and compliance

    Review scenario edits for audit trails

    Stronger audit defensibility

    Review steps and change history provide evidence for governance checks around scenario and risk revisions.

  • Sustainability governance committees

    Route TCFD drafts through approvals

    Controlled disclosure sign-off

    Organizational roles manage review stages and approvals around scenario-based climate risk disclosures.

Best for: Fits when ESG teams need structured TCFD disclosures with controlled review workflows and traceable assumption changes.

#9

Datamaran

vertical specialist

Datamaran monitors ESG regulations, materiality topics, climate risks, and reporting obligations.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Scenario analysis workflow that carries assumptions and supporting inputs through to TCFD-ready disclosure outputs.

Datamaran is a climate and ESG reporting workflow tool built around automated data collection and structured reporting outputs. The system links company data inputs to climate scenario analysis tasks and produces TCFD-aligned disclosures with audit-friendly documentation.

Pros
  • +Scenario-to-disclosure workflows reduce manual stitching of TCFD sections
  • +Audit trails stay tied to input sources and calculated outputs
  • +API and connector options support automated refreshes for reporting cycles
  • +Multi-entity configuration supports consistent reporting across affiliates
Cons
  • –Scope 3 coverage quality depends on upstream supplier and factor inputs
  • –Advanced modeling requires disciplined configuration to avoid inconsistent assumptions
Use scenarios
  • Carbon accounting and sustainability teams

    Create emissions-focused disclosure records

    Disclosure-ready inventories

  • Venture capital ESG teams

    Standardize portfolio ESG responses

    Comparable portfolio updates

Show 2 more scenarios
  • Annual report disclosure owners

    Coordinate period-based approvals and outputs

    Controlled disclosure workflow

    Teams manage period-based data collection, narrative edits, approvals, and reporting outputs with visible edit history.

  • Investor relations and ESG teams

    Refresh framework-aligned KPI packs

    Traceable KPI packs

    Teams update validated metrics and investor-facing reporting views without rebuilding the workflow.

Best for: Fits when ESG teams need repeatable TCFD reporting workflows with traceability across multiple data sources and entities.

#10

IBM Envizi

enterprise

IBM Envizi manages ESG data, emissions accounting, climate metrics, and sustainability disclosures.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Audit trail logging ties emission calculation inputs to disclosure outputs for traceable TCFD reporting.

IBM Envizi centralizes emissions data capture, mapping, and reporting workflows for TCFD-aligned climate disclosures. It uses a governed data model to connect operational inputs to reporting outputs, including structured climate risk content and audit trail logging for disclosure readiness.

Pros
  • +Governed workflows support approval states for climate risk narratives.
  • +Audit trail logging captures calculation inputs and output lineage.
  • +API and connector surface supports automated refresh from enterprise sources.
  • +Configurable mapping reduces rework when scopes and categories shift.
Cons
  • –Climate scenario setup needs disciplined configuration before scaling.
  • –Some reporting formats require admin support to finalize layouts.
Use scenarios
  • ESG reporting operations teams

    Govern emissions inputs for disclosure readiness

    Governed disclosure outputs

  • Finance and sustainability teams

    Run recurring scenario and metric calculations

    Consistent calculated metrics

Show 2 more scenarios
  • Enterprise data teams

    Ingest inputs via connectors and APIs

    Connected enterprise data flows

    Teams pull operational inputs from enterprise systems and push standardized reporting outputs into disclosure workflows.

  • Assurance-focused disclosure teams

    Maintain audit trail for report figures

    Audit-ready documentation

    Teams use audit trail logging tied to structured inputs to support disclosure readiness and review.

Best for: Fits when enterprise ESG teams need governed calculations, change control, and API-driven refresh for TCFD disclosures.

Conclusion

After evaluating 10 tcfd reporting software, Watershed stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Watershed

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Tcfd Reporting Software

Which tool is better for recurring TCFD reporting with reusable assumptions and audit trails: Greenly or Datamaran?
Greenly is built for recurring TCFD outputs using reusable assumptions and documented audit trails, and it emphasizes traceable links from reported figures to underlying calculation inputs and factor versions. Datamaran focuses on repeatability and traceability across multi-entity reporting chains, using automated data collection and scenario workflow execution that carries assumptions into TCFD-ready disclosure outputs.
How do Greenly and Novata differ in traceability of disclosure outputs to climate inputs?
Greenly preserves a link between TCFD disclosure exports and the underlying calculation inputs and factor versions, which supports audit workflows that need source-to-output traceability. Novata links disclosure sections to versioned climate risk inputs through workflow-driven narrative generation, which helps when review teams need controlled updates tied to risk input changes.
When scenario analysis inputs change mid-cycle, what breaks in Coolset versus IBM Envizi workflows?
In Coolset, evidence-linked review workflows tie edits to specific disclosure sections and keep a draft-level audit trail, so changes that require re-scoping evidence collection can create rework across the affected sections. In IBM Envizi, governed data model updates and approval flows keep scenario and metric outputs consistent, so misalignment between contributor-submitted inputs and the governed model can stall recurring calculation runs until data governance inputs are corrected.
Which tool best supports API-first automation for importing operational data into TCFD reporting: Greenly or Watershed?
Greenly uses an API-first surface for importing operational data and synchronizing models so ESG teams can automate data refresh into climate disclosures. Watershed provides API access for reporting inputs and status updates across the climate reporting lifecycle, which supports automation of workflow state but can require additional configuration of scenario and emissions workflow settings for each reporting cycle.
How do RBAC and approval controls differ between Watershed and ESG Book for review and sign-off?
Watershed includes admin-controlled contributor access and manages submission cycles while teams run calculations, evidence capture, and review steps in one system. ESG Book supports configurable organizational roles and review steps around drafts, which targets review orchestration but depends on how teams structure their role definitions for each reporting stage.
Where does Emitwise fall short for scenario workflow depth compared with Metrio?
Emitwise concentrates on emissions data configuration, GHG factor management, calculation runs, and audit trail logging tied to factor selections and disclosure numbers. Metrio places scenario assumptions inside the workflow that links scenario inputs to TCFD disclosure outputs with traceable input changes, which makes Metrio more suitable when scenario-driven narratives are a primary deliverable.
How does Metrio handle traceable changes across reporting cycles compared with Measurabl?
Metrio emphasizes controlled updates and traceable changes across reporting cycles by linking scenario assumptions to TCFD disclosure outputs with traceable input changes. Measurabl maintains property-level measurement workflows with an audit trail that preserves calculation input history for each reporting output, which targets real estate operators with entity-level submission requirements.
Which tool is best for multi-entity reporting repeatability with structured outputs: Datamaran or ESG Book?
Datamaran is built for repeatable TCFD reporting workflows across multiple data sources and entities, using scenario analysis workflow execution that carries assumptions and supporting inputs through to disclosure outputs. ESG Book centers on importing entity data and reconciling emissions inputs with climate narratives, while maintaining change history for audit trails tied to structured disclosure content and review workflows.
What tradeoff occurs when relying on connector-oriented ingestion in Coolset versus connector and API workflows in IBM Envizi?
Coolset drives integration depth through connector-oriented ingestion paths into reporting drafts, which can be efficient for specific data pipelines but may require more mapping work when data sources do not align with the ingestion structure. IBM Envizi integrates through connectors and APIs into a governed data model, so workflow consistency depends on how well enterprise systems map into the governed model used for recurring calculations and approval flows.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Tcfd Reporting Software

Options differ most in how well they turn tcfd reporting inputs into a consistent narrative and emissions-informed outputs. The biggest separator is whether scenario and risk outputs stay traceable through an audit log.

Scenario and risk workflow depth

Why it matters

Scenario and risk workflow depth determines whether your tcfd reporting can reflect both transition and physical risk in one repeatable process, not just a slide export. It also affects how quickly teams can rerun results when assumptions change.

How to check

Ask for a demo that starts from assumptions and ends at the risk sections you plan to publish. Request a sample scenario run with at least one transition and one physical risk output, then ask how edits to assumptions propagate to the output.

Data model mapping to calculations

Why it matters

Data model mapping to calculations matters for tcfd reporting because missing or unclear field mapping leads to inconsistent numbers across narratives and tables. It also reduces rework when you refresh baseline inputs.

How to check

Request a sample import template and show how a row-level change affects totals and any written risk disclosures. Try mapping one activity dataset through to an output and confirm where units and time periods are enforced.

Audit log and export traceability

Why it matters

Audit log and export traceability lets stakeholders see what changed and why, which is central for tcfd reporting reviews. It also supports smoother assurance-ready workflows by keeping a consistent change history.

How to check

On a demo, make a small change (like an assumption value or an included dataset) and then export the report. Check whether the export retains references to the inputs used and whether the audit log records who changed what and when.

Automation and API for refresh runs

Why it matters

Automation and API for refresh runs separates tools that stay manual from tools that keep tcfd outputs current as data updates. It also reduces the risk of mismatched versions across teams.

How to check

Ask whether refresh runs can be triggered via an API or scheduled workflow. In the demo, request a repeatable run that regenerates outputs after loading a revised dataset, then verify where versioning shows up.

RBAC for report roles

Why it matters

RBAC for report roles matters because tcfd reporting often involves contributors, reviewers, and approvers. Clear permissions help prevent accidental edits that break traceability.

How to check

Request a walkthrough of user roles and permissions (for example, contributor vs reviewer). Try changing a field as a non-privileged user in the demo and confirm what the system blocks and what it allows.

Red flags

  • Scenario edits don’t change the outputs you’re meant to publish
  • Exports don’t let you trace inputs and edits back to a history
  • Template imports don’t show how fields map into calculations

Fit by situation

  • If we refresh assumptions every quarter, prioritize automation and API for refresh runs.
  • If multiple teams contribute assumptions and narratives, prioritize RBAC for report roles.
  • If we expect reviewers to question numbers and wording, prioritize audit log and export traceability.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.