GHG Boundary Coverage

Audit greenhouse-gas boundary coverage.

Description

GHG boundaries determine which emissions categories enter an inventory.

GHG boundaries determine which emissions categories enter an inventory. Coverage checks depend on a correctly specified reporting scope.^[1]

Audit greenhouse-gas boundary coverage.

When to use GHG Boundary Coverage

Use this tool to audit greenhouse-gas boundary coverage.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use GHG Boundary Coverage and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter requiredCategories, includedCategories using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredCategories	Required GHG boundary categories	list of string	Required
includedCategories	Included categories	list of string	Required

Enter requiredCategories as the nonempty expected list and includedCategories as observations, which may be empty. Trim entries, compare case-insensitively using en-US lowercase and collapse duplicates. Return matched/missing expected labels and unexpected observed labels. Output follows first occurrence order with the last duplicate’s trimmed spelling.

coverage%=100matchedUnique/expectedUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredCategories": [
      "alpha",
      "beta",
      "gamma",
      "delta"
    ],
    "includedCategories": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 50,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma",
      "delta"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No emissions, boundary appropriateness or GHG-standard compliance is verified. Blank entries are errors; requirements are entirely caller-supplied and items have equal weight.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Science-Target Readiness: Audit science-based-target assurance readiness. For a complementary task, use Audit-Universe Coverage: Audit audit-universe entity and process coverage.

References

GHG Boundary Coverage — tool.io

Similar or alternative tools

Science-Target Readiness
Audit science-based-target assurance readiness.
Audit-Universe Coverage
Audit audit-universe entity and process coverage.