How long does a DPP take? Days for the data entry — weeks for the evidence you don’t have yet.

Ask how long a Digital Product Passport takes and you’ll hear everything from "an afternoon" to "a year". Both can be true, because the duration isn’t set by the software — it’s set by where your data currently lives. This page breaks the work into its real components, gives ranges you can plan around without wishful thinking, and explains which parts tooling genuinely compresses and which parts only a calendar can solve.

In one line: a first passport can be assembled in days when the documents are at hand; plan in weeks when supplier evidence must be chased — and start 6–12 months before your deadline so the chasing happens on your schedule, not customs’.

What actually drives the duration

A passport is assembled from data, and four factors set how long the assembly takes:

How scattered the data is. The required information almost always exists — in spec sheets, certificates, test reports, supplier declarations and ERP fields — but rarely in one place. Locating it is the first real cost.
How many fields the product group demands. A battery passport runs to roughly 110+ data points across identity, chemistry, carbon footprint, due diligence, performance and circularity; other product groups will define their own lists via delegated acts.
How much evidence must come from third parties. Anything requiring a supplier to produce, sign or confirm a document moves at the supplier’s pace, not yours.
How many products you have. The first passport carries all the setup cost; siblings in the same product family reuse most of it.

Realistic ranges — without the sales gloss

With that structure in mind, honest planning figures look like this. If the documents are already in your hands — complete technical file, current declarations, test reports on disk — a first passport is a matter of days: extract, review, structure, publish. If material data must be requested from suppliers, budget weeks, dominated by response times you don’t control; a single missing carbon-footprint calculation or due-diligence attestation can hold an otherwise finished passport open. Complex products with deep supply chains sit at the long end. We deliberately give ranges rather than a single number: anyone quoting one duration for every product is describing their demo, not your supply chain.

What AI extraction compresses — and what it can’t

The part of the work that tooling genuinely collapses is data entry. Reading a 40-page specification, finding the twelve relevant values and keying them into the right fields is exactly what PassPer’s AI extraction does with the documents you already hold — spec sheets, certificates, supplier declarations — with a human reviewing every extracted value before it enters the passport. Sealing (eIDAS qualified seal), the GS1 Digital Link QR and registry filing are likewise automated rather than manual steps.

What no software compresses is the wait for evidence that doesn’t exist yet. If a supplier has never produced a due-diligence report, the tool can tell you it’s missing on day one — which is valuable — but the report still has to be written. Good tooling moves the discovery of gaps to the start of the project instead of the end. That is where most of the calendar time is actually saved.

Why 6–12 months of runway is sane, not cautious

Work backwards from a hard date — say the battery passport’s 18 February 2027. Goods manufactured months before they reach the EU market need compliant passports at placement, so your real deadline is when the relevant production run ships, not when the regulation bites. In front of that sit the slow items: supplier requests, evidence that must be produced from scratch, and the review loop when a document comes back wrong.

Starting 6–12 months out doesn’t mean 6–12 months of effort — most of that span is waiting you’ve made harmless by starting early. Run the gap analysis first (a free readiness check takes minutes), fire off supplier requests in week one, and let the passports assemble themselves as evidence arrives. The teams under pressure in 2027 will be the ones who discovered their gaps in 2027.

Frequently asked questions

Can a Digital Product Passport really be created in a day?

The data-entry part, yes — if every required document is already in your hands, extracting the fields and assembling the record is fast, especially with AI extraction and human review. What no tool can compress is the wait for documents you don’t yet have: a missing test report or supplier declaration adds however long that supplier takes to respond.

Why do battery passports take longer than most?

Scale and sourcing. A battery passport runs to roughly 110+ data points across identity, chemistry and materials, carbon footprint, due diligence, performance and circularity — and several of those blocks depend on evidence from upstream suppliers, not from your own files. The DIN DKE SPEC 99100 guidance helps structure the work, but the supplier dependency is what sets the calendar.

What is usually the slowest part?

Evidence collection. In our experience the pattern is consistent: fields you can fill from documents on hand take hours; fields that need a supplier to produce or confirm something take weeks, because you are waiting on someone else’s queue. Duration is set by your slowest supplier, not by your own team.

Does the second passport go faster than the first?

Substantially. The first passport forces you to locate every data source, build the supplier contact list and settle open questions; subsequent products in the same family reuse most of that structure and shared data. The first one is a project; the rest are a process.

See where you stand — three ways, all free.

Take the 2-minute readiness check, watch the 10-minute interactive walkthrough, or download the full 2026 compliance guide. No account needed.

Free readiness check → See it in action Get the guide (PDF)