Scoring scale
- 0 — Not started: information is absent or depends on informal knowledge.
- 1 — Partial: data or activity exists, but without full coverage, standards or an owner.
- 2 — Governed: the process has an owner, evidence, controls, documentation and update rules.
The twelve controls
Product scope
Category, use, markets, variants and applicable legislation are classified and documented.
Company role
Manufacturer, importer, representative, distributor and other roles are defined for the real case.
Granularity and identifiers
The model, batch or item level is defined and connected to master data.
Data dictionary
Fields, definitions, units, formats, conditions and vocabularies are held in a controlled model.
Sources and data owners
Each field has a source, accountable owner, approver and update rule.
Evidence
Values and claims are linked to documents, tests, methods, versions and validity dates.
Suppliers
Specifications, portal, deadlines, exceptions and change notifications support supply-chain collection.
Access and confidentiality
Public, B2B, authority and recycler information is separated with verifiable permissions.
Workflow and versions
Contribution, checking, approval, publication and changes are traced.
Carrier and user experience
QR/NFC, resolver, domain, readability, accessibility and continuity have been tested.
APIs and Registry
Export, integrations, registration, error handling and registration proof are designed.
Continuity and governance
Backup, portability, retention, accountability and provider-change arrangements are defined.
Interpreting the score
| Score | Interpretation | Priority |
|---|---|---|
| 0–8 | Early preparation | Define scope, owners and a pilot product before selecting tools. |
| 9–16 | Elements exist but are fragmented | Standardise data, suppliers, evidence and approvals. |
| 17–21 | Good operational base | Test identifiers, lifecycle, APIs, access and registration end to end. |
| 22–24 | Governed process | Verify legal coverage, scalability, auditability and continuity. |
The score is a prioritisation tool, not a certification. A single zero on a critical requirement may matter more than the total. A visually complete passport without stable identity or evidence remains weak.
The minimum viable pilot
A useful pilot does not need the whole catalogue, but it should cover the complete workflow:
- one clearly identified product and variant;
- at least one internal or external supplier;
- a dataset containing public and restricted fields;
- real documents and evidence;
- a contribution, review and approval sequence;
- a carrier applied to or simulated on the product;
- an accessible mobile passport page;
- a change that creates a second version;
- an export or API integration;
- a registration test where relevant and available.
A 90-day operating plan
Product, legislation, roles, identifiers and objectives.
Dictionary, sources, evidence, access and suppliers.
Workflow, templates, portal, page and carrier.
Version, API, Registry, gap audit and scale plan.
Five mistakes to avoid
- Starting with the QR code. Carrier comes after identity, data and accountability.
- Confusing a roadmap with a duty. Dates must come from the applicable act.
- Uploading documents without structure. A repository is not a data model.
- Delegating every decision to software. Data ownership and conformity decisions remain with the business.
- Ignoring updates. The DPP is a service over time, not a static page.
Expected pilot outputs
At the end of the project, the business should have a regulatory matrix, data dictionary, source map, RACI, supplier template, published passport, validation report, gap register and an estimate for extending the model to other product families.
NexusDPP can configure this path in the platform and measure collection time, completeness, exceptions and dependency on manual documents.
References for the assessment
- Regulation (EU) 2024/1781 — ESPRGeneral DPP framework and system requirements.
- Commission Implementing Regulation (EU) 2026/1778EU DPP Registry arrangements.
- Commission Implementing Decision (EU) 2026/1736Harmonised infrastructure and interoperability standards.
The checklist is an organisational method and should be adapted to the product category, company role and applicable legislation.