What data a battery passport needs

If you are asking what data is needed for a battery passport, the short answer is this: enough verified information to identify the battery, prove what it is made of, show where key materials came from, document its environmental footprint, and support safe use, repair, reuse and recycling. A battery passport is not just a product label in digital form. It is a structured record that follows the battery through manufacturing, sale, use and end-of-life handling.

In practice, that means pulling together technical specifications, compliance evidence, supply chain data, due diligence records, carbon footprint information, and lifecycle event data in a way that different parties can access and trust. The exact fields depend on battery type, market and legal scope, but the logic is consistent across categories: the passport must help regulators, customers, operators, repairers and recyclers make decisions based on reliable data.

A battery passport exists to make a battery legible across its whole lifecycle. It should allow a person or system to answer four basic questions quickly.

First, what exactly is this battery? That requires unique identification and core product data.

Second, does it comply with the rules that apply to it? That requires conformity, safety and due diligence information.

Third, where did it come from and what happened to it? That requires traceability from raw materials through manufacturing, distribution, use and end-of-life processing.

Fourth, what should happen next? That requires practical data for maintenance, repair, repurposing, dismantling, collection and recycling.

Under the EU Batteries Regulation, battery passports are part of a wider compliance and transparency framework for certain battery categories, especially industrial batteries, electric vehicle batteries and light means of transport batteries as the detailed rules phase in. The EU framework is the main reference point because it creates the passport obligation for batteries placed on the EU market. The UK is not applying the same battery passport regime today in the same way as the EU, but UK manufacturers and exporters selling into the EU still need to meet EU requirements for batteries placed there. If you need the cross border position set out clearly, our guide to battery passport rules before selling from the UK into the EU explains where the distinction matters.

The data in the passport therefore needs to do more than satisfy a checklist. It has to support a chain of use cases. Customs and market surveillance authorities may need to verify identity and compliance. OEMs and buyers may need to compare performance and sustainability attributes. Service teams may need to confirm configuration and maintenance history. Recyclers may need to know chemistry, hazardous content and dismantling instructions. If the data cannot support those decisions, the passport is not doing its job.

The first block of data is basic identification. Every battery passport needs a unique identifier that can be linked to a physical battery through a data carrier such as a QR code or equivalent machine readable method. That identifier should resolve to a stable record and should distinguish one battery model, batch or individual unit from another, depending on the applicable rules and the level of granularity required.

We normally expect this identification layer to include:

• Battery name or commercial designation
• Model number
• Product code or SKU
• Unique battery identifier
• Manufacturer name and contact details
• Manufacturing site, where relevant
• Date of manufacture
• Batch, lot or serial number
• Battery category, such as EV, industrial, LMT or portable where applicable
• Market destination or placing-on-market information where needed for compliance management

Then comes the technical profile. This is the data that tells users what the battery is and how it is expected to perform. Typical fields include:

• Battery chemistry, for example lithium-ion with more specific chemistry where available
• Electrochemical composition
• Nominal voltage
• Rated capacity
• Energy in Wh or kWh
• Power capability
• Weight
• Dimensions
• Cell, module and pack architecture where relevant
• Expected cycle life or durability metrics
• Operating temperature range
• Charging parameters
• Safety limits and protection features
• Intended application or use case

For industrial and EV batteries, the intended use matters. A battery designed for traction, stationary storage or industrial machinery may have different duty cycles, safety conditions and end-of-life routes. The passport should make that clear.

Where legislation or delegated acts require specific performance and durability values, those should be recorded in the exact format required, not paraphrased into marketing language. The passport is not a brochure. It is a compliance and operational data asset.

It is also good practice to link the technical data to the source document that governs it, such as the product specification, declaration of conformity, test report, bill of materials, or approved engineering release. That way, if a value changes after requalification or redesign, the update process is controlled.

The next major category is composition and sourcing. A battery passport needs to say enough about the materials in the battery to support legal compliance, responsible sourcing and downstream handling.

At a minimum, that usually means identifying the key raw materials and active materials used in the battery. For many batteries, this will include metals such as lithium, cobalt, nickel, manganese, graphite, copper and aluminium, depending on the chemistry and construction. It may also include hazardous substances or substances requiring specific handling information.

Material data often needs to cover:

• Material types and composition
• Mass of key materials
• Presence of critical raw materials
• Recycled content, where required
• Hazardous substance information
• Safe handling information relevant to dismantling and recycling

Origin data is separate from composition data. Knowing that a battery contains cobalt is not the same as knowing where that cobalt came from. For due diligence and traceability, businesses may need to capture:

• Country of origin for relevant raw materials
• Smelter, refiner or processor identity where available
• Supplier names and tiers
• Chain of custody references
• Procurement records and declarations
• Risk assessment outputs
• Corrective action records where risks were identified

Under the EU framework, due diligence obligations for certain economic operators are tied to battery raw materials and supply chain risk management. That means the passport may need to connect with a due diligence system rather than duplicate the whole file. In practice, we usually structure this as a combination of disclosed passport fields and linked evidence records held in the compliance system.

The key point is that the passport should not rely on a single supplier declaration with no supporting trail. If you are asked to prove origin, recycled content or responsible sourcing, you need traceable evidence. That may include supplier questionnaires, contractual flow-down clauses, audit findings, mass balance records, certificates, transport documents and internal approvals.

This is one of the reasons many businesses move away from spreadsheets once battery passport work becomes real. Material and sourcing data changes across suppliers, plants and versions. A controlled system is far better for maintaining data lineage, approvals and audit history. If you are comparing approaches, our article on choosing a digital product passport system in the UK covers the practical issues that matter when compliance data has to stay usable.

A battery passport may also need to carry environmental performance data, especially around carbon footprint. For batteries placed on the EU market, carbon footprint rules are being introduced through category-specific requirements and implementing measures. The exact disclosure points and timing depend on battery type and the relevant legal provisions, but the direction is clear: carbon data must be structured, comparable and linked to a defined methodology.

In practice, that means recording enough data to support the declared carbon footprint value and any associated class or threshold once those apply. Relevant data can include:

• Carbon footprint result for the battery
• Scope and system boundary used
• Functional unit
• Lifecycle stages included
• Data collection period
• Primary and secondary data sources
• Manufacturing energy inputs
• Transport assumptions
• Allocation rules
• Verification status
• Reference to the underlying calculation or declaration

It is also common to hold supporting sustainability data that may not always sit in the public facing layer of the passport but still needs to be linked to it, such as:

• Electricity mix used in manufacturing
• Renewable energy sourcing claims and evidence
• Water use, where relevant to internal reporting or customer requirements
• Waste generation and treatment data
• Environmental management certifications at site level
• Substance restriction compliance records
• Social or human rights risk controls linked to due diligence

The level of disclosure should match the legal requirement and the sensitivity of the data. Not every underlying dataset belongs in open view. But the passport should make clear what has been declared, who declared it, to which methodology, and when it was last validated.

This is also where businesses often struggle with version control. Carbon data can change if the product design changes, if the manufacturing site changes, if the electricity mix changes materially, or if the calculation methodology is updated. A battery passport therefore needs effective date logic. Users should be able to tell which data applied to which battery placed on the market at which time.

A useful battery passport does not stop at manufacture and sale. It should support the use phase and the end-of-life phase as well.

For use phase tracking, the exact data depends on the battery category and business model. Some batteries remain in tightly managed fleets or industrial assets, where operational records are available. Others are sold through distribution channels with limited downstream visibility. Where lifecycle data is captured, it can include:

• Installation date
• Commissioning status
• Asset or equipment association
• State of health metrics
• Usage cycles
• Maintenance events
• Software or firmware version where relevant
• Repair history
• Safety incidents
• Warranty status

For repair and repurposing, the passport should help determine whether a battery is suitable for continued use, refurbishment, remanufacture or second life deployment. That usually requires data such as:

• Replaceable components
• Disassembly instructions
• Repair restrictions
• Diagnostic information
• Test results
• Remaining capacity
• Remaining useful life estimate
• Conditions for repurposing
• Storage and transport instructions for used batteries

For end-of-life treatment, the passport should support safe collection and efficient material recovery. Recyclers and treatment operators need practical information, not just a broad statement that the battery is recyclable. Useful fields include:

• Chemistry and hazardous content
• Location of key components
• Dismantling sequence
• Tooling or safety precautions
• Fire risk handling guidance
• Mass of recoverable materials
• Collection category
• Waste classification references where applicable
• Recycling route or preferred treatment method
• Recovery and recycling performance data, where recorded after treatment

Where producer responsibility schemes apply, collection and treatment records may sit outside the passport itself, but the passport should still connect the battery to the relevant identifiers and compliance records. In the EU this sits within the wider battery regulatory framework. In the UK, waste batteries and producer responsibility remain governed through separate domestic rules rather than an EU style battery passport regime, so businesses operating in both markets need to manage the overlap carefully.

The hardest part is rarely deciding what data is needed. It is deciding where each field comes from, who owns it, how it is checked, and how it stays current.

We organise battery passport data around a controlled data model with clear source mapping. Each field should have four things defined.

First, the source system or source document. For example, technical specifications may come from PLM or ERP, supplier identity from procurement, material composition from BOM and supplier declarations, carbon footprint from LCA tools, and maintenance events from service systems.

Second, the data owner. Engineering should own technical attributes. Procurement or responsible sourcing teams should own supplier and origin data. Sustainability teams may own footprint calculations. Compliance should own legal mapping and evidence controls. Nobody should assume someone else is maintaining a field.

Third, the validation rule. Some fields need format checks only. Others need document-backed approval. Others need third-party verification or internal sign-off before publication.

Fourth, the update trigger. A passport should be updated when there is a design change, supplier change, site change, regulatory change, recalculated footprint, repair event, or end-of-life event, depending on the field.

In practical terms, we recommend structuring the data in layers:

• Public or access-controlled passport view
• Compliance evidence repository
• Operational lifecycle data layer
• Audit trail and version history

That avoids overloading the visible passport with every internal document while still maintaining traceability to the evidence.

It also helps to distinguish static data from dynamic data. Model number and nominal voltage are relatively static. State of health, repair history and end-of-life status are dynamic. If you treat all fields the same way, either the passport becomes stale or the maintenance burden becomes unmanageable.

Validation matters as much as structure. We build passport workflows so that high risk fields cannot be published or changed without approval, and every material revision leaves a record. That is especially important where a declaration in the passport is tied to a legal obligation, such as due diligence, recycled content or carbon footprint.

Finally, make the passport usable by the people who actually need it. Regulators need formal compliance data. Customers need understandable product and sustainability information. Service teams need technical and maintenance records. Recyclers need chemistry and dismantling instructions. If one audience can use the passport but the others cannot, the design is incomplete.

If you are building this capability now, our guide to selecting a digital passport approach for industrial batteries is a good next step, especially if you need to connect compliance data with product and lifecycle systems.

A battery passport works when it is treated as governed product infrastructure, not as a one-off disclosure exercise. The right data is the data that lets each battery be identified, assessed, serviced and recovered properly, with evidence behind every important claim.