Calculating lifecycle carbon footprints stage by stage

To calculate a carbon footprint across lifecycle stages, we start by fixing the boundary, listing every stage that sits inside it, collecting activity data for each stage, and applying the right emission factors without double counting. The result should show gross emissions by stage, with assumptions and data sources recorded clearly enough that someone else can follow the calculation.

That stage-by-stage structure matters far beyond internal reporting. It is how product carbon footprint rules are being implemented, how category rules are applied consistently, and how sustainability information can be carried into digital product records and passports. If you need to work out how to calculate a carbon footprint across lifecycle stages in a way that stands up to product rules, the practical discipline is always the same: define the system, calculate each stage on its own terms, and keep offsets outside the footprint total.

Before we calculate anything, we state the lifecycle boundary. Without that, a footprint number is incomplete and often misleading.

Two of the most common boundaries are cradle-to-gate and cradle-to-grave.

Cradle-to-gate covers the stages from raw material extraction and processing through manufacture, up to the point the product leaves the factory gate, or another clearly defined dispatch point. It usually includes inbound transport, processing losses, packaging where relevant, and manufacturing energy and waste treatment up to that gate.

Cradle-to-grave goes further. It includes everything in cradle-to-gate, plus distribution, use, maintenance where relevant, and end of life treatment such as collection, sorting, recycling, recovery, or disposal.

For services, the same logic applies even though there may be no single physical product gate. We still define where the service starts and ends, and which upstream and downstream activities belong to it. If we are assessing a maintenance service, for example, we decide whether the boundary includes technician travel, spare parts, depot energy, outsourced cleaning, software hosting, customer travel, and final waste handling of replaced components.

The boundary must be stated in the result itself, not buried in a spreadsheet tab. A declaration that says only "12 kg CO2e per unit" is not enough. It should say something like "12 kg CO2e per unit, cradle-to-gate" or "12 kg CO2e per service visit, cradle-to-grave". The declared unit also matters. A footprint per kilogram of product is different from a footprint per item, per battery pack, per wash cycle, per passenger-kilometre, or per service call.

Product-category rules can narrow what is allowed. Depending on the product type, the applicable framework may prescribe the functional unit, the lifecycle stages to include, cut-off rules, allocation methods, data quality requirements, and end of life modelling. That is why we do not choose the boundary in isolation. We check first whether a product-category rule, a sector rule, a programme rule, or legislation has already defined it for us.

This is also where supply chain structure becomes critical. If we cannot see which materials, components, processes, and movements sit upstream, our boundary will be weak from the start. Good supplier traceability across the chain makes it much easier to define what belongs in the footprint and what evidence supports it.

Once the boundary is fixed, we list the stages inside it. For products, the core stages usually include:

1. Raw materials and intermediate inputs Extraction, cultivation, refining, and production of purchased materials and components.

2. Manufacture and assembly Energy use, process emissions, consumables, scrap, rework, packaging, and waste treatment at production sites.

3. Transport and distribution Inbound freight, inter-site transfers, warehousing where relevant, outbound distribution, and sometimes retail logistics if the rule includes them.

4. Use stage Electricity, fuels, water, consumables, maintenance, replacement parts, and losses during use, where relevant to the product.

5. End of life Collection, transport, sorting, disassembly, recycling, energy recovery, landfill, incineration, and any credits or burdens handled under the applicable rule.

That list is familiar for physical goods, but services need the same discipline. A service footprint often spans several hidden sources that sit behind a single invoice line. Depending on the service, we may need to include:

• Vehicles used to deliver the service
• Energy-intensive processes carried out as part of the service
• Buildings that support the service, such as depots, workshops, offices, data rooms, or retail premises
• Staff travel, including commuting if the chosen rule requires it, and business travel where it materially supports delivery
• Purchased products consumed in the service
• Waste generated during service delivery
• Digital infrastructure, if it is material and within scope

A short worked example makes this clearer.

Suppose we are calculating the footprint of an industrial cleaning service delivered per site visit. The service includes a technician driving to the customer, using a manufactured cleaning unit on site, running a high-temperature process, and returning to a depot.

The stages could look like this:

• Raw materials and manufacture: the embodied emissions of the cleaning chemical used per visit, the replacement filter installed during the visit, and the share of the cleaning unit's manufacturing footprint allocated to each visit over its service life.
• Transport and distribution: fuel used by the van for the round trip, plus upstream freight for the replacement filter if that sits inside the chosen boundary.
• Use stage: electricity or fuel consumed by the high-temperature cleaning process during the visit.
• Buildings: a share of depot electricity and heating allocated to each service visit, based on floor area, labour hours, or another justified driver.
• Staff travel: technician business travel is already counted in the van fuel if the van is the transport mode. If the technician also travels by rail to training that directly supports the service and the rule requires it, that would need separate treatment.
• End of life: disposal or recycling of the used filter and chemical containers, and end of life treatment of the cleaning unit if the boundary includes capital goods and their retirement.

That is one service, but the same logic applies elsewhere. One family funeral director, for example, has set out its approach to calculating the carbon footprint of a cremation funeral, counting the private ambulance transfers, the coffin's production and transport, the hearse on the day, the cremation itself, and the emissions of its branches and care centre, including staff travel. The footprint is rarely just the fuel in a vehicle or the electricity on a meter. It is the sum of the lifecycle stages that make the service possible.

At stage level, the basic calculation is straightforward:

Activity data × emission factor = emissions

Activity data is the measurable quantity. It might be kilograms of aluminium, kWh of electricity, litres of diesel, tonne-kilometres of freight, hours of machine use, or kilograms of waste sent to recycling.

The emission factor converts that quantity into greenhouse gas emissions, usually expressed as kg CO2e per unit of activity.

A few simple examples:

• 500 kWh of electricity × the relevant electricity emission factor
• 120 litres of diesel × the diesel combustion factor, and where required, the upstream fuel factor as well
• 2,000 tonne-km of road freight × the factor for the relevant vehicle type and load basis
• 15 kg of polymer resin × the cradle-to-gate factor for that resin grade and geography

The detail lies in making the units and scopes line up.

If the factor is per kg, our activity data must be in kg. If the freight factor is per tonne-km, we need both mass and distance. If an electricity factor is location-based or market-based, we must use the method required by the rule we are following and disclose it.

Allocation is the next issue. Many processes serve more than one product or service. A factory may make several product lines. A vehicle may deliver multiple orders on one route. A building supports several teams. We then need an allocation key that reflects how the resource is actually used, or follows the applicable rule. Common allocation bases include:

• Mass
• Energy content
• Economic value
• Machine hours
• Floor area
• Production volume
• Distance or route share
• Time spent delivering the service

The key point is consistency. If we allocate depot electricity to service visits by labour hours, we should not also allocate the same electricity by floor area elsewhere. That creates double counting.

Double counting is one of the most common errors in lifecycle work. It usually happens when stage boundaries overlap. Examples include:

• Counting the full manufacturing footprint of a machine in the product stage, then also counting a supplier's service factor that already includes use of that machine.
• Counting business travel separately when the same fuel is already captured in fleet data.
• Counting purchased electricity in a manufacturing stage and again in a site-wide overhead stage.
• Counting waste treatment emissions both in the manufacturing process data and in a separate end of life line.

The practical fix is to build the model stage by stage and source by source, then reconcile totals. Every line item should answer three questions: what activity is this, which stage does it belong to, and has it been counted anywhere else?

For complex supply chains, track and trace across the supply chain helps keep those stage assignments anchored to actual material and logistics flows, rather than assumptions made too late in the process.

Good enough does not mean perfect. It means fit for the intended use, transparent, and aligned with the rule set that applies.

The first distinction is between activity data and emission factors.

Activity data is evidence of what happened. It comes from purchase records, bills of materials, meter readings, fuel cards, logistics data, production logs, waste transfer notes, maintenance records, travel records, and similar operational sources.

Emission factors are the conversion values we apply to that activity data. They may come from supplier-specific studies, verified product declarations, recognised databases, national inventories, or programme-approved datasets.

The second distinction is between primary and secondary data.

Primary data is specific to the process, site, supplier, or service being assessed. Examples include actual electricity consumption at a named plant, actual fuel used by a delivery fleet, a supplier-specific footprint for a purchased component, or measured process gas losses.

Secondary data is generic or industry-average data used where primary data is unavailable. Examples include database factors for generic steel, average freight factors by mode, or grid-average electricity factors.

In general, we prioritise primary activity data for processes we control directly and for hotspots that materially affect the result. Secondary data is often acceptable, and sometimes necessary, especially in upstream tiers where supplier-specific information is not yet available. But if a product-category rule sets minimum data quality requirements, those requirements take precedence.

Documentation is not optional. We record:

• The declared unit or functional unit
• The lifecycle boundary used
• Each included and excluded stage
• Data sources for activity data
• Sources and versions of emission factors
• Geography and time period
• Allocation methods
• Assumptions and proxies
• Data gaps and how they were filled
• Category-specific rule choices where alternatives were allowed

This matters because many footprint rules do not merely ask for a total. They ask how the total was built. That is especially true where data may later support declarations, conformity work, procurement responses, or digital product records.

If you are preparing information that may eventually feed a digital product passport, structure matters as much as the number itself. Stage-level data, source references, and supplier links are easier to carry forward into product data systems built for brands and product records than a single rolled-up figure with no audit trail.

Offsets do not change the calculated footprint of the product or service itself. They are a separate claim about action taken elsewhere.

If a product has a cradle-to-grave footprint of 25 kg CO2e, buying 25 kg CO2e of offsets does not make the product's footprint zero. The footprint remains 25 kg CO2e. Any offsets purchased should be disclosed separately, with their type, volume, and claim basis explained clearly.

There are two reasons for this.

First, the footprint is an attribute of the lifecycle being assessed. It reflects emissions caused across the defined stages. Netting off unrelated credits obscures that attribute.

Second, keeping offsets separate preserves comparability. Two products with the same physical lifecycle emissions should show the same footprint, even if one company has purchased offsets and the other has not. Otherwise comparisons become a mix of product performance and compensation strategy.

This separation is standard good practice and is particularly important where declarations are used for regulatory or quasi-regulatory purposes. If a rule allows separate reporting of avoided emissions, removals, or offsetting instruments, we report them in that separate field, not by subtracting them from the stage totals.

Stage-by-stage carbon data is becoming operational infrastructure. It supports product carbon footprint requirements, category rules, and the information architecture behind digital product passports.

The exact rule depends on the product category. There is no single EU-wide lifecycle method that overrides every sector-specific requirement in the same way for every product. In practice, we have to check the legislation, delegated acts, implementing acts, category rules, and any referenced standards that apply to the specific product.

A clear example is the EU Battery Regulation. It provides for a carbon footprint declaration that is phased in by battery category through Commission acts. That means the detailed requirements are not the same for every battery type at every point. The applicable category and the relevant Commission measures determine what must be declared and how. In that context, stage-level data is essential because the declaration depends on a defined lifecycle approach, specific data inputs, and consistent treatment across suppliers and manufacturers.

The Ecodesign for Sustainable Products Regulation, or ESPR, also points in the same practical direction. Where product information requirements apply, the underlying data has to be structured, attributable, and capable of being shared across the value chain. Carbon information is only one part of that, but it is a good example of why a single headline number is not enough. If we need to populate product records, support verification, or respond to downstream requests, we need the stage breakdown, the assumptions, and the source trail.

That is one reason traceability and lifecycle accounting belong together. If we can connect materials, components, processes, logistics events, and end of life assumptions to the right product record, we are in a much better position to maintain footprint data over time rather than rebuilding it from scratch for each request.

In practice, the workflow looks like this:

1. Identify the applicable product or service rule.
2. Set the declared unit and lifecycle boundary.
3. Map the stages and suppliers in scope.
4. Collect primary activity data where available.
5. Fill justified gaps with secondary data.
6. Apply the correct emission factors and allocation rules.
7. Check for overlap and double counting.
8. Publish the gross footprint by stage.
9. Record offsets separately, if any.
10. Store the results in a structured format that can support declarations and digital product information.

If you follow that sequence, the calculation is not just an internal estimate. It becomes usable compliance-grade data, or at least data that can be improved toward that standard as category rules tighten.

That is the practical answer to how to calculate a carbon footprint across lifecycle stages. We define the boundary first, count the stages that genuinely belong inside it, calculate each stage from activity data and emission factors, document the quality of what we used, keep offsets outside the footprint itself, and preserve the result in a form that can support product rules and digital product passports.