A product team can often find a product name, a specification sheet and a QR code quickly. What usually takes longer is proving where each material claim came from, whether supplier documents relate to the correct product version, and who is accountable for keeping the record current. A Digital Product Passport is not simply a new product webpage or a code attached to packaging. It is a structured way to prepare, connect and maintain product information, traceability data and supporting evidence for applicable EU requirements. Precise requirements, timelines and data fields depend on the product group and the measures that apply. This is general guidance, not legal advice.
What a DPP readiness assessment is designed to do
A DPP readiness assessment is a structured diagnosis of whether an organisation can assemble and maintain the product information needed for Digital Product Passport preparation. It tests operational capability, not just the existence of documents.
The assessment should reveal whether information is complete enough for its intended use, whether its source can be identified, whether it can be connected to the relevant product or batch, and whether a named owner can resolve gaps. A spreadsheet full of supplier declarations may be useful, but it is not automatically evidence that is current, attributable or traceable to a specific product configuration.
The result is not legal certification, regulatory approval or proof of compliance. It is a prioritised picture of readiness: what is available, what is missing, what needs validation and what action should happen next. DPPLogic model 1.0.0 scores six operational dimensions from a self-report. A high score does not mean a passport is required.
- Common misconception
Readiness is not an official EU certification or a notified-body mark.
- Common misconception
A readiness score is not a legal compliance determination.
- Common misconception
Having a QR code, a field list or a software licence is not readiness by itself.
Readiness, compliance and certification
Operational diagnostic
Self-reported capability to prepare data, evidence, systems and owners. DPPLogic model 1.0.0 and Quick Check qc-1.0.0 live here.
Conformity with an applicable act
Exists only when a product is covered by an adopted measure and the duties in that measure are met. A readiness score cannot establish this.
Third-party or notified-body confirmation
Where a product measure requires conformity assessment, that is a separate legal process. DPPLogic does not issue certificates.
Confirmed requirements and developing measures
Confirmed: Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation, establishes a framework under which Digital Product Passport requirements can be set through product-specific delegated acts. It creates the direction of travel. It does not mean every product category has identical live passport obligations today.
Confirmed for specified batteries: Regulation (EU) 2023/1542 Article 77 requires a battery passport for each LMT battery, each EV battery and each industrial battery with capacity greater than 2 kWh placed on the market or put into service from 18 February 2027. A QR code duty from the same date is a separate Article 13(6) obligation. Not every battery needs an Article 77 passport. Teams should read the Regulation on EUR-Lex against their products and their supply-chain role.
Developing: for textiles, apparel, electronics and other ESPR groups, detailed product-specific requirements still depend on later measures. Iron and steel remain early preparation. Do not treat anticipated fields, market commentary or generated suggestions as adopted law.
Preparation: the absence of a final category-specific rule is not a reason to wait. Product data structures, supplier evidence, document controls and internal ownership take time to establish. Preparing those foundations reduces the risk that a future requirement exposes a problem that is difficult to fix at scale.
The six live readiness dimensions
A credible assessment follows information through the business, from product definition to supplier evidence, technical systems and accountable decision-making. Model 1.0.0 scores these six dimensions only. Do not treat a seventh theme as a live score. Each dimension has five Full Assessment questions. A passport record is only as dependable as the weakest connection in that chain.
Product data
Identifiers, models, variants, bills of materials, composition, technical characteristics, lifecycle-related attributes, quality, provenance, ownership and versions.
Supplier data
Supplier identity, facility and material information where relevant, declarations, certificates, responses, defined requests, validation and follow-up.
Traceability
Links between product, component, material, batch, supplier and supporting record, at the granularity required for the intended use.
Evidence
Source, issue date, scope, version, product relationship, reviewer status, retention, searchable files and access controls.
Systems
Where information is held, how records are matched, whether data moves reliably, how changes are controlled and which source is authoritative.
Governance
Named owners, approval routes, escalation, remediation deadlines, sourced applicability decisions, roadmap and ongoing review.
A preparation path, not a legal sequence
These dimensions are interdependent. A manufacturer may have detailed composition data but no reliable way to associate it with the supplier declaration that supports it. Another may receive good documents from suppliers but lack a stable product identifier shared across procurement, product development and enterprise systems. Neither issue is solved by generating a QR code.
Use this path to organise work. The legal result remains the applicable instrument, the product-specific measure and the application date.
- Understand what applies
- Assess readiness
- Identify gaps
- Take action
- Prepare the passport
- Monitor change
How to run the assessment without creating another reporting exercise
Start with a defined product population. It may be one battery line, a set of textile styles or a representative group of electronic products. A narrow, realistic scope exposes the actual flow of information better than a broad questionnaire completed from memory.
- Build a structured supplier data request
- Digital Product Passport data requirements
- Digital Product Passports for EU manufacturers
- Digital Product Passports for EU importers
| Step | What to do | Do not |
|---|---|---|
| 1. Scope | Record products, markets, legal-entity roles and expected milestones. Distinguish confirmed obligations from preparation assumptions. | Collect every imaginable field without knowing why it is needed or which product it relates to. |
| 2. Provenance | For every material data point, ask separately: is it available, is it fit for the claimed purpose, and can you show the source and product version? | Mark a recycled-content figure complete because it appeared in a supplier email. |
| 3. Hand-offs | Map the journey from supplier request to product record, review and passport preparation. Look for rekeying, conflicting identifiers and files in personal folders. | Assume a QR package will reconcile identifiers after a design change. |
| 4. Owned gaps | Give each gap an owner, action, due date, dependency and the evidence that will close it. | Stop at “supplier declarations inconsistent” with no request method or escalation. |
| 5. Reassess | Repeat when products, rules or suppliers change. Use a proportionate cadence based on product risk and regulatory maturity. | Treat readiness as a one-off project that expires into a static file. |
How the DPPLogic assessment works
The Quick Check (qc-1.0.0) asks ten questions and returns an immediate directional result. The Full Assessment asks 30 questions across the six dimensions and produces a conservative self-reported score, category view and recommended next actions.
Every question and category has equal weight in model 1.0.0. Not sure earns no readiness credit and is treated as an evidence-verification gap. High classifications require balanced category performance, not only a high average. The result renders without a generative AI service. The public guidance and readiness assessment are deterministic. The DPPLogic workspace does not use runtime AI on your data: values, evidence references and review decisions are entered and made by people, on every plan. DPPLogic does not publish passports, and a general-purpose generative or regulatory assistant is not offered.
If document classification or field suggestions are added later, those outputs would still require human review, source checking and an approval process. A suggestion is not evidence, and a complete-looking record is not a compliance determination.
What good readiness looks like in practice
Good readiness does not mean that every record is complete before detailed product rules exist. It means the organisation can state its position honestly and act on it. Teams can identify the applicable product and version, locate the relevant source documents, explain what each document supports, identify missing information and assign the next action to a responsible person.
This is especially valuable where supplier networks are complex. A request for data should not disappear into an inbox with no connection to the product record. It should be tied to a supplier, a request status, the expected evidence and a decision on whether the response is accepted, incomplete or rejected.
The practical test is simple: when a colleague asks why a product claim would appear in a future passport record, can the team show the source, the product relationship, the review status and the responsible owner? If not, that is a starting point for work that can be assigned, evidenced and maintained.
Using assessment results to prepare passport records
Once gaps are visible, organise work in sequence. First stabilise product identifiers and core product data. Then collect and review priority supplier information, attach evidence to the relevant product or component, and resolve exceptions through controlled remediation. Passport preparation should draw from these maintained records, rather than becoming a separate data collection exercise at the end.
DPPLogic supports this route with the ten-question diagnostic and the 30-question assessment across the six live dimensions. Platform outputs remain preparation records, not legal certification.
| If the result shows | Do this next | Do not |
|---|---|---|
| Unknown applicability | Classify the product against adopted instruments and Working Plan status. | Treat a vendor checklist as the legal answer. |
| Weak product or supplier data | Name owners, identifiers and a request process before buying a generator. | Assume a QR package will invent missing evidence. |
| Weak evidence or systems | Build a searchable register and a source-of-truth map. | Equate file storage with controlled evidence. |
| Weak governance | Write sources, assumptions, owners and a review date. | Call the score a compliance certificate. |
Primary and authoritative sources
Source links are provided for verification. Scope, consolidated versions and later measures should be checked again before implementation or reliance.
Regulatory disclaimer. This content provides general diagnostic and preparation information. It is not legal advice, certification or regulatory approval. Requirements may differ by product category, jurisdiction, market and supply-chain role and may change over time.