Frameworks define what to disclose. Traceability proves what happened.

Battery Passport Readiness Starts with 71 Data Decisions

The battery passport is often presented as a digital interface. The harder task is organisational: deciding which data applies, where it originates, who can substantiate it and how it remains current. New Commission guidance provides a practical map of 71 data points, creating a useful basis for testing ownership before passport duties begin in February 2027.

The guidance turns a large requirement into a map

On 21 August 2026, the European Commission published updated guidance to support digital battery passport preparation. It compiles 71 data points and classifies them as mandatory, optional, conditional or not required, with links to their legal sources. The Commission also warns that the guidance is not legally authoritative and may be updated.

The Commission’s battery passport sector page states that passports apply from 18 February 2027 to electric-vehicle batteries, light-means-of-transport batteries and industrial batteries above 2 kWh.

A data-point list is a planning tool, not permission to freeze the interpretation. Readiness needs version control for the guidance as well as for the data.

Applicability comes before collection

Teams can waste months collecting every imaginable field without deciding which batteries and obligations are in scope. Start by identifying battery category, model, economic-operator role and the conditions that make each field applicable.

Battery categoryModel identityOperator roleMandatory fieldConditional triggerLegal source

Store the applicability decision with its source and date. If the interpretation changes, the organisation can update the result without losing why the earlier decision was made.

Every field needs a source and an accountable owner

The 71 data points will not come from one system. Technical specifications may sit with engineering, material composition with suppliers, conformity evidence with compliance teams and lifecycle information with service or recovery partners. A passport programme therefore needs a field-level responsibility matrix.

For each applicable point, name the system of record, evidence owner, update trigger, access level and reviewer. “Supplier data” is not an owner. The record should identify which supplier, which contract or declaration, which version and which battery model the evidence covers.

Ownership should include a response when evidence is late or contradictory. Procurement may request the source, engineering may test plausibility and compliance may decide whether the field is usable. Recording those roles prevents a data-integration team from becoming the unacknowledged legal interpreter. It also makes escalation possible before a production passport contains a value that nobody is prepared to defend.

The passport is only as current as the least-governed upstream field.

Conditional data needs executable rules

A conditional field should not depend on someone remembering an exception. The business needs a documented trigger and a test that can be repeated when product characteristics or regulations change.

For example, a change in capacity, chemistry, component supplier or intended market may alter the data or evidence required. The change process should identify affected passports, preserve the prior version and publish the correction through the appropriate access route.

Trigger ruleAffected productsEvidence requestReviewVersion updatePublication status

Test access and confidentiality together

Battery passport information may have different access rights. A useful pilot tests public, restricted and competent-authority views rather than placing all information behind one QR code. It should also prove that a service failure, provider change or corrected field does not break the link between the battery identifier and its passport.

Access testing is part of evidence governance. The wrong restriction can hide required information; an overly open design can disclose commercially sensitive records. Both failures should be discovered before production scale.

Build a 71-point readiness register

Create one row for every guidance data point and record applicability, legal reference, source, owner, evidence status, access class, update trigger and last review. Pilot the register on one real battery model, including at least one corrected source document and one conditional field.

Finish with a gap register that distinguishes missing evidence, unresolved interpretation, integration work and information deliberately awaiting a later Commission update. This avoids converting uncertainty into false completeness. Review the register with engineering, procurement, compliance and service teams so that ownership works across the full battery lifecycle rather than only at launch.

The useful readiness metric is not “71 fields filled”. It is “every applicable field has a governed source, owner and change path”.
A passport displays product information. Governance makes that information dependable.
Start the conversation

How can we transform your waste?

Tell us what you have and what you need. We assess your waste streams and structure a tailored programme, before you commit to scale.

Free Waste Assessment →