How Should a Dated Timeline Be Prepared for Specific Batteries?

Preparing a dated timeline for specific batteries means building a timeline that is specific to the battery models, categories, placing dates and operator roles in that operation, with every date labelled by basis and every entry dated as checked. A generic timeline copied from a summary, a vendor or another operator will misstate at least one duty, because the generic timeline cannot know the categories, the placing dates or the roles. The dated timeline in this guide is a method for building that timeline, not a timeline to copy, and the output is a controlled document that the operation can use for planning and for authority questions.

The method starts from the battery register, not from the calendar. The register lists every model, its category, its capacity, its rechargeability and its placing history. The timeline is then built by applying the Regulation duty dates to each model in the register, with the basis labelled and the evidence referenced. A timeline built from the register will be complete for those models and will show gaps where a model lacks classification or placing evidence. A timeline built from the calendar will be complete as a calendar and incomplete as a record for those batteries.

What is the starting point for a dated timeline?

The starting point is a battery register listing every model, with category, capacity, chemistry, rechargeability, manufacturing site, placing dates and operator roles, as checked on 28 October 2026 for the framework. The register should be complete before the timeline is built, because a timeline built on an incomplete register will omit models and duties. A register check should confirm that every model placed, in production or in planning is listed, with no model missing and no duplicate entry, and the check should be dated. A register with duplicates or omissions will produce a timeline with duplicates or omissions, and the timeline error will be a register error, not a date error.

Register completeness should be tested by reconciling the register against production records, sales records and import records, with the reconciliation filed. A reconciliation that lists only the register, without the source records, cannot show completeness. A reconciliation with source records and differences explained shows that the register is complete, and it allows a missing model to be found before the timeline is built. The reconciliation should be repeated when a new model is added or a model is discontinued.

How are duties mapped to each model?

Duties are mapped to each model by applying the category, capacity and rechargeability tests, then listing each duty that applies to that model, with its application date, its basis and its evidence. The mapping should be a table, with a row per model and duty, so that the timeline for a model can be read as a set of dated duties. A mapping that lists duties without models, or models without duties, cannot be used for planning, because the reader cannot tell which duty applies to which model. The table should be the controlled timeline document, with version control and review dates.

Worked check: a register with three models, one portable, one LMT and one industrial above 2 kWh, produces three duty tables. The portable table has no passport entry, the LMT table has a passport entry from 18 February 2027, and the industrial table has a passport entry from the same date, with the capacity evidence cited. A reader can see, model by model, which duties apply and when. A single timeline for the three models, without per model tables, would hide the portable non applicability and the industrial capacity basis.

How are dates labelled and dated in the timeline?

Dates in the timeline are labelled fixed, conditional or expected, with the basis cited, and the timeline as a whole is dated as checked, with the check date stated on the document. A timeline without a check date cannot be judged for currency, because a reader cannot tell whether the timeline reflects the Regulation and act status at the time of reading or at an earlier date. A timeline with a check date, a basis label per date and a review date allows the reader to judge currency and to know when the timeline will next be reviewed. The check date should be updated at each review, with the previous version preserved.

Date labelling should be reviewed at each timeline review, with the basis updated where an act has been adopted or a work programme has changed. A review that updates dates without updating bases will retain an expected label for a date that has become fixed, or a fixed label for a date that has become conditional. The basis review is the point of the timeline review, and it should be recorded in the version history, with the reviewer named.

How are operator roles shown in the timeline?

Operator roles are shown in the timeline by adding a role column to each duty entry, stating which role must act, what the role must do and what evidence the role must hold. A duty entry without a role cannot be assigned, and a duty entry with every role listed cannot be owned. The role column should name a single responsible role per duty, with supporting roles listed separately where needed. A timeline with role assignments can be used to plan work, to assign gates and to answer an authority question about who carried out a duty. A timeline without role assignments can only be used as a calendar.

Role assignment should be checked against the operator chain, with each role confirmed as existing in the operation and as holding the evidence for the duty. A role assigned to a function that does not exist, or to a vendor without an authorisation, is an unowned duty. A role assignment that is confirmed, with the evidence route stated, is an owned duty. The assignment check should be carried out when the timeline is built and when the operator structure changes, with the check dated.

How is the timeline reviewed and updated?

The timeline is reviewed after each delegated act, implementing act, guidance publication, standards citation and national rule change, and at least quarterly in the run up to 18 February 2027, with the review dated and the version updated. Review should cover the register completeness, the duty mapping, the date bases, the role assignments and the evidence references, with each element marked as confirmed, updated or open. A review that covers only dates will miss a register omission or a role change, and the timeline will drift from the operation. A full review, with each element checked, keeps the timeline accurate as a record for the operation.

Review evidence should be filed as a version history, with the version, the date, the reviewer, the changes made and the reason for each change. A version history without reasons cannot show why a date or a duty changed, and a later reader cannot judge whether the change was correct. A version history with reasons allows the timeline to be audited, and it allows a change to be reversed where the reason is found to be incorrect. The history should be retained with the timeline.

What should a dated timeline not contain?

A dated timeline should not contain invented dates, unverified penalty levels, vendor dates presented as duties, or guidance presented as law. As checked on 28 October 2026, every date should carry its basis, every penalty reference should carry its jurisdiction label, and every guidance reference should be cited as explanation, not as law. A timeline that contains an unverified figure should be returned for correction before it is used. 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 timeline is a controlled document built from the register, and it should be reviewed after every act, guidance or standards change.