Why EF 3.1 matters
EF 3.1 exists to stop companies comparing environmental results that were never comparable. Before a harmonised method, two LCAs of the same product could reach very different numbers simply because they used different impact models or datasets. EF 3.1 fixes the method, the categories, and the characterisation factors, which creates a level playing field. That is exactly why the EU has built it into regulation.
For anyone producing a regulated footprint, EF 3.1 is not optional. If your LCA is not EF 3.1-aligned, it will not satisfy EU Battery Regulation carbon footprint requirements or current EPD programmes.
What EF 3.1 actually covers
EF 3.1 is a life cycle impact assessment method built on a cradle-to-grave perspective. It assesses impact across a defined set of categories, 16 in total, that go well beyond climate change to include acidification, eutrophication, freshwater ecotoxicity, resource depletion, and water use. The climate change category uses the IPCC's latest characterisation factors (AR6 / 2021), which is one of the key reasons EF 3.1 is considered current best practice.
A common misunderstanding: EF is not a replacement for LCA. It is the methodology for doing the LCA. An EPD, in turn, is a declaration based on the results of an LCA performed using the EF method.
EF 3.1 versus EF 3.0
EF 3.1 is an update, not a new framework. It revised characterisation factors across several categories, most notably aligning climate change with IPCC AR6 and improving the representation of ecotoxicity and acidification. The transition period from EF 3.0 ended in 2024. Since then, new EPDs under major programmes and new regulated footprints have been expected to use EF 3.1 factors. Working from an older version risks producing results that no longer comply.
EF 3.1 and the EU Battery Regulation
The carbon footprint methodology for batteries is built on the PEF method and its category rules, which sit on EF. For a battery manufacturer, this means the carbon footprint declaration that feeds your carbon performance class has to be calculated within an EF-aligned model, using appropriate background datasets and documented data quality. Getting the method right is a precondition for a defensible declaration.
Minviro's LCAs are built to EF 3.1 and ISO 14040/14044/14067, with independent critical review. See how Minviro's methodology supports regulated footprints →
Why EF 3.1 matters
EF 3.1 exists to stop companies comparing environmental results that were never comparable. Before a harmonised method, two LCAs of the same product could reach very different numbers simply because they used different impact models or datasets. EF 3.1 fixes the method, the categories, and the characterisation factors, which creates a level playing field. That is exactly why the EU has built it into regulation.
For anyone producing a regulated footprint, EF 3.1 is not optional. If your LCA is not EF 3.1-aligned, it will not satisfy EU Battery Regulation carbon footprint requirements or current EPD programmes.
What EF 3.1 actually covers
EF 3.1 is a life cycle impact assessment method built on a cradle-to-grave perspective. It assesses impact across a defined set of categories, 16 in total, that go well beyond climate change to include acidification, eutrophication, freshwater ecotoxicity, resource depletion, and water use. The climate change category uses the IPCC's latest characterisation factors (AR6 / 2021), which is one of the key reasons EF 3.1 is considered current best practice.
A common misunderstanding: EF is not a replacement for LCA. It is the methodology for doing the LCA. An EPD, in turn, is a declaration based on the results of an LCA performed using the EF method.
EF 3.1 versus EF 3.0
EF 3.1 is an update, not a new framework. It revised characterisation factors across several categories, most notably aligning climate change with IPCC AR6 and improving the representation of ecotoxicity and acidification. The transition period from EF 3.0 ended in 2024. Since then, new EPDs under major programmes and new regulated footprints have been expected to use EF 3.1 factors. Working from an older version risks producing results that no longer comply.
EF 3.1 and the EU Battery Regulation
The carbon footprint methodology for batteries is built on the PEF method and its category rules, which sit on EF. For a battery manufacturer, this means the carbon footprint declaration that feeds your carbon performance class has to be calculated within an EF-aligned model, using appropriate background datasets and documented data quality. Getting the method right is a precondition for a defensible declaration.
Minviro's LCAs are built to EF 3.1 and ISO 14040/14044/14067, with independent critical review. See how Minviro's methodology supports regulated footprints →
Why EF 3.1 matters
EF 3.1 exists to stop companies comparing environmental results that were never comparable. Before a harmonised method, two LCAs of the same product could reach very different numbers simply because they used different impact models or datasets. EF 3.1 fixes the method, the categories, and the characterisation factors, which creates a level playing field. That is exactly why the EU has built it into regulation.
For anyone producing a regulated footprint, EF 3.1 is not optional. If your LCA is not EF 3.1-aligned, it will not satisfy EU Battery Regulation carbon footprint requirements or current EPD programmes.
What EF 3.1 actually covers
EF 3.1 is a life cycle impact assessment method built on a cradle-to-grave perspective. It assesses impact across a defined set of categories, 16 in total, that go well beyond climate change to include acidification, eutrophication, freshwater ecotoxicity, resource depletion, and water use. The climate change category uses the IPCC's latest characterisation factors (AR6 / 2021), which is one of the key reasons EF 3.1 is considered current best practice.
A common misunderstanding: EF is not a replacement for LCA. It is the methodology for doing the LCA. An EPD, in turn, is a declaration based on the results of an LCA performed using the EF method.
EF 3.1 versus EF 3.0
EF 3.1 is an update, not a new framework. It revised characterisation factors across several categories, most notably aligning climate change with IPCC AR6 and improving the representation of ecotoxicity and acidification. The transition period from EF 3.0 ended in 2024. Since then, new EPDs under major programmes and new regulated footprints have been expected to use EF 3.1 factors. Working from an older version risks producing results that no longer comply.
EF 3.1 and the EU Battery Regulation
The carbon footprint methodology for batteries is built on the PEF method and its category rules, which sit on EF. For a battery manufacturer, this means the carbon footprint declaration that feeds your carbon performance class has to be calculated within an EF-aligned model, using appropriate background datasets and documented data quality. Getting the method right is a precondition for a defensible declaration.
Minviro's LCAs are built to EF 3.1 and ISO 14040/14044/14067, with independent critical review. See how Minviro's methodology supports regulated footprints →