CirculeID

concept

Data Quality in a Product Passport

A passport publishes your data quality to everybody. The failure modes that matter, how to detect them, and what to do about the gaps you cannot close.

CirculeID Research5 min read1,224 words

Passport data quality differs from ordinary data quality because errors become public, verifiable assertions rather than internal inconveniences. The failure modes that matter most are stale values, unit confusion, granularity mismatch and silent defaults, and each needs a different detection method.

What this gives you

The data-quality rules that decide whether a passport survives inspection, how to measure completeness against a delegated act, and where to place validation.

Key takeaways

  • A passport publishes your data quality, which is a different exposure from internal reporting.
  • Stale data is more dangerous than missing data, because it looks complete.
  • Unit and granularity errors survive validation and produce plausible wrong answers.
  • Recording provenance lets you publish imperfect data honestly rather than not at all.

Internal data quality problems are absorbed by the people who know the data. A passport removes that buffer, exposing whatever is in the record to consumers, regulators, recyclers and competitors simultaneously.

That changes which quality problems matter and how much effort each deserves.

Missing data is safer than wrong data

A gap is visible, and everybody handling the record knows it is a gap. A wrong value is invisible and is acted upon.

This inverts the instinct on most data programmes, which treat completeness as the primary measure. For a passport, an incomplete record honestly labelled is a considerably better outcome than a complete record containing values nobody has verified.

The four failure modes that matter

Most passport data problems fall into four categories, and they need different detection approaches because only one of them is caught by ordinary validation.

The failure modes, and how each is actually detected
FailureWhat it looks likeHow to detect it
Stale valueCorrect once, no longer trueAge monitoring against expected refresh
Unit confusionGrams recorded where kilograms expectedDistribution and outlier analysis
Granularity mismatchA group average recorded as a product valueProvenance, not validation
Silent defaultA placeholder that was never replacedFrequency analysis of repeated values
Format errorMalformed identifier or dateOrdinary schema validation
The failure modes, and how each is actually detected

Only the last row is caught by validation, which is where most quality effort goes. The four above it all produce values that pass every schema check and are wrong.

Stale data is the commonest problem

Product data decays. A supplier substitutes a material, a specification is revised, a test is repeated with a different result, a calculation method changes.

A passport built on copies rather than references accumulates these silently, and the record looks exactly as complete and confident when stale as when current.

The practical defence is to record when each value was established and what its expected refresh interval is, then monitor age against that interval. A footprint figure four years old is not necessarily wrong and it should be flagged for review rather than published with the same confidence as one from last quarter.

Outlier analysis catches what validation misses

Unit confusion and misplaced decimals produce values that are structurally valid and physically implausible, which makes them detectable statistically rather than syntactically.

Comparison against similar products finds what schema checks cannot.

The last step matters. Automatically correcting outliers destroys genuine variation, and some of the most useful findings from this exercise are products that really are unusual for reasons nobody had noticed.

Provenance is the honest answer to gaps

No programme achieves fully verified, supplier-specific, current data across a whole portfolio. The question is what to do about the difference between that ideal and reality.

  • Record the source of every value — measured, supplier-declared, calculated, or estimated from a category average.
  • Record when it was established, and by whom.
  • Record the method where one applies, since a figure without its method is not interpretable.
  • Record the evidence reference, so a challenge can be answered.

A value labelled as a category-average estimate is useful and honest. The same value presented as a supplier-specific measurement is a misrepresentation, and the difference between them is entirely in the provenance record rather than in the number.

What to measure instead of completeness

Since completeness targets are counterproductive, a programme needs measures that reward the right behaviour.

Proportion of attributes with recorded provenance is a better primary measure, because it can only be improved honestly. Proportion resting on primary rather than estimated data shows genuine progress. Median age of values shows whether the record is being maintained or merely populated once.

These three together describe a passport programme’s actual health far better than a completeness percentage, and none of them can be improved by filling a field with a guess.

Where to put the effort

Quality effort should follow consequence rather than spreading evenly across attributes, because the consequences of being wrong differ enormously between them.

A wrong substance concentration has safety and legal consequences. A wrong carbon figure is a green claims exposure. A wrong product weight is embarrassing. Ranking attributes by what happens if the value is wrong produces a very different priority list from ranking by how hard they are to obtain, and it is the more useful ordering.

Frequently asked questions

Why is wrong data worse than missing data?

Because a gap is visible and everybody handling the record knows it is a gap, while a wrong value is invisible and gets acted upon. For a passport, an incomplete record honestly labelled is considerably better than a complete one containing values that nobody has actually verified.

What is wrong with completeness targets?

They create pressure to fill fields with plausible values. The measured number goes up, the record becomes less trustworthy, and nobody can subsequently distinguish the values that were genuinely verified from the ones filled in to hit a target that quarter.

Which failure modes matter most?

Stale values that were correct once, unit confusion producing structurally valid nonsense, granularity mismatch where a group average is recorded as a product value, and silent defaults never replaced. None of these are caught by ordinary schema validation, which only catches format errors.

How do we detect stale data?

By recording when each value was established and its expected refresh interval, then monitoring age against that interval. A footprint figure four years old is not necessarily wrong, and it should be flagged for review rather than published with the confidence of a recent one.

How do we catch unit errors?

Through distribution analysis rather than validation. Group similar products by category or material family, examine each attribute across the group, and flag values orders of magnitude from their peers. Investigate those rather than correcting automatically, because some outliers are genuinely real.

What do we do about data we cannot verify?

Record its provenance honestly. A value labelled as a category-average estimate is useful and truthful, while the same number presented as a supplier-specific measurement is a misrepresentation. The difference lies entirely in the provenance record rather than in the value itself.

What should we measure instead of completeness?

Proportion of attributes with recorded provenance, proportion resting on primary rather than estimated data, and median age of values. These three describe a programme’s health far better than a completeness percentage, and none of them can be improved by filling a field with a guess.

Sources

  1. Regulation (EU) 2024/1781 establishing a framework for ecodesign requirementsEUR-Lex, European Union, 2024-06
  2. Directive (EU) 2024/825 on empowering consumers for the green transitionEUR-Lex, European Union, 2024-02

Continue reading

Next step

Guarda un passaporto costruito su questo

CirculeID trasforma i requisiti descritti sopra in un passaporto digitale di prodotto funzionante per i tuoi prodotti.

Index