Skip to content
UK SRSThe UK Sustainability Reporting Standards, ESOS, SECR and TCFD, read against the published text.HUBUK SRS GuideAn independent reference guide to UK SRS, ESG, TCFD, SECR, ESOS and the global standards.YOU ARE HEREGlobal Reporting StandardsSustainability reporting standards worldwide: ISSB, the EU CSRD after Omnibus I, California SB 253 and SB 261, and UK SRS.UK SRS StandardsUK SRS S1 and S2 at the provision: reliefs, comply or explain, and the FCA statements.ESOS QuestESOS Phase 4 in depth: qualification, the audit, sign-off, action plans and penalties, read against the Regulations.SRS EngineeringThe data build behind a UK SRS report: metrics, owners, controls and timing.SRS ReportWhat a UK SRS report contains, how it is assembled, and how to read one.UK SRS ReportAnalysis and commentary: CDP, the DESNZ emission factors, SECR and ESOS, with every figure cited.UK SRS NewsThe cluster's news publication, and what a UK SRS report contains.UK SRS DeliveryTemplates, costs, ESOS delivery guides and readiness assessment.UK SRS FinanceFinanced emissions, PCAF and IFRS S1/S2 for banks, insurers and asset managers.SECRStreamlined Energy and Carbon Reporting: deadlines, thresholds, eligibility and guidance.Carbon CreditsCarbon credit ratings, risk analysis, valuation and market structure.Environmental RegimesThe eight UK environmental reporting regimes, their thresholds, deadlines and regulators.UK SRS ServicesThe services arm: ESOS, SECR, net zero and sustainability consultancy.

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.

Allocate the workRequirements and evidence

Module 01 / 03

Records

Identify repeatable collection and calculation tasks.

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.

Task categories for a buyer’s allocation exercise rather than claims about particular providers.
Evidence questionReview approachWhat to avoid
CollectionGather defined records and track gapsAssuming collection determines materiality
CalculationApply the selected method with retained inputsAssuming a formula approves its own basis
InterpretationExplain scope, significance and limitationsTreating a completed field as judgement
PublicationPrepare and review the actual outputCalling 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.

Specify repeatabilityRequirements and evidence

Module 01 / 03

Inputs

Identify records and definitions to collect.

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.

Requested demonstrations depend on the actual reporting task and accepted scope.
Evidence questionReview approachWhat to avoid
CollectionWhich source records and responsible users are included?An integration claim without defined fields
CalculationCan inputs, units and method versions be traced?A total with no reproducible basis
CorrectionCan a reviewer inspect the original and revised record?A silent overwrite
ExportCan 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.

Name the decisionRequirements and evidence

Module 01 / 03

Scope

Explain the organisation and activities assessed.

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.

Editorial deliverable tests rather than a claim that advice certifies the report.
Evidence questionReview approachWhat to avoid
QuestionState the specific interpretation or decision neededA general strategy workshop
EvidenceIdentify records and assumptions examinedAn opinion without a source basis
ReasoningExplain alternatives, conclusion and limitationsOnly a traffic-light status
HandoverProvide usable decision records and next stepsKnowledge 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.

Fictional combined briefRequirements and evidence

Module 01 / 03

Internal team

Own the reporting purpose and accepted decisions.

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.

Fictional scientific-publishing example; no provider performance or real company assessment is asserted.
Evidence questionReview approachWhat to avoid
Company inputDefine the question and supply relevant recordsAn assumption that missing evidence can be invented
System workDemonstrate collection, status and exportA claim that the tool decides the significance
Advisory workExplain the bounded evidence question and limitsA promise to approve all suppliers
AcceptanceReview the joined-up evidence and decisionsAccepting 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.

Compare the whole scopeRequirements and evidence

Module 01 / 03

Included work

Identify the named deliverables.

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.

Scope questions only; no provider prices, cost ranges or superiority claims.
Evidence questionReview approachWhat to avoid
Initial workWhat setup, mapping or analysis is included?A headline figure with no deliverable list
Client effortWhich records and decisions must the company supply?An assumed fully outsourced process
Ongoing workWhat updates, support or repeat-cycle tasks are included?Assuming future work is free
Exit or transitionWhat 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.

Keep engagements distinctRequirements and evidence

Module 01 / 03

Preparation

Build records and disclosures.

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.

Use actual engagement evidence and permissions rather than the labels in this fictional comparison.
Evidence questionReview approachWhat to avoid
Software usedName the supported workflowA claim that the platform certified the report
Advice obtainedDescribe the bounded preparation or reviewAn unspecified statement that the business was approved
Target validationIdentify the actual validated target and routeAn internal target plan called validated
Assurance obtainedIdentify the information and conclusion coveredA 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.

Keep the process usableRequirements and evidence

Module 01 / 03

Records

Receive portable sources and accepted outputs.

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.

  1. 101

    Define the output

    Identify the reporting or business decision the project must support.
  2. 202

    Separate the tasks

    Distinguish collection, calculation, interpretation and publication.
  3. 303

    Review internal capability

    Identify the people and evidence already available.
  4. 404

    Request demonstrations

    Test any proposed system on representative records and corrections.
  5. 505

    Specify advisory questions

    Define bounded reasoning and handover deliverables.
  6. 606

    Join the interfaces

    Check that providers and internal owners use the same scope and evidence.
  7. 707

    Compare actual scope

    Review quoted inclusions, dependencies, recurring work and transition.
  8. 808

    Review the claims

    Keep preparation, assurance, certification and validation distinct.
  9. 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.

Book a free consultation