Turn agreed material topics into a data collection plan
Suggested planning aid: after a material topic is agreed, plan management-evidence requests separately from quantity-evidence requests. Check both streams for scope, source, reporting period and gaps before a reviewer decides what can be used. This is the guide’s suggested planning sequence, not a mandatory GRI workflow, evidence that collection is complete, an assessment of materiality or a compliance conclusion.
Before sending a request for “waste data” or “people data”, decide what the response needs to explain. A useful collection plan connects each agreed material topic to a clear question, defined evidence, a reporting boundary and a review decision. It collects management explanations alongside quantities.
This guide is for reporting teams moving from a reviewed topic list into data collection. The request structure and example below are optional working aids. They do not determine material topics, replace the GRI Standards or establish that a report is complete.
Carry the topic decision into the request
GRI material topics concern an organisation’s most significant impacts on the economy, environment and people, including human rights. A financial-risk ranking alone does not establish this impact-based topic list. Start from the documented decision and the specific impacts it covers. GRI 3: Material Topics 2021
Use the material-topics impact worksheet for the preceding topic-review step. Give the collection plan a topic-decision reference and version. Retain the relevant activities, locations, business relationships and affected groups, together with unresolved questions. If the decision only says “waste”, ask the topic owner to clarify the impacts before translating that label into a questionnaire.
Agreement on a topic does not approve its future data, settle every disclosure boundary or demonstrate compliance. A missing source remains a collection gap. If collection reveals a previously overlooked impact, return that evidence to the topic-review process rather than silently changing the topic list.
Map management evidence and quantities separately
For reporting in accordance with GRI, Disclosure 3-3 covers each topic’s impacts, policies, actions, effectiveness and stakeholder input. Collect explanations as well as numbers. If a specified policy or process does not exist, report that fact accurately. GRI 3, Disclosure 3-3
Then select Topic Standard disclosures relevant to the impacts, checking applicable Sector Standards. A topic may need more than one Standard. Where a Topic Standard disclosure listed in an applicable Sector Standard is not relevant, retain the required explanation for the content index. GRI 1: Foundation 2021, Requirement 5
Record each mapping down to the requirement being answered. A quantity may support one part of a disclosure while the method explanation or breakdown is still missing. Reuse a source for several requests where suitable, but record separately what it supports in each.
Define seven fields before assigning the work
Question and reference. State the answer needed, linked to the topic decision and disclosure requirement.
Indicator or explanation. Specify the quantity, unit and breakdown, or the narrative and supporting records.
Boundary. Name included sites, activities or populations and relevant business relationships. Identify exclusions and unresolved coverage.
Source and method. Name the record, location, version and calculation or extraction instructions.
Owner. Assign the person who can obtain and explain the evidence, with a named reviewer.
Period and timing. State start and end dates, snapshot dates where relevant, submission deadline and review date.
Review condition. Explain what the reviewer will check, and what happens if evidence is missing or contradictory.
These fields can sit in your existing request tracker, such as the departmental data request and ownership tracker. Keep the instructions next to the request ID so a forwarded email does not lose its boundary or method. Confirm with each owner that the record exists and the deadline is workable before issuing the full collection round.
A fictional waste topic becomes three requests
Suppose a manufacturer has agreed that waste-related impacts are material. Its topic record identifies potential harm from storage at Sites A, B and C and from waste managed by contracted handlers. The reporting team is preparing information for 1 April to 30 June 2026. All organisations, records, dates and figures in this example are invented.
GRI 306 distinguishes management of waste-related impacts from waste quantities. Disclosure 306-3 covers waste generated in the organisation’s own activities, with weight, composition and compilation context; generation is a different event from dispatch or treatment. The example selects a few requests, not the complete set needed for this topic. GRI 306: Waste 2020, Disclosures 306-2 and 306-3
Fictional requests linked to topic record W-01
W-M1 Management actions
Question and mapping. What actions were in place to manage the identified waste impacts? Supports selected parts of 3-3(c)/(d) and 306-2(a)/(b).
Response and boundary. Explain controls and implementation at A, B and C, and checks on contracted handlers. Identify which activities and handlers each action covers.
Source, owner and timing. Policy versions, dated implementation records and handler-review records. EHS lead collects; reporting lead reviews. Cover the quarter, including controls already in force. Submit 10 July; review 15 July.
Review condition. Match each action to a record and scope. A policy file alone leaves implementation unresolved. Mark unsupported locations or handler claims for follow-up.
W-M2 Effectiveness and stakeholder input
Question and mapping. How was effectiveness assessed, and what changed following stakeholder input? Supports selected parts of 3-3(e)/(f).
Response and boundary. Explain evaluation methods, defined indicators or targets, findings and lessons. State which sites, affected groups and handler activities the evidence covers.
Source, owner and timing. Dated review notes, indicator calculations and appropriately protected feedback summaries. EHS lead and engagement owner collect; reporting lead reviews. Quarter evidence, due 10 July; review 15 July.
Review condition. Check whether the evidence supports the claimed result and its limits. Keep an action’s completion date separate from evidence that it worked.
W-Q1 Generated waste quantities
Question and mapping. How much waste was generated, and what was its composition? Supports 306-3(a)/(b).
Response and boundary. Metric tonnes by composition for waste generated in own activities at A, B and C during the quarter. Preserve site-level figures and explain compilation. Do not add handlers’ own waste.
Source, owner and timing. Site generation records and documented measurement or stock-based calculations. Site EHS owners collect; reporting analyst reconciles; reporting lead reviews. Due 10 July; review 15 July.
Review condition. Check sites, period, units, composition and method. Reconcile supporting records. A dispatch total or a missing site cannot silently become a complete generation total.
The management requests follow the impacts into relevant business relationships. The selected quantity request has its own defined population. Keep those boundaries visible instead of forcing every response into one site-only subtotal. Protect sensitive underlying feedback; the collection plan can point to controlled records without copying personal details.
Decide what the returned evidence supports
Assume the fictional reviewer accepts Site A’s 10 tonnes and Site B’s 20 tonnes as generated waste for the requested quarter, with their composition and methods supported. Site C returns a 9-tonne dispatch statement but no evidence connecting that dispatch quantity to generation during the quarter.
Supported subtotal: 10 + 20 = 30 tonnes generated at A and B.
Open question: C’s generated quantity remains unknown. Request its generation records or a supported reconciliation of stock and movements.
Unsupported conclusion: 39 tonnes generated across all three sites. The extra 9 tonnes describes a different event.
Three returned files do not mean three usable generation responses. Two supported sites out of three also do not establish that two-thirds of waste mass is covered. Keep the 30-tonne subtotal labelled with its limited coverage; do not enter zero for C.
Suppose W-M1 also contains a signed policy, but implementation evidence is available only for A and B. The reviewer can acknowledge receipt of the policy and the supported implementation records while leaving C open. W-M2 still needs evidence about results. Neither the quantity subtotal nor the existence of a policy establishes effective management.
Hand over a reviewable plan and an explicit gap list
Use separate states for requested, received, clarification needed and accepted for a stated use. Attach the reviewer’s reason to each decision. If a response answers only part of the request, record that part and keep the remainder open, with an owner and next evidence date.
Where a permitted disclosure omission is needed, GRI 1 requires the specific missing requirement, an allowed reason and its explanation in the content index. Incomplete information needs its missing scope, cause, recovery steps and expected timing explained. The internal request status is not the public reporting decision. GRI 1, Requirement 6
Before drafting, pass on the topic-decision version, mapped requests, accepted evidence, limited-use subtotals and open questions. The content-index owner can then check the information actually disclosed. Keep collection planning focused on making those inputs usable.
Check editions before reusing last year’s requests
Record the Standard edition and intended report publication date. As checked on 13 October 2026, the 2021 Universal Standards remain the basis used here. GRI 101: Biodiversity 2024 took effect on 1 January 2026, replacing GRI 304: Biodiversity 2016. GRI 102: Climate Change 2025 and GRI 103: Energy 2025 take effect from 1 January 2027. GRI resource centre; GRI biodiversity edition notice
For climate reporting published on or after 1 January 2027, GRI’s FAQ specifies use of GRI 102; earlier adoption is encouraged. Its transition affects GRI 305-1 to 305-5 and GRI 201-2, rather than every disclosure in those Standards. GRI 102 FAQ, question 10
GRI 103 replaces GRI 302: Energy 2016 from 1 January 2027, with earlier adoption encouraged. Recheck the actual requirements and relevant sector alignment before reissuing requests; simply changing a disclosure number can miss new information needs. GRI 302 transition notice, cover and effective-date page
Prepare the collection round
Nitium’s sustainability and GRI reporting support includes disclosure mapping, draft content and information gaps within an agreed scope. Discuss your reporting plan with your reporting objectives, agreed topics and a non-confidential description of the evidence gaps.
Sources checked 13 October 2026. This is reporting-preparation guidance with a fictional example, not a complete GRI disclosure, legal opinion, certification or independent assurance conclusion.
Comments