A train being cancelled because it is cancelled isn't a reason. Whether you like it or not.
No, the train has been cancelled due to a short notice change to the timetable. The reasoning behind that could be anything, the fact is it doesn't matter to a certain extent why an individual train has been cancelled, the information passengers want to know is 'when is my next train to my destination'. Why spend time explaining issues such as depot issues, driver shortage, when the top line is 'train is cancelled, short notice change to tt for operational reasons'. I'm not claiming it's a perfect announcement, just that it is adequate for it's intended use.
What I found insulting was the assumption that one would have to be an enthusiast to want an explanation, as if it's some kind of anorak interest driving the desire for one. Rather than common courtesy and a desire not to be insulted.
You have been given an explanation though, something has happened that has necessitated a short term change in the timetable. There may not be a reason code for it, or a programmable announcement, but the announcement is adequate for many others who are traveling to remind them check the day's timetable for any updates. I would advise against getting insulted by a cancellation announcement though, can't be good for the old health.
maybe? but most regular travellers i've known had a good idea of which types of problem occured and the likely impact.
"oh thats its for the day then, lets switch to the bus." or "lets sit around a bit and take the train in an hour" . Although they mostly weren't rail enthusiasts, they'd usually have a pretty accurate idea in an instant.
This made their travel more efficient so they spent time building up standard responses to common problems.
if no reason is given then this breaks down.
The announcement should prompt people to check apps/departure boards and make that call for themselves. I'd imagine if there was a more suitable reason available in the system, they'd use it.
At least leaves on the line or engineering works are a root cause - If you hear "short notice change to the timetable", it just leaves you with the next question of "Why was it changed?".
Which goes back to 'does it matter?'. I can almost guarantee your next question is 'when is the next available train' which is more important than why the cancellation occurred IMO.
You bet wrong. Previous research by the Rail Delivery Group (RDG) has suggested many do want to know the reason. I can't remember if it was a majority or not, but it was much larger than 10%.
Otherwise there wouldn't be reason codes to use in the first place.
Are we talking 'a' reason, or 'the' reason. Just showing a train as cancelled does spark questions, but a short notice change to the timetable is 'a' reason, and as I've said before the more important bit of information at that time is 'when is my next train'.
My understanding of reason codes is they are primarily used in the delay attribution process (hence why there's a lot of them, and some rarely used) and integration into PIS was a secondary benefit for what they were designed for, but happy to be corrected on that.