UK HM Treasury Sustainability Reporting Guidance 2026-27 (FReM)
Chapter 2: greenhouse gas emissions, energy, carbon offsets, Scope 3 and value chain, renewable, sequestered and embodied carbon (paragraphs 2.1 to 2.88) – UK HM Treasury Sustainability Reporting Guidance 2026-27 (FReM)

UK HM Treasury Sustainability Reporting Guidance 2026-27 (FReM) 2.38-2.41-OFF: Carbon offsets mandatory minimum: where credits are purchased, held or retired, disclose the volume in tonnes of carbon dioxide equivalent, whether they are reductions or removals, whether removals are nature-based or technology-based, and the integrity of the credits, and buy only high-integrity credits

What does 2.38-2.41-OFF require?

Buying credits from projects that avoided or removed carbon elsewhere is offsetting. It can deal with residual emissions that are not yet technically or economically abatable, but it is rare in departments and any wider use would need cross-government agreement on value for money and environmental integrity. The priority for public bodies should be cutting their own emissions quickly; where credits are bought they should meet the high-integrity criteria set by government policy. Whenever credits have been bought, held or retired, the annual report shall state the volume bought, held and retired in the period in tonnes of carbon dioxide equivalent; the kind of credit, distinguishing reduction from removal and, for removals, nature-based projects such as woodland creation or forest restoration from technology-based ones such as direct air capture; and the integrity of the credits bought and used. Total spend on credits by category completes the disclosure.

Maintained by Gerard Blokdyk

Other controls in Chapter 2: greenhouse gas emissions, energy, carbon offsets, Scope 3 and value chain, renewable, sequestered and embodied carbon (paragraphs 2.1 to 2.88) – UK HM Treasury Sustainability Reporting Guidance 2026-27 (FReM)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.