How to Prepare a GRI Report without a Dedicated ESG Team

ANSWER | EXPLAIN | APPLY | EVIDENCE | CONNECT | PUBLISH

This Knowledge Card gives a direct answer, explains the technical logic, shows how to apply it, identifies the evidence needed, and provides a controlled publishing package. Requirements, recommendations, implementation practice and expert interpretation are kept distinct.

First-time reporters frequently assume that the choice is between building a full sustainability department and assigning the report to communications. Neither assumption is sound. GRI reporting requires impact assessment, evidence from across the organisation, technical interpretation and governance decisions. These functions can be distributed across existing roles, but they cannot be replaced by polished drafting alone.

The lean model is not “one person does everything”. It is a temporary and repeatable operating system in which existing functional owners contribute facts and decisions, a reporting owner coordinates the process, specialists are brought in where judgement is material, and the highest governance body or delegated governance process reviews and approves the reported information and material topics as applicable.

A controlled first cycle should favour a defensible scope, traceable evidence and transparent gaps over a visually ambitious report that cannot be reproduced. The organisation can improve design, automation and breadth in later cycles once the underlying reporting system is stable.

The first question is not “Who is our ESG manager?” but “Which decisions and evidence must be owned?” A small organisation can allocate the work to people who already understand operations, finance, workforce, safety, procurement, legal and communications. The reporting owner converts those contributions into one controlled process.

Figure 1. Minimum viable team. Roles may be combined, but materiality, evidence, technical review and governance approval should not disappear.

Communications is often the most available function and may be highly capable at managing deadlines, interviews, report structure and publication. The risk arises when an editorial function becomes the de facto owner of impact identification, metric definitions, estimates and compliance claims.

External support should fill specific capability or independence gaps rather than replace organisational ownership. A consultant cannot determine impacts credibly without access to operational knowledge, affected stakeholders and decision-makers. Equally, a first-time team should not improvise human-rights, biodiversity, climate, geospatial, legal or assurance judgements beyond its competence.

Word and Excel can support a first report when the organisation controls identifiers, versions, owners and evidence. The danger is not the file format itself; it is uncontrolled copies, unclear definitions and decisions made in email. A shared folder should contain one controlled master for each register and published output.

A simple naming convention materially reduces errors: YYYY_Project_Register_Version_Status. Use read-only snapshots at governance gates. Store evidence through stable links rather than embedding uncontrolled copies in multiple workbooks. Lock calculation cells where appropriate and retain an exported PDF of approved tables.

The plan below is an implementation example, not a GRI requirement or a promise that every first report can be completed in 12 weeks. It assumes senior sponsorship, a reasonably contained organisation, prompt access to data and a limited number of major technical gaps.

Figure 2. Illustrative 12-week roadmap with four governance gates. Timings must be adapted to organisational complexity, stakeholder engagement and data readiness.

A 12-week calendar does not mean 12 weeks of full-time work for every contributor. It does mean that the reporting owner needs protected capacity and that data owners must respond during their active windows. The following ranges are illustrative LRA planning assumptions, not GRI requirements.

A lean team should resist two opposite pressures: attempting every possible metric before material topics are determined, and excluding difficult impacts because data are not ready. The scope should follow the GRI architecture and material-topic process. Where required information is unavailable or incomplete, the organisation should address the applicable omission requirements and improve the data plan rather than inventing completeness.

Start with the reporting basis and applicability decisions, not a graphic design concept.

Collect information on activities, business relationships and impact evidence before finalising the data request.

Prioritise negative impacts and potentially severe impacts when resources are constrained.

Use estimates only where they are reasonable, controlled and transparently explained.

Keep a visible list of source gaps, assumptions and information that needs specialist review.

Do not describe an immature management process as effective without outcome evidence.

Publish a narrower, well-supported report rather than a broad report filled with generic narrative — while still meeting the conditions of the reporting claim selected.

A communications manager may coordinate drafting and publication, and can act as reporting owner with appropriate technical support. Communications should not decide material topics, invent methodologies, approve data or make technical claims alone; functional owners, specialist review and governance approval must remain explicit and appropriately separated.