What Is the Difference Between Expected and Fixed Dates?

Expected versus fixed dates is the distinction between a date set in the Regulation text that applies regardless of a further act, and a date that is expected because it depends on a delegated or implementing act, a work programme, or a guidance publication that has not yet occurred. Fixed dates can be planned to, with the Regulation text as the authority. Expected dates can be planned around, with a review trigger and a contingency, but they cannot be presented as fixed duties, because the act or publication that creates the duty has not yet occurred. The distinction is the core discipline of battery timeline planning.

Date confusion is the most common timeline error in battery planning. A work programme date, a consultation date, a secondary report date or a vendor date is treated as a fixed duty date, and a programme is built to it. When the act slips, the programme is judged late, even though the duty never applied on the assumed date. The correction is to label every date in a timeline with its basis: fixed in the Regulation, conditional on an act, expected from a work programme, or indicative from guidance. A timeline without basis labels cannot be audited, and it will mislead every reader who uses it.

What makes a date fixed?

A date is fixed when the Regulation text sets it as the application date for a duty, without a condition that depends on a further act. The passport date of 18 February 2027 in Article 77 is fixed, because the Regulation sets it directly for the categories named, without a condition on a delegated act for the duty itself, although detail on access and updating depends on acts. The separate collection symbol date of 18 August 2025 and the general labelling date of 18 August 2026 are fixed in the same way, because Article 13 sets them directly. A fixed date should be cited with its article, so that the reader can verify it in the Regulation text.

A fixed date entry in a timeline should state the date, the article, the duty and the categories affected, with the entry dated as checked on 28 October 2026. An entry that states only the date and the duty, without the article, cannot be verified. An entry with the article allows verification in EUR-Lex, and it allows a later reader to check whether the article has been amended. The entry should be reviewed after any amendment to the Regulation, with the review dated.

What makes a date conditional?

A date is conditional when the Regulation sets it as a fixed date or a stated period after a delegated or implementing act enters into force, whichever is later. Carbon footprint declarations are the clearest conditional case, with fixed dates and periods per category that depend on the methodology delegated act. A conditional date cannot be derived from the fixed date alone; it requires the act status, the entry into force date and the period calculation. A timeline that shows only the fixed date for a conditional duty overstates certainty and understates the effect of an act delay.

Worked check: a carbon footprint declaration for electric vehicle batteries is shown as fixed on 18 February 2025 in a timeline. The act status check shows that the methodology delegated act has not entered into force, so the duty applies 12 months after entry into force, on a later expected date. The corrected timeline shows the fixed date, the act status and the expected date, labelled expected. A programme built to the fixed date alone would have prepared a declaration on a method that did not exist. The corrected timeline prevents that wasted work.

What makes a date expected?

A date is expected when it comes from a Commission work programme, an indicative timeline, a consultation plan or a secondary report, without a legal act setting it as an application date. Expected dates are useful for planning, because they show the direction and the likely sequence, but they are not duties, and they move when the underlying act or programme moves. An expected date should be labelled expected, with the source named, so that a reader does not mistake it for a fixed duty. A timeline that presents expected dates without labels will be read as a fixed timeline, and the reader will judge the programme against dates that were never duties.

Expected date entries should state the date, the source, the subject and the review trigger, with the entry dated. A source that is a work programme should be named as such, with the programme date. A source that is secondary reporting should be named as such, with a prompt to check the primary source. The entry should be reviewed after the next work programme or act publication, with the review dated, so that the expected date is updated or confirmed.

How are fixed, conditional and expected dates shown together?

Fixed, conditional and expected dates are shown together in a timeline table, with a basis column that states the basis for each date, so that the reader can see at a glance which dates are duties and which are planning assumptions. A graphic timeline without a basis column, or a list of dates without labels, hides the distinction and invites misreading. The table should be the primary timeline presentation, with any graphic derived from the table, so that the graphic cannot drift from the labelled basis. The table should be the controlled document, with version control and review dates.

Table discipline should include a review of the basis for each date at each timeline review, with the basis updated where an act has been adopted or a work programme has changed. A table reviewed only for dates, without reviewing bases, will retain an expected label for a date that has become fixed, or a fixed label for a date that has become conditional through an amendment. The basis review is the point of the timeline review, and it should be recorded.

What happens when an expected date is treated as fixed?

When an expected date is treated as fixed, the programme builds to a date that is not a duty, judges itself late when the date passes without a duty, and may place a battery on the market with a record based on an assumed method or threshold. The cost is wasted work, rework when the act is adopted, and a record that must be corrected. The correction is to relabel the date, rebuild the plan around the act status, and review any records created on the assumed basis. A record created on an assumed method should be marked interim and reviewed when the act is adopted, rather than presented as final.

Relabelling should be recorded as a timeline correction, with the original label, the corrected label, the reason and the date. A correction without a record will allow the original label to reappear in a later plan, because the team will not remember why the date was relabelled. A recorded correction, filed with the timeline, prevents the error from recurring. The correction file should be retained with the timeline evidence.

How should dates be checked before use?

Dates should be checked in the Regulation text on EUR-Lex and, for conditional and expected dates, in the delegated act status and work programme material, as checked on 28 October 2026 for the framework in this guide. A date taken from a secondary source should be verified in the primary source before it is used for planning, and the verification should be dated. 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. Every date in a timeline should carry its basis label, and the basis should be reviewed at each timeline review.