In brief: An Environmental Product Declaration presents quantified life-cycle information under defined rules. It is not a general certificate that a product is environmentally superior. Compare EPD results only when function, units, rules and boundaries are sufficiently consistent.
EPDs can improve procurement evidence, but their tables are easy to misuse. A low number in one module may not represent the complete product life cycle, and two declarations may use different assumptions. Procurement teams need a structured reading method before transferring EPD figures into project assessments.
Confirm product identity and validity
Check the manufacturer, product, plant or geography, declaration programme, publication and expiry dates, verifier and referenced product category rules. Ensure the supplied product actually falls within the declaration scope.
Understand the declared or functional unit
Results may be stated per kilogram, cubic metre, square metre or a functional performance. Convert quantities carefully and consider density, strength, thermal performance or service life. A mass-based comparison can be misleading if products perform different functions.
Read lifecycle modules and scenarios
Identify which production, transport, construction, use and end-of-life modules are declared. Review scenario assumptions and whether modules are mandatory, optional or not declared. Do not treat missing modules as zero impact.
Place the EPD in the project model
Use actual quantities, transport, waste, maintenance and replacement assumptions where relevant. Keep the original declaration and record conversions. EPD data supports assessment; it does not replace project-specific design judgement.
A practical implementation sequence
Create an EPD review sheet used consistently by design and procurement teams. Reject comparisons where functional equivalence or boundaries cannot be established, and document when generic data remains more appropriate.
- Verify product, programme, date and product category rules.
- Check declared unit and functional equivalence.
- Map all declared and omitted life-cycle modules.
- Review geography, data age and scenario assumptions.
- Record conversions and project-specific quantities.
For every step, retain the owner, source, reporting period, method, version, reviewer and known limitations. Estimates can be useful during transition, but they should never be presented as measured data.
Decision risks to control
- Treating an EPD as a green product certification.
- Comparing one headline number across different modules.
- Assuming a module not declared has zero impact.
Retain the EPD file, review sheet, validity check, quantity conversion, project assumptions, comparison decision and procurement record. Version control matters when declarations are renewed or products change.
Frequently asked questions
Does an EPD prove that a product is low carbon?
No. It reports information under defined rules. Superiority requires a valid comparison using equivalent function and boundaries.
Can EPD values be compared directly?
Only when product category rules, units, functions, boundaries and scenarios are sufficiently aligned.
What does MND mean?
It generally means a module is not declared, not that the environmental impact is zero.
What if no product-specific EPD exists?
Use an approved generic or industry data source transparently and record the plan for improving evidence if the item is material.
Authoritative sources
- ISO 21930:2017 Environmental Product Declarations for Construction Products
- CIC Carbon Assessment Tool
- Hong Kong Green Building Council BEAM Plus Introduction
This article is for general information and education only. It is not legal, investment, financial, assurance, certification, compliance or other professional advice.