GRI Reporting Software

GRI’s system combines Universal, applicable Sector and selected Topic Standards, so a product that handles only environmental metrics may leave important work outside its interface GRI 1, section 1.3.

Use GRI Standards for the reporting requirements and sustainability software for the wider platform decision, then test the GRI-specific handovers described here.

Start with a small representative reporting pack, because importing a large spreadsheet successfully does not demonstrate that its meaning, limitations and relationships survive the transfer.

GRI 3’s four-step process is guidance, so do not accept a product claim that its particular questionnaire or scoring formula is the mandatory GRI method GRI 3, guidance on determining material topics.

For applicable Sector Standards, reporters must review likely material topics and explain relevant topics judged not material in the content index, which makes rationale and index linkage practical procurement tests GRI 1, Requirements 3 and 7 GRI Sector Program.

The organisation should decide the access requirements before the demonstration and use synthetic evidence to establish whether the proposed workflow can meet them.

The permitted omission categories are not applicable, legal prohibitions, confidentiality constraints and unavailable or incomplete information, with explanations required under the relevant rules GRI 1, Requirement 6.

Reasons for omission are not permitted for GRI 2 disclosures 2-1 to 2-5 or GRI 3 disclosures 3-1 and 3-2, so a universal skip button is an inadequate control GRI 1, Requirements 2 and 4.

The intended claim matters because reporting in accordance requires all nine GRI 1 requirements, whereas reporting with reference has its separate index, statement-of-use and notification requirements GRI 1, section 3 and with-reference requirements.

Treat a warning as something a person must resolve, because a technically valid export can still contain unsupported explanations or an inappropriate reporting claim.

The group uses synthetic employee records for a sales demonstration and finds that one business unit has supplied an average while the other has supplied a period-end count.

The buyer asks the demonstrator to preserve the original submissions, document the selected reporting basis and route the correction back to the relevant contributor.

GRI 2’s employee disclosure distinguishes reporting details such as whether numbers are headcount or full-time equivalent and the methodology and assumptions, so the basis cannot safely disappear during aggregation GRI 2, disclosure 2-7.

The fictional pilot passes only if reviewers can trace the final narrative and number to the corrected record and inspect who accepted it.

Agree the expected file formats and field meanings before the pilot so that a polished PDF does not conceal the absence of reusable source and decision records.

In the fictional worker-data pilot, correcting the count should reopen the explanation where it still describes the previous basis.

An editorial acceptance check asks whether reviewers can identify that mismatch before publication rather than assuming a populated field is correct.

GRI’s current programme includes an application and licence agreement, verification of content implementation and confirmation of licensing GRI licensing process.

The 2025 update introduced a revised verification process and licensing mark, so older references to a certified-software programme should not be treated as a current product-quality verdict GRI software verification update, 29 April 2025.

Check the exact product in GRI’s partner directory and contact GRI if its status is unclear, rather than inferring coverage from a provider’s unrelated service or training badge GRI Licensed Software and Tools Partners.

GRI’s copyright policy states that it is not an auditor, assessor, certifier or verifier of sustainability reports, and permission to use protected content is distinct from the quality of the user’s report GRI copyright policy.

Do not assume a report’s accounting period alone selects the correct standard version, or that a product’s taxonomy feature already supports every newly issued standard.

The taxonomy page describes automated XBRL and manual webform routes and outputs including XBRL, iXBRL, Excel and PDF, but this does not make XBRL filing a universal GRI reporting requirement GRI taxonomy features GRI 1, Requirement 9.

Include historical standard versions, source references, review decisions and the mapping between published disclosures and underlying records in the acceptance discussion.

For shared data supporting another framework, retain the separate materiality and disclosure judgements explained in ISSB versus GRI rather than treating a common export as blanket equivalence.

Return to the sustainability reporting standards hub when a new reporting request changes the scope of the software project.