DPP ownership

How it applies

• Who knows what: Product development and engineering know design and materials; procurement and suppliers know sourcing and declarations; quality and regulatory affairs know test results and compliance status; sustainability teams know footprint data; service knows repair and spare parts; documentation knows structured content, versions and languages; IT runs the systems.
• Central coordination: One role or small team decides scope per product group, keeps the rules for access, confidentiality and change, and settles which system is the source of truth.
• Failure modes: An IT-only passport is technically sound but filled with unowned data. A sustainability-only passport covers footprints and misses repair, safety and supplier facts. A compliance-only passport meets the minimum but nobody maintains it once the product changes.
• Starter workshop: Bring the teams together and answer five questions: which products and dates apply, which data is already held and where, who owns each data area, who may see what, and who coordinates. The answers show where existing processes are strong enough and where gaps remain.
• Technical documentation: Documentation teams contribute reuse, versioning, approvals, language variants and lifecycle updates — practices a passport needs from day one.

Ownership vs. accountability

Legal accountability for the passport sits with the economic operator. Ownership inside the company is how that accountability is carried out: who maintains each field, who approves it and who answers when an authority or customer asks.

Compared with the USA, Canada and China

Traceability rules in the USA, Canada and China also cut across functions — US forced-labor import evidence, for example, needs procurement, logistics and legal. The EU passport adds a partly public, lasting record, which makes unclear ownership visible to outsiders.