What Is LCA and How It Powers Better Product Passports

Monday's product meeting starts with a familiar problem. A textile brand has a new sneaker line, an ESPR deadline approaching, a buyer asking for verified carbon figures, legal warning about greenwashing, and marketing requesting one clean sentence for the launch. On the table sits a stack of PEFCR files, while the team realizes that nobody has commissioned an LCA before.

The pressure isn't only about calculating a footprint. The team needs evidence that can survive internal review, supplier questions, public scrutiny, and eventually a Digital Product Passport. The result must show what was measured, which assumptions were used, how the model can be updated, and where every published figure came from.

This guide follows that work from the first definition to a passport-ready evidence record. You'll see how LCA works under ISO 14040 and ISO 14044, why two assessments can disagree, how to choose a system boundary, and how to connect approved results with DPP fields without turning a complex study into an unsupported marketing claim.

• A Product Team's First Encounter With LCA
• What LCA Really Means Beyond the Acronym
• LCA is broader than a carbon footprint
• The Four Phases of an ISO 14040 Study
• Goal and scope definition
• Life cycle inventory analysis
• Life cycle impact assessment
• Interpretation
• Why Two LCAs for the Same Product Disagree
• The main variance drivers
• Choosing the Right System Boundary for Your Product
• Cradle to gate
• Cradle to grave
• Cradle to cradle
• Plugging LCA Results Into a Digital Product Passport
• Three views of the same evidence
• Required data versus useful context
• How to Run or Commission an LCA in Practice
• Set the study up
• Control the gaps
• Putting It Together for ESPR and DPP Readiness

The sustainability lead begins by asking a simple question: “What exactly are we assessing?” The answer determines almost everything that follows. Is the team studying one sneaker model, the entire line, or a representative product? Will the assessment stop at the factory gate, or include transport, consumer use, and disposal? Which environmental indicators will the buyer need?

The product manager initially wants one carbon number. Legal asks for the methodology behind it. Procurement needs suppliers to provide material, energy, and process information. Marketing wants a concise claim, but the LCA practitioner knows that a concise claim is only credible when its boundary, functional unit, data sources, and review status are clear.

A useful starting point is to treat the study as an evidence project rather than a calculator exercise. The team needs to assemble:

• Product definition: The exact model, materials, components, packaging, and production configuration.
• Purpose: The decision the LCA must support, such as design comparison, procurement, compliance, or public communication.
• Supplier evidence: Process data, energy information, material specifications, transport details, and relevant end-of-life assumptions.
• Methodology record: Boundary, allocation rules, database versions, impact method, assumptions, exclusions, and data-quality requirements.
• Review package: Calculations, interpretation, limitations, and any critical review statement required for external publication.

Practical rule: If the team can't explain what the number represents in one careful sentence, it isn't ready to publish the number.

The project will hit several checkpoints. First comes the definition of LCA and the difference between a product footprint and a broader corporate inventory. Then come the four ISO phases, the reconciliation of conflicting results, and the choice between cradle-to-gate, cradle-to-grave, and cradle-to-cradle. Finally, the team must map the approved study into a DPP, preserve its audit trail, and establish a commissioning workflow that can be repeated for future products.

A product team may begin with a simple question: which material has the lower environmental impact? Life Cycle Assessment, or LCA, is a structured method for evaluating the environmental aspects and potential impacts of a product, material, service, or process across its life cycle. It turns that question into documented evidence that can support design decisions, purchasing, compliance, and product information that regulators, retailers, and consumers can assess.

An LCA works like a set of receipts for nature. Raw materials, electricity, fuels, water, transport, emissions, wastewater, and discarded materials become traceable entries. The practitioner connects those entries to the product system, then translates them into impact categories using a stated method. The result is a model, not a single universal score.

The life-cycle view follows the product through relevant stages, from raw material acquisition through production, use, end-of-life treatment, recycling, and final disposal. That cradle-to-grave logic has roots in a 1969 Coca-Cola-commissioned packaging study, which compared beverage containers by quantifying raw materials, fuels, and environmental loadings across their life cycle, as documented in the history of LCA.

!A diagram illustrating the Life Cycle Assessment (LCA) process, including inputs, product system stages, outputs, and impact categories.

A carbon footprint focuses on climate change impacts, usually through greenhouse-gas results. An LCA may also examine water use, resource use, toxicity, eutrophication, land-related effects, and other categories selected for the study. The chosen categories depend on the goal, scope, available data, and impact-assessment method.

An EPD, or Environmental Product Declaration, isn't the same thing as an LCA. An EPD is a standardized communication format built from an underlying assessment and applicable rules. An internal carbon-accounting exercise generally focuses on an organization's emissions, while an LCA models the environmental profile of a particular product system.

The technical foundation comes from ISO 14040:2006 and ISO 14044:2006. ISO published both standards in July 2006, superseding four earlier standards and consolidating the framework into two internationally recognized documents, as described by ISO's standard record. Together, they organize work around goal and scope definition, inventory analysis, impact assessment, and interpretation.

That structure gives LCA its practical value. A claim such as “eco-friendly sneaker” provides little evidence. A documented LCA lets qualified reviewers examine what was measured, which assumptions shaped the result, and whether the conclusion follows from the evidence. Those records also provide the foundation for transferring approved results into a Digital Product Passport without turning a complex study into an unsupported label.

An ISO LCA develops through repeated checks. A product team may revise the scope after learning that supplier data is unavailable, update the inventory after receiving a clarification, or revisit the conclusion when sensitivity testing shows that an assumption affects the result. The four phases provide the structure, while iteration keeps the study connected to evidence.

Use a cotton T-shirt to follow the process from definition to a result that can support a Digital Product Passport.

The first phase sets the study's purpose and intended use. The team may be comparing fabric options, preparing a customer disclosure, guiding design decisions, or producing evidence for a passport. These purposes affect what the model must represent and how its results may later be communicated.

The functional unit makes the comparison fair. “A T-shirt” describes an object, not the service it provides. A clearer functional unit could be one T-shirt used over a specified service scenario, such as a garment worn for two years. The team then records related assumptions, including care and replacement behavior when those factors fall within the study's scope.

The scope also defines the product system, geographical and temporal coverage, cut-off rules, allocation approach, and system boundary. A factory-gate study does not include consumer washing or disposal by default. A study that includes those stages must explain how they are represented. These decisions become important evidence when LCA outputs are transferred into a DPP, because a passport user needs to know what the result covers.

Inventory analysis collects the inputs and outputs associated with the functional unit. For the T-shirt, the team might request information on cotton cultivation, yarn spinning, dyeing, cut-and-sew operations, packaging, transport, retail, consumer care, and end of life.

The inventory is more than a quantity spreadsheet. Every value needs context: its source, unit, geography, time period, technology, uncertainty, and any substitution or allocation rule. A dataset without that context may look precise while representing a different process or condition. Traceable records and reviewable metadata help analysts identify whether datasets can be combined and whether a result is suitable for external reporting.

!A diagram illustrating the four phases of an ISO 14040 Life Cycle Assessment study for a t-shirt.

The inventory lists flows such as electricity, fuels, water, emissions, and waste. Impact assessment converts those flows into selected environmental impact categories through a defined method. The team might choose EF 3.1 or ReCiPe, depending on the study's purpose, applicable rules, geography, and reporting requirements.

Method selection affects the meaning of the result. Different methods organize and characterize environmental mechanisms in different ways, so the team records the method and version beside the result. A published score without that information is difficult for a retailer, regulator, or consumer to interpret.

The calculation path is:

1. Collect flows associated with the product system.
2. Classify flows into relevant impact categories.
3. Characterize flows using the selected impact method.
4. Review category results for hotspots, uncertainty, and trade-offs.

Interpretation checks whether the study is complete, consistent, sensitive to important assumptions, and suitable for its intended use. Dyeing may dominate one impact category, while consumer care or material production may drive another. The team should examine these patterns rather than rely on a single headline score.

Conclusions should separate strong findings, conditional findings, and unresolved data gaps. ISO 14044 makes the process structured and reviewable, helping an organization show how it reached a conclusion. That documented chain from scope to inventory to interpretation is what allows approved LCA outputs to support a DPP without turning a complex assessment into an unsupported label.

Two LCAs can assess the same product and produce different results without either practitioner making a mathematical mistake. The disagreement often comes from choices made before the calculation starts.

Consider two studies of a T-shirt. One models a garment worn through a shorter care scenario. The other models a longer service life with more washing. Even if the fabric and factory data match, the functional unit changes the amount of service the result represents.

The same issue appears in the system boundary. One assessment may include raw material extraction, distribution, use, and end of life. Another may stop at finished production. Comparing the headline results without comparing boundaries is like comparing two travel budgets when one includes the return journey and the other doesn't.

Allocation rules matter when a process creates multiple products or co-products. The practitioner must decide how shared inputs and emissions are assigned. Different defensible rules can produce different product results, especially when the process is complex.

Data quality compounds these choices. Supplier-specific electricity, generic industry data, regional production data, and different time periods can all change the model. Electricity grid mix is particularly important when manufacturing energy contributes materially to the result.

The review of LCA challenges and research needs identifies gaps across inventory, impact assessment, and evolving methodology. That supports a practical conclusion: “the LCA number” is incomplete without the model context.

Before publishing: Ask for the functional unit, boundary, allocation rules, data sources, electricity assumptions, impact method, version, and review status.

Critical review doesn't make every LCA identical. It makes the study's choices visible and tests whether the method fits the stated purpose. For public claims, conformance with ISO 14040 and ISO 14044, along with a clear review record, gives buyers and regulators a basis for comparing like with like.

The right boundary depends on the decision the product team needs to make. A supplier selling a material to a manufacturer may need a factory-gate result. A consumer-facing brand making a whole-product claim needs a broader view.

Cradle-to-gate covers raw material extraction and processing through manufacturing up to the finished product leaving the factory. It answers, “What is the impact up to our factory door?”

This boundary can work well for B2B disclosure, material procurement, and background datasets that another organization will combine with downstream information. It's also useful when the customer controls transport, use, or end-of-life conditions. The limitation is obvious: it doesn't describe the product's full life.

The team must document whether inbound transport, packaging, manufacturing waste, and auxiliary materials are included. Excluding downstream stages isn't a flaw when the scope is intentional. Presenting the result as a full product footprint would be misleading.

Cradle-to-grave follows the product from raw materials through manufacturing, distribution, use, and end-of-life disposal or treatment. It answers, “What environmental impact does the customer's product system create across its modeled life?”

This scope is appropriate when consumer behavior, care, durability, transport, and disposal can materially influence the result. The team needs evidence or justified scenarios for those stages. Generic disposal assumptions can be useful for screening, but they should remain visible in the study and passport record.

For teams connecting supplier information with broader value-chain reporting, the Scope 3 Category 1 guidance can help clarify how purchased goods data relates to product evidence.

Cradle-to-cradle extends the assessment into a new product cycle. Reuse, recycling, remanufacturing, or composting pathways become part of the model, with material flows returning as resources for another system.

This boundary supports circularity decisions, but it requires careful treatment of collection rates, sorting, quality loss, recycling energy, substitution assumptions, and the point at which the next product system begins. A circular claim isn't established by labeling a material recyclable. The LCA must model the relevant pathway and explain its assumptions.

!A diagram explaining life cycle assessment system boundaries: Cradle-to-Gate, Cradle-to-Grave, and Cradle-to-Cradle with their definitions.

Rule of thumb: Match the boundary to the claim. A factory-door claim can use cradle-to-gate. A whole-life consumer claim needs cradle-to-grave. A circularity claim needs a modeled loop, not just a recycling symbol.

A DPP shouldn't flatten an LCA into one unexplained score. It should preserve the relationship between the published result and the evidence that produced it.

The first layer is primary data stored with the product record. This can include the approved impact value, functional unit, boundary, impact category, study identifier, assessment date, calculation version, and approval state. The passport doesn't need to reproduce every calculation, but it should preserve enough metadata to show what the value represents.

The second layer is external evidence linked to the record. That may include the full LCA report, inventory extracts, supplier documents, database references, electricity data, allocation explanations, and critical review statements. A link without version control isn't enough. If a supplier replaces a dataset, the organization needs to know whether the published result changed and why.

A useful passport model separates the information into three views:

• Stored evidence: The product record holds approved values, study identifiers, methodology metadata, versions, confidence states, and review status.
• Linked evidence: The record points to detailed reports, datasets, supplier contributions, and supporting documentation.
• Published insight: The consumer, retailer, or regulator sees the permitted impact fields, explanations, limitations, and relevant improvement information.

The published footprint tile should be generated from an approved study version, not from an editable spreadsheet that can change without a publication event. A DPP platform should retain an immutable snapshot of what was published, along with the underlying JSON or document representation used for audit and machine-readable exchange.

Some fields may be required by an applicable product rule or registry process. Others can make the passport more useful to a retailer or consumer, such as repair information, recycled content evidence, durability context, or end-of-life instructions. The team should label each field according to its regulatory status and confidence rather than presenting every available value as equally authoritative.

Versioning is the control point. If a supplier refreshes energy data, the LCA model changes, or the impact method is updated, the team should create a new assessment version, record the reason, rerun approval, and publish a new snapshot where necessary.

The practical benefit is reuse. One approved LCA can support product design, procurement, retailer disclosure, compliance review, and multiple passport surfaces, while each surface remains traceable to the same controlled evidence layer.

!A diagram illustrating how Lifecycle Assessment (LCA) data integrates into a Digital Product Passport (DPP) system.

Start with one clearly defined SKU or product configuration. A study that tries to cover every variant before the team understands its data structure can create ambiguity around materials, suppliers, energy use, and functional units.

1. Write the decision brief. State whether the study supports design comparison, customer disclosure, compliance, procurement, or a public claim.
2. Freeze the product definition. Gather the bill of materials, component weights, packaging, manufacturing route, production location, and expected use scenario.
3. Choose the modeling environment. Practitioners may work in tools such as SimaPro, openLCA, or Sphera's GaBi environment, depending on expertise, database access, sector requirements, and review needs.
4. Select background data. Document the chosen database, dataset geography, technology fit, licensing, version, and any substitutions.

The supplier request pack should ask for material specifications, process energy, production quantities, transport mode and distance assumptions, manufacturing waste, recycled content evidence, chemical or finishing information, packaging, and end-of-life information where relevant. Ask suppliers to identify whether a figure is measured, calculated, estimated, or copied from a generic dataset.

Data gaps are normal. Hidden gaps are the problem. Record each missing input, the proxy used, the reason it was selected, and the likely effect on the result. If the result will support a public claim, arrange an appropriate critical review and keep the reviewer's findings with the final report.

Validate the finished model against the relevant PEFCR or Product Environmental Footprint Category Rules where they apply. Check that the functional unit, boundary, impact method, allocation, data quality, and reporting format align with the category requirements before sign-off.

The handover package should contain the final report, inventory extracts, assumptions register, supplier evidence, database and impact-method versions, review documents, and machine-readable exports such as CSV or JSON where available. A practical LCA handover example shows the kind of evidence structure a passport workflow needs.

An LCA becomes useful for ESPR and DPP readiness when the study connects to a governed product record. The team shouldn't publish a carbon value without the report, boundary, methodology, datasets, assumptions, approval status, and review evidence behind it.

The Digital Product Passport requirements guide can help teams organize the broader information architecture, while legal and regulatory specialists should confirm which obligations apply to a particular product and market. LCA-derived information may sit alongside fields such as recycled content, repair potential, durability, and circularity evidence, but the exact required fields depend on applicable rules.

A practical action list for the next year is:

• Scope priority SKUs and identify the product rules, claims, and passport fields that matter.
• Commission or run assessments with documented boundaries, methods, datasets, and review requirements.
• Collect supplier evidence through structured requests with clear deadlines and confidence states.
• Connect approved results to passport records without overwriting earlier published versions.
• Rehearse retailer and regulator disclosure using the same evidence a public user or auditor would receive.

For organizations also coordinating producer responsibility, an ITAD partnership for EPR compliance can provide useful context around take-back and end-of-life obligations. The LCA and the DPP should meet at that evidence layer, where disposal and recovery assumptions are recorded rather than implied.

DPP Grid helps product teams connect LCA reports, supplier evidence, approvals, persistent product identities, and versioned passport snapshots in one governed workflow. Visit DPP Grid to see how your approved LCA evidence can move from assessment to a traceable Digital Product Passport.