Cradle-to-Gate vs. Cradle-to-Grave: Manufacturers Are Choosing the Wrong PCF Boundary — and It's Costing Them Compliance

Your PCF calculation can be perfectly accurate and completely non-compliant at the same time.

The emission factors can be correct. The BOM can be complete. The methodology can be documented. And an OEM customer can still reject the entire report — because the system boundary was wrong from the start.

Cradle-to-gate where cradle-to-grave was required. Six weeks of work that cannot be salvaged. The scope must be redefined and the study restarted.

This is not a data quality problem. It is a boundary problem. And it is the most common methodological error in PCF reporting today.

The system boundary defines which life cycle stages are included in a PCF assessment. It is the decision about where carbon accounting starts and where it stops. Everything inside the boundary gets modeled. Everything outside it is excluded — legitimately, if the boundary is correct; problematically, if it is not.

There are four system boundaries commonly used in PCF calculations and Life Cycle Assessments:

The most consequential choice for manufacturers calculating product-level carbon footprints is between cradle-to-gate and cradle-to-grave. Choosing incorrectly does not produce a minor methodological nuance — it fundamentally changes what the report measures, what it can be used for, and whether it meets the requirements of the standard it claims to follow.

Both ISO 14067:2018 and the GHG Protocol Product Life Cycle Accounting and Reporting Standard require that the system boundary be clearly defined, explicitly justified, and consistent with the goal of the PCF study.

Under ISO 14067, cradle-to-gate can be used as the system boundary of a CFP study only if information on specific stages is not available and reasonable scenarios cannot be modelled, or if there are stages that are insignificant for the GHG emissions of the product. Cradle-to-gate is permissible as a partial CFP under ISO 14067, but it must be clearly labelled as such.

Under the GHG Protocol Product Standard, the boundary requirements are explicit: companies shall perform full lifecycle GHG inventories — cradle-to-grave — for all final products. For intermediate products where the use or end-of-life stages may not be reasonably assumed, a cradle-to-gate assessment may be performed. Any exclusion of attributable processes must be disclosed and justified in the inventory report.

The compliance failure is not always about choosing the simpler boundary. It is about choosing a boundary that does not match the product type, the product's actual emissions profile, the customer's data requirements, or the regulatory framework the report is intended to satisfy.

Cradle-to-gate is technically appropriate — and in many B2B contexts the standard approach — in the following situations:

The use phase is not a minor footnote for most finished products. In certain categories, it is the dominant source of emissions — and excluding it does not produce a conservative estimate. It produces a structurally misleading one.

For products that consume energy during operation — appliances, vehicles, electronics, heating systems, industrial equipment — the emissions generated during years or decades of use dwarf those generated during manufacturing. A cradle-to-gate PCF for a product in these categories captures only the upfront embodied carbon, leaving the majority of the product's actual lifetime emissions unaccounted for.

Cradle-to-grave is required or strongly indicated in the following situations:

The GHG Protocol Product Standard states that companies shall perform full lifecycle GHG inventories — cradle-to-grave — for all final products. PCFs typically follow standards like ISO 14067 or the GHG Protocol Product Standard. For final products, the GHG Protocol requires a cradle-to-grave boundary; ISO 14067 sets it as the default system boundary.

Under ISO 14067, the exclusion of lifecycle stages is only permitted where those stages do not significantly change the overall conclusions of the study. For any product where the use phase or end-of-life carries material emissions, excluding these stages is not permissible under a conformant full CFP study.

The GHG Protocol Product Standard requires that public inventory reports include a disclaimer on limitations, including product comparison. Using a partial cradle-to-gate footprint to support consumer-facing low-carbon claims on a product whose dominant emissions occur in the use phase constitutes a misleading environmental claim and a greenwashing risk under applicable standards.

Sector-specific Product Category Rules and emerging digital product passport frameworks increasingly specify full lifecycle coverage. A PCF submitted under one of these frameworks using a cradle-to-gate boundary does not conform to that framework's requirements, regardless of how accurately the included stages are calculated.

Choosing the correct boundary must always start with the goal of the study. Under both ISO 14067 and the GHG Protocol Product Standard, the selection of the system boundary must be consistent with the declared goal of the PCF study. Before defining a system boundary for any PCF calculation, five questions need clear answers.

The consequences of a mismatched PCF system boundary operate on three levels.

Regardless of which boundary is chosen, both ISO 14067 and the GHG Protocol Product Standard require that the boundary decision be formally documented as part of the PCF study report.

Under ISO 14067, required documentation includes: a clear statement of the system boundary selected; the criteria used in establishing it; identification and explanation of any excluded lifecycle stages, processes, inputs, or outputs; and the functional or declared unit against which all emissions are calculated.

Under the GHG Protocol Product Standard, public GHG inventory reports must disclose: whether the inventory is a final product cradle-to-grave or intermediate product cradle-to-gate assessment; a process map of all attributable processes; any exclusion of attributable processes with justification; and a disclaimer on the limitations of various uses of the report, including product comparison.

Missing or incomplete boundary documentation is itself an audit finding under both frameworks — independent of whether the chosen boundary was technically appropriate.