Practical guide · Educational reading

Build a traceable greenhouse gas inventory workflow by deciding organizational boundaries, mapping emissions sources and structuring data requests before collecting totals.

Audience / jurisdiction: International; organizations preparing a corporate greenhouse gas inventory using GHG Protocol guidance. Jurisdiction-specific legal reporting obligations require separate assessment.

1. Define the inventory before requesting data

Before requesting fuel records and energy bills, decide which operations the inventory will cover. The GHG Protocol Corporate Standard separates organizational boundaries, which determine the operations consolidated, from operational boundaries, which classify their direct and indirect emissions. Keeping these decisions separate gives data owners a clearer explanation of what to submit.

Suggested practice: prepare a short inventory brief stating the reporting purpose, intended users, reporting period, preparer and reviewer. Record any reporting-program criteria that need separate checking. This guide is for organizations using the GHG Protocol framework internationally; it does not establish a legal reporting duty. Its templates are suggested working tools, not mandatory forms.

Sources: [1]

2. Keep a traceable boundary-decision record

Chapter 3 of the Corporate Standard distinguishes consolidation by equity share from consolidation by control. Control can be assessed financially or operationally. The selected approach should be applied consistently across the organization rather than chosen separately for each facility to produce a preferred result.

Suggested practice: create a boundary-decision record with fields for operation or site, ownership interest, control assessment, selected consolidation approach, inclusion decision, rationale and supporting document reference. Assign unresolved decisions to an owner before issuing the main data request.

For each decision, retain enough explanation for another reviewer to follow the reasoning. A site name and an inclusion checkbox alone will not explain why an operation belongs inside or outside the inventory.

Sources: [1]

3. Map sources before assigning data requests

Once the organizational boundary is established, map the activities and emissions sources associated with those operations. Chapter 4 addresses operational boundaries and emissions classification. Scope 2 should not be treated as an electricity-only category: its guidance also covers purchased or acquired steam, heat and cooling.

Suggested practice: use a source map containing the site, activity or equipment, proposed scope, classification rationale and unresolved questions. Keep the map linked to the boundary record so that changes in included operations prompt a review of the sources being collected.

Do not force a final classification where the necessary facts remain unclear. For example, unresolved control or lease arrangements should become review questions, not assumptions hidden in a spreadsheet. Detailed classification decisions may require further guidance beyond this introductory workflow.

Sources: [1], [2]

4. Make collection repeatable and gaps visible

Chapter 7 of the Corporate Standard supports consistent collection procedures and inventory-quality checks. Translate that principle into a request that people can answer repeatedly, rather than asking different sites for loosely defined annual totals.

Suggested request fields are source identifier, reporting period, quantity, unit, evidence reference, data owner, actual or estimated status, estimation rationale and reviewer. Explain the expected period coverage and ask respondents to identify missing records explicitly.

Maintain a separate gaps-and-review log. Suggested checks include missing months, duplicate entries, inconsistent units, unsupported estimates, unexplained changes and differences between the approved site list and the data received. Compare historical information where available, and investigate unusual results rather than automatically accepting or replacing them.

Sources: [1]

5. Test the workflow with a small example

Hypothetical example: an organization lists an owned workshop, a rented office and a jointly operated facility. Its preparer first documents the consolidation approach, then records the evidence needed to resolve control questions for the joint operation. This example does not establish the correct classification of any facility.

The preparer requests energy quantities with units and period coverage from the relevant data owners. If the office has incomplete records, the missing period is flagged for follow-up rather than silently entered as zero. A reviewer then checks whether every included operation has a corresponding source map and whether each requested source has either data or an open issue.

The useful output is a decision trail: what was included, why, what evidence was collected and what remains unresolved. A first collection workbook is a preparation tool, not by itself proof that the inventory is complete.

Sources: [1]

6. Record the guidance used

GHG Protocol’s corporate-suite update page states that existing standards and guidance remain in effect until it communicates otherwise. Development activity should therefore be kept separate from the published material used for an inventory.

Suggested practice: record the source documents used and check their status before approving the inventory methodology. Keep future revisions on a monitoring list without treating proposals as current requirements or inventing a transition deadline.

Sources: [3]

Sources

1. The Greenhouse Gas Protocol: A Corporate Accounting and Reporting Standard, Revised Edition
2. Scope 2 Guidance
3. GHG Protocol Corporate Suite of Standards and Guidance Update Process

Your experience

Could a reviewer trace every operation in your inventory from its boundary decision to its data request and unresolved issues?

Originally published by AdviseISO, a knowledge-sharing initiative of W3 Solutionz.