> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://tieback.io/docs/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server. # DPP Readiness Assessment > A vendor neutral ten dimension assessment that scores how prepared an organisation is for Digital Product Passport implementation and shows where the gaps are. This is a practical tool, not a canonical Knowledge article and not a [tieback framework](/docs/knowledge-base/frameworks/overview). 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. ## 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 ## Scoring Scale 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 ## 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. > **Note** > > Worked example: see this tool used end to end, alongside the other two Templates, in [Example 01: From DPP Readiness to Defensible Supplier Evidence](/docs/knowledge-base/examples/readiness-to-evidence-manufacturer-example). ## Limitations And Regulatory Caution ## Related Articles * [Supplier Evidence Register](/docs/knowledge-base/templates/supplier-evidence-register) * [Passport Data Origin Worksheet](/docs/knowledge-base/templates/passport-data-origin-worksheet) * [From DPP Readiness to Defensible Supplier Evidence: A Worked Manufacturer Example](/docs/knowledge-base/examples/readiness-to-evidence-manufacturer-example) * [How Should Organisations Prepare for Digital Product Passports?](/docs/knowledge-base/implementation/how-should-organisations-prepare-for-digital-product-passports) * [Product Data](/docs/knowledge-base/glossary/product-data) * [DPP Governance: Who Owns What?](/docs/knowledge-base/compliance-frameworks/dpp-governance-who-owns-what) * [How Will Digital Product Passports Change Product Compliance?](/docs/knowledge-base/standards-and-technology/how-will-digital-product-passports-change-product-compliance) * [Sustainability Data](/docs/knowledge-base/glossary/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](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](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](https://tieback.io/docs/knowledge-base/implementation/how-should-organisations-prepare-for-digital-product-passports) ## About This Article About This Article
Last Reviewed
2026-08-10
Next Scheduled Review
2027-08-10
Article Version
1.0
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. ## Page Metadata | Field | Value | | ------------- | ----------------------------------------------------------- | | Asset type | Template / practical tool | | Published | 2026-08-10 | | Last Reviewed | 2026-08-10 | | Version | 1.0 | | Reading Time | 9 min | | Author | tieback Editorial Team | | Category | Templates | | Tags | readiness, assessment, maturity, governance, implementation | ## Related Docs * [Templates](/docs/knowledge-base/templates/overview) * [tieback Framework Library](/docs/knowledge-base/frameworks/overview) * [Implementation](/docs/knowledge-base/implementation/overview) * [Governance & Assurance](/docs/knowledge-base/compliance-frameworks/overview) * [Example 01: From DPP Readiness to Defensible Supplier Evidence](/docs/knowledge-base/examples/readiness-to-evidence-manufacturer-example)