Common Implementation Mistakes for the Battery Passport

Common implementation mistakes for the battery passport share a pattern, in which an operator starts with the visible element, such as a system or a QR code, and skips the invisible elements, such as scope, category, data and pilot proof, that decide whether the visible element works. The pattern matters because each mistake looks like progress at the time, with a system bought, a code printed or a record created, while the underlying method remains unproved. The mistakes in this guide are described as patterns, drawn from the structure of the Regulation and from the preparation method in this cluster, not as findings about any particular operator. Each mistake is paired with the correction that the method in this cluster provides, so that the guide can be used as a review of a preparation plan.

The scope is implementation mistakes for Article 77 preparation, as checked on 28 October 2026. The guide states no finding about any operator or system.

What happens when scope is skipped?

When scope is skipped, an operator builds records for batteries that do not need them, misses batteries that do need them, or builds the wrong record for a category, and the error is found only at market surveillance or at sale, when the record is read. The correction is the controlled model register, with category, capacity and placing date recorded for every model, reviewed before any record is created. A scope error is cheap to fix at the register stage and expensive to fix after records are created, because every record for a wrongly classified model must be rebuilt. The register is therefore the first output of any preparation, and a preparation without a register should be paused until the register exists.

What happens when data collection is left to the system?

When data collection is left to the system, the system collects whatever fields it is configured to collect, without a field by field plan, and the resulting records contain the fields that were easy to collect, not the fields that the Commission guidance marks as mandatory for the category. The correction is the field by field data plan, with source, format, quality check and gap handling for each field, built from the guidance before the system is configured. A system configured without a field plan will need reconfiguration after the first independent record reading, and reconfiguration after roll out is more disruptive than configuration before roll out. The field plan should precede the system, not follow it.

What happens when the pilot is skipped?

When the pilot is skipped, an operator rolls out a method that has never been proved end to end, and the first production records become the pilot, with failures found by buyers, authorities or recyclers rather than by the operator. The correction is the pilot record plan, with one representative model, an independent reading, failure fixing and a retest, before roll out. A skipped pilot saves time in the short term and costs more time later, because production failures must be fixed record by record, with the method also fixed, while a pilot failure is fixed once, in the method. The pilot is the cheapest test in the whole preparation, and skipping it is the most expensive mistake.

What does a mistakes table look like?

A mistakes table pairs each mistake pattern with its symptom and its correction, so that a preparation plan can be reviewed quickly. The table below uses general patterns.

What happens when the carrier is never tested?

When the carrier is never tested, an operator prints codes that scan in the factory, or that do not scan at all, or that resolve to the wrong record, and the failure is found when a buyer, a repairer or an authority tries to read the record. The correction is the carrier test plan, with scans at manufacture, at handover and at collection, with resolution checked at each scan, and with failures remedied by preserving the identifier. A carrier test is quick, and a carrier failure found early is cheap, while a carrier failure found at sale damages trust in the whole record system. The carrier is the only part of the passport that a reader touches, and it deserves a test at every stage.

What happens when roles are left unowned?

When roles are left unowned, a stage stalls at a handover, a gap is known but not tracked, or a decision is made but not recorded, and the preparation drifts until a deadline forces a rushed decision. The correction is the roles and ownership plan, with a named owner and deputy for every stage, decision records for every material decision, and handover notes for every handover. Unowned work is not work that no one does, and it is work that everyone assumes someone else does, which is worse, because the gap is invisible until it blocks progress. A roles review that finds an unowned stage has found a mistake before it blocks the timeline.

What limits apply to mistake analysis?

The limits are that mistake patterns describe risks in general terms, and they do not predict that any particular operator will make any particular mistake. This guide gives general educational information only and is not individual legal advice. An operator reviewing a preparation plan should check the Regulation text as checked on 28 October 2026 before acting.