CCUS monitoring compliance and leakage incidents
Measurement answer
What this metric measures
Reports CCUS monitoring-plan compliance across sites and injection facilities, together with detected leakage events or significant irregularities and their site-level incidence.
Specification
Metric specification
- Result format
- Structured table
- Unit
- Structured table — see field-level units
- Reporting basis
- Reporting period
- Aggregation
- Report the number and proportion of CCUS sites and injection facilities operating under compliant monitoring and verification plans, and the number of detected leakage events or significant irregularities per site.
- Pillar
- Environmental
- Topic
- Carbon capture, utilization and storage
- Controlled domain
- Climate and greenhouse gases
- Entity type
- Metric
Reporting boundary
CCUS sites and injection facilities operated by, or within the reporting boundary of, the organization during the reporting period.
Verified source occurrences
Framework coverage
This is one canonical metric. The bindings below show every verified framework occurrence without creating duplicate metric pages. Edition, disclosure, role, and relationship remain source-specific.
- Adopting DisclosureSource evidence
TNFD sector guidance
- Publisher
- Taskforce on Nature-related Financial Disclosures
- Edition
- Final English sector guidance collection through August 2026 (17 documents)
- Requirement
- Not Specified
- Relationship
- Defines Disclosure
- Mapping outcome
- Direct Evidence
- Source locator
- page 116, Table AF.C23.3
- Adopting DisclosureAF.C23.3
TNFD sector guidance
- Publisher
- Taskforce on Nature-related Financial Disclosures
- Edition
- Version 1.0, June 2026
- Requirement
- Conditional
- Relationship
- Maps Source Identity
- Mapping outcome
- Published
- Source locator
- page 116, Table AF.C23.3
Value structure
Dimensions and units
- Unit
- Structured table — see field-level units
- Reporting basis
- Reporting period
Unit meaning: Each field uses its stated unit and retains the applicable sector, reporting boundary, period and method.
Table fields and units
- CCUS sites and injection facilities in scope
- Sites and injection facilities operating under compliant monitoring and verification plans
- Proportion of sites and injection facilities operating under compliant monitoring and verification plans
- Detected leakage events or significant irregularities
- Detected leakage events or significant irregularities per site
Published dimensions
- facility type (CCUS site or injection facility)
- monitoring and verification plan compliance status
- incident type (detected leakage event or significant irregularity)
- site or facility identifier
Disclosure method
Formula information
- Status
- Not applicable
- Formula type
- Structured Disclosure
Disclosure form
No single formulaReport the source-defined result with its stated fields and method disclosures. The source specifies reportable outputs rather than merely a calculation input or contextual statement: counts and proportions of facilities operating under compliant monitoring and verification plans, plus detected leakage events or significant irregularities per site. These outcomes require a structured table because they use distinct field-level units and facility-level dimensions. None of the shortlisted existing metrics has the same CCUS monitoring-compliance and leakage-incident construct, boundary or value shape.
Verified sources
Evidence and status sources
Sustopedia checked each record-specific claim directly against primary publisher material. Labels distinguish current measurement authority from future compatibility and corroborative, legal, edition, or method status context. Corroborative evidence can support a stated limitation but cannot establish the core measurement by itself.
Measurement evidence
- Measurement evidenceChecked 30 August 2026
TNFD additional sector guidance collection
- Publisher
- Taskforce on Nature-related Financial Disclosures
- Edition
- Final English sector guidance collection through August 2026 (17 documents)
- Locator
- page 116, Table AF.C23.3
Supports: The official TNFD sector guidance supports the identity, boundary and method basis of “CCUS monitoring compliance and leakage incidents”.
Open official source
Use with context
Interpretation boundaries
Method disclosures required
Source-edition basis: TNFD sector guidance, Final English sector guidance collection through August 2026 (17 documents).
- Define the CCUS sites and injection facilities included in the reporting boundary and identify whether operated, owned, controlled or otherwise attributable facilities are included.
- Disclose the monitoring and verification plan compliance criteria, including the governing regulatory, permit, contractual or internal standard.
- Disclose the method for identifying, classifying and counting detected leakage events and significant irregularities, including detection thresholds and materiality criteria.
- Disclose the denominator used for the proportion of compliant sites or facilities and the method used to calculate or present incidents per site.
- Disclose the reporting-period coverage, any facilities entering or leaving the boundary, and material data gaps or estimation methods.
Record-specific limitations
- The metric does not establish a universal definition of compliant monitoring and verification plans; the reporting organization must disclose the applicable plan, standard, permit or regulatory basis.
- Incident counts may not be comparable where detection thresholds, monitoring coverage, incident-materiality criteria or reporting requirements differ across sites or jurisdictions.
- The source describes incidents per site; organizations should not aggregate site-level incident rates without disclosing the aggregation method.
Interpret this metric with the stated reporting boundary, period convention, value shape, and unit. Results prepared with different boundaries or conventions may not be directly comparable.
Measurement evidence supports the core record-specific claims described above. Corroborative evidence can support limitations, while compatibility and status sources provide their separately labelled context. None of these cards by itself determines an organisation's legal applicability, filing readiness, assurance status, or compliance conclusion.