EV record anatomy

The anatomy of an EV battery record follows Annex XIII of Regulation (EU) 2023/1542, which sets out the information categories for the battery passport. The categories cover general battery information, composition, carbon footprint, recycled content, performance and durability, due diligence, and end of life information, with access levels that differ by category. Model level information describes the battery model and the production site, while individual battery information describes the single battery and its use history. The record must keep the layers separate and linked, so a model correction does not overwrite an individual history, and an individual update does not change a model declaration. A flat file that mixes the layers cannot be updated safely.

Record anatomy means the structure of the passport record, including the information categories, the level at which each item sits, and the access level for each item. The scope is EV batteries under Article 77 and Annex XIII.

How is the EV category decided?

EV record anatomy applies to that category, and the record should state the vehicle category, the weight basis, and the reason the battery falls inside the definition. Article 77 and Annex XIII is the operative provision for the point in question, and Annex XIII sets the passport content where a passport applies. A data architect designing the EV passport record structure should not assume that a traction battery for another vehicle type follows the same entry. A carbon footprint declaration for a model should sit at model level, while the state of health for one pack should sit at individual level, with the individual record linked to the model record by model identifier.

How are model and individual layers kept separate?

For EV record anatomy, the record should keep the two layers separate, with a link from the individual record to the model record. The record schema, field definitions, and access matrix for a model value should name the test or calculation method and the date, while evidence for an individual value should name the measurement, the date, and the source system, such as the battery management system. Commission guidance on passport data points organises the Annex XIII information by battery category and by whether each point is mandatory, optional, conditional, or not required at the start, and the record should state the guidance version used, as checked on 28 October 2026, without treating guidance as law.

How are performance values stated?

For EV record anatomy, a capacity value, a power value, a cycle life value, or a capacity retention value should state the test conditions, the reference temperature, the charge and discharge rates, and the end point used. A data architect designing the EV passport record structure should record which requirement applies to the EV battery in question and which requirement does not, with the article reference. A carbon footprint declaration for a model should sit at model level, while the state of health for one pack should sit at individual level, with the individual record linked to the model record by model identifier.

How is use phase information recorded?

For EV record anatomy, state of health, cycle count, temperature history, and fault history, where recorded, should be tied to the unique identifier and dated, so a later reader can see the sequence. The record schema, field definitions, and access matrix should include the data extraction date and the version of the software or method used, where that information is available. Commission guidance on passport data points organises the Annex XIII information by battery category and by whether each point is mandatory, optional, conditional, or not required at the start, and the record should state the guidance version used, as checked on 28 October 2026, without treating guidance as law.

How are repair and second life operations distinguished?

For EV record anatomy, the record should name the operation, the operator who carried it out, the date, the parts changed, and the tests applied after the operation. A data architect designing the EV passport record structure should check whether a new passport, a linked passport, or an updated passport is required for the operation, and should record the reasoning. A carbon footprint declaration for a model should sit at model level, while the state of health for one pack should sit at individual level, with the individual record linked to the model record by model identifier.

How is access and handover handled?

For EV record anatomy, the passport access rules in Article 77 set different levels for the public, for persons with a legitimate interest, and for authorities and notified bodies, and the record should not promise wider access than the Regulation allows. Commission guidance on passport data points organises the Annex XIII information by battery category and by whether each point is mandatory, optional, conditional, or not required at the start, and the record should state the guidance version used, as checked on 28 October 2026, without treating guidance as law. A data architect designing the EV passport record structure should retain the handover record with the identifier, so a later dispute can be traced to a dated transfer.

How is one field traced through the record layers?

Tracing one field, such as recycled cobalt content, starts at the model level, where the declaration states the value, the method, and the period. The field is then followed to the passport entry, where the same value appears with the same method and period, and to the underlying calculation, where the input quantities are shown. A worked trace shows the three locations, the value in each, and the checker who compared them. If the model value changes, the trace shows the new model version, the passport update, and the date, while the old value remains in version history. A field that appears in the passport without a model source, or in the model file without a passport entry, is an untraced field.

Anatomy is a discipline for updates, and a record that cannot say which layer changed has no reliable history.