Run an environmental data review that produces decisions
Leave an environmental data review with a decision about each disputed input: what it supports, what must change, who owns the remaining question and what evidence would allow the next use. A file can support a quantity while leaving its accompanying claim unresolved.
This guide is for teams consolidating environmental schedules across sites. It assumes that the reporting objective and boundary have been agreed. The review method below is a suggested internal working aid for turning exceptions into usable reporting inputs. It does not establish compliance, approve a complete disclosure or replace technical measurement review.
Fix the intended use before discussing the number
Identify the period, boundary version, metric definition, unit and destination for each schedule. “Water for April” is incomplete: water withdrawn, consumed and discharged answer different questions. Likewise, a waste-dispatch record and a recycling claim need different support.
Bring the expected submission list, the received versions and an exception list. Give each exception an ID linked to an exact source page, row or meter interval. Include the proposed treatment and affected output. Ask the source owner to explain the record and the method owner to decide any treatment outside the preparer's authority.
GRI 1's Accuracy guidance addresses reproducible calculations and identified estimates; its Verifiability guidance addresses original sources, decision records and uncertainty. These principles support the evidence discipline here. The fields and statuses in this guide are Nitium's suggested workflow, not a prescribed GRI form. GRI 1: Foundation 2021, section 4
Ask four questions that change the disposition
Does the source fit the request? Check the actual activity, site, dates, unit and measurement basis. A correctly copied number can still answer the wrong question.
What establishes the proposed treatment? Inspect the relevant records, calculation and assumptions. An owner's explanation can guide the investigation; record whether it is corroborated.
What changes downstream? Identify the schedule, subtotal, comparison and sentence affected. Accepting kWh does not also approve an emissions factor, renewable classification or efficiency claim.
What can proceed now? Record the permitted use and its conditions. Keep an unsupported claim held even when a narrower activity quantity is accepted.
Start with exceptions that could change a release decision or require specialist input. A small numerical difference can reveal a missing source or wrong boundary; do not close it solely because its percentage is low. Safety, legal or operational concerns need the appropriate immediate escalation rather than waiting for this reporting review.
Keep evidence status and permitted use separate
Record whether an input is missing, received but unchecked, checked with a query, or checked and accepted for a defined use. Alongside that, state whether the affected output can proceed, must be corrected and rechecked, or remains held. These descriptions prevent “received” from becoming “approved” and let a source serve one purpose without being stretched to another.
For every decision retain: exception ID; question and proposed use; source references and versions; supported facts and unresolved assumptions; treatment and reason; changed outputs; decision owner; action owner and agreed date; reviewer; and the evidence required to remove the hold. Where the reviewer lacks authority, record the escalation rather than an approval.
IFC's ESMS Implementation Handbook recommends retaining written management-review decisions. It provides broad management-system context; this narrower data-review workflow does not implement the whole ESMS or establish conformity with IFC Performance Standard 1. IFC ESMS Implementation Handbook, printed page 62
A fictional review with six expected schedules
All sites, documents, roles, decisions and quantities below are invented. A reporting lead reviews April 2026 inputs on 6 May. Boundary B1 covers the organisation's own operations at Sites A and B and excludes an unrelated tenant. The selected internal dashboard requests three activity schedules per site: purchased-electricity consumption, water withdrawal and waste dispatched. This is a limited dashboard, not a complete environmental report.
The period runs from 00:00 on 1 April to 00:00 on 1 May 2026, Indian Standard Time. All intervals use an included start and excluded end. Within this example, the stated source checks are assumed to have been performed by the fictional reviewers; they are not checks performed for a real business.
A electricity: 42,000 kWh, accepted from April meter schedule EA1.
B electricity: 9,300 kWh entered in version V2, with a cross-period bill exception.
A water: 310 kL entered in V2, with a tenant-boundary exception.
B water: 180 kL, accepted from April withdrawal record WB1.
A waste: 2,400 kg of dispatches, accompanied by a proposed “all recycled” statement.
B waste: no schedule received at the review cut-off.
Five of six schedules have arrived. That count describes submissions; it says nothing about the proportion of environmental quantities covered or whether the proposed statements can be used.
D1 Correct the electricity period
Bill EB1 records 9,300 kWh from 00:00 on 20 March to 00:00 on 20 April. Checked interval extract EB2 for the same meter splits that bill into 3,700 kWh before 1 April and 5,600 kWh from 1 to 20 April. Extract EB3 records another 3,300 kWh from 20 April to 1 May. The meter references, time convention, multiplier and sequence have been checked, with no unexplained overlap or gap.
Decision: replace the 9,300 kWh entry with 5,600 + 3,300 = 8,900 kWh for April. The bill cross-check remains 3,700 + 5,600 = 9,300 kWh. This uses the checked interval evidence; it does not divide the bill evenly by days.
Owner and release test: the B facilities owner supplies the corrected schedule; the reporting analyst checks V3 against EB1–EB3 and the April subtotal before accepting it. In this fictional review that check is completed on 6 May. The 3,700 kWh March portion is linked to the March schedule and checked for duplication; it is not added to April. The decision approves electricity quantity only.
D2 Apply the agreed water boundary
Site A main-meter record WA1 covers 310 kL in April. Tenant sub-meter record WA2 covers 30 kL within that same main-meter total and period. Meter map WA3 and boundary B1 establish that these 30 kL belong entirely to the excluded tenant; assume no shared or unallocated water remains in this simplified example.
Decision: use 310 − 30 = 280 kL for A's own-operation withdrawal schedule. Keep the original main-meter reading and the exclusion visible. The review applies the already agreed boundary; it does not invent a new exclusion to improve the result.
Owner and release test: the A facilities owner records the adjustment, and the reporting lead checks V3 against WA1–WA3 and B1. That check is completed on 6 May. The result supports the defined withdrawal quantity; no consumption or discharge quantity is established.
D3 Accept a dispatch quantity and hold the recycling claim
Site A movement register DA1 and matched collection receipts DA2 support 2,400 kg leaving the site in April. The supplied receipts establish collection only. They do not identify the final recovery operation for those loads. The proposed “all recycled” wording exceeds the supplied evidence.
Decision: accept 2,400 kg solely as A's documented dispatch quantity. Hold the recycling claim and remove it from the draft dashboard. Neither waste generated nor waste recycled is inferred from the dispatch total.
Owner and release test: the EHS owner agrees to obtain load-linked evidence of the claimed recovery operation, quantity and period by 8 May. The reporting lead must review that evidence and the exact proposed wording before lifting the claim hold. If it does not arrive, the supported dispatch entry can remain with its narrow label; the recycling statement stays absent. No vendor misconduct is inferred from the gap.
D4 Keep the missing waste schedule visible
Decision: B's waste-dispatch quantity remains unknown. The 2,400 kg from A cannot become the two-site total, and a blank cell cannot become zero.
Owner and release test: the B EHS owner agrees to supply its April movement population and supporting records by 8 May. The analyst must check period, units, duplicates and coverage before proposing a combined total. If the record remains unavailable, the reporting lead retains the hold on a complete two-site waste total and labels any internal A-only subtotal explicitly. An internal limited-use decision does not settle any public disclosure omission requirements.
Close the review with a bounded result
The checked V3 electricity subtotal is 42,000 + 8,900 = 50,900 kWh. Water withdrawal is 280 + 180 = 460 kL. These are separate metrics and must not be added together. Waste dispatch remains 2,400 kg for A only; B is unknown. The recycling claim remains held.
Five activity schedules are now accepted for their stated uses, and one is missing. One accepted dispatch schedule also has a held claim. Do not add the claim hold as a seventh schedule or describe five accepted schedules as 83.3% of environmental data complete. The two open decisions have owners, agreed dates and different closure tests.
Hand over V3 with the decision record, source index and open items D3–D4. Name the exact values and wording that may move into the next draft. Final disclosure approval follows the organisation's governance process; see the management sign-off guide.
Reopen affected decisions when evidence changes
A revised bill, changed boundary, new source or different method can invalidate a previous conclusion. Link the new evidence to the original decision, identify affected calculations and wording, and obtain the required recheck. Retain earlier versions rather than silently replacing the record.
At the next review, start with the open decisions and any changed evidence. Repeated cut-off errors may warrant a process action, but correcting April's number alone does not establish that the cause has been removed. Use the corrective-action closure guide for that separate test. Use the site reconciliation guide for the detailed entity roll-up.
Prepare evidence for a useful review
Nitium's sustainability and GRI reporting support can help organise data, draft narrative and information gaps within an agreed scope. Discuss your reporting needs with the intended output, reporting period and a non-confidential description of the unresolved decisions.
Primary sources checked 13 October 2026. The review method and worked example are illustrative. No client result, professional assurance, legal conclusion or certification is claimed.
Comments