L

Lord Dixon of Jericho (LD)

Speaking in the House of Lords on 26 October 2026

Debate

Railways Bill

Contribution

My Lords, in moving Amendment 291A, I will also speak to the other amendments in my name in this group. I am grateful to the noble Lord, Lord Moylan, for adding his name to all of them. This is the first chance we have had since the publication of the draft retail code to look at the issues of data and a potential subsidy. In general, I am very sympathetic to high-level principles-based approaches of regulation, but in these specific areas I think the code is less future-proof and will be more cumbersome in practice than it needs to be. I will start with data and then move on to talk about money. Despite many attempts over the years to specify that data should be more open and easier to use, we are in a complete mess. Fares come as large XML file dumps, and, as I said the last time we spoke about this, 11 operators publish accessibility data in 11 different formats—one of which is a PDF. The problem here is that the draft retail code takes the same approach that has failed time and again for many years. It is deliberately and consciously high-level principles only. I think we can do it differently and do it better. I am acutely aware that this needs to be future-proofed. As we have just said, while infrastructure moves slower than legislation, technology moves faster than legislation, and people are right to worry that a detailed technical standard that looks right in 2027 will look odd in 2035 and unworkable by 2040. The code presents that as a binary choice between high-level principles and short-sighted technical detail, but that is a false choice, and that framing is exactly what has got us into the mess that we are in today. I urge us not to make the same mistake again. Amendment 330JD tries to reframe how we think about this problem. If noble Lords will forgive me, the core idea is basically that GBR must eat its own cooking. The simplest way to make sure a meal tastes good is to make the person who cooked it eat it, and then we have to make sure it tastes good not just to them but to everyone else. In practice, that means that GBR’s retail app must use the same services it offers to everyone else—the same data, functions and pipe. That is, in essence, the whole idea, and the rest is basically detail. If you get that incentive right then the thing works without needing to be policed. If GBR’s own app depends on a set of interfaces, it has every reason to make them fast, reliable and well-documented. If it were ever tempted to give a competitor a slower feed, or a new fare a week late, it would be doing the same thing to itself. You would therefore not need the regulator to spot discrimination after the event because it would be fundamentally baked-in. This idea is not at all new. It is exactly how Amazon Web Services has worked since 2002, and it is how Openreach works. Section 89A of the Communications Act has basically the same mechanism. It is pretty much how open banking works: the interface that third-party apps use must have the same level of availability and performance as the bank’s own. Really importantly, certainly from our point of view, this is extremely simple to deliver and police. It is far easier to maintain one codebase—one kitchen and set of ingredients, in food terms—and it will result in far less work for lawyers than the proposed principle in the draft code of non-discriminatory access, which would have to be reinterpreted every single time something new launches.

More from Lord Dixon of Jericho (LD)

Other recent Hansard contributions by the same speaker.

About Hansard

Hansard is the official verbatim record of proceedings in the UK Parliament. Every word spoken in the Commons and Lords is recorded and published — this page is a single contribution from that record.