Check which policy version your rollout evidence supports

A policy approved in June, effective in July and reflected in a procedure in August leaves three different dates to explain. Before saying that a revised policy was implemented across a business, check whether the supporting records refer to the right version, people and period.

This is a practical check for governance and sustainability-reporting teams. Its output is a version-and-rollout record with specific open questions. It is an optional working method, not a legal compliance assessment or proof that a policy works.

Keep approval, applicability and rollout separate

GRI 2: General Disclosures 2021 separates reporting about policy commitments, including approval level, coverage and communication, from reporting about how commitments are embedded through responsibilities, procedures, business relationships and training. These are different evidence questions. See Disclosures 2-23 and 2-24. The check below is a suggested internal method; GRI does not prescribe this record format.

Start with one commitment and its exact document section. Give each relevant version its own entry. For this check, record:

• The version identifier, approval record and effective date stated in the records.

• The entities, sites and groups covered, including exclusions.

• The linked procedure, form or communication, its version and the date it was used.

• The question that remains, the person responsible for answering it and the evidence needed.

A file upload date cannot substitute for an effective date. If the records disagree, retain both dates and refer the discrepancy to the responsible owner rather than choosing the more convenient one.

A worked check: the July form still names the old policy

All records and dates in this example are fictional. Policy P01 version 2 applies from 1 January 2025. Version 3 is approved on 15 June 2026, effective from 1 July. The reporting team is reviewing the quarter ending 30 September 2026.

1. Approval file: identifies version 3 and its 1 July effective date. Record that document status. It does not show who received the revised text.

2. July acknowledgement: names version 2. Keep it linked to version 2 until the owner establishes what was actually sent and acknowledged. Do not silently relabel the form as version 3 evidence.

3. Procedure revision: is dated 15 August. Ask what instructions applied from 1 July, when the revised procedure was first used, and which locations and periods each version covered. A revision date alone does not establish when a procedure began to operate.

The supported conclusion is narrow: the supplied records identify version 3 as approved and effective, while rollout evidence contains unresolved version and timing questions. They do not establish that it was fully implemented across the group from 1 July. Nor do these mismatches, alone, establish a legal breach or prove that staff followed the wrong process.

Turn the mismatch into an answerable action

A useful open item would read: “P01-v3 rollout: the July acknowledgement names v2. The policy owner will identify the text issued, the recipient group and the supporting distribution record. The procedure owner will explain the July-to-August transition. Until reviewed, group-wide implementation from 1 July remains unsubstantiated.” Set an agreed due date; do not invent one after the fact.

Keep the original form and both policy versions. Add the response, its source and the review decision beside the open item. If the owner supplies only a present-day screenshot, record what it shows now; it cannot by itself establish what recipients saw in July.

Close the question without erasing the history

Before handover, have a reviewer follow one rollout record back to its applicable policy version, then follow the revised commitment forward to its affected procedures and communications. Note where either trail stops. Close a question only when the response addresses the original version, coverage and timing issue, or record the remaining limitation explicitly.

Retain restricted personnel or legal records in their authorised locations; a register can hold a controlled reference rather than a copy. A corrected link or completed acknowledgement is evidence of that action, not automatic evidence of understanding, consistent practice or effectiveness.

For help organising policy evidence into a sustainability disclosure, see Nitium's sustainability and GRI reporting support or discuss your reporting needs. Advisory preparation does not provide a legal opinion, certification or independent assurance conclusion.

GRI source checked 12 October 2026. This focused exercise does not constitute a complete GRI disclosure.