AN INDEPENDENT KNOWLEDGE PUBLICATION Our editorial approach ↗
BatteryPassport.digital Search guides /
Menu & topics
The 2027 milestone

What Is the Delegated Acts Pipeline for Batteries?

Delegated and implementing acts set detailed Battery Regulation rules, tracked from empowerment through consultation and adoption to entry into force and application.

GUIDE / THE 2027 MILESTONEIDENTITY → INFORMATION → EVIDENCE

The delegated acts pipeline is the sequence of delegated and implementing acts by which the Commission sets the detailed rules for the Battery Regulation, including carbon footprint methodology, performance classes, recycled content, passport access and updating, and other detailed provisions. Delegated acts are adopted by the Commission under the empowerment in the Regulation, subject to scrutiny by the European Parliament and the Council, and they enter into force on the date set in the act. The pipeline is therefore a legislative sequence, not a publication calendar, and each act must be tracked from empowerment, through consultation and adoption, to entry into force and application.

Pipeline tracking matters because many Battery Regulation duties are conditional on a delegated act. A duty that is conditional cannot be planned to a fixed date alone; it must be planned to the act status, with the fixed date, the conditional period and the resulting expected application date shown together. A pipeline log that lists only expected dates, without act status, will be wrong when an act slips, and a log that lists only act names, without dates, cannot support planning. The combined log, act plus status plus date, is the planning tool.

What is a delegated act in this Regulation?

A delegated act in the Battery Regulation is a non legislative act adopted by the Commission to supplement or amend non essential elements of the Regulation, under the empowerment and conditions set in the Regulation, including the power to set methodologies, thresholds, classes and detailed rules. Delegated acts are distinct from implementing acts, which set uniform conditions for implementation, and from guidance, which explains the Regulation without creating legal duties. A delegated act creates legal duties when it enters into force and applies, a guidance document does not, and the distinction must be kept clear in every pipeline entry.

A pipeline entry should state the act type, the empowerment article, the subject, the status and the entry into force and application dates where known. An entry that states only a subject and a date, without act type and empowerment, cannot be verified. An entry with act type, empowerment, subject, status and dates allows a reader to check the act in EUR-Lex and to judge its legal effect. The entry should be updated at each stage, with the update dated.

Which delegated acts affect battery passports?

Delegated and implementing acts that affect battery passports include the acts under Article 77 on passport access rights and on introducing, modifying and updating passport information, the acts on carbon footprint methodology, performance classes and maximum thresholds under Article 7, the acts on recycled content under Article 8, and the acts on performance and durability values and on other detailed provisions. Each act affects a different set of passport fields or duties, and the pipeline log should map each act to the fields and duties it affects, so that a delay in one act can be judged for its specific effect, rather than as a general delay to the whole passport programme.

Act areaPassport effectPlanning consequence of delay
Article 77 access and updatingAccess tiers and update rulesHold open tier and update design
Article 7 carbon footprintDeclaration, classes, thresholdsHold open carbon field presentation
Article 8 recycled contentRecycled content fieldsHold open recycled content presentation

Worked check: the Article 77 access act is delayed. The passport programme proceeds on settled fields, such as model and identifier data, and holds open the access tier implementation for fields that the act will define. A programme that proceeds on an assumed access design, without holding the open fields, will need rework when the act is adopted. A programme that pauses the whole passport on the delay will miss the milestone for settled fields. The mapped log allows the programme to proceed and to hold, field by field.

How is the pipeline tracked?

The pipeline is tracked through EUR-Lex, the Commission Have Your Say consultation portal, and Commission work programme and news material, with each act logged from consultation draft, through adoption, to entry into force. Tracking should be assigned to a named role, with a review calendar tied to consultation and adoption cycles. A tracking duty assigned to no one, or to a general inbox, will miss a consultation that affects a duty, and the operator will lose the chance to comment and to plan. The log should be reviewed after each publication, with the review dated, and the duty map updated where the act changes a field or a date.

Tracking evidence should include the EUR-Lex reference, the consultation reference where applicable, the adoption date and the entry into force date. A log entry without a reference cannot be verified, and a log entry with a reference but no status cannot support planning. The combined entry, reference plus status, is the tracking evidence, and it should be retained with the duty map. The log should be dated as checked on 28 October 2026 as the baseline.

What is the difference between adoption and application?

Adoption is the act by which the Commission adopts a delegated or implementing act, entry into force is the date on which the act becomes legally effective, and application is the date from which the duties in the act must be met, which can be the entry into force date or a later date set in the act, including a period after entry into force. For conditional duties in the Battery Regulation, application can be a fixed date or a stated period after entry into force, whichever is later. A plan that treats adoption as application will be early, and a plan that treats entry into force as application, where the act sets a later application date, will also be early.

Date discipline in the pipeline log should show adoption, entry into force and application as three separate dates, with the conditional calculation shown where it applies. A log with a single date per act cannot show the three stages, and a reader cannot tell whether the act is adopted, in force or applicable. A log with three dates, and the calculation where conditional, allows the planning date to be derived correctly. The log should be updated at each stage, with the stage change dated.

How do delegated acts interact with harmonised standards?

Delegated acts interact with harmonised standards where the act sets a methodology or a threshold that a standard implements in technical detail, or where a standard provides the test method for a requirement set in the act. The interaction is complementary: the act sets the legal rule, the standard sets the technical method, and the operator must meet both. A standard cited in the Official Journal provides a presumption of conformity for the requirement it covers, while a delegated act sets the requirement itself. A plan that treats a standard as a substitute for an act, or an act as a substitute for a standard, misses one half of the requirement.

Interaction tracking should list, per duty, the act, the standard and the citation status, with the three elements shown together. A duty file with only the act, without the standard, cannot show the test method. A duty file with only the standard, without the act, cannot show the legal requirement. The combined file allows the operator to plan the legal and technical work together, and to update the plan when either element changes.

What pipeline assumptions should be avoided?

Pipeline assumptions to avoid include assuming that a draft act will be adopted unchanged, assuming that a consultation date is an adoption date, and assuming that an expected date in a work programme is a fixed application date. Each assumption should be replaced by a status entry, with the draft, consultation or work programme status labelled as such. As checked on 28 October 2026, the pipeline should be read from EUR-Lex and Commission sources, with secondary reporting used only as a prompt to check the primary source. This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting.

This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting. The pipeline is tracked act by act, stage by stage, with the duty map updated at each publication.

Sources & further reading

Source links point to primary materials and further reading, including commercial implementation resources where cited. This introductory guide does not replace the legislation.

Continue your reading

Back to The 2027 milestone ↗