Given it’s automated for a lot of these claims, it’s probably not worth the cost of putting that extra barrier in, especially as the TOCs won’t want to put too much store in what box a claimant ticks.
I wouldn't want to have to explain that to an auditor, frankly.
"Why are you paying out money that hasn't been claimed?"
"We don't want to put too much store in what box a claimant ticks."
Realistically, that's not gonna be the end of that conversation, is it?
If it's auto delay repay, I can understand why asking the passenger how much they want and paying the lesser of that or the amount the TOC thinks is due, would add unnecessary bureaucracy. But when I fill in a manual claim and they ask me to enter the cost of the ticket(s) and which delay repay bracket I'm claiming for, then I really can't see what the problem would be in taking that into account rather than ignoring it?
Nor can I see why they ask the passenger how long the delay was if they're going to ignore the passenger's answer?
What I
can see, however, is that it might cost money to rectify the system once it's been designed incorrectly so that it can pay more than has been claimed. But capping payments at the amount claimed absolutely should have been in the design specs for any software that is supposed to automate (fully or partly) the processing of claims, in my humble opinion.