Skip to main content

EPD Lifecycle

This page describes the end-to-end lifecycle of an EPD on Smart EPD, from initial draft through third-party verification to publication and beyond.

Overview​

Every EPD follows a structured path through six phases:

Phase 1: Project setup​

Before an EPD can be created, the workspace, Category, and project must be configured. See Onboarding & Setup for the full walkthrough.

Phase 2: Author the EPD​

With the project in place, the manufacturer (or consultant) creates and fills the EPD:

  1. Create a draft EPD -Choose the EPD type based on the Category mode:

    • Standard EPD -For manual Categories or standalone assessments
    • Reference EPD -For tool-based Categories. Linked to an EPD Template with locked fields and validation constraints
    • Variant EPD -Derived from an approved reference EPD with different product parameters

  2. Fill sections -Enter data for each EPD section: general information, product description, system boundary, LCA methodology, environmental impact results, and more.

  3. Upload LCA documentation -Attach the LCA methodology report, background data documentation, and supporting files.

Converting to a Reference EPD​

A standard draft EPD can be converted ("morphed") to a reference EPD. This links it to an EPD Template from the project's specification chain, locking certain fields and enabling variant EPD production after verification.

note

Only one reference EPD is allowed per project. Converting to reference is a one-way operation.

Phase 3: Submit for verification​

When the EPD and LCA documentation are ready, the manufacturer bundles them into a submittal package: a structured collection of items that the verifier will review as a unit.

A submittal package can contain:

Item typeDescription
LCAThe project's LCA documentation
Standard EPDIndividual EPDs for manual review
Reference EPDEPD linked to the tool/template for tool verification
Variant EPDsProduction EPDs derived from an approved reference

Once all items are added, submitting the package locks it: no further edits until the verifier returns feedback.

Phase 4: Verification review​

A verifier is assigned to the package, and the review begins. The verifier works through each item independently, examining every section.

For each EPD section, the verifier:

  • Evaluates conformance -marks each section as conformant, opportunity for improvement (OFI), or non-conformant
  • Adds comments — creates discussion threads on specific findings. The EPD author can reply to comments, enabling back-and-forth dialogue between verifier and manufacturer to resolve findings without leaving the platform.
  • Uses AI hints — optionally reviews AI-generated conformance suggestions with confidence levels
  • Fills the checklist — records compliance status for each requirement in the specification (Yes / No / OFI / N/A)

If the verifier finds issues:

  • Flag -Marks the item for attention while continuing the review
  • Request revision -Returns the item to the manufacturer for corrections. The manufacturer revises and resubmits.

For more detail on the verifier's process, see Verification Workflow.

Phase 5: Approval gates​

Items within a submittal package must be approved in a specific dependency order:

  • The LCA must be approved before any EPDs can be approved
  • The Reference EPD must be approved before variant EPDs can be approved
  • Once all items are approved, the submittal package itself can be approved

These gates ensure that foundational documentation is verified before dependent deliverables are signed off.

Package-level actions​

If the verifier wants to return the entire package (not just individual items):

  • Return for feedback -Unlocks the package so the manufacturer can make revisions
  • Reject -Permanently closes the package (rare; typically feedback is preferred)
  • The manufacturer can create a new revision of the package, which copies all items with review status reset

Phase 6: Publish​

After the submittal package is approved, an admin publishes the EPD. Publication:

  • Assigns an auto-generated reference number (e.g., Smart EPD-2025-001-0001-01)
  • Sets the date of issue and a 5-year validity period
  • Snapshots the PCR and template settings at the time of publication
  • Makes the EPD visible in the public EPD library

Republishing (post-publication updates)​

After an EPD is published, any changes require a republishing workflow:

Republishing preserves the same EPD reference number and creates a version lineage chain, so the full history of changes is traceable.