Ask any importer who has started on the battery passport where the time went, and the answer is the same: waiting for supplier data. The passport software exists. The 71 data points are published in the Commission's guidance (v3.2, 19 October 2026). What doesn't exist yet, in most companies, is a reliable way to get those values out of a cell maker in Shenzhen, a pack assembler in Vietnam and a test lab that only answers by email.
This playbook is how we run that work: in two 14-day sprints, side by side with the importer's team. You can run it yourself with the same steps.
Before the sprints: one hour of preparation
Pick one product line. Don't start with the whole catalogue. Pick the model you ship most, or the one whose next container arrives after 18 February 2027.
Collect what you already have. Datasheets, the safety data sheet, the declaration of conformity, UN 38.3 transport test summaries, test reports, label artwork, ERP exports. You'll typically find 40–60% of the public data points in documents that are already in your inbox.
Name one person on each side. One person in your team who can make decisions, and one contact at each supplier who can answer technical questions. Most delays come from questions sent to a general sales mailbox.
Sprint 1 (days 1–14): map, find the gaps, ask once
Days 1–3: map what you have
Map every value you already hold to the 71 data points, per battery category. You'll see three groups:
- Complete: the value is in a document and fits the data point as defined.
- Ambiguous: a value exists but doesn't match the definition. A typical example: a "cycle life" figure without the test conditions behind it, where the passport needs cycle life to 80% state of health and the C-rate of the test (#31, #39).
- Missing: nothing in your documents.
Days 4–5: write one structured request per supplier
Suppliers answer specific questions and ignore questionnaires. One request per supplier, containing only what that supplier holds:
- Cell maker: chemistry and active materials (#12, #46), hazardous substances (#13), critical raw materials (#15), cell internal resistance (#38), cycle life test conditions (#31, #39).
- Pack assembler: manufacturing plant and date logic (#8, #9), mass and rated capacity (#10, #11), voltages and power (#26–#30), temperature range (#34), dismantling information and safety measures (#48, #49), spare parts (#47).
- Test lab: the performance and durability test report (#50), which is read only by authorities but has to exist, and the reference test behind the published figures (#32).
Each question names the data point, the unit and an example answer. "Rated capacity in Ah, as on the label, e.g. 13.4 Ah" gets answered. "Please provide battery specifications" doesn't.
Days 6–14: follow up and check every answer
Answers come back incomplete. Check each one against three rules:
- Is it the right quantity? Nominal and rated aren't the same thing; pack and cell values aren't interchangeable.
- Is it consistent? Rated capacity times nominal voltage should roughly match the energy on the label. Mass should match the transport documents.
- Is there evidence? A value with a source document beats a value typed into an email.
Send per-field follow-ups: "#36 round-trip efficiency: you gave 0.95 without test conditions; please add the reference test." By day 14 you should have a gap list per supplier that is short and specific, with a date next to each open item.
Sprint 2 (days 15–28): close the gaps, build the passports
Days 15–21: close or decide
For each open item, one of three things happens:
- The supplier delivers.
- You derive it from evidence you hold, documented as such (e.g. the separate-collection symbol from the label artwork).
- You escalate. The importer, not the supplier, carries the obligation, and Article 41 requires importers to make sure the manufacturer has met its obligations before placing the battery on the market. A missing mandatory value is a reason to hold a shipment, and suppliers respond to that.
Days 22–28: build, check, prepare registration
With the model data complete: build the model passport, check it against the Commission's battery schemas, issue unit passports for the serial range, send the QR print files to the factory, and prepare the registration in the EU DPP Registry, which needs your organisation verified there.
What not to ask for yet
The v3.2 guidance marks several data points as "not to be filled" for February 2027: the carbon footprint, supply-chain due diligence and recycled-content shares. The due-diligence obligation itself has been pushed to 2027. Asking suppliers for these now costs goodwill and time you need for the mandatory points. Ask once you have the mandatory set, and frame it as "we will need this later."
When a supplier goes quiet
It happens in every project. What works, in order:
- Ask a smaller question. Three specific fields by Friday, not the whole list.
- Offer a form instead of a spreadsheet. A structured web form with autosave and file upload gets better answers than an Excel attachment that comes back with merged cells.
- Go through purchasing. A note from the buyer that the next purchase order depends on the data moves faster than any technical email.
- Plan another sprint, not an open-ended wait. If data is still missing after sprint 2, run another 14-day sprint with a fixed list and fixed dates.
How we run it
This is the work we do for importers. You send what you have, and a named specialist runs both sprints with your team. Supplier requests go out as structured forms that suppliers can save, complete and attach files to, without an account. Every answer is checked and reviewed by a person, per-field change requests go back to the supplier, and nothing reaches the passport until you've approved it. If supplier data is still missing after sprint 2, we run another 14-day sprint until it's in.
Start with the free 71-point checklist to see your own gaps, or book a kick-off call.
Not legal advice. The regulation text is binding.