§ The board · sourced from Regulation (EU) 2026/253
Departures & arrivals - the TEL TSI schedule
Departures are obligations your organisation must meet, listed per role. Arrivals are what ERA and the Member States owe the sector - dependencies, not liabilities. Every entry is dated and carries its reference; a passed date means the obligation is in force, not over. The readiness check turns the departures that bind your role into your action plan: dated, cited tasks. The live board on the home page counts these down in real time.
Departures - freight railway undertakings
| Date | Obligation | Reference |
|---|---|---|
| 02 Sep 2026 | ERA Change Control Management (CCM) process From this date ERA must have established and applied its CCM process for schema updates. As a Freight RU you are obliged to track and incorporate all ERA CCM changes into your schema governance on an ongoing basis - a one-time integration is not sufficient. |
Art. 12 |
| 13 Dec 2026 | Reference data - your organisation & location codes Every message you send must carry your Agency-assigned organisation code, and reference the correct location codes for origin and destination, and points in between. |
Art. 7 Art. 9 Annex pt. 1.2 Appendix G |
| 15 Dec 2026 | Train running information to drivers (OPE TSI) Under the OPE TSI (Reg. (EU) 2019/773, point 4.2.1.2.3, as amended by Reg. (EU) 2023/1693), your organisation must provide train running information digitally to train drivers by this date. This is a railway-undertaking-to-driver duty concerning working-plan information - it is not a TEL TSI requirement, not an infrastructure-manager-to-railway-undertaking data exchange, and not a telematics obligation. It is shown here because it is a real, binding duty that falls before any TEL TSI deadline, and missing it while preparing for the TEL TSI would be exactly the kind of gap this tool exists to help you catch. This tool does not assess OPE TSI compliance - see our FAQ for the boundary. |
OPE TSI Reg. (EU) 2019/773, point 4.2.1.2.3, as amended by Reg. (EU) 2023/1693 |
| 30 Sep 2027 | Common sector specification for the common Union API and web UI (the lead railway undertaking) Art. 21(2)+(4): as a freight railway undertaking, the lead railway undertaking must cooperate on developing and, by 30 September 2027, deliver its own common sector specification for the common Union API and web UI for the management of freight wagons and their load (Art. 14(6)), within the ERA-managed process. This is a 'shall' obligation on freight RUs directly - separate from, and additional to, the infrastructure managers' own capacity-management specification. Separation of duties: delivering the specification is mandatory, but actually using the resulting common Union API/web UI once available is optional for freight RUs under Art. 14(6) ('may jointly use'). |
Art. 21(2) Art. 21(4) Art. 14(6) |
| 02 Mar 2028 | Implementation report to the Agency As a freight railway undertaking, you must report your implementation status and plans for train preparation and the management of freight wagons and their load. |
Art. 17(2)(b)(i) |
| 10 Dec 2028 | Rolling stock reference database (RSRD) Vehicle keepers must set up and maintain the federated rolling stock reference database (RSRD). Your TrainCompositionMessage must reference vehicle numbers registered in this database - if RSRD is not operational, train composition exchanges cannot be correctly validated. |
Annex pt. 3.3.2 Appendix G |
| 10 Dec 2028 | Intermodal loading unit reference database (ILU) ILU keepers must maintain the federated ILU reference database. All containers, swap bodies and semi-trailers handled at the terminal must be identifiable via ILU numbers from this database - required for wagon composition messages and intermodal loading unit movement tracking. |
Annex pt. 3.3.3 Appendix G |
| 04 Mar 2029 | Capacity management Object identifiers and the path request/confirm exchange with the first infrastructure manager and the second infrastructure manager must be fully compliant. |
Annex pt. 2.1 Annex pt. 2.3 Appendix G |
| 09 Dec 2029 | Core operational compliance The bulk of your day-to-day message exchanges converge on this single date. |
Annex pt. 2.6.1(3)(5)(6) Annex pt. 2.7 Annex pt. 3.1.1 Annex pt. 3.2 Appendix G |
Departures - passenger railway undertakings
| Date | Obligation | Reference |
|---|---|---|
| 14 Dec 2025 | Passenger timetable data This is a pre-existing obligation carried over from the MMTIS Delegated Regulation and the legacy TAP TSI National Access Point framework - not a deadline newly created by TEL TSI. Passenger timetable data must be published to National Access Points (NAPs) in NeTEx format; the underlying duty continues under TEL TSI Art. 6(1) and Annex pt. 4.2.1 from TEL TSI's 2 March 2026 application date. If this has not yet been done, it is a compliance gap requiring urgent remediation. |
Art. 6(1) Annex pt. 4.2.1 Appendix G MMTIS Reg. (EU) 2017/1926, Art 4(1)(b)/5(1)(b) |
| 02 Sep 2026 | ERA Change Control Management (CCM) process From this date ERA must have established and applied its CCM process for schema updates. As a Passenger RU you are obliged to track and incorporate all ERA CCM changes into your schema governance on an ongoing basis - a one-time integration is not sufficient. |
Art. 12 |
| 13 Dec 2026 | Common reference data; Conditions of carriage; ERSAD; Ticket format Common reference data (organisation codes, location codes), conditions of carriage (general, luggage, bicycle, car, PRM), accessibility data (ERSAD submission to ERA), and harmonised ticket formats must all be in place by this date. |
Art. 6(1) Art. 9(3) Art. 9(4) Annex pt. 1.2 Annex pt. 4.4 Annex pt. 4.4.3.2 Annex pt. 4.6 Appendix G |
| 15 Dec 2026 | Train running information to drivers (OPE TSI) Under the OPE TSI (Reg. (EU) 2019/773, point 4.2.1.2.3, as amended by Reg. (EU) 2023/1693), your organisation must provide train running information digitally to train drivers by this date. This is a railway-undertaking-to-driver duty concerning working-plan information - it is not a TEL TSI requirement, not an infrastructure-manager-to-railway-undertaking data exchange, and not a telematics obligation. It is shown here because it is a real, binding duty that falls before any TEL TSI deadline, and missing it while preparing for the TEL TSI would be exactly the kind of gap this tool exists to help you catch. This tool does not assess OPE TSI compliance - see our FAQ for the boundary. |
OPE TSI Reg. (EU) 2019/773, point 4.2.1.2.3, as amended by Reg. (EU) 2023/1693 |
| 12 Dec 2027 | Connection times; Passenger information in stations and on-board Station managers must publish connection time data to NAPs, and passenger information systems in stations and on-board trains must be operational per Annex pt. 4.7 requirements. |
Art. 6(2) Art. 15(3) Annex pt. 4.2.2 Annex pt. 4.7 Appendix G |
| 02 Mar 2028 | Implementation report to the Agency Each telematics stakeholder must submit a report to ERA describing its implementation plan and status for passenger rail telematics obligations. Use ERA's monitoring web application (available from March 2027). |
Art. 17(2)(b) |
| 10 Dec 2028 | Passenger train running & forecast; Ticketing reference data; Tariff data Train traffic messages for passenger services (Appendix C, index [1] - ERA Ontology v4; sent to you by the infrastructure managers and published by them under BY-SA), ticketing reference data, and tariff data (NeTEx, BY-ND) must all be operationally shared by this date. |
Art. 5(1)(b) Art. 6(3) Annex pt. 2.6.1 Annex pt. 4.3 Appendix G |
| 04 Mar 2029 | Capacity management Object identifiers and the path request/confirm exchange with the first infrastructure manager and the second infrastructure manager must be fully compliant. As a passenger RU you act as an applicant for path requests the same way a freight RU does - Annex pt. 2.1 (object identifiers) and pt. 2.3 (capacity allocation) bind any applicant generically, with no freight-only scoping. |
Annex pt. 2.1 Annex pt. 2.3 Appendix G |
| 10 Jun 2029 | Availability and reservations Your attributing system must be operational and accessible to distributors for availability checking and reservations, compliant with ERA TD-B5 (TAP-legacy, OSDM, OMSA), by this date. |
Art. 6(4) Annex pt. 4.5 Appendix G ERA TD-B5 |
| 09 Dec 2029 | Passenger train composition; Train ready and readiness forecast PassengerTrainCompositionMessage (including accessibility data) and the TrainReadyMessage - including the NotReady status that conveys the readiness forecast - must all be operationally exchanged via the Common Interface by this date. |
Art. 14 Annex pt. 2.5.1 Annex pt. 2.5.2 Annex pt. 2.5.3 Appendix G |
Departures - infrastructure managers
| Date | Obligation | Reference |
|---|---|---|
| 02 Sep 2026 | ERA Change Control Management (CCM) process From this date ERA must have established and applied its CCM process for schema updates. As the infrastructure manager you are obliged to track and incorporate ERA CCM changes on an ongoing basis. |
Art. 12 |
| 02 Sep 2026 | RINF position of location codes assigned before entry into force Art. 9(7): by 2 September 2026, each infrastructure manager - or another competent entity established in the Union designated by it - must specify the position of the location codes assigned to it before entry into force, relative to the relevant infrastructure data in the RINF. Operators of rail freight service facilities carry the same duty for their own codes. It covers codes the infrastructure manager already holds and feeds the 13 December 2026 common reference data milestone. You may designate another competent entity to do the work, but the obligation stays with the infrastructure manager. |
Art. 9(7) Art. 9(6) Annex pt. 1.2.2 |
| 02 Dec 2026 | Network-specific data requirements shared with ERA (Art. 11) UNIQUE TO IMs: Each infrastructure manager must share with ERA the network-specific data requirements it applies or intends to apply to telematics applications on its network. This is an IM-only deadline with no RU equivalent. |
Art. 11(2) |
| 13 Dec 2026 | Common reference data: organisations & locations Organisation codes and location codes for the infrastructure manager, the lead railway undertaking, the passenger railway undertaking, the adjacent infrastructure manager, and all telematics stakeholders on your network must be fully deployed. Primary Location Codes for all the infrastructure manager network locations must be registered in the ERA Common Central Repository. |
Art. 7 Art. 9 Art. 10 Annex pt. 1.2 Appendix G |
| 02 Sep 2027 | IM implementation report to ERA UNIQUE TO IMs (earlier than the RU deadline of 2 March 2028): Art. 17(2)(a) - IMs must report implementation status to ERA covering capacity management, train preparation, and traffic management. The common sector specifications (Art. 14(5)/Art. 21) are a separate milestone due 30 September 2027. |
Art. 17(2)(a) |
| 30 Sep 2027 | Common sector specification for the common Union API and web UI (ENIM) Art. 21(1)+(4)/Art. 14(5), point (a): IMs must cooperate on developing and deliver their own common sector specification for the capacity-management/traffic-management common Union API and web UI, coordinated via ENIM. Separate milestone, 28 days after the 2 September 2027 implementation report. Freight RUs and operators of rail freight service facilities carry the same 'shall cooperate/deliver' obligation for their own specifications (Art. 21(2)/(3)+(4); Art. 14(6)/(5)(b)) - see their respective content packs. |
Art. 14(5), point (a) Art. 21(1) Art. 21(4) |
| 10 Dec 2028 | Passenger train running and forecast information TrainRunningInformationMessages and TrainRunningForecastMessages for passenger services (including the passenger railway undertaking's service) must be fully operational and shared per Annex pt. 2.6. |
Annex pt. 2.6 Appendix G |
| 10 Dec 2028 | Rolling stock reference database (RSRD) - dependency awareness Vehicle keepers - not the infrastructure manager - are responsible for setting up and maintaining the federated Rolling Stock Reference Database (RSRD); this is a vehicle-keeper obligation under Annex pt. 3.3.2, not an infrastructure manager obligation. But freight train composition exchanges you process reference vehicle numbers registered in the RSRD - if RSRD data is missing or inaccurate, downstream validation of that composition data can be affected. |
Annex pt. 3.3.2 Appendix G |
| 04 Mar 2029 | Capacity management - object identifiers & allocation Capacity allocation messages (PathRequestMessage, PathDetailsMessage, etc.) must comply with TEL TSI specifications by this date, for all rail transport services. Appendix G rows 2.1 and 2.3 carry a single date with no freight/passenger split, so the passenger railway undertaking's paths are due alongside the lead railway undertaking's. Path identifiers and route objects (Annex pt. 2.1) must be fully operational. |
Annex pt. 2.1 Annex pt. 2.3 Appendix G |
| 09 Dec 2029 | Freight train traffic, composition, train ready; full CI deployment Train traffic messages for freight trains (Annex pt. 2.6), train composition exchange for freight (Annex pt. 2.5.1), TrainReadyMessage processing (Annex pt. 2.5.2) and the train readiness forecast (Annex pt. 2.5.3), and full Common Interface deployment must all be operational by this date. |
Annex pt. 2.5.1 Annex pt. 2.5.2 Annex pt. 2.5.3 Annex pt. 2.6 Appendix G |
Departures - terminal & service-facility operators
| Date | Obligation | Reference |
|---|---|---|
| 02 Sep 2026 | RINF position of location codes assigned before entry into force Art. 9(7): by 2 September 2026, each infrastructure manager and each operator of rail freight service facilities - or another competent entity established in the Union designated by either - must specify the position of the location codes assigned to them before entry into force, relative to the relevant infrastructure data in the RINF. This is the earliest deadline in the Regulation falling directly on the terminal, and it covers codes you already hold. It feeds the 13 December 2026 common reference data milestone. You may designate another competent entity to do the work, but the obligation stays with the terminal. |
Art. 9(7) Art. 9(6) Annex pt. 1.2.2 |
| 02 Sep 2026 | ERA Change Control Management (CCM) process From this date ERA must have established and applied its CCM process for schema updates. As a terminal operator and telematics stakeholder you are obliged to track and incorporate ERA CCM changes on an ongoing basis. |
Art. 12 |
| 13 Dec 2026 | Common reference data: organisations & locations Organisation codes for the terminal and all trading partners (the lead railway undertaking, the combined-transport operator, the first infrastructure manager) and location codes for your terminal facility must be fully deployed and validated in the ERA Common Central Repository by this date. |
Art. 7 Art. 9 Art. 16(2) Art. 16(3) Annex pt. 1.2 Appendix G |
| 30 Sep 2027 | Common sector specification for the common Union API and web UI (the terminal) Art. 21(3)–(4): as an operator of a rail freight service facility, the terminal must cooperate on developing and, by 30 September 2027, deliver its own common sector specification for the common Union API and web UI within the ERA-managed process. The Regulation places this obligation directly on facility operators (a 'shall'), alongside IMs and freight RUs - not just on IMs. Separation of duties: delivering the specification is mandatory, but actually using the resulting common Union API/web UI to share data is optional for facility operators under Art. 14(5)(b). Distinct from the 2 September 2027 IM implementation report (Art. 17(2)(a)). |
Art. 21(3) Art. 21(4) Art. 14(5) |
| 02 Mar 2028 | Implementation report to the Agency Art. 17(2)(b)(ii) requires each operator of rail freight service facilities to report to ERA in the area of traffic management by this date. Terminal operators are telematics stakeholders per Art. 3(8)/(9), so this is a binding obligation on the terminal - not a matter of prudent compliance. Reporting runs until proof of compliance is provided under Art. 18. |
Art. 17(2)(b)(ii) Art. 18 |
| 10 Dec 2028 | ILU & rolling stock reference data; Freight reference data Intermodal Loading Unit reference data (containers, swap bodies, semi-trailers) must be registered in the ILURD. Annex pt. 3.3.3 places that duty on ILU keepers, not on terminals as such; it reaches the terminal directly only where the terminal is itself an ILU keeper. Keep the roles apart on the transitional period: the flat 12-month extension under Art. 16(3) is granted to operators of rail freight service facilities, so it shifts this deadline to 10 December 2029 only for an entity that qualifies as one - a keeper that is not an operator of rail freight service facilities stays bound to 10 December 2028. |
Art. 16(2) Art. 16(3) Annex pt. 3.3.3 Appendix G TD103 §7 |
| 10 Dec 2028 | Rolling stock reference database (RSRD) - dependency awareness Vehicle keepers - not the terminal - are responsible for setting up and maintaining the federated Rolling Stock Reference Database (RSRD); this is a vehicle-keeper obligation under Annex pt. 3.3.2, not a terminal obligation. But the TrainCompositionMessage you receive from the lead railway undertaking references vehicle numbers registered in the RSRD - if RSRD data is missing or inaccurate for a wagon handled at the terminal, you cannot correctly validate that composition data. |
Annex pt. 3.3.2 Appendix G |
| 04 Mar 2029 | Capacity management - object identifiers & path requests If the terminal acts as an applicant for path requests (e.g. for shunting paths or internal terminal movements on the first infrastructure manager's network), capacity allocation messages must comply with the TEL TSI specifications by this date. |
Art. 16(2) Art. 16(3) Annex pt. 2.1 Annex pt. 2.3 Appendix G |
| 09 Dec 2029 | Train traffic, train closure, wagon data, eCN, train composition All core terminal operational obligations under TEL TSI must be fully implemented: receiving ConsignmentNoteMessage and TrainCompositionMessage (Annex pt. 2.5.1(3)), sending TrainRunningInformationMessage with train closure confirmation (Annex pt. 3.2.1.3(3), which calls for the message referred to in Annex pts. 2.6.1(6) and 2.6.3), sharing block train traffic data (Annex pt. 2.6.1(6)), providing historic data access (Annex pt. 2.7 - the record and the duty to grant access are mandatory, while public disclosure for freight follows the freight RU's Art. 5(4) opt-in), and wagon/ILU status data exchanges. |
Art. 5(2) Art. 5(4) Art. 16(2) Art. 16(3) Annex pt. 3.2.1.3(3) Annex pt. 2.6.1(5)(6) Annex pt. 2.6.3 Annex pt. 2.5.1(3) Annex pt. 2.7 Annex pt. 3.1.1 Annex pt. 3.2 Appendix G |
Arrivals - what the framework owes the sector
| Date | Deliverable | Reference |
|---|---|---|
| 02 Mar 2026 | TEL TSI enters into force Any new telematics application deployed from this date must comply immediately with TEL TSI. This is the official legal date per Art. 27(1): the twentieth day following publication in the Official Journal on 10 February 2026. |
Art. 16(1) Art. 27(1) |
| 15 Mar 2026 | ERA manages & assigns organisation, location and ticketing codes From this date, organisation code governance is formally with the Agency. Verify your organisation code is registered and correctly assigned. |
Art. 9(3)-(6) Art. 27(3) |
| 02 Sep 2026 | ERA central repository operational (metadata, reference data, API subscriptions) The ERA common central repository becomes the single source of truth for reference data. Subscribe to automated notifications of updates. |
Art. 8(1)(a)(c)(d) Art. 8(2) Art. 27(2) |
| 02 Sep 2026 | ERA publishes user manual for code-assignment web applications Guidance on how to request and update organisation and location codes via the Agency's web applications. |
Art. 9(2) Art. 27(2) |
| 02 Dec 2026 | IMs share network-specific data requirements with ERA Each infrastructure manager shares with the Agency the network-specific data requirements it applies or intends to apply. May introduce new data requirements affecting your systems per network - monitor for impact on the first infrastructure manager and the second infrastructure manager interfaces. |
Art. 11(2) |
| 02 Dec 2026 | Member States communicate national contact point (NCP) details to ERA The Agency publishes NCP details. Relevant for code allocation escalation and national coordination of TEL TSI implementation. |
Art. 20(4) |
| 02 Mar 2027 | ERA provides web applications for code assignment Replaces the current CRD-based code management system. New tool for submitting code requests - ensure your team is familiar with the new interface. |
Art. 9(1) Art. 27(4) |
| 02 Mar 2027 | ERA provides implementation monitoring web application for IMs and RUs The tool where IMs and RUs will report their implementation progress against Appendix G milestones. Your reporting obligation (2 March 2028) depends on this tool being operational. |
Art. 17(1) Art. 27(4)(c) |
| 02 Mar 2027 | ERA's self-assessment tool goes live This is when the Agency must provide the web application telematics stakeholders use to self-assess their telematics applications against TEL TSI - the starting point for being checked, not a deadline of your own. |
Art. 18 Art. 27(4)(d) |
| 02 Sep 2027 | IMs report implementation status to ERA the first infrastructure manager and the second infrastructure manager must report on capacity management, train preparation and traffic management. Affects your IM interfaces - their reported status informs your own integration timelines. |
Art. 17(2)(a) |
| 30 Sep 2027 | IMs' common sector specification for the capacity/traffic-management API and web UI Infrastructure managers must deliver their own common sector specification for the common Union API/web UI used for capacity management, train preparation and traffic management (Art. 14(5)(a)) by 30 September 2027, coordinated through ENIM and the future Network Coordinator - this is a mandatory 'shall' obligation on IMs. It does not cover your own obligation: as a freight railway undertaking you separately must cooperate on and deliver your own common sector specification for the freight-wagon/load API by the same date (Art. 21(2)+(4); Art. 14(6)) - see the 'common-specs' entry in your Deadlines. Once delivered, actually using either common Union API/web UI remains optional for freight RUs (Art. 14(6): 'may jointly use'). |
Art. 14(5), point (a) Art. 21(1) Art. 21(4) |
| 31 Dec 2028 | ERA recommends update of functional/technical specifications to the Commission Based on this recommendation, specifications may be revised - potential future changes to the technical documents in Appendix C. Monitor for impact on your TEL TSI implementation plans post-2029. |
Art. 23 |
TSI Solution GmbH checked this content against the Official Journal text on .