Questions for your situation
Can the closest-sounding PCR be used if no suitable one exists?
Match rule scope with product function and programme conditions. A similar title does not justify an out-of-scope PCR. Discuss development or acceptance options with the programme operator where needed. Include this work in timing and cost before the lifecycle study begins.
Can one EPD cover every product from several factories?
Review programme and PCR grouping, averaging and representation conditions. Differences in energy, materials and technologies may affect results. Identify which products and facilities are represented by which data. Copying one factory's figures elsewhere without justification does not establish verified coverage.
Can carbon figures from two EPDs be compared directly?
Check units, function, PCRs, modules, periods and scenarios together. Totals covering different lifecycle stages may not be equivalent. Justify the comparison before claiming superiority from one indicator. Do not disregard other environmental indicators significant to the product.
Is an EPD considered published once the LCA report is complete?
LCA is a core input; the declaration format, programme verification and registration or publication remain separate stages. Check verifier authority within the programme. A number on a draft does not create published status. Material sent to customers should state its actual stage and open technical findings.
Can an EPD remain unchanged until expiry after formulation and energy-source changes?
Expiry alone does not eliminate update needs. Assess effects on results and scope under programme rules. Prepare new data, calculation versions and verification where necessary. Keep clear which declaration represents the earlier and changed production.
Who should act when an error is found in a published EPD?
Identify duties of the owner, preparer, verifier and programme operator. Calculate effects and complete necessary correction, review or publication-status actions. Explain changes to customers using the earlier declaration. Quietly replacing a file is not adequate version control.