Most emissions miscalculations don’t come from bad data; they come from scope boundaries drawn incorrectly before any data collection even begins. An emissions source gets classified under the wrong scope, a Scope 2 calculation mixes market-based and location-based approaches inconsistently, or an entire Scope 3 category simply gets left out of the boundary altogether. The underlying meter readings and utility bills might be perfectly accurate, and the final reported figure can still be wrong, because the boundary defining what should have been included was never set correctly in the first place.
For sustainability teams and FM leaders responsible for emissions reporting, understanding where boundary errors typically occur matters, because these mistakes are structural: they don’t get caught by better data validation; they require getting the underlying methodology right from the start.
This distinction is easy to overlook, because boundary errors and data quality errors can look identical from the outside: both produce a final figure that turns out to be wrong. But the fix is completely different. A data quality problem gets solved by better metering, more consistent collection, tighter validation. A boundary problem gets solved by revisiting the methodology itself, and no amount of additional data collection effort will correct a figure that was scoped incorrectly to begin with.
Why scope boundaries are harder to get right than they look
The GHG Protocol provides a detailed framework for classifying emissions into Scope 1, 2 and 3, but applying that framework correctly to a specific real-world portfolio involves genuine judgement calls, particularly around organisational boundaries, ownership structures and which specific activities fall into which category.
This is exactly why scope boundaries are one of the most common sources of genuine emissions miscalculation: not through carelessness, but because the methodology itself requires careful, consistent interpretation that many organisations apply inconsistently across different parts of their reporting.
Where scope classification errors actually happen
Understanding the specific recurring mistakes helps organisations check their own reporting against known failure patterns.
Confusing operational control with financial control
Organisations can report emissions using operational control, financial control or equity share approaches, but many apply these inconsistently across different parts of their portfolio without realising it, exactly the ambiguity explored in how portfolio structure affects ESG accuracy.
Scope 2: market-based vs location-based confusion
Reporting energy emissions requires choosing between market-based and location-based methodologies, and mixing the two inconsistently across different sites or reporting periods produces figures that aren’t genuinely comparable.
Scope 3 categories left out entirely, not just underestimated
Rather than simply being underestimated, entire Scope 3 categories, particularly those related to construction, refurbishment or downstream leased assets, are often omitted from the boundary altogether, undermining the completeness explored in aligning net zero commitments with building-level data.
If your organisation has never explicitly documented which boundary approach it uses and why, that gap is a strong candidate for where your emissions figures may already be miscalculated. Find out how Codedevza AI helps correct scope boundary errors.
The consequences of getting scope boundaries wrong
Boundary errors create specific, identifiable risks once a disclosure is genuinely tested against the methodology it claims to follow.
Double counting across organisational boundaries
Inconsistent boundary approaches across joint ventures or shared ownership structures can result in the same emissions being counted by more than one reporting entity, undermining the accuracy explored in the relationship between ESG strategy and estate reality.
Understated totals that look better than reality
Omitted Scope 3 categories or inconsistently applied boundaries frequently result in reported totals significantly lower than genuine emissions, creating exactly the exposure covered in avoiding narrative-led sustainability reporting.
Boundary errors that surface only during assurance
Boundary methodology mistakes are often invisible internally until a third-party assurance provider specifically tests the classification approach, connecting to the standard covered in what audit-ready ESG data really means.
Scope boundary errors don’t announce themselves; they sit quietly in the methodology until someone tests it against the actual protocol requirements. Talk to Codedevza AI about correcting scope boundary errors in your emissions reporting.
Getting scope boundaries right from the start
Correcting boundary errors requires deliberate methodology decisions, documented clearly and applied consistently.
Choose and document a consistent boundary approach
Decide explicitly whether operational control, financial control or equity share will be used, document that choice and apply it consistently across the entire portfolio rather than case by case.
Map every emissions source against the GHG Protocol categories
Systematically map every known emissions source, direct, purchased energy and value chain activities, against the full set of GHG Protocol categories, ensuring nothing is inadvertently omitted from the boundary.
Review boundary decisions as the portfolio changes
As assets are acquired, disposed of or restructured, boundary classifications need to be reviewed and updated rather than left applying an outdated structure to a portfolio that has genuinely changed.
A practical framework for correcting scope boundary errors
For organisations ready to review their current methodology, the process follows a consistent structure.
Step 1: audit current boundary classifications against the protocol
Compare your current scope classifications directly against GHG Protocol guidance, identifying any inconsistencies in approach or gaps in coverage across the portfolio.
Step 2: identify and correct double counting or omissions
Trace emissions sources across organisational boundaries to identify where double counting or complete omissions may be occurring, correcting the underlying classification rather than just the final figure.
Step 3: document the boundary methodology for future consistency
Create clear, documented guidance on boundary methodology that future reporting cycles can follow consistently, supported by the same discipline behind evidence mapping for ESG disclosures.
Final thoughts
Scope boundary errors are structural, not incidental: they happen in the methodology decisions made before any data collection begins, which is exactly why better validation alone can’t catch them. Organisations that explicitly choose and document a consistent boundary approach, map every emissions source against the full GHG Protocol framework and review that methodology as their portfolio changes build emissions figures that genuinely reflect what the protocol actually requires. The ones that leave boundary decisions implicit or inconsistent often discover the error only once an assurance provider specifically goes looking for it, by which point the correction is far more disruptive than it would have been to get right from the outset.
Correct scope boundaries are the foundation every subsequent emissions figure depends on. Speak to Codedevza AI about getting scope boundaries right across your portfolio.
Frequently asked questions
What are scope boundaries in emissions reporting?
They define which emissions sources and organisational entities fall within an organisation’s reporting scope, following the classification framework set out in the GHG Protocol.
Why do scope boundary errors happen even with accurate underlying data?
Because the mistake occurs in the classification methodology itself, before data collection even begins, meaning accurate readings can still be assigned to the wrong scope or omitted entirely.
What’s the difference between operational and financial control approaches?
They determine which entities and assets an organisation includes in its reporting boundary, and inconsistent application across a portfolio can create genuine classification errors.
Why does mixing market-based and location-based Scope 2 methods cause problems?
It produces figures that aren’t genuinely comparable across sites or reporting periods, undermining the reliability of any trend or progress analysis built on them.
Why are entire Scope 3 categories sometimes omitted rather than underestimated?
Certain categories, particularly construction, refurbishment or downstream leased assets, are often overlooked entirely during boundary setting rather than being included but calculated imprecisely.
How can double counting occur across organisational boundaries?
Inconsistent boundary approaches across joint ventures or shared ownership structures can result in the same emissions being counted by more than one reporting entity simultaneously.
When do scope boundary errors typically get discovered?
Often only during third-party assurance review, when a provider specifically tests the classification methodology against protocol requirements, rather than during routine internal reporting.
What’s the first step in correcting scope boundary errors?
Audit current classifications directly against GHG Protocol guidance, identifying inconsistencies in approach and gaps in coverage across the portfolio.
Should boundary methodology be reviewed regularly?
Yes. As a portfolio changes through acquisitions, disposals or restructuring, boundary classifications need to be reviewed and updated to reflect the current organisational structure.
How does this connect to wider ESG governance?
Correct scope boundaries are foundational to achieving audit-ready ESG data, since every subsequent figure and disclosure depends on the underlying methodology being sound.



