Standards and reporting
ESG Software vs Consultant
The useful choice is who will perform each reporting task and how the organisation will inspect and retain the result.
Should the decision be software or a consultant?
An editorial buying decision should allocate specific tasks between internal people, software and external support rather than assuming the options are mutually exclusive.
Module 01 / 03
Records
Identify repeatable collection and calculation tasks.
Module 02 / 03
Judgement
Identify decisions needing interpretation.
Module 03 / 03
Responsibility
Keep the reporting owner and acceptance clear.
Read the detailed guidance and evidence
UK SRS S1’s reporting purpose and claim conditions concern the actual information produced, not whether it was assembled in a platform or with external assistance UK SRS S1, objective and paragraphs 72–73A.
The useful question is which combination can deliver the required evidence and review process for the organisation’s circumstances.
Begin with the standards hub, the software guide and the consultancy guide to define the output before comparing proposals.
Which tasks should be separated first?
This editorial task map avoids comparing unlike proposals under a single ESG-project label.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Collection | Gather defined records and track gaps | Assuming collection determines materiality |
| Calculation | Apply the selected method with retained inputs | Assuming a formula approves its own basis |
| Interpretation | Explain scope, significance and limitations | Treating a completed field as judgement |
| Publication | Prepare and review the actual output | Calling any delivered PDF compliant |
Which repeatable tasks might a system support?
GHG Protocol corporate and value-chain accounting require defined inventory boundaries, methods and data, which makes their record handling a separate task from deciding the accounting basis Corporate Standard, chapters 3–4 Scope 3 Standard, boundary and data collection.
Module 01 / 03
Inputs
Identify records and definitions to collect.
Module 02 / 03
Methods
Retain approved calculation assumptions.
Module 03 / 03
Review
Preserve corrections and unresolved gaps.
Read the detailed guidance and evidence
A buyer can request a demonstration of repeated collection, calculation and export without assuming that every product provides those functions in the same way.
The acceptance test should examine a relevant record, a correction and the resulting output rather than relying on the category label carbon software.
If the organisation lacks a settled method or boundary, automating the current spreadsheet can simply preserve an unresolved decision at greater scale.
The software RFP turns those needs into tests, while implementation guidance addresses the subsequent operating process.
What should a software proposal demonstrate?
These editorial questions test the work proposed without recommending a product.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Collection | Which source records and responsible users are included? | An integration claim without defined fields |
| Calculation | Can inputs, units and method versions be traced? | A total with no reproducible basis |
| Correction | Can a reviewer inspect the original and revised record? | A silent overwrite |
| Export | Can the internal owner reuse the evidence? | Only a dashboard image |
Which decisions need an explicit interpretation owner?
GRI 3 material-topic determination concerns significant impacts, while UK SRS S2 addresses climate strategy, risks and metrics, so technical outputs do not settle every reporting judgement GRI 3, steps 3–4 UK SRS S2, core content.
Module 01 / 03
Scope
Explain the organisation and activities assessed.
Module 02 / 03
Significance
Apply the relevant reporting criteria.
Module 03 / 03
Claim
Check what the evidence supports.
Read the detailed guidance and evidence
An organisation can ask external support to analyse a defined question, but should specify the evidence, reasoning and limitations it expects to receive.
Equally, an internal team may already have the relevant capability and need only a system for organising the accepted process.
The distinction is about the task and available competence, not an unsupported claim that consultants always interpret better or software always costs less.
A useful proposal identifies the decisions to be made, who supplies the facts and who accepts the resulting interpretation.
What should an advisory deliverable explain?
This editorial acceptance test makes advice reviewable without promising that a provider will reach a particular conclusion.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Question | State the specific interpretation or decision needed | A general strategy workshop |
| Evidence | Identify records and assumptions examined | An opinion without a source basis |
| Reasoning | Explain alternatives, conclusion and limitations | Only a traffic-light status |
| Handover | Provide usable decision records and next steps | Knowledge retained solely by the adviser |
What would a combined approach look like?
In this fictional case, a scientific-publishing group separates recurring supplier-information collection from the judgement about what the evidence means.
Module 01 / 03
Internal team
Own the reporting purpose and accepted decisions.
Module 02 / 03
System
Support the defined collection and evidence record.
Module 03 / 03
External support
Review a bounded interpretation question.
Read the detailed guidance and evidence
The group wants a repeatable way to gather records across business units, but it also needs to understand the limits of information about particular business relationships.
The UN Guiding Principles describe human-rights due diligence as assessing impacts, acting, tracking and communicating, so a completed questionnaire is not the whole process UN Guiding Principles 17–18.
The OECD Guidelines likewise describe a wider due-diligence cycle and relationships beyond the first tier, as government recommendations rather than a new statutory duty OECD Guidelines 2023, commentary 15–17.
The fictional brief assigns collection workflow to the proposed system and a defined evidence-interpretation review to external support, with the company retaining the acceptance decision.
How should the fictional combined scope be divided?
This original editorial allocation keeps the interfaces between work packages explicit.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Company input | Define the question and supply relevant records | An assumption that missing evidence can be invented |
| System work | Demonstrate collection, status and export | A claim that the tool decides the significance |
| Advisory work | Explain the bounded evidence question and limits | A promise to approve all suppliers |
| Acceptance | Review the joined-up evidence and decisions | Accepting two disconnected deliverables |
How can cost be compared without invented benchmarks?
An editorial comparison should use the actual scope and quoted terms, including client work, recurring needs, changes and handover, rather than assuming two proposals describe equivalent services.
Module 01 / 03
Included work
Identify the named deliverables.
Module 02 / 03
Dependencies
Identify internal effort and missing inputs.
Module 03 / 03
Continuation
Identify ongoing use, updates and support.
Read the detailed guidance and evidence
Ask each bidder to separate the work needed to establish the process from the work needed to run or update it later.
A software quote may need implementation work, while an advisory quote may depend on a client-owned system, but the actual proposal must establish those facts.
Do not insert a market price, presumed saving or promised payback without evidence specific to that proposition.
The comparison should also identify what happens when the reporting scope changes, because an apparently complete first-cycle deliverable may not define later support.
Which scope differences belong in the comparison?
These editorial questions let the buyer compare the real commercial propositions.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Initial work | What setup, mapping or analysis is included? | A headline figure with no deliverable list |
| Client effort | Which records and decisions must the company supply? | An assumed fully outsourced process |
| Ongoing work | What updates, support or repeat-cycle tasks are included? | Assuming future work is free |
| Exit or transition | What usable files and instructions are delivered? | A final slide deck as the only knowledge transfer |
Are consulting, software, certification and validation interchangeable?
ISO does not itself perform certification, and GRI 1 sets its own reporting-claim conditions, so software delivery or advice should not be relabelled as certification of the report ISO certification GRI 1, section 3.
Module 01 / 03
Preparation
Build records and disclosures.
Module 02 / 03
Review
Inspect the defined work and limitations.
Module 03 / 03
External conclusion
Identify any actual certification or validation route.
Read the detailed guidance and evidence
If a project includes a climate target, the relevant SBTi criteria and validation process are separate from buying a platform or commissioning a general report SBTi Corporate Net-Zero Standard Criteria.
Read the SBTi standard guide for versions and validation context rather than assuming a consultant’s preparation work validates the target.
Similarly, identify any independent assurance engagement and its actual scope before describing information as assured.
The buyer should record the actual engagement, the information covered and the conclusion obtained before choosing the public wording.
What should the public wording identify?
This editorial claim review makes the service actually performed visible.
| Evidence question | Review approach | What to avoid |
|---|---|---|
| Software used | Name the supported workflow | A claim that the platform certified the report |
| Advice obtained | Describe the bounded preparation or review | An unspecified statement that the business was approved |
| Target validation | Identify the actual validated target and route | An internal target plan called validated |
| Assurance obtained | Identify the information and conclusion covered | A whole-company claim from a limited review |
What should remain with the organisation?
An editorial handover should preserve the evidence, definitions, decisions and instructions needed to operate the next cycle whichever delivery mix is chosen.
Module 01 / 03
Records
Receive portable sources and accepted outputs.
Module 02 / 03
Reasoning
Retain methods, limitations and approvals.
Module 03 / 03
Capability
Name the internal owner and repeat-cycle tasks.
Read the detailed guidance and evidence
The fictional publishing group asks an internal reviewer to follow one supplier-information record from collection through the bounded interpretation review without relying on either provider’s memory.
The result exposes whether the system export and advisory conclusion use the same scope and accepted evidence.
The buyer can then accept the demonstrated work, retain conditions for unresolved issues and decide what support is still required.
Choosing a combination is therefore a practical allocation decision rather than a guarantee that software, a consultant or an internal team alone will establish reporting compliance.
The UK SRS consultancy buying guide helps specify the reporting basis, preparation work and evidence handover in an engagement brief.
Use the GRI reporting consultancy guide to specify topic reasoning, disclosure support, index review and the final handover.
How can the buyer choose the delivery mix?
This is an editorial preparation sequence rather than a prescribed assessment method or a conformity checklist.
- 101
Define the output
Identify the reporting or business decision the project must support. - 202
Separate the tasks
Distinguish collection, calculation, interpretation and publication. - 303
Review internal capability
Identify the people and evidence already available. - 404
Request demonstrations
Test any proposed system on representative records and corrections. - 505
Specify advisory questions
Define bounded reasoning and handover deliverables. - 606
Join the interfaces
Check that providers and internal owners use the same scope and evidence. - 707
Compare actual scope
Review quoted inclusions, dependencies, recurring work and transition. - 808
Review the claims
Keep preparation, assurance, certification and validation distinct. - 909
Accept the handover
Retain usable records, decisions and ownership for the next cycle.
Frequently asked
Questions people ask
Do we have to choose either software or a consultant?
No, the organisation can allocate different tasks internally, to a system and to external support, provided the interfaces and acceptance responsibilities are clear.
Is software always cheaper than consulting?
No general price conclusion is supplied here, because actual inclusions, implementation work, client effort, recurring needs and transition terms must be compared.
Can software decide materiality for us?
A system can organise a chosen process, but the significance reasoning and applicable reporting judgement still need an accountable owner.
Does consulting establish that a report is certified?
No such equivalence is assumed, and reporting claims, certification and any separate assurance engagement need their own basis.
Can a consultant validate a climate target by preparing it?
Preparation is distinct from the relevant SBTi criteria and validation route, which must be checked for the actual target and version.
What should be retained whichever option is chosen?
An editorial acceptance record can require source records, definitions, methods, decisions, limitations, usable exports, instructions and a named internal owner.
Sources
Primary sources
Primary provisions and official owner guidance checked on 26 October 2026; historical and draft resources are labelled in the guide.
- Department for Business and TradeUK SRS S1, February 2026
- Department for Business and TradeUK SRS S2, February 2026
- Global Reporting InitiativeGRI 1: Foundation 2021
- Global Reporting InitiativeGRI 3: Material Topics 2021
- GHG ProtocolGHG Protocol Corporate Accounting and Reporting Standard, revised edition
- GHG ProtocolCorporate Value Chain Scope 3 Accounting and Reporting Standard
- ISOCertification and accreditation
- OHCHRUN Guiding Principles on Business and Human Rights, Principles 17–18
- OECDOECD Guidelines for Multinational Enterprises,2023
- Science Based Targets initiativeCorporate Net-Zero Standard CriteriaV 1.3.1
Continue reading
Read next
Software RFP
Write testable procurement requirements.
Software implementation
Test migration and operating workflows.
Reporting consultancy
Define an evidence-led engagement.
GRI reporting consultants
Scope the GRI-specific reporting work.
Sustainability software
Understand the platform workflow.