A Lower Number Is Not Yet a Lower-Carbon Decision
Environmental product declarations are structured disclosures, not universal scorecards. They report environmental results for a defined product, quantity, method, scope, location, and period. If any of those foundations differ, ranking two headline numbers can create false confidence rather than a defensible material decision.
This matters because sustainability teams rarely compare documents in isolation. An architect needs to preserve performance and design intent. A contractor needs an installable and available product. Procurement needs a commercially viable source. The owner needs credible progress toward the project target. The product with the lowest published figure may require more material, a different assembly, additional replacement, or a transport route that changes the project result.
The comparison therefore begins with the service the project needs—not with the first GWP value found in a PDF.
Disclosure is not equivalence.
Two products can each have a valid, independently verified EPD and still be unsuitable for direct comparison. Verification improves confidence that each declaration follows its stated rules; it does not make different rules, scopes, or product functions identical.
What Must Be Aligned Before EPDs Are Compared?
Use the following checks as a comparison gate. A difference does not always invalidate the analysis, but it must be understood, normalized where technically appropriate, and disclosed in the decision record.
Exact Product Identity and Intended Use
Confirm that each declaration covers the exact product, model, mix, thickness, density, finish, manufacturing facility, and application being considered. Industry-average EPDs and product-specific EPDs represent different levels of specificity.
Ask: Does this declaration represent the product the project could actually purchase?Equivalent Function and Performance
Compare products that can deliver the same required service. Fire rating, structural capacity, thermal resistance, acoustic performance, durability, maintenance, and expected service life can change the quantity or assembly needed.
Ask: Would either option meet the same requirement without compensating materials or redesign?Declared or Functional Unit
One EPD may report per kilogram, another per square metre, and another per cubic metre. Convert values to the quantity required by the project—only after establishing equivalent function.
Ask: Are the results expressed for the same project-relevant service and quantity?Lifecycle Boundary and Modules
Do not compare A1–A3 with A1–A5, or a cradle-to-gate result with a cradle-to-grave result, as if the totals describe the same scope. Keep modules visible and align only like-for-like stages.
Ask: Which modules are reported, omitted, estimated, or declared separately?PCR, Standard, and Method Version
The Product Category Rule defines how the LCA is conducted and reported. Check the governing PCR, core standard, program operator, allocation rules, impact method, and version before treating results as methodologically aligned.
Ask: Were these values produced under compatible calculation and reporting rules?Geography, Facility, and Data Period
Factory energy, raw-material sources, transport assumptions, grid mix, recycled content, production technology, and data age can materially affect results. Confirm that the information represents the proposed supply route.
Ask: Is the data representative of the facility and market serving this project?Validity, Verification, and Project Quantity
Check publication and expiry dates, verification statement, applicable standards, declared variations, exclusions, and the amount of product required. Then calculate the project quantity using an explicit conversion that another reviewer can reproduce.
Ask: Is the evidence current, verified, applicable, and correctly scaled to the project?Classify the Comparison Before Ranking the Products
Not every review should end with a simple first and second place. A transparent comparison can produce three valid outcomes.
The products deliver equivalent service, the units and lifecycle modules align, and the methods and data are sufficiently compatible for the intended decision.
Differences can be normalized or bounded, but assumptions, uncertainty, and limitations must remain attached to the conclusion.
The function, scope, quantity, methodology, or evidence differs too much. Request better data or compare at the assembly or building level instead.
“Do not rank” is not a failed sustainability review. It is a quality-control result. It prevents an attractive but unsupported number from becoming a specification, procurement commitment, or public claim.
Preserve the Reasoning, Not Just the Winning Number
The final comparison should remain understandable after design development, tender, value engineering, substitution review, and purchase. A screenshot or isolated spreadsheet total will not explain which version was used, whether the selected facility changed, or why one difference was considered acceptable.
Minimum fields for a defensible EPD comparison
Connect the product decision to the evidence and assumptions that support it.
This shared record also improves collaboration. The designer can confirm equivalence. The supplier can verify the proposed facility and configuration. The contractor can validate quantity and installation implications. The sustainability lead can evaluate the methodology. The owner can see how the decision supports the project target.
How Sustainability Teams Can Run the Test
Define the Required Service
Record the product application, performance, service life, dimensions, finish, compliance conditions, and other requirements that alternatives must preserve.
Build the Eligible Candidate Set
Remove products that cannot meet the requirement before examining carbon values. Keep technically conditional options clearly separated.
Run the Seven Checks
Review identity, function, unit, modules, methodology, representativeness, validity, verification, and project quantity for every candidate.
Normalize Transparently
Convert values only where technically justified. Preserve the original figure, formula, source, assumptions, and person responsible for the calculation.
Classify Confidence and Decide
Mark the comparison as comparable, conditional, or unsuitable for ranking. Approve the product only after cost, schedule, compliance, installation, and carbon implications are understood together.
Monitor the Selected Evidence
Recheck the record when the product, facility, quantity, EPD, PCR, design requirement, supplier, or procurement route changes.
Why Comparison Quality Is Becoming More Important
In the United States, federal work to improve PCR and EPD consistency reflects a wider market need: purchasers cannot reliably identify lower-embodied-carbon materials unless the underlying declarations are transparent, representative, and sufficiently comparable. Project teams should still apply the requirements of the relevant owner, program, specification, and procurement policy.
In Europe, the main provisions of the revised Construction Products Regulation have applied since January 8, 2026. The regulation introduces predetermined LCA-based environmental characteristics and a Digital Product Passport framework, while product families transition individually from CPR 2011 to CPR 2024. Teams may therefore encounter documents produced under different regulatory and technical routes for years. Better digital access will not remove the need to establish functional and methodological comparability.
EPD Comparison Questions
Can two EPD carbon values be compared directly?
Only when the products provide equivalent function and the declarations use compatible units, lifecycle boundaries, PCRs, methods, and representative data. A lower number alone is not enough.
What is the difference between a declared unit and a functional unit?
A declared unit expresses results for a quantity of product, such as one kilogram or cubic metre. A functional unit describes the service delivered, including relevant performance and sometimes a reference period.
Does a product-specific EPD prove that a product is low carbon?
No. It reports environmental information for a defined product and scope. A credible “lower carbon” conclusion requires a valid benchmark or comparison with functionally equivalent alternatives.
When should an EPD comparison be repeated?
Repeat or review it when the product, facility, supplier, quantity, design requirement, EPD version, PCR, transport route, or procurement decision changes.
Make Every Carbon Comparison Explainable
Sustainability teams do not need more isolated carbon numbers. They need product decisions that connect performance, evidence, quantity, methodology, uncertainty, cost, schedule, and approval. That is what allows a recommendation to survive value engineering, substitution, procurement, and final reporting.
The seven-check test turns EPD review from document collection into decision control. It helps the project select lower-carbon materials without trading away the function the building, owner, and end users still require.
From EPD library to decision-ready comparison
See how BuildBetter can support the comparison workflow described in this article
Ready to make EPD comparisons easier to review and defend?
Request access to BuildBetter and explore a more connected way to manage product identities, declarations, comparison criteria, assumptions, approvals, and the final material decision.