# Who has to own this, and what happens when a field turns out to be wrong

Source: https://activatedigital.ai/knowledge/evidence/owning-a-published-field
Last verified: 28 August 2026
Summary: The company that placed the product on the market owns every field it publishes, and the accuracy standard sitting on those fields carries no materiality threshold and no reasonable efforts qualifier. The instrument that runs the passport registry contains no correction procedure, so the only one there is is the one the business writes for itself. Inside that business, the signature that counts is a record of what was checked, against what, on what date and by whom.

## In 60 seconds

The company that placed the product on the market owns every field it publishes, the accuracy standard the ecodesign framework sets on that data is unqualified, and the implementing regulation behind the passport registry contains no procedure for correcting or withdrawing a field that turns out to be wrong.

- Commission Implementing Regulation (EU) 2026/1778 requires registered data to be accurate, complete and up to date at all times. It sets no interval and no trigger.
- A third party can register on the operator's behalf, but the operator stays fully responsible.
- The registry's automated checks confirm structure and completeness. They are not proof that a product complies with anything.
- A sign-off has five parts: what was checked, against what, on what date, by whom and what the check could not establish.
- Not established: what happens to a unit already sold when the passport behind it is corrected.
Inside the company, the person who can sign is whoever can produce a record of what was checked, against what, on what date and by whom. [How the estate corrects its own work](https://activatedigital.ai/knowledge/evidence) is a method statement about these pages, and this page is about the reader's governance rather than ours. [Which economic operator carries the duty](https://activatedigital.ai/knowledge/regulation/who-carries-the-obligation) is a question about how duties fall between operators, and this one is about who inside a single business decides.

That combination makes the subject awkward. The duty is unqualified and it is continuous, the instrument that runs the register is silent on retraction, and the evidence under a typical field belongs to somebody else and moves without anybody being told. A business can do everything carefully and still be publishing a field whose support was withdrawn in June.

## The part that is already settled

Responsibility outside the business is not in dispute. It sits with the economic operator that placed the product on the market, and working out which operator that is for a given product is a question with a settled answer and a page of its own. That question is answered by role rather than by company, and one business can occupy more than one role at once. Most people arrive here having already had that answer and still not knowing what to do on Monday morning.

What they arrive with is narrower and harder. A company is not a person, and the sentence that the company is responsible does not tell anybody whose name goes next to a [recycled content](https://activatedigital.ai/knowledge/fields/recycled-content) percentage that a supplier supplied, that nobody in the room measured and that a document in a folder only half supports.

## What the registry regulation says, provision by provision

The implementing regulation behind the passport registry is more precise than its summaries, and the precision lives in four separate provisions doing four different pieces of work. Merging any two of them is how a governance conversation goes wrong, usually in the direction of comfort.

Four provisions of the registry implementing regulation, kept apart, each named by what it does rather than by a number.

| The provision | What it does | What it does not do |
|---|---|---|
| Responsibility at the moment of registration | Puts responsibility for the accuracy and the completeness of the registered data on the operator, at the point of registration. | It does not reach forward on its own. A point in time duty is discharged at a point in time, which is why a second provision exists. |
| The continuing duty | A separate provision requires the data to be accurate, complete and up to date at all times. | It sets no interval, no review cadence and no trigger. At all times is a standard rather than a schedule, and nobody is told when to look. |
| Registration by a third party | Allows a third party to register on the operator's behalf, requires that third party to be verified in its own right, and leaves the operator fully responsible. | It does not move responsibility to whoever does the keystrokes. Delegating the act delegates the act and nothing else. |
| Controller of the submitted data | Makes the operator the controller of the data it submits. | Controller status is a status. The instrument does not turn it into a correction route, and it answers no question about who signs. |

One more sentence from the same read is the one most likely to be misread in the other direction. The automated checks the registry runs confirm structure and completeness, and they are not proof that a product complies with anything. A field can pass every check the register makes and still be wrong about the goods.

Why there are no article numbers above

The instrument was read at article level by one research programme in August 2026, and those four provisions are the substance of that read. The internal numbering has not been checked against the Official Journal PDF, so each provision is named here by what it does. The source note at the foot of the page records that check as outstanding.

Registration is the act that sets all four running at once, and [what registration commits you to](https://activatedigital.ai/knowledge/regulation/enrolling-in-the-registry) is set out separately, including what the register keeps and for how long. None of the four is about a field published on a website. They are about the data an operator registers, which is a narrower object and, once registered, a more consequential one.

## Current at all times, and no act by which a wrong one is retracted

The framework's accuracy standard is unqualified. Accurate, complete and up to date, with no materiality threshold under which a small error stops counting, and no reasonable efforts qualifier that trades diligence for correctness.

The instrument that runs the register contains no correction, withdrawal, deactivation or supersession procedure. Change is handled through logging, versioning and a registration status whose permitted values the instrument does not define. So the law asks for a passport that is current at all times and supplies no legal act by which a wrong one is taken back.

Two things follow. The first is that the correction procedure is the operator's, by default rather than by design: no instrument read for this page writes one, so whatever the business does becomes the procedure. The second is that what happens to a unit already sold when the passport behind it is corrected is not established, and we did not find an instrument that answers it on the routes we searched.

## Nothing propagates

Underneath all of that sits one mechanical fact. When a document supporting a published field stops being good, nothing moves. There is no route by which the invalidation of a certificate reaches the field it was holding up, and nothing on either side of the join is watching for one.

Across the scheme documentation read for this estate, six schemes state their own limits in their own documents, and not one of those six operates automatic invalidation propagation. The nearest thing to a counter example is a scheme whose transaction certificates cite the input certificates behind them and carry an invalidation reason code. Even there the act is a certification body's discretionary decision, taken one node at a time, by somebody who has to notice first.

The clearest public test of it is a scheme's own published answer after an accreditation body suspended a certification body. Certificates already issued were still to be treated as valid unless the scheme notified otherwise. That is a defensible position for a scheme to hold. It is also a plain description of a system in which nothing downstream is told anything.

The data model side is no different. The public precedent registered as a source here grades where a value came from. That is useful. It holds no state at all for a value whose support has since been withdrawn.

The document half of this, which is what ends the useful life of each kind of paper and whether anything announces it, is set out in [what stops being current, and when](https://activatedigital.ai/knowledge/evidence/documents). This page is about the consequence for a field that has already been published.

## A standard withdrawn in June, and nothing noticed

The worked example is live and ordinary. The catalogue records an edition of the self declared environmental claims standard as withdrawn on 24 June 2026 and replaced by a new one. Every policy, supplier contract and technical pack citing the withdrawn edition now cites a document that no longer exists.

Nothing flagged that. No mechanism between a standards catalogue and a published product field would have. A recycled content field whose supporting declaration is written against that edition is in the position this page describes: the field has not changed and neither has the declaration, and the thing both of them rest on stopped existing in June.

This page doesn't describe what the new edition contains. It's behind a purchase, hasn't been bought and hasn't been read here, so anything written about its contents would be invention with a reference number attached. What's used above is the catalogue entry, not either text.

That's the shape of silent invalidation, and it differs from the failure people expect. Nobody published something false. Something that made a published field defensible was withdrawn, and no channel existed to tell anybody holding the field.

## Four clocks that do not reconcile

Ask the simplest question anybody can ask of a published field. Was this true of this unit at the moment it was sold. Four different clocks bear on the answer and no system holds all four against a single unit.

- **The production date.** One instant, fixed by the goods rather than by anybody's records.
- **The claim date.** The day the field was published, which is usually later and sometimes much later.
- **The applicable period.** The window the evidence itself says it covers, which is a property of the document rather than of the product.
- **The validity of the evidence.** The clock running on the document, where the document has one at all.
The scheme documents sharpen the mismatch: the scope certificate runs a one year clock and prints on its face that it provides no proof any goods its holder delivers are certified, while the transaction certificate, the one about goods, has no expiry field at all. So the paper that expires isn't about your unit and the paper about your unit doesn't expire, as set out on [certificates, declarations and test reports](https://activatedigital.ai/knowledge/evidence/documents#two-certificates).

No standard read for this estate reconciles the four, and none of the four is wrong. They are answers to different questions that happen to be written in dates, and the question a reader wants answered sits between them.

## What a sign-off actually consists of

A sign-off on a published product field is not a name on a form. When the evidence belongs to somebody else, which is the normal case rather than the awkward one, the only thing a signature can honestly assert is what the signer checked and what the check could not reach.

A sign-off has five parts. What was checked, against what, on what date, by whom and what the check could not establish.

The fifth is the one that gets dropped, and it is the one that makes the record worth keeping. A sign-off that records only the positives is indistinguishable from a sign-off that looked at nothing, because both of them say the same thing about the parts nobody reached. A record that names its own limits can be inspected a year later by somebody who was not there, which is the whole point of writing it down.

Is this field ready for somebody to sign?

1Does the document behind the field say, on its own face, what it covers?

- YesCopy that scope onto the record in the document's own words rather than in yours. Two schemes print a disclaimer on the face of a scope certificate saying it proves nothing about goods delivered by its holder, and that sentence is part of the scope.
- NoRecord that it does not say. Supplying a scope the document never claimed is the commonest way a folder turns into evidence it is not.
SourceChain of custody scheme rules, scope and transaction certificate specificationsChecked 28 August 2026

2Does that scope cover this product, this variant, this market and this period?

- YesWrite the comparison down. It is the step nobody can reconstruct afterwards.
- NoThe field is not supported by this document. A nearly relevant certificate supports nothing, and the honest output is a stated gap with its reason.
- Not sureTreat it as unsupported until somebody establishes otherwise, and record which of the four you could not settle.
SourceChain of custody scheme rules, scope and transaction certificate specificationsChecked 28 August 2026

3Do you know what ends this document's useful life, and would anybody tell you?

- It carries a validity periodThat is the only kind of expiry a calendar can watch. A scope certificate runs a one year clock and is the worked case.
- It carries noneRecord that there is no expiry rather than leaving the box empty. A blank expiry field and an absent expiry are different states, and the transaction certificate that does say something about goods has no expiry field at all.
SourceChain of custody scheme rules, scope and transaction certificate specificationsChecked 28 August 2026

4If this field turns out to be wrong, who takes it down and where is that written?

- A named person, in a written procedureSign. The record now carries what was checked and what happens if the check was wrong.
- The supplier or the platformAuthorising a third party to register on the operator's behalf leaves the operator fully responsible under the instrument. The name has to be somebody inside the operator.
- Nobody has decidedThat is the gap this page exists for. The registry instrument writes no correction procedure, so the operator's own is the only one in existence.
Source[Commission Implementing Regulation (EU) 2026/1778 establishing the Digital Product Passport registry](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32026R1778)Checked 28 August 2026

This settles what your own record shows and what it admits it cannot show. It does not settle what the field is worth in law, and nothing in this estate certifies, verifies or validates any claim about any product.

None of that makes the field true. It makes the field accountable in the ordinary sense: somebody can reconstruct how it came to be published, on what basis and who would take it down. Where a business cannot answer those questions about a field it has already published, the field is not signed off, whatever the form says.

## Internal ownership and DPP update authority

Internal ownership answers who approves a product fact. The DPP framework separately decides which actors may introduce or update each class of data. [See the update-authority model.](https://activatedigital.ai/knowledge/guides/who-can-update-a-dpp)

## What to do in the next week

This is a procedure rather than a project, and it can be run against a single field first to see how long it takes. The field to test it on is the one that would be most expensive to be wrong about rather than the one with the tidiest folder.

- **Establish where the fact is currently asserted.** A published field is rarely in one place. The same percentage tends to sit in a product page, a marketplace feed, a tender response, a supplier contract and, once registered, in the register. Write the list before deciding anything, because the list is usually the surprise.
- **Decide whether it is still supported.** Take the document, read what it says it covers on its own face and hold that against the wording of the field. A document written against a withdrawn edition of a standard is a change of support even though nothing about the goods moved.
- **Decide who takes it down.** Name a person rather than a function. Authorising somebody else to register or to publish leaves responsibility with the operator, so the name has to be inside it.
- **Record having decided.** The date, the evidence, the decision and what the decision could not establish. Where the law supplies no procedure the record is the procedure, and it is the only artefact that will still exist when the people change.
One absence: no first-person account of a business amending live product information because upstream evidence changed was found by any of the research programmes behind this estate. That is a fact about our search rather than about the market, and it does not tell us whether the problem is unserved or whether nobody minds it enough to write about.

## When a wrong fact is also a safety issue

If the wrong product fact also creates a safety issue, correction is only one part of the response. [See what happens to the DPP when the product is recalled.](https://activatedigital.ai/knowledge/guides/dpp-after-product-recall)

## Keep exploring

The question this one usually raises next.

- [CompareEvidence & suppliersWhat a value will supportThe scope test that decides whether a document reaches the words of the claim, before anybody signs anything.→](https://activatedigital.ai/knowledge/evidence/claims-and-substantiation)
Also worth reading

- [CompareEvidence & suppliersWhat ends a document's useful lifePer document type and per scheme, what stops each one counting and whether anything announces that it has.→](https://activatedigital.ai/knowledge/evidence/documents)
- [Another anglePassport technologyWhen the party holding it stopsThe other way a published field quietly stops being supported, and what the framework says has to survive it.→](https://activatedigital.ai/knowledge/passport/when-the-link-dies)
- [CompareNext questionWhat happens when a certification scheme is replacedThe standards behind most textile recycled and responsible material certificates are being consolidated.→](https://activatedigital.ai/knowledge/evidence/when-the-scheme-behind-a-certificate-changes)

## Related

- [Who Checks DPP Information? Registry, Conformity and Market Surveillance](https://activatedigital.ai/knowledge/evidence/who-checks-dpp-information) — The four verification layers

## Sources

Four of these rows carry a text somebody read and one carries a catalogue entry rather than a text. The difference matters on this page more than most, because the worked example in the middle of it is a document nobody here has bought.

- [Commission Implementing Regulation (EU) 2026/1778 establishing the Digital Product Passport registry](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32026R1778) Delegated or implementing actCELEX 32026R1778In forceRelevant provisions reviewed
The four provisions in the table above come from this instrument, read at article level by one research programme in August 2026. The internal article numbering has not been checked against the Official Journal PDF, so no article number is published on this page and each provision is named by what it does instead. That check is outstanding and it is the one thing that would change how these four are cited. The same read establishes the two absences the page rests on: the instrument carries no compliance deadline of its own and no correction, withdrawal, deactivation or supersession procedure.

- [Ecodesign for Sustainable Products Regulation (EU) 2024/1781, consolidated text](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02024R1781-20240628) EU lawCELEX 02024R1781-20240628In forceRelevant provisions reviewed
Here for one thing only, which is that the accuracy standard on passport data is unqualified: accurate, complete and up to date, with no materiality threshold and no reasonable efforts qualifier attached to it. Two independent reads of this instrument attributed the passport provisions to different articles, so this page names no article of it.

- ISO 14021, self-declared environmental claims, edition withdrawn 24 June 2026 Withdrawn 24 June 2026Official source confirmed, detailed review pending
The live worked example of silent invalidation. What is used here is the catalogue entry, which records the edition as withdrawn on 24 June 2026 and replaced. That is a fact about the catalogue rather than about any text. The replacing edition is behind a purchase, has not been bought and has not been read, so nothing on this page describes what it contains.

- Chain of custody scheme rules, scope and transaction certificate specifications Scheme rulesRelevant provisions reviewed
Carries the scope certificate disclaimer and its one year clock, the transaction certificate with no expiry field, and the six schemes that state their own limits in their own documents. Three of these documents carry effective dates in late 2026 and early 2027 and both changes alter what is said above. The scheme statement about certificates issued before a certification body was suspended is a public answer rather than a rule, and it is described here rather than named, because no address for it is registered.

- [Battery Pass Consortium data model](https://thebatterypass.eu/) Secondary sourceIndependentRelevant provisions reviewed
Read as one of the public precedents this estate positions against. Used here for a single sentence: it grades where a value came from, and it holds no state for a value whose support has since been withdrawn.