PCS TG 006 Landfill Methane Capture Tool Guide_v1.0

Document Control

Document identification

• Document code: PCS-TG-006

• Title: Landfill Methane Capture Tool Guide

• Scope: User guidance for applying the PCS landfill methane quantification tool (model inputs, calculation logic, monitoring data requirements, QA/QC, reporting)

• Crediting outcome: Supports emission reductions quantification under the associated methodology (tCO₂e)

Version history and change log

Table DC-1. Revision history

Version	Date	Status	Summary of changes	Prepared by	Approved by
v1.0	TBD	Draft	Release for public consultation	PCS	TBD

Superseded versions

No superseded versions for v1.0.

Governance note on versioning and archiving

Only the latest approved version of this Tool Guide shall be used for new project registrations and for verification of monitoring periods unless PCS specifies otherwise. Superseded versions shall be archived and retained for traceability, including for projects assessed under earlier versions where applicable, consistent with PCS governance rules.

Executive summary

PCS-TA-010 is the PCS calculation workbook used to quantify annual GHG emission reductions (ER_y, tCO₂e) from landfill methane capture projects under PCS-TR-001.

The tool:

• Takes baseline methane generation (CH₄_gen) and baseline oxidation (OX_bsl) as inputs.

• Converts monitored landfill gas flow and methane concentration into captured methane (tCH₄).

• Applies documented destruction efficiency (DE) and conservative treatment of downtime, missing data, fugitive emissions, and leakage.

• Produces a single auditable output: ER_y (tCO₂e) for the reporting period.

Chapter 1 - Normative language and PCS principles

1. This guide uses PCS normative wording:

• Shall / must = mandatory PCS requirement.

• Should = recommended best practice.

• May = optional.

1. PCS principles implemented in this tool:

• Conservativeness: uncertainty shall not result in over-crediting.

• Traceability: key inputs shall be supported by documentary evidence.

• Verifiability: monitoring and performance parameters shall be independently checkable.

Chapter 2 - Applicability

1. The tool shall only be used for projects that meet PCS-TR-001 Chapter 2 (Scope & Applicability) and have monitoring arrangements consistent with PCS-TR-001 Chapter 7 (Monitoring Requirements).

2. The tool supports:

• Methane destruction via open/enclosed flare or oxidation unit.

• Methane utilization via gas-to-energy (electricity/heat), where applicable.

1. The tool does not replace:

• Additionality demonstration (PCS-TR-001 Chapter 5)

• Safeguards requirements (PCS-TR-001 Chapter 9)

• Project description and monitoring report narrative requirements

Chapter 3 - Tool workbook map

1. PCS-TA-010 (v1.0) contains the following sheets:

• INSTRUCTIONS

• PROJECT_INFO

• BASELINE_INPUTS

• PROJECT_DATA

• SYSTEM_PERFORMANCE

• PROJECT_EMISSIONS

• LEAKAGE

• EMISSION_REDUCTION_SUMMARY

• QA_QC_LOG

• EVIDENCE_REFERENCE

Chapter 4 - Cross-reference matrix (PCS-TR-001 ↔ Tool sheets)

PCS-TR-001 reference	Requirement theme	Primary tool sheet(s)
Chapter 3	Project boundary definition	PROJECT_INFO + EVIDENCE_REFERENCE
Chapter 4.3 + Annex A1–A2	Baseline methane generation and baseline emissions	BASELINE_INPUTS
Chapter 6 + Annex A3–A10	Emission reduction equations	SYSTEM_PERFORMANCE, PROJECT_EMISSIONS, EMISSION_REDUCTION_SUMMARY
Chapter 7	Monitoring requirements	PROJECT_DATA, QA_QC_LOG
Chapter 8	Data/parameters and QA/QC	QA_QC_LOG, EVIDENCE_REFERENCE
Chapter 10	Uncertainty & conservativeness	PROJECT_DATA, SYSTEM_PERFORMANCE, QA_QC_LOG
Chapter 11	Leakage assessment	LEAKAGE + EVIDENCE_REFERENCE
Annex D	Documentation checklist	EVIDENCE_REFERENCE + QA_QC_LOG

Chapter 5 - Step-by-step tool use workflow

1

Read tool instructions

Sheet: INSTRUCTIONS

• Follow the workbook sequence.

• Do not overwrite formulas.

• Keep one archived copy per reporting period.

2

Enter project identifiers and boundary descriptors

Sheet: PROJECT_INFO

Enter, at minimum:

• Project name, landfill name, country/region, coordinates

• Operational status (active/closed) and included cells/areas

• Operator / entity responsible for monitoring

• Project start date and reporting period

PCS requirement: boundary descriptors shall be consistent with PCS-TR-001 Chapter 3.

3

Enter baseline methane generation and baseline oxidation

Sheet: BASELINE_INPUTS

Enter (for each year being quantified):

• Year

• CH₄ generated (CH₄_gen, tCH₄)

• Baseline oxidation fraction (OX_bsl)

Important (v1.0): CH₄_gen is entered as an input. CH₄_gen shall be derived using PCS-TR-001 Chapter 4.3.1 / Annex A1 (IPCC FOD) or another PCS-accepted approach.

Oxidation rule: OX_bsl shall be conservative and justified with evidence when deviating from defaults.

4

Enter monitoring data (flow, CH₄%, uptime, temperature)

Sheet: PROJECT_DATA

Enter monitored data per interval (row-by-row):

• Datetime / Period

• Flow (m³/h at STP)

• CH₄ concentration (%)

• Duration (h)

• Flare/engine temperature (°C), where applicable

• Device uptime (h)

• Electricity generated (MWh), if applicable

• Electricity consumed (kWh), if applicable

PCS requirement: monitoring shall follow PCS-TR-001 Chapter 7, including correction to standard conditions and documented downtime.

Conservativeness: missing/invalid monitoring data shall receive conservative treatment (no credit for capture/destruction during those periods).

5

Confirm system performance assumptions

Sheet: SYSTEM_PERFORMANCE

Enter:

• Destruction efficiency (DE) (fraction)

• Fugitive emission rate (fraction of captured CH₄), measured or conservative default

• Methane slip (if measured/required)

PCS requirement: if site testing indicates lower DE than defaults, the lower (measured) value shall be used.

6

Review project emissions components

Sheet: PROJECT_EMISSIONS

The tool calculates project emissions from:

• Uncaptured methane (as applicable)

• Fugitive methane (measured or default)

• Methane slip / combustion-related components (as applicable)

• Electricity consumption (if included)

PCS requirement: GWP_CH₄ and EF_grid inputs (where relevant) shall follow PCS rules for the applicable reporting vintage and approved public sources.

7

Assess leakage

Sheet: LEAKAGE

• Identify and quantify any leakage source (tCO₂e), with evidence.

• If leakage is zero, document the justification.

PCS requirement: leakage shall be assessed and reported per PCS-TR-001 Chapter 11.

8

Read final results

Sheet: EMISSION_REDUCTION_SUMMARY

This sheet reports:

• Baseline emissions (BE_y)

• Project emissions (PE_y)

• Leakage (LE_y)

• Electricity displacement benefit (if applicable)

• Total emission reductions (ER_y)

These outputs shall be used consistently across the Monitoring Report and any PCS submissions.

Chapter 6 - Evidence and audit trail

6.1 Evidence register

Sheet: EVIDENCE_REFERENCE

Every key input shall have an evidence reference, including:

• Reference code

• Document name/type

• Link or storage location

• Notes (page/section, parameter values)

Typical evidence includes:

• Waste deposition records / weighbridge summaries

• Waste composition / DOC basis or national studies

• Monitoring system specifications and raw logs

• Calibration certificates (flow meters, analyzers, temperature/pressure sensors)

• Flare/engine manufacturer specifications and performance tests

• Grid emission factor source (if applicable)

• Leakage justification evidence

6.2 QA/QC log

Sheet: QA_QC_LOG

Record at minimum:

• Calibration events

• Maintenance events

• Equipment failure and corrective actions

• Data gaps and conservative substitutions

Chapter 7 - Transparency and disclosure

PCS recommends that project documentation clearly describes:

• What is measured (methane captured and destroyed; energy exported if applicable).

• The key data sources used in the tool.

• Conservativeness features (downtime handling, missing data rules, defaults).

All documentation shall remain consistent with EMISSION_REDUCTION_SUMMARY.

Chapter 8 - Common issues and PCS-compliant fixes

• Optimistic baseline inputs (DOC/k/MCF assumptions not evidenced)

  • Fix: use conservative values and document sources.

• Uncorrected flow data (not at STP)

  • Fix: correct upstream and retain correction evidence.

• Ignoring downtime

  • Fix: record downtime and apply conservative no-credit periods.

• Assuming high DE without proof

  • Fix: use manufacturer spec + testing; apply lower value if measured.

• Leakage assumed zero without justification

  • Fix: document why leakage is negligible and keep evidence.

Chapter 9 - Outputs for PCS decision-making and verification

For PCS leadership review

Key decision signals include:

• Monitoring system completeness and alignment with PCS-TR-001 Chapter 7.

• Evidence support for major assumptions (baseline CH₄_gen, DE, EF_grid, leakage).

• Conservative and auditable treatment of downtime, missing data, and performance parameters.

For VVB review

Key verification checks include:

• Traceability of each key input to EVIDENCE_REFERENCE.

• Completeness of raw monitoring logs and calibration records.

• Consistency of reported ER_y with EMISSION_REDUCTION_SUMMARY.

Chapter 10 - Version control and integrity

• Users shall not modify formulas or protected calculation logic.

• Each reporting period shall archive the completed workbook, raw monitoring logs, and referenced evidence.

• If PCS publishes an updated tool version, projects shall migrate according to PCS transition guidance.