This article explains what the settlement means for contract administration, design approvals and competition in major railway procurement.
A settlement closes a dispute over project information
Tilsta, a construction company belonging to the Fegda group, and LTG Infra, the infrastructure company of Lithuania’s Lietuvos geležinkeliai group, have settled a dispute concerning part of a Rail Baltica contract worth €149.4m including VAT. The section runs between Kaunas (Palemonas) and Šveicarija. The settlement was reported on 3 November by Verslo žinios, citing BNS. The supplied report does not state the terms agreed by the parties, whether any payment was made or whether either side accepted responsibility. It therefore records a resolution, not a finding that either party breached its obligations.
What Tilsta asked the court to order
Tilsta said it had gone to court during the summer, seeking an order requiring LTG Infra to check and approve the working project for the section. It also sought a penalty of €600 for each day. The contractor said it did not have the necessary data for the second part of the section. Those statements describe Tilsta’s position in the dispute, rather than facts established by a judgment. The report does not provide LTG Infra’s response, explain the contractual allocation of design information, or say whether the court ruled on the claims before the parties reached their settlement.
Why working-project approval matters in a works contract
A working project is the detailed design information used to organise and carry out construction, so its preparation, checking and approval can affect whether a contractor is able to proceed with the works. This dispute illustrates a procurement issue that can recur in complex infrastructure contracts: the agreement must make clear which party supplies information, which party develops the design and which party approves it. When those steps are delayed or disputed, the parties may argue about access to the site, responsibility for disruption and financial consequences. Here, the reported claim centred on approval and missing data, but the settlement leaves those responsibilities undisclosed.
The procurement signal is about clarity, not blame
For public buyers and bidders, the reported outcome points to the value of precise arrangements for design review, information handover and escalation when approvals are contested. A request for a daily penalty can be a contractual remedy sought by a bidder, but it is not evidence that the remedy is owed. Equally, a public contracting authority’s role in checking a working project does not by itself establish responsibility for a delay. The parties’ agreement to end this dispute may avoid a longer court process, while the absence of published settlement terms means it cannot show which interpretation of the contract prevailed.
IN NUMBERS
The Rail Baltica case shows how a major works contract can become a dispute over the boundary between design preparation, approval and information supply. Its immediate resolution is clear; the contractual lessons will depend on details that have not been reported.
Reported from 15min.lt, 2026-11-03. The Tender Wire is published by Otnox.
