What Happens If a Delegated Act Slips?

What happens if a delegated act slips is the question of how a delay in a delegated or implementing act affects the duties that depend on it, the planning that was built around it, and the records that were prepared on an interim basis. A slip means that the act is adopted later than expected, enters into force later than expected, or is adopted in a different form from the draft, and each form of slip has a different effect. The planning response is not to wait for the act in silence, but to track the slip, recalculate the conditional dates, hold open the affected fields, and review interim records, with the slip and the response recorded in the pipeline log.

Slip handling is a normal part of Battery Regulation implementation, because many duties are conditional on acts, and acts have slipped in the carbon footprint and passport detail areas as checked on 28 October 2026. A programme that treats a slip as an exception, without a procedure for it, will improvise a response under pressure and will create records that are difficult to correct. A programme with a slip procedure, with tracking, recalculation, holding and review steps, will handle a slip as a planned event, and the programme will remain auditable through the delay.

How is a slip identified and recorded?

A slip is identified by comparing the expected adoption or entry into force date in the pipeline log with the current status in EUR-Lex and Commission sources, and recording the difference as a slip entry, with the act, the expected date, the current status and the reason for the delay where published. A slip entry without a reason, or without a current status, cannot support planning, because the reader cannot tell whether the act is delayed by weeks, by months, or by a substantive change in form. A slip entry with status, reason and a new expected date, labelled expected, allows the programme to be replanned on the best available information.

Slip recording should be dated, with the previous expected date preserved in the log history, so that the slip can be seen as a change from the previous expectation, not as a new expectation without history. A log that overwrites the previous expected date without preserving it hides the slip, and a later reader cannot tell that the date moved. A log with a history of expected dates shows the slip pattern, and it allows the programme to judge whether the act is slipping repeatedly, which affects the confidence that should be placed in the new expected date.

How are conditional dates recalculated after a slip?

Conditional dates are recalculated after a slip by applying the conditional rule in the Regulation: the fixed date or the stated period after the act enters into force, whichever is later, using the new entry into force date where known, or a new expected entry into force date where the act has not yet entered into force. The recalculated date must be labelled expected until the act enters into force, and the calculation must be shown, with the fixed date, the period, the entry into force date and the resulting date all stated. A recalculated date stated without the calculation cannot be verified, and a recalculated date stated as fixed before entry into force overstates certainty.

Worked check: a carbon declaration fixed date passes while the methodology act remains pending. The recalculation uses the expected entry into force date plus 12 months, producing a new expected application date in the second half of 2027. The programme updates the timeline to the expected date, labels it expected, and holds the declaration presentation work pending the act. A programme that retains the fixed date as the planning date would prepare a declaration on a method that does not exist, and would need rework when the act is adopted. The recalculation prevents that wasted work.

What work should proceed during a slip?

Work that should proceed during a slip is work on settled fields, settled methods and settled systems, including classification, supplier data collection for settled fields, identifier and carrier design, access design for settled tiers, and whole system testing on sample batteries using the settled data structure. Work that should be held open is work on the fields, methods and thresholds that the delayed act will define, including carbon presentation, access tier detail for affected fields, and performance class assignment. A programme that pauses all work during a slip loses preparation time, and a programme that proceeds on assumed act content creates rework. The mapped holding approach, field by field, is the correct response.

Holding decisions should be recorded per field, with the field, the act, the holding reason and the review trigger stated. A holding decision recorded only as a general pause cannot show which fields are held and which proceed. A per field holding record allows the programme to proceed on settled fields and to restart held fields promptly when the act is adopted, without a general restart delay. The record should be reviewed when the act status changes, with the review dated.

How are interim records reviewed after a slip?

Interim records prepared before a slip, or during a slip on an interim method, should be reviewed when the act is adopted, with the interim method compared against the adopted method, and the record corrected where the methods differ. An interim record should have been marked interim, with the method version and the review trigger stated, so that the review can identify it without searching. A record prepared on an assumed method, without an interim mark, will be treated as final and will not be reviewed, and the error will remain in the passport. The interim mark is the control that ensures review.

Review should be carried out as a batch, listing every interim record, the interim method used, the adopted method, the difference and the correction, with the review dated. A review carried out record by record, without a batch list, will miss an interim record that was not identified. A batch review, with a list generated from the interim marks in the system, ensures completeness. The batch list and the corrections should be filed with the passport evidence, so that an authority can see that interim records were reviewed and corrected.

What communication should follow a slip?

Communication after a slip should inform the planning team, the supplier chain where supplier data are affected, and, where the slip affects a placing date, the distribution chain, with the slip, the recalculated dates and the holding decisions stated. Communication should be factual and dated, with the act status and the expected dates labelled expected, and with no commitment to a fixed date that the act has not yet set. A communication that states a new fixed date, based on an expected entry into force, repeats the original error in a new form. A communication that states the slip, the calculation and the review trigger allows each audience to plan on the same basis.

Communication records should be filed with the pipeline log, with the audience, the date and the message stated. A communication file without an audience list cannot show who was informed, and a communication file without a date cannot show when the information was provided. The file should be retained, so that a later question about planning on the basis of the slip can be answered from the communication record.

How is slip history used for future planning?

Slip history is used for future planning by showing the pattern of slips per act area, the confidence that should be placed in new expected dates, and the holding approach that minimises rework. As checked on 28 October 2026, the carbon and passport detail acts had slipped, and future planning should place lower confidence in expected dates for acts in those areas, with longer holding periods and more interim marking. A programme that ignores slip history will place the same confidence in every expected date, and will repeat the rework pattern. A programme that uses slip history will plan with contingencies that match the pattern. 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. A slip should be handled as a planned event, with the pipeline log, the timeline and the interim records all updated together.