How to use this guide
This page explains the topic, a proportionate scope, useful outputs and questions to ask. It is not a fixed consulting package; the actual work should follow your reporting basis, business boundary, maturity and decision needs.
When reporting support is useful
Reporting support is most valuable when the organisation needs to interpret requirements, coordinate many data owners, strengthen the evidence behind disclosures or turn a fragmented reporting process into a repeatable annual cycle.
Common triggers
- First ESG or sustainability report.
- HKEX or group reporting requirements have changed.
- Current disclosures are generic or difficult to evidence.
- Data collection starts too late each year.
- Finance, risk and operations are not connected to the reporting process.
Best project objective
Do not define the scope as “write our ESG report”. Define the reporting basis, management decisions, evidence, review controls and capability that should remain after publication.
What the scope should cover
| Workstream | Questions answered | Typical outputs |
|---|---|---|
| Requirements mapping | Which rules, standards and customer or group requests apply? | Disclosure index, applicability assessment, gap register. |
| Reporting plan | Who owns each disclosure, when is evidence due and who reviews it? | Calendar, RACI, data request pack, review timetable. |
| Data and evidence | Are boundaries, methods, assumptions and source records clear? | Data dictionary, calculation files, evidence register, control notes. |
| Narrative development | Does the report explain governance, actions, performance and limitations clearly? | Draft disclosures, case studies, KPI commentary, cross-references. |
| Quality control | Are claims consistent with records and with the annual report? | Review comments, consistency checks, substantiation log, final disclosure index. |
Useful deliverables
- Regulatory and framework requirements matrix.
- Reporting boundary and methodology memo.
- Project plan with owners, reviewers and escalation points.
- Data templates and supporting-evidence requirements.
- Draft report content and disclosure index.
- Management review pack highlighting gaps and decisions.
- Year-two improvement plan rather than a fresh restart.
Match the approach to reporting maturity
First report
Prioritise a credible baseline, clear boundaries, a focused materiality process and disclosures that can be supported. Avoid overclaiming maturity.
Established reporter
Improve decision-usefulness, connectivity with financial information, target governance, Scope 3 coverage and consistency across channels.
Assurance-ready reporter
Strengthen controls, evidence retention, methodology approvals, change logs, reconciliations and management sign-off.
What your team should prepare
- Legal entity and operational boundary.
- Previous reports, policies, board papers and KPI files.
- List of business units, locations and data owners.
- Investor, customer, lender or parent-company requests.
- Known data gaps, incidents and significant organisational changes.
- Publication deadline and annual-report coordination points.
What good reporting advice should not do
An adviser should not invent policies, imply controls that do not exist or substitute polished wording for management action. Difficult gaps should be disclosed transparently with a practical improvement plan.
Watch for
Scopes that focus almost entirely on design and word count, without explaining requirements mapping, evidence, data review, management decisions or handover.