Hafren
|
 |
« Reply #3 on: February 19, 2025, 22:48:12 » |
|
This having to pick a specific train has turned into quite a bugbear recently...
A lot of people now buy on apps, and because they're given an itinerary they assume they have an 'advance' ticket and can't travel on a different train. I ask to see their ticket and it turns out to be an Off-Peak Return or whatever. It does say 'suggested' or whatever somewhere on the itinerary but still.
I suppose if it didn't happen they might use the off-peak ticket on a peak train without realising!
Also it's very hard to buy the right fare, or even know about it, when there are options. If the starting point were choosing the ticket, rather than choosing the journey, this would be alleviated. People would save money in some cases as they would see cheaper options that the planners don't offer because the algorithm doesn't pick out t hat journey. And people might even come to understand the fare structure better because the grids currently shown by the planners make it feel like the whole system is built around per-journey quota-controlled fares.
Examples:
Brighton Main Line: typically 3 routings - Any Permitted (great for Gatwitck Express, which is often lightly loaded - a useful gem at times!), Not Gatwick Express, Thameslink Only. Thameslink only is cheapest. But at certain times it's hard to pick out from a planner if the Victoria journeys are picked out by the algorithm, especially if it's a day when engineering work messes with the outcomes.
London: Do I want London Terminals, London Thameslink (Brighton Main Line example again), London U1, or Travelcard? I recently did a split journey where the best options involved splitting at London - i.e. one of the legs was booked to/from London U1 or London Thameslink. But there's a certain art to finding London U1 journeys. Why not just offer the options when entering London? For London Thameslink I tried entering Farringdon, but on that day it decided going to Victoria then Underground was quickest, and it was hard to force the Thameslink option! Someone who doesn't know the system well and isn't inclined to play around just woudln't get there.
Wales - London (and Southern Region destinations, actually): Via Salisbury is often cheaper. (For some destinations there's no route Salisbury fare so splitting is needed.) It's a very good way to save money, and sometimes avoid the same scale of peak fares, for those who don't have the flexibility to buy an Advance fare. But because it's slower, the planners don't find the journeys via Salisbury unless the user is in the know. If someone just asked for a flexible London ticket, the system would offer the fare.
I recently assisted someone with a journey plan between South London and the Midlands. The cheapest fare was route Nottingham but at certain parts of the day it wouldn't offer them this fare because going via Derby gave better options. They wouldn't have known to tell it to offer journeys via Nottingham.
Back when QJump was around and had its own engine (I think later it was absorbed into TheTrainLine) there was a button to list all fares. Very useful feature!
I've never been quite convinced that mileage-based fares are the answer, as rural routes and major arteries have such different fares now, which also potentially ties in with local economic needs, not to mention that there are so many mileage permutations for some A-B journeys, which could create a lot of anomalies, or require different more complex 'via' routings.
Dealing with the peak fare issue would do a lot to simplify journeys. I'm not convinced we need evening peak fares any more. Retaining morning peak restrictions would serve a purpose by by crudely differentiating between commuter travel (to maintain/maximise income) and leisure travel (lower off-peak fares to attract non-captive customers). Evening peak fares make planning long-distance journeys overly complex, and also could cause worries if late running causes the last off-peak train to be missed, or if unsure of return travel time - do I buy the off-peak and hope I make it in time, or buy the peak fare just in case, and then make it at the off-peak time after all? But even with just mornming peak fares we really don't need so many restriction codes. It might require more than one code but not hte number we have now! It might make sense to have before 09:30 for some flows, and arriving London after 10am for some flows, and some flows with peak ending before 09:30 if there are longer gaps in service, but doesn't need hundreds of restriction codes. And for railcards... either do away with the peak restriction, or just say it isn't valid for a discount on the peak fare! (That might cause problems where the peak ticket is the only fare, on routes with no peak/off-peak distinction...)
If there were just a morning peak, and just a handful of restriction codes, and if booking systems were based on purchasing the ticket rather than the journey, the system would immediately be much, much simpler, and easy to plan around!
For a recent journey that required crossing London in the evening peak, it took what felt like hours looking at all the split options - even on that one axis there were different restriction codes for the different combinations! And the trains weren't exactly overloaded. Perhaps without peak fares they would be though... but that's probably no different from the crowding on the first & last off-peak trains!
|