Keep three questions separate
- Which organization and reporting period does the document describe?
- Which operations, sites or people are included in this particular metric?
- Which activities and business relationships are relevant to the impact being discussed?
Answering one question does not automatically answer the others. Keep the boundary alongside the metric instead of leaving it in an unrelated policy document.
Use a boundary note
A practical note can identify included entities, excluded activities, acquisitions or closures, leased operations, the treatment of contractors and the dates to which the inclusion decision applies. Not every item will be relevant to every metric. Explain the relevant differences.
Illustrative wording: “Electricity data covers the two owned production sites for the calendar year. The leased storage facility is excluded because tenant-level consumption was not available. The exclusion has not been estimated.” This example shows a limitation; it does not make that exclusion compliant with any particular disclosure requirement.
Changed boundaries need changed comparisons
If a site is added or removed, separate the effect of that change from changes in performance. Keep the original series and the revised calculation trail. Do not silently splice a new scope onto an old denominator.
For an acquisition, record when data became available, whether the comparative period was recalculated and how the report explains that choice. A reviewer should be able to identify which version is used in each table.
Ask an operational colleague to test the note
Give the boundary note and an organizational chart to someone outside the reporting team. Ask which invoice, employee group or facility they would include. Differences in their answer reveal wording that needs clarification.
Use the current applicable Standard to determine the actual reporting requirements. The worksheet here is a way of organizing decisions, not an alternative reporting framework.