Days 1–30: map products, markets and requirements
Create an inventory of product families, brands, models and markets. Identify the business role for each product—such as manufacturer, importer or supplier—and assign a regulatory owner to check which EU legislation applies.
Build a requirements register with source links and status labels such as confirmed, expected or under review. Include the relevant product-specific act when available, rather than copying dates from a generic roadmap. Use this phase to choose one pilot product with manageable data complexity.
Days 31–60: map data and suppliers
For the pilot, list data fields, systems of record, data owners, suppliers and evidence. Note units, reporting periods, calculation methods and whether each value is measured, estimated or verified. Keep missing information visible so that teams can prioritize real follow-up.
Agree a supplier request template and secure way to exchange documents. Connect materials and components to the right product version, and decide who approves changes before data is published or shared.
Days 61–90: test a passport workflow
Test the workflow with internal users and a small number of suppliers. Check whether data can be traced back to its evidence, whether users see only the information intended for them, and how the team handles corrections and updates.
At the end of the pilot, record what took time, what could not be verified and which integrations would remove repetitive work. Use those findings to build a realistic rollout plan. The objective is a repeatable data process—not a claim that a product is compliant simply because a passport page exists.
- Keep official legal sources in the requirements register.
- Treat supplier data quality and document expiry as ongoing work.
- Review the plan whenever a product-specific rule changes.
Official sources
Organizing product information for your DPP work?
Talk through your use case