There is a particular moment that tends to happen inside manufacturing companies. It usually begins with a perfectly reasonable question.

Someone asks where a specific piece of information comes from. For a few seconds, nobody answers. Eventually someone says, “I think Sarah has that.” Another colleague opens a spreadsheet that has existed for years. It has been copied so many times that nobody remembers where it originally came from. Some figures match the Enterprise Resource Planning system. Others come from supplier declarations received months apart. A technical datasheet introduces another variation. None of the documents appears obviously wrong. None inspires complete confidence either.

Scenes like this are remarkably ordinary. They rarely appear in conference presentations or policy papers because they are too mundane to attract attention. Yet they reveal something fundamental about the way organisations actually work.

That was the first thought that came to mind while reading the documentation for the European Union Digital Product Passport Registry.

The Registry itself is an important milestone. Europe needs common infrastructures if Digital Product Passports are to become interoperable across sectors and borders. Shared registries, common identifiers and agreed technical standards are all necessary pieces of a much larger system. Without them, the vision behind the Ecodesign for Sustainable Products Regulation would remain largely theoretical. None of that seemed particularly surprising.

What stayed with me after finishing the documentation was a different question altogether: What has to happen inside an organisation before any Digital Product Passport can genuinely deserve to be trusted?

The Registry was never intended to answer that question, nor should it. Its role is different. Reading it simply highlighted how much of the conversation still takes place after the organisational work is assumed to have already happened.

That assumption deserves closer attention.

Across many European digital initiatives there is an implicit expectation that organisations already understand their own information. The expectation sounds almost self-evident. Companies know which data they need. They know where it is stored. They know who owns it, who validates it and how its quality is maintained before it reaches external systems.

Anyone who has spent enough time inside businesses knows that reality is often more complicated.

Information rarely lives in one place. It accumulates over years, sometimes decades. New software is introduced without completely replacing the old. Departments develop their own naming conventions. Suppliers provide documentation in different formats and at different levels of detail. One process quietly adapts while another continues unchanged because changing it would interrupt production. None of these decisions appears particularly significant on its own. Together they create an organisation that functions remarkably well on a daily basis while remaining surprisingly difficult to describe from the outside. That difference matters.

Digital Product Passports depend on information. Organisations depend on people making thousands of small decisions about that information every week. Those are not the same thing.

Consider a relatively simple question: Who is responsible for confirming the composition of a material before it becomes part of a Digital Product Passport?

At first glance the answer appears obvious. Someone must already know. Sometimes they do. Sometimes responsibility is shared across purchasing, quality assurance, product development and compliance. Each department understands one part of the process. No single person sees the entire chain. The organisation functions because experienced people compensate for gaps that have never been formally documented.

That kind of institutional knowledge is enormously valuable. It is also remarkably difficult to digitalise.

Technology has become exceptionally good at processing structured information. It is much less effective at discovering why information exists in its current form or which assumptions people quietly rely upon every day.

Perhaps this explains why conversations about Digital Product Passports often begin with technology.

• Which platform should we use?
• Which standard should we follow?
• Which identifier should we implement?

These are sensible questions. They simply arrive later than many organisations realise. Before choosing a platform, an organisation has to understand itself. It has to know where information originates, who is authorised to change it, what evidence supports it and what happens when two apparently reliable sources disagree.

Software can process uncertainty. It cannot remove uncertainty that nobody has recognised.This distinction may prove more important than it first appears.

European legislation describes obligations with increasing precision. Standards continue to mature. Technical infrastructures are steadily taking shape. Together they establish a common language that did not exist only a few years ago. Yet legislation does something very specific. It defines what must ultimately exist. It does not describe how every organisation should reorganise itself in order to make that possible. That work remains local.

Every company has to translate legal requirements into operational routines that fit its own people, products and supply chains. There is no universal template because organisations rarely resemble one another beyond the surface.

A regulation can require evidence. It cannot decide who will collect it.

It can define reporting obligations. It cannot determine how responsibilities should be distributed between engineering, procurement and quality teams.

It can establish transparency requirements. It cannot build the habits that make transparency reliable year after year.

Those things emerge gradually. They are shaped by organisational culture as much as by technology. This is why I increasingly think that there is an organisational layer sitting quietly between regulation and implementation.

It receives surprisingly little attention because it is difficult to visualise. There are no dashboards that immediately demonstrate it. No architectural diagrams neatly capture it. Progress often consists of conversations, governance decisions, clarified responsibilities and small improvements that appear insignificant until someone tries to trace the origin of a single piece of information several years later.

That layer is unlikely to attract headlines. It may nevertheless determine whether Digital Product Passports become trusted sources of information or simply another compliance exercise.

One thought kept returning as I reflected on the Registry. Its purpose is to confirm the existence of a Digital Product Passport. That is precisely what it should do. It tells other systems where a passport can be found and how it can be referenced. It contributes to the infrastructure that makes interoperability possible. Yet I suspect that, over time, the questions surrounding Digital Product Passports will begin to change.

Today, much of the discussion revolves around whether a passport exists. Eventually, attention is likely to shift elsewhere:

• How reliable is the information behind it?
• What evidence supports the published claims?
• Who reviewed that evidence?
• Under which process?
• If an auditor, a market surveillance authority or a business partner challenges a particular declaration several years from now, can the organisation reconstruct the reasoning that led to it?
• Can it explain not only what was published, but why it was considered sufficiently reliable at the time?

Those questions belong to a different stage of maturity.

Most digital systems follow a similar trajectory. The first challenge is making information available. Once that becomes routine, availability gradually stops being the primary concern. Confidence takes its place.

The same information can exist in two organisations and carry completely different levels of credibility. One company may be able to trace every declaration back to documented procedures, supplier communication, internal approvals and supporting evidence. Another may arrive at exactly the same published result through a chain of assumptions that exists only in the experience of a handful of employees.

From the outside, the two Digital Product Passports might appear almost identical. Internally, they represent two very different organisations. That distinction interests me far more than the passport itself.

The Digital Product Passport is ultimately an expression of organisational behaviour. It reflects the quality of decisions made long before data reaches a digital platform. Every field inside the passport represents a process, a responsibility or a judgement that happened somewhere within the organisation.

We tend to think of products as the centre of the discussion. Products, however, do very little on their own. They do not interpret legislation. They do not challenge incomplete supplier documentation. They do not decide whether laboratory results are sufficient or whether another declaration should be requested before information is published. People make those decisions. Processes support them. Governance gives them consistency. Remove those elements and the technology has surprisingly little to work with. Perhaps this is why conversations about Digital Product Passports sometimes feel incomplete.

The technical architecture is becoming increasingly sophisticated. Standards continue to evolve. Common vocabularies are emerging. Interoperability receives the attention it deserves. At the same time, the organisational work that makes trustworthy information possible often remains invisible because it happens quietly, inside individual businesses. There are no demonstrations for that.

No elegant system diagram can fully describe the gradual process of assigning responsibilities, agreeing validation rules, documenting exceptions or deciding who has the authority to approve conflicting information. Yet those decisions shape the final outcome every bit as much as the technology itself.

Europe’s next challenge is less about creating new Digital Product Passports than about helping organisations become ready to produce them with confidence. That readiness is not a software feature. It is something that develops over time.

It begins with understanding information before attempting to exchange it. It grows through clearer governance, stronger ownership and better evidence practices. Eventually, technology starts reinforcing those decisions instead of compensating for their absence.

Seen from that perspective, implementation becomes something rather different from installing a new platform. It becomes an organisational transition. Perhaps that also changes the way we should think about success.

A successful Digital Product Passport is unlikely to be the one that contains the greatest number of data fields. Nor the one that integrates with the largest number of external systems. Its real strength may lie elsewhere. In the confidence that every important statement can be explained, supported and defended years after it was first published.

That level of confidence cannot be generated automatically. It has to be built. Slowly. Sometimes through work that appears almost invisible while it is happening.

The Registry made me think about this because it represents an important moment in Europe’s digital journey. Shared infrastructures are becoming real. The broader ecosystem is taking shape. Those developments deserve recognition.

At the same time, they remind us that infrastructure alone cannot determine the quality of the information flowing through it. Roads can connect cities. They cannot teach people how to drive responsibly. The same principle applies here.

Digital Product Passports will undoubtedly become part of everyday business across Europe. The technology will continue to improve. Standards will mature. New services will emerge around them.

What will ultimately differentiate organisations is unlikely to be their ability to generate a passport. It will be their ability to demonstrate that the information inside it deserves to be trusted. That is a quieter conversation than discussions about platforms, interoperability or digital architecture. It is also a more demanding one. It asks organisations to look inward before looking outward. To understand their own information before sharing it. To strengthen governance before automating processes. To recognise that transparency is not created at the moment data is published. It begins much earlier, when responsibilities are defined, evidence is evaluated and everyday operational decisions gradually become part of a system that others can rely upon.

Perhaps this is the next chapter in the Digital Product Passport journey. Europe has invested considerable effort in building the common infrastructure. The years ahead may be shaped just as much by something less visible: helping organisations develop the capability to use that infrastructure well.

When that happens, the conversation will no longer be centred on whether a Digital Product Passport exists. It will focus on something far more valuable. Whether the organisation behind it has earned the trust that the passport represents.