15 EPD mistakes that delay verification, trigger corrections, and weaken submission quality
Environmental Product Declarations rarely run into verification problems because the framework is unclear. In most cases the problem is execution — weak modelling logic, incomplete documentation, inconsistent interpretation of PCR requirements, and poor data governance.
What follows is a structured list of 15 critical mistakes that undermine EPD submissions, each with practical guidance on avoiding it before the verifier finds it for you.
Results, rules, documentation, and boundaries
Impact result tables contain errors or omissions
Submitting tables with missing indicators, incorrect values, formatting inconsistencies, or results that do not match the final LCA model raises immediate concern — the published declaration is expected to reflect the verified model exactly.
Reconcile every reported indicator against the final model export, check required indicators against the applicable PCR and EN 15804, and run a table-by-table technical check before submission.
PCR or c-PCR requirements are interpreted incorrectly
Many developers move into modelling before translating the PCR into operational modelling rules, then apply the wrong scope, declared unit, impact reporting structure, or scenario requirements.
Build a PCR conformance checklist before any modelling begins, covering scope, modules, data quality, scenarios, and reporting format. Treat the PCR as a technical instruction document, not background reading.
Background report documentation is incomplete or ambiguous
Even where the model is broadly acceptable, weak documentation creates verification friction. If assumptions, exclusions, data sources, conversion rules, and methodological choices are not clearly documented, the verifier cannot trace how results were produced.
The background report should explain the modelling logic transparently and traceably. Every major assumption needs to be explicit, justified, and tied to primary data, secondary sources, or PCR rules.
System boundaries and life cycle modules are defined incorrectly
Inaccurate treatment of A1–A3, A4–A5, B stages, C1–C4, or module D is a frequent failure point. Some submissions exclude required stages, include non-permitted ones, or describe the scope differently in different parts of the report.
Map the system boundary visually and textually before modelling. Confirm the required modules from the PCR, then align the model, background report, and EPD document so all three describe the same boundary.
Impact assessment, scenarios, and data
LCIA calculations contain mistakes, or required impact categories are missing
Using the wrong characterisation method, omitting mandatory categories, or mixing incompatible indicator sets creates a serious conformance problem. These errors usually come from reused templates or accepted software defaults.
Lock the impact assessment method at project start, check it against the PCR and programme operator requirements, and confirm every mandatory indicator appears in the final output set.
End-of-life scenarios are oversimplified or unrealistic
C1–C4 modelling becomes a weak point when developers apply generic disposal assumptions, unrealistic landfill or recycling rates, or poorly justified waste treatment routes.
Use regionally relevant waste treatment assumptions where possible, justify every end-of-life pathway, and document how the scenario choices reflect actual or representative practice for the product category.
Data sources, database versions, and data quality are not reported properly
Unclear data lineage is one of the most frequently flagged issues. Developers fail to distinguish primary from secondary data, omit database version information, or provide no meaningful data quality discussion.
Declare every database and version used, identify which data are primary and which secondary, and include a structured data quality assessment covering representativeness, completeness, consistency, and temporal relevance.
Electricity mix selection and energy modelling are incorrect
Electricity is usually a high-influence input. The wrong grid mix, non-representative datasets, or inconsistent electricity assumptions across processes can materially distort results.
Use location-specific electricity data aligned with the manufacturing context and the PCR. Apply the same logic consistently across the model and state clearly whether the energy source is measured, contracted, or generic.
Life cycle scenarios and technical assumptions are poorly justified
Assumptions on service life, maintenance, replacement, installation losses, or use-stage behaviour are often inserted casually. Weak or unverifiable assumptions leave the whole submission exposed.
Base technical assumptions on product documentation, engineering input, industry references, or client records. Avoid placeholders, and check that every scenario in the model can be defended during verification.
Transport, units, allocation, and internal consistency
Transport distances, modes, and fuel assumptions are modelled poorly
A2 and A4 are frequently underestimated or generalized — arbitrary distances, unrealistic logistics chains, or inappropriate vehicle datasets weaken both result quality and credibility.
Use actual logistics data wherever possible. Where estimates are necessary, document the basis clearly: transport mode, load assumptions, backhaul treatment, and fuel or emission factors.
The functional or declared unit is inconsistent across the submission
The unit used in the model, described in the report, and displayed in the EPD table do not always match. Even small inconsistencies invalidate interpretation and comparability.
Define the declared or functional unit at project start and lock it across the model, report text, calculation sheets, and final EPD layout. Review every unit reference before submission.
Allocation rules are applied incorrectly in multi-output systems
Allocation remains one of the more technically sensitive issues in LCA and EPD work. Problems arise when co-products, scrap flows, recycled inputs, or shared utilities are divided using weak or unjustified methods.
Follow the hierarchy in ISO 14044 and the PCR. Where allocation is unavoidable, justify the chosen basis clearly and show the rule is applied consistently across the whole model.
Cut-off criteria are applied inconsistently or without evidence
Some developers exclude flows too aggressively; others state cut-off criteria in the report but never apply them systematically in the model. Either way, stated methodology and actual execution diverge.
Define cut-off rules before modelling, apply them consistently, and document which flows were excluded and why. Avoid vague statements such as “minor inputs were neglected” with no technical justification.
The LCA model and the final EPD report do not fully match
A common operational failure. During editing, revisions are made to the model or the report but not both, leaving inconsistencies in numbers, assumptions, modules, or text between the technical files and the submission package.
Run a full model-to-report reconciliation as the final quality control step. One responsible reviewer should confirm the model, background report, EPD layout, and annexes all reflect the same final version.
No independent pre-submission review is carried out
Many developers submit straight to verification without independent technical review — which means structural errors, documentation gaps, inconsistent assumptions, and reporting weaknesses are first found by the verifier rather than resolved internally.
Build a formal pre-submission review step into the process. Independent technical review before verification identifies methodological weaknesses, improves submission quality, reduces revision cycles, and protects credibility.
EPD services
End-to-end Environmental Product Declaration development aligned with ISO and EN standards.
Explore service →EPD pre-submission audit
Independent technical review to confirm your EPD is review-ready before submission.
Explore service →EPD training programs
Professional training to build internal capability in EPD development and LCA workflows.
Explore training →EPD data framework
Structured data collection system covering A1–D modules for review-ready workflows.
Explore framework →Request a quotation
Get a tailored quotation aligned with your EPD scope and timeline.
Request a quotation →
