I agree with the last point, but not the offhand dismissal of the suggestion that cancellation of an hourly service be deemed to cause an hours delay. There is something especially galling about being delayed by the decision of an operator, that is only compounded when the effect of some regained time is to move you out of a refund bracket. It is also a simple rule to apply.
That doesn’t alter the fact that there is a measure of win some, lose some. I gained on Wednesday night because my train was 31 late, having expected to be 29 based on most of the journey beforehand. Other times, I’ve had the frustration of being 31 late most of a journey, then regaining 2 minutes with recovery time.
Unfortunately it is not as simple as you may think.
Do you want it to apply across the whole railway network? Shall we have different rules for different routes? If not, how do we handle those routes with services at irregular intervals? If yes, you are now starting to complicate things for customers.
Let's say we just consider those routes with a frequent service, many won't have clockface timetables. For example, a four-train-an-hour timetable may have services at 10/20-minute intervals. What frequency would you call that route?
Even if we just take into account routes with clockface timetables, what happens when you have services booked at xx40 one hour, and then xx39 the next hour, as is the case with most clockface timetables at least for some hours during the day? Is that still considered hourly? Does this get treated as 59 minutes later or 60 minutes later? If the latter, what if it were only 58 minutes behind? Should that be treated as 60 minutes too? You can say perhaps use 55 minutes as the benchmark, but you have now changed a system with easy to remember and calculate thresholds to one with a number many people would struggle with. Progress?
Taking even a smaller subset of routes (which now won't see many left) with strict clockface times at all hours, I now go back to the question asked in the previous post which is a repeat of the same question upthread, what would you do when the service is further delayed in reality? Say you have a half-hourly service and the customer gets on the train behind only to be delayed further by another 45 minutes. Do you compensate for 30 minutes as per booked arrival time at destination, or 75 minutes as per actual arrival time? If the former then I can already see half of the forum getting their pitchfolks ready. If the latter, why is it booked times in some cases and why is it actual times in others? How do you explain it to the average punter, for whom any mention of railway fares would be sufficient to make their heads explode?
These are just some of the issues that popped into my mind right now. I'm sure there would be others too, and this is not even yet considering the validation process becoming more convoluted.
Delay Repay is a simple system to understand, and it is based on the principle of actual delay to a customer's journey so it is fair. (It probably sucks for those who narrowly miss out but this is an inherent problem for all systems, unless you truly run the scheme on a true sliding scale. Maybe that's what we should have? Good luck figuring out how much compensation is due to the Average Joe in that case.) All it perhaps needs in terms of structure is for some issues surrounding minority cases (such as split tickets) to be clarified by DfT/RDG ideally. If on top of that there is a more rigorous quality assurance mechanism by relevant authorities then I think it can be the holy grail of delay compensation. For now, it has laid down a good foundation stone. What it needs is being built on, not being dumbed down by further complication and undoing the good work so far.