Skip to main content
All CollectionsLCA Methods & Standards
Explained: Environmental Footprint Method
Explained: Environmental Footprint Method

Learn about the latest Environmental Footprint (EF) Method version - EF v3.1 - available in Ecochain Helix & Mobius.

Emily Lalonde avatar
Written by Emily Lalonde
Updated over a month ago

The Environmental Footprint (EF) v3.1 method, the LCIA method, is now available in Helix & Mobius!

In July 2022, the Joint Research Centre (JRC) of the European Commission released version 3.1 of the Environmental Footprint (EF) method. The new EF v3.1 method significantly updates various impact categories and integrates new characterization factors. This article answers the following questions:

  • Why use the EF v3.1 method?

  • What are the main updates in EF v3.1?

  • Is EF v3.1 integrated with EN 15804+A2?

  • What are the implications for Helix?

Feel like you're missing information? This article builds upon the following articles - check them out if you want to learn more:


Why use the EF v3.1 method?

The transition to EF v3.1 is becoming increasingly important as LCA standards and guidelines adopt this new version. The EF v3.0 characterization factors have been phased out, with a final transition period ending in August 2024. From September 1, 2024, all new EPDs for EPD International must use the EF v3.1 characterization factors. This change reflects the continuous evolution of LCA practices and the need to use the most up-to-date data for environmental impact assessments.


What are the main updates in EF v3.1?

EF v3.1 includes several important updates to characterization factors across multiple impact categories:

  1. Climate change: Updated factors to reflect the latest scientific understanding (e.g., aligned with the IPCC 2021 (AR6) report).

  2. Acidification: Revised characterization factors for more accurate impact assessment.

  3. Ecotoxicity (Freshwater): Improved representation of ecotoxic impacts on freshwater ecosystems.

  4. Photochemical Ozone Formation: Updated to reflect new data on ozone formation potential.

  5. Human Toxicity (Cancer and Non-Cancer): Improved factors distinguishing cancer and non-cancer health impacts.

These updates ensure that the EF method is aligned with current environmental science and policy needs.


Is EF v3.1 integrated with EN 15804+A2?

The EF v3.1 update is also incorporated into the EN 15804+A2 standard, which is crucial for the construction sector. This integration ensures that construction products' Environmental Product Declarations (EPDs) are based on the most current and scientifically robust data. The EN 15804+A2 standard mandates using the latest characterization factors (in this case EF v3.1), providing consistency and reliability in the environmental impact assessments of construction materials.


What are the implications for Ecochain software?

Caution - Standard database: The EF v3.1 method must be used with the ecoinvent v3.9.1 database.

Using EF v3.1 in Helix

EF v3.1 is available in Helix. If you want your LCA to comply with this method, set it as your LCA standard in the Calculation method page of Helix.

Using EF v3.1 in Mobius

If you want your LCA to comply with EF v3.1, specify this in your workspace settings in Mobius. Fill in the following:

  • Impact method sets: Environmental Footprint Method

  • Impact assessment method: EF 3.1 Method ( Ecoinvent v 3.9 Cut-Off)

  • Preferred databases: Ecoinvent v3.9


Conclusion

The EF v3.1 release is a significant step forward in environmental impact assessment, with updated characterization factors across several key impact categories. Its integration into the EN 15804+A2 standard highlights its relevance to the construction sector. As the transition period ends in September 2024, LCA practitioners and EPD developers must adopt EF v3.1 to ensure their assessments are based on the latest scientific data. For more information on the EF v3.1 method and its application, please refer to the official documentation provided by the JRC and related LCA resources.

Did this answer your question?