Skip to content

Stage Contribution Table

Data display — instantiates Lifecycle Trade-Off Evaluation

Breaks one option's total lifecycle impact down by stage, so the analyst can see which stage — extraction, use, or disposal — actually carries the burden.

A Stage Contribution Table lays a single option's lifecycle impact out as a grid whose rows are lifecycle stages and whose cells report how much each stage contributes to the total — usually as both an absolute figure and a share of 100%. Its one job is stage attribution: granted that an option has some footprint, where in its life does that footprint come from? It works on one option at a time and it decomposes rather than compares — it does not rank alternatives against each other, and it does not reconcile conflicting impact categories. It answers a single, sharp question so the analysis can point at the stage worth attacking instead of the stage that happens to be visible.

Example

A clothing brand wants to know why its cotton T-shirt has the footprint it does. The Stage Contribution Table lists the stages down the left: fibre cultivation, spinning and knitting, dyeing and finishing, distribution, the use phase (a garment washed and tumble-dried dozens of times over its life), and end-of-life. Each row's inventory flows are aggregated into one column — here, cradle-to-grave energy — and expressed as a percentage. The result reorders the team's intuition: manufacturing, which everyone assumed was the villain, is modest, while the use phase dominates — illustratively well over half the total, driven by hot-water washing and tumble drying. That single reordering redirects the whole intervention. A "greener" shirt is not mainly a question of organic fibre; it is a care-label and behaviour question — cold wash, line dry. The table did not choose between shirts; it told the brand which stage to fight.

How it works

The table is built in four moves, and its discipline is that every move is explicit:

  • Fix the boundary. Decide which stages are counted; the row list is that decision made visible.
  • Pull the stage flows. Take the inventory flows already assigned to each stage from the underlying model.
  • Aggregate to the chosen impact. Collapse each stage's flows into one impact figure for that row.
  • Express as absolute and share. Show both the magnitude and the percentage, so a large total and a large fraction are not confused.

Reading the finished table is then trivial — the dominant row is the hotspot candidate — which is exactly why the value lives in building it honestly rather than in interpreting it.

Tuning parameters

  • Stage granularity — a few coarse stages or a fine breakdown (e.g. splitting "manufacturing" into weaving, dyeing, cut-and-sew). Finer rows locate the hotspot precisely but multiply data demands and noise.
  • Absolute vs. share — whether cells show physical quantities, percentages, or both. Shares make dominance legible; absolutes stop a "small percentage of a huge number" from being dismissed.
  • Impact shown — one table per impact category, or a single headline impact. A single-impact table is clean but can crown a stage that matters for carbon and is irrelevant for water.
  • Cut-off threshold — the share below which minor stages are folded into an "other" row. Tidier, but it can bury a stage that a different impact category would light up.

When it helps, and when it misleads

Its strength is that it kills the assumption that the visible stage is the whole story — the exact failure the archetype exists to prevent. It is cheap, legible to non-specialists, and it turns "where is the burden?" from an argument into a picture.

It misleads whenever its one-dimensional view is mistaken for the verdict. A single-impact table can show the use phase dominating carbon while a hidden dyeing stage dominates freshwater toxicity — decompose only carbon and you will optimize the wrong stage.[1] Percentages flatter and mislead in both directions, and the boundary choice silently determines what can appear at all: an omitted stage is a zero row you never see. The guarding discipline is to read the table beside the full impact-category picture and to never present a one-category contribution table as the lifecycle conclusion — it is a pointer to a hotspot, not a decision about which option wins.

How it implements the components

  • lifecycle_stage_model — the rows are the stages; the table makes stage decomposition the primary axis of the whole display.
  • inventory_flow_profile — each cell is the sum of that stage's inventory flows collapsed into the chosen impact figure.
  • system_boundary_map — the set of rows enumerates exactly the stages inside the boundary; a stage absent from the table is a boundary choice made visible.

It decomposes one option and does not lay alternatives against each other across the impact_category_vector, nor render the stage_hotspot_and_trade_off_matrix for cross-option inspection — that comparison surface is Impact Trade-Off Heatmap, its nearest twin. It also applies no explicit_decision_weighting_rule; converting the hotspot into a decision is Lifecycle Hotspot Review Workshop.

Editorial Notes

Form Classification

Form family: Representation, Specification & Plan

Rationale: Stage Contribution Table operates by externalizes stage boundaries, flows, contributions, and units in a persistent table. That concrete deployed or enacted form is Representation, Specification & Plan under the frozen taxonomy.

Nearest alternative: Interface, Display & Cue — Although Interface, Display & Cue can support this mechanism, the frozen evidence makes its operative form the act that externalizes stage boundaries, flows, contributions, and units in a persistent table; the alternative is therefore secondary rather than defining.

Review outcome: Adjudicated after independent review; high confidence.

Origin Attribution

Primary origin: Environmental Science & Climate Studies

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Breaking lifecycle burden into extraction, use, and disposal stages is life-cycle assessment.

Related originating lineages:

  • Accounting & Auditing — The table reconciles total impact.
  • Biology & Ecology — Biological and ecological research supplies a parallel or contributing lineage for the mechanism's defining operation: breaks one option's total lifecycle impact down by stage, so the analyst can see which stage — extraction, use, or disposal — actually carries the burden.
  • Engineering & Design — Stage impacts guide redesign.
  • Operations Research — Contribution analysis prioritizes leverage.

Review resolution: The blind reviewers agree that environmental_climate is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of multi_domain records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Reconciled after independent review; high confidence.

Notes

The table answers which stage within one option; the heatmap answers which option and which category across many. People conflate them because both are grids — but a contribution table has stages on one axis and a heatmap has alternatives; keeping that distinction is what stops a hotspot analysis from being read as a choice between products.

References

[1] Contribution analysis is the standard LCA step of attributing a result to its constituent stages or processes to locate where impact concentrates — the ISO 14044 practice this table renders. Its known limit is that the contribution pattern can differ category by category, which is why a single-impact table must never stand alone. withdrawn registry