DPP Readiness Assessment
Establish how prepared your organisation actually is for Digital Product Passport implementation, across ten dimensions, using evidence rather than opinion. The output is a readiness position, a gap list and a short priority sequence you can take into a programme plan.
- Small and mid sized manufacturers starting from nothing
- Compliance and regulatory teams scoping obligations
- Sustainability teams sourcing product level data
- Product, data and IT teams assessing systems and integration
- Enterprise DPP programmes baselining multiple business units
- Before committing budget or selecting any tooling
- At the start of a programme, to set a defensible baseline
- Every six to twelve months, to measure movement
- When a new delegated act brings a product family into scope
This is a practical tool, not a canonical Knowledge article and not a tieback framework. It applies the existing Knowledge estate rather than restating it. Every dimension links to the canonical article and framework that explain the underlying subject, so nothing is duplicated here.
The assessment is vendor neutral. It can be completed, scored and acted on with a spreadsheet and no tieback product. Nothing you enter leaves your browser.
Start assessment ↓Goes straight to the interactive assessment. The context below stays here if you want it.
Purpose
Most organisations discover their readiness position the expensive way: partway through delivery, when a field turns out to have no owner, a supplier will not answer, or two systems disagree about the same value. This assessment surfaces those conditions before they become programme risk, and separates the three states that get confused with each other:
- work that has not started,
- work that has started but cannot be measured,
- work that is real but not yet governed, connected or repeatable.
Who It Is For
The assessment is deliberately scale neutral. An SME with one product family and a spreadsheet can complete it honestly and score well on the dimensions that matter to it. A multinational with twelve business units should run it per business unit, because averaging across units hides the weakest one, which is usually the one that fails first.
When To Use It
Run it before selection, not after. Readiness decisions taken after a platform choice tend to be rationalised rather than assessed. Re run it on a fixed cadence so that movement, or the absence of movement, is visible.
Instructions
- Agree the scope before you score. One product family and one market, or one business unit. Do not assess "the company" as a whole on the first pass.
- Assemble the people who hold the answers: compliance, product data, procurement, quality and IT. A single assessor produces a single view, which is usually optimistic.
- Score each of the ten dimensions against the six level scale. Score what you can evidence today, not what is planned, funded or in flight.
- Where scoring is contested, take the lower level and record the disagreement. Contested scores are findings in their own right.
- Read the constrained level, not just the average. A gating dimension at Level 1 caps what the rest of the estate can deliver.
- Take the top three priority actions into a plan with a named owner and a date. Re run the assessment on the agreed cadence.
Scoring Scale
This assessment does not introduce a new scoring model. It scores every dimension on the six levels of the Product Data Maturity Model (TBF-024), with Level 0 added for work that has not started.
| Level | Name | What it means for any dimension |
|---|---|---|
| 0 | Not started | No deliberate work has been done on this dimension. |
| 1 | Collection | The information exists somewhere identifiable, even if only a person knows where. |
| 2 | Quality | The condition of the information is known, measured and written down. |
| 3 | Governance | It has a named owner, an agreed definition and rules for changing it. |
| 4 | Integration | It is drawn from an authoritative source rather than copied by hand. |
| 5 | Automation | Validation and publication run without manual effort. |
| 6 | Continuous improvement | Defects feed back into the rules, so the capability improves on its own evidence. |
Four dimensions are marked gating: regulatory applicability, product identification, authoritative data sources, and governance and ownership. A weak score in any of them limits the whole programme regardless of strength elsewhere, because passport content that cannot be scoped, identified, sourced or owned cannot be published defensibly. The tool reports this as the constrained level alongside the average.
The Assessment
Do you know which passport obligations apply to which of your products, in which markets, and from when?
What a Level 3 or better looks like, and the evidence to check
Applicability is assessed per product family and market, recorded with a date and a named owner, and re-checked when a delegated act or product change lands.
- A written applicability determination per product family
- The instrument and product specific measure each determination relies on
- A review trigger for new or amended delegated acts
Investigate further: Where the applicable product specific measure is not yet adopted, record the assumption and the date it must be revisited rather than scoring the dimension high.
Frameworks: TBF-005, TBF-006, TBF-007Which Products Will Require a Digital Product Passport?What Are Delegated Acts?
Can every in scope product, batch or item be identified unambiguously by a party outside your organisation?
What a Level 3 or better looks like, and the evidence to check
Identifiers are globally unique, assigned at the right level of granularity, allocated by a controlled process, and stable across systems and trading partners.
- The identification scheme in use and the level it applies at
- The register that records allocated identifiers
- The rule that decides when a change creates a new identity
Investigate further: If granularity is still undecided, treat that decision as the gap. Granularity chosen late is expensive to reverse.
Frameworks: TBF-012What is GS1?
Does the information a passport is expected to present actually exist in a state fit for publication?
What a Level 3 or better looks like, and the evidence to check
Each expected data category is graded as already held, held but not fit, obtainable, or not yet obtainable, and the grading is reviewed rather than assumed.
- A field level inventory of expected passport content
- A completeness measurement per product family
- A list of fields with no current source
Investigate further: Fields that nobody can locate are the most common cause of programme slippage. Record them explicitly rather than leaving them blank.
Frameworks: TBF-003, TBF-024What Information Does a Digital Product Passport Contain?How to Build a Trusted Product Data Foundation
For each field, is there one agreed system or party of record, and does everyone use it?
What a Level 3 or better looks like, and the evidence to check
Every published field maps to a single named system of record with an owner, and downstream copies are derived from it rather than maintained in parallel.
- A field to system of record map
- The named owner of each source
- Evidence that duplicates have been retired or marked derived
Investigate further: Two systems holding the same field with different values is not a data quality problem. It is an unresolved source of record decision.
Frameworks: TBF-023, TBF-042What Data Goes in a Digital Product Passport?What is Product Data Governance?
Can you obtain, refresh and rely on the information that only your suppliers hold?
What a Level 3 or better looks like, and the evidence to check
Suppliers are segmented by what they must provide, requirements are contracted, submissions arrive in a defined format, and refresh is scheduled rather than reactive.
- Supplier segmentation against passport data needs
- Contractual data and evidence clauses
- A submission and refresh calendar with response rates
Investigate further: Upstream tiers you have no direct relationship with usually need a different mechanism from tier one. Score them separately if the difference is material.
Frameworks: TBF-032How to Prepare Suppliers for Digital Product Passports
For claims that require proof, can you produce the underlying evidence, current and attributable?
What a Level 3 or better looks like, and the evidence to check
Evidence requirements are defined per claim, documents are associated with the product and version they support, validity dates are tracked, and expiry is detected before an authority finds it.
- An evidence register linked to claims
- Validity and expiry dates per document
- A defined acceptance step before a claim is published
Investigate further: A claim published without retained evidence is a compliance exposure even when the claim is true.
Frameworks: TBF-034How to Manage Evidence for Digital Product Passports
Will your identifiers, carriers and data structures be readable by parties who did not build your systems?
What a Level 3 or better looks like, and the evidence to check
Identifier, carrier and data model choices follow published standards, are documented as decisions, and have been tested with an external reader rather than only internally.
- The standards each choice conforms to
- A resolution route that works from a scan
- An external read test result
Investigate further: Standards work in this area is still settling. Record which parts of your design are standard and which are local convention.
Frameworks: TBF-012Standards and Technology
Can data move from the systems that own it to the surface that publishes it without manual re-keying?
What a Level 3 or better looks like, and the evidence to check
Interfaces exist between the systems of record and the publication surface, they run on a schedule or on change, and failures are visible to someone accountable.
- An integration map from source to published field
- Run frequency and failure alerting
- A manual fallback that is documented rather than improvised
Investigate further: Integration attempted before source of record decisions are settled tends to automate the disagreement rather than remove it.
Frameworks: TBF-024Enterprise Systems and Data Architecture
Is it clear who decides, who owns each data domain, and who is legally accountable?
What a Level 3 or better looks like, and the evidence to check
Decision rights, domain ownership and external legal accountability are separately named, and the difference between them is understood.
- A named executive accountable for passport obligations
- Domain owners for each data area
- A decision forum with a record of decisions
Investigate further: Internal ownership never rewrites statutory responsibility. Record both, and do not let one stand in for the other.
Frameworks: TBF-002, TBF-037How to Govern a Digital Product Passport ProgrammeWho Needs a Digital Product Passport?
Once published, can you keep passports correct, available and current through change, error and incident?
What a Level 3 or better looks like, and the evidence to check
Update, correction, withdrawal and incident routes exist and have been exercised, with availability monitored and retention understood.
- A correction and re-publication procedure
- Availability monitoring for the published surface
- A tested response to an incorrect published passport
Investigate further: Assurance testing before launch is not the same as operating capability after launch. Score what you can demonstrate, not what is planned.
Frameworks: TBF-011, TBF-035How to Operate a Digital Product Passport ProgrammeHow to Test and Assure a Digital Product Passport
There is no assessable passport capability yet. The first task is discovery, not delivery.
How To Interpret The Result
Read three numbers in this order. The constrained level is the honest ceiling: it is the lowest score among the four gating dimensions, and it describes what the programme can actually support today. The average level describes the breadth of the estate and is useful for tracking movement between assessments. The spread between the two tells you whether your problem is capability or sequencing.
Average high, constrained low: you have invested in the visible work and deferred a foundational decision, usually identification granularity or system of record. Reordering the plan will do more than adding resource.
Average low, constrained equal: the estate is early but coherent. Sequential progress across all ten dimensions is appropriate; do not attempt automation yet.
Several dimensions at Level 2: you know the condition of the estate but have not assigned ownership. This is the most common stall point and it is a governance task, not a technology one.
Any dimension above Level 4 while others are at Level 1: effort is being automated ahead of agreement. Automating a disputed field multiplies the dispute.
A high total score is not evidence of compliance. It is evidence of capability. Compliance is determined against the applicable legal instrument and the product specific measure that applies to your product, not against this assessment.
Related Frameworks And Knowledge
Individual dimensions link to further reading inside the tool itself, under each dimension’s detail panel.
Worked example: see this tool used end to end, alongside the other two Templates, in Example 01: From DPP Readiness to Defensible Supplier Evidence.
Limitations And Regulatory Caution
- This assessment measures organisational capability. It does not determine legal applicability, and completing it does not establish compliance with any instrument.
- Product specific requirements are set by delegated acts and equivalent measures that are still being adopted. Scope, data content and timing can change after you score.
- Scores are self reported. Where a score cannot be evidenced, treat it as one level lower until it can be.
- Averaging across business units, product families or markets hides the weakest unit. Assess each separately where they differ materially.
- This is not legal advice. Applicability determinations should be confirmed with qualified regulatory or legal advice for your products and markets.
Related Articles
- Supplier Evidence Register
- Passport Data Origin Worksheet
- From DPP Readiness to Defensible Supplier Evidence: A Worked Manufacturer Example
- How Should Organisations Prepare for Digital Product Passports?
- Product Data
- DPP Governance: Who Owns What?
- How Will Digital Product Passports Change Product Compliance?
- Sustainability Data
References
- Regulation (EU) 2024/1781 (Ecodesign for Sustainable Products Regulation), Chapter III on the Digital Product Passport: https://eur-lex.europa.eu/eli/reg/2024/1781/oj
- tieback Knowledge, “How to Build a Trusted Product Data Foundation” (TBF-024, the maturity scale used by this assessment): https://tieback.io/docs/knowledge-base/enterprise-systems-and-data-architecture/how-to-build-a-trusted-product-data-foundation
- tieback Knowledge, “How Should Organisations Prepare for Digital Product Passports?” (TBF-011): https://tieback.io/docs/knowledge-base/implementation/how-should-organisations-prepare-for-digital-product-passports
About This Article
tieback Knowledge is a continuously maintained reference library covering Digital Product Passports, product traceability, product compliance and related regulations. Articles are reviewed regularly as legislation, standards and implementation guidance evolve.