How · Yours
How to use EC3 without treating every EPD as directly comparable
EC3 makes Environmental Product Declaration data searchable and useful for embodied-carbon decisions, but its own 2026 data account explains why EPD structures and indicators can differ. Comparison needs aligned product category, functional unit, life-cycle scope, geography and indicator definitions.

EC3 turns disclosure documents into decision data
Building Transparency describes EC3 as a free, open-access embodied-carbon accounting tool. It combines building material quantities with a digital database of third-party Environmental Product Declarations.
That structure supports two related tasks: comparing material options during specification and estimating potential or realised project embodied carbon. The result remains dependent on the project quantities and the scope of the underlying declarations.
Documented development: public launch and open scaling
Building Transparency records that EC3 launched publicly in 2019 through the Carbon Leadership Forum and more than fifty industry partners. The nonprofit Building Transparency was formed in 2020 to manage and scale the tool.
The history matters because EC3 is not a static product catalogue. Its value comes from data ingestion, validation, alignment and ongoing curation across many programme operators.
Present position: compliant EPDs can still use different data structures
In February 2026, Building Transparency explained that EPDs were usually written as standalone documents rather than database records. Programme operators may report global-warming-potential indicators differently—even when their declarations comply with the relevant standard.
EC3’s curation makes comparison more practical, but it does not erase category, unit, module, geography or methodological differences. The original EPD should remain available for the final technical decision.
- Compare like product categories and functions
- Match declared or functional units
- Check life-cycle modules and indicator definitions
- Review geography, production site and validity dates
- Carry the selected EPD into project documentation
The opportunity is better procurement, not an automatic winner
EC3 can move embodied carbon into early specification and procurement, where alternatives can still be considered. It can also help teams document potential and as-built project emissions.
Eight June’s interpretation is that the tool is strongest as a disciplined comparison environment. A lower displayed number is not automatically the best product once durability, maintenance, transport, code compliance, replacement and full project performance are included.
Before you decide
Keep these five things with you.
- 01Define the material function first
- 02Align category, unit and life-cycle modules
- 03Open the original EPD
- 04Check geography and validity
- 05Include durability and project performance
How this story earns trust
Sources, method and relationship—visible.
Each reference is tagged by the geography and authority of the source. Country-specific evidence is never presented as a global rule.
Method
This Yours article uses Building Transparency’s EC3 tool description, EPD guidance, launch history and February 2026 account of database curation. It is general editorial information, not life-cycle assessment or specification advice.
Commercial relationship
Independent editorial. Building Transparency, programme operators and manufacturers did not pay for inclusion. EC3 results are not Eight June product recommendations.
Correction or improvement
Found a mistake, a missing perspective or a source we should review? Send it to the editorial desk ↗
- 01The EC3 Tool ↗
Building Transparency. Current tool purpose, EPD database and project-comparison functions.
- 02How to Get an EPD ↗
Building Transparency. Third-party EPD database and service-provider context.
- 03Behind the Data: What It Takes to Keep Up EC3’s EPD Database ↗
Building Transparency. February 2026 explanation of ingestion, validation, alignment and comparability challenges.
- 04Five Years of EC3 ↗
Building Transparency. Public-launch and organisational history.
Useful questions
Quick answers,
kept specific.
Does an EPD certify that a product is low carbon?
No. An EPD discloses environmental information under a defined method and scope; comparison and project context still matter.
Can every EPD number be compared directly in EC3?
No. Product category, unit, modules, geography, dates and indicator definitions need alignment.
What should be retained after choosing a material?
Keep the original EPD, the comparison assumptions and the project quantity and performance context.