Confirm which batteries need a passport

From February 18, 2027, a battery passport is required for electric vehicle batteries, light means of transport (LMT) batteries, and industrial batteries with capacity greater than 2 kilowatt-hours (kWh) placed on the EU market or put into service. The 2 kWh threshold applies to the industrial category. Check statutory definitions and exemptions for your products. [1] [3]

Create a scope register listing battery category, capacity where relevant, model, intended market, and the event that constitutes placing it on the market or putting it into service. Have the designated compliance reviewer confirm the classification and record the reason for each scope decision.

For example, an industrial battery model rated at 4.8 kWh warrants a passport scope review. Record the supporting technical specification and identify the entity bringing the completed battery to market. A connector supplier supporting that battery has a different role: supplying relevant evidence rather than assuming that every connector needs its own battery passport.

Assign responsibility before requesting data

The Commission identifies the economic operator placing the finished battery on the market as responsible for creating and maintaining its passport. Component and module suppliers support the evidence chain. Practical work can be delegated through written authorization, while ultimate responsibility remains with the responsible economic operator. [2] [4]

Name a passport owner and agree who supplies, reviews, publishes, and updates each field. Engineering may hold technical specifications and test evidence; supply chain may manage supplier requests; compliance may determine applicability and review evidence; IT may operate identifiers, access controls, and data exchange. These are suggested assignments, not roles prescribed by the regulation.

Before commissioning a platform or outsourcing data work, document the handoff. Specify who approves a new record, resolves conflicting supplier evidence, responds to a change, and preserves access if a provider changes. Give every unresolved dependency an owner and a due date.

Map the evidence field by field

Annex XIII covers both battery-model information and information specific to an individual battery. Keep those levels distinct in your data model. [3]

Use the Commission-hosted data-point guidance to build an applicability map. It distinguishes mandatory, optional, conditional, and later requirements by battery category. It is supporting guidance, not an authoritative interpretation or an amendment to the law. Examples include manufacturer identity, chemistry, capacity, performance information, component references, and dismantling information. [5]

For every applicable field, record its legal reference, source, unit or format, reviewer, access classification, and update trigger. Preserve the source document and its version. Where evidence is missing, distinguish an open request from a field that is genuinely not applicable. An internal unknown status is a work-tracking label; it does not authorize leaving a required field unresolved.

Keep supplier requests specific. Ask for the identified battery model or component revision and the exact missing data, rather than a general statement that the supplier complies with EU requirements. If two documents disagree, retain both and route the conflict for technical review.

Keep the application dates separate

Current Commission guidance says carbon-footprint, recycled-content, and due-diligence information is not required in the passport at its February 2027 introduction; those obligations have separate application dates. Recheck the guidance and underlying acts before deciding which fields apply. [4]

Regulation (EU) 2025/1561 moved the battery due-diligence application date to August 18, 2027. Assess that obligation’s own scope and exemptions separately. Its postponement does not move the passport date. [6]

Maintain a dated requirements register instead of putting every obligation under one 2027 deadline. For each requirement, record the battery category, applicability condition, operative date, and current legal source. Keep a short change log showing what was rechecked and whether the field map or implementation plan changed.

Test one battery record through the complete workflow

The passport connects to the battery through a QR code and unique identity; its technical requirements include interoperability, controlled access, and data integrity. Design the pilot around those functions. [2] [3]

Select one representative in-scope model and one individual battery record. Confirm that the identifier resolves to the correct record, model data can be reused without confusing units, evidence links work, and an authorized update changes the intended field. Test data export and exchange with the systems your organization will actually use.

Keep passport hosting and Registry registration as separate tasks. The Commission FAQ describes the Registry as holding registration information and metadata, while the responsible operator or authorized operator hosts the passport data. Its access-rights implementing act remains pending as of this review. [4]

Include a permissions test: a public user should receive the appropriate public view, while restricted information follows the applicable access rules. Have the regulatory reviewer and system owner assess the result together. Record defects and retest them before expanding to additional models; a successful demonstration should have evidence behind it.

Build the update process alongside the launch

The Commission FAQ anticipates applicable dynamic data from the passport’s introduction. It does not equate that with universal real-time transmission; relevant status changes and the purpose of the data matter. Define a suitable update process for each applicable field. [4]

Decide how information from manufacturing, service, and later battery use enters the review queue. Record what changed, which batteries it affects, who checked it, and when it was published. Include a handoff plan for repurposing or remanufacturing and check the applicable passport-linking requirements before changing identity or responsibility.

Test continuity as well as the initial release. A colleague should be able to reconstruct the record from the identifier, approved evidence, and change history. A new service partner should receive the information and permissions needed for its assigned work without relying on the original project team’s inboxes.

Start with a scope decision and a pilot

In Q4, complete the scope register and ownership agreement, then map the applicable evidence for your pilot. Before expanding, test identity, access, data exchange, registration, and an update. Assign unresolved gaps and track them against the February milestone. This is a suggested implementation sequence, not a guarantee of compliance.

This brief provides general information and practical process recommendations, not legal advice or a battery compliance determination. Apply the current legislation and relevant implementing measures to your products and circumstances.