So when I buy my Freedom of the North West Rover and scan the Aztec code to create my user created pass similar to post 19, this is going to be fine if someone scans it, but if they visually inspect it at a gateline I would suggest they should be suspicious, especially if they don't intend to scan it.
In my opinion, if you are unable to show the full ticket details in human readable form, then you do not have a valid ticket. The fact that most of the time scanning a barcode is sufficient doesn't mean that you can assume that only having the barcode is sufficient.
I agree with you, however I could add all of the human readable details in the ticket in post 19 to the pass - I just didn't do this to demonstrate it. At that point do I have a valid ticket? And if I do, what is materially different to my just taking a photo of the PRT and presenting that?
Where it will look exactly the same as a ticket added from a PDF scan, or a screenshot.
Although it's worth noting the ticket PDFs and wallet passes can vary quite dramatically between producers
Agreed (I don't think it's right you should have problems, but that's the reality)
Absolutely. And the fact the gates reject to many valid tickets spuriously doesn't help this either, as the staff don't treat it as an abnormal event
You can't solve a people problem with technology though.
I was paying attention to this for the first time travelling on LNER this morning. I’ve only ever bought e-tickets from TrainSplit or the forum site so hadn’t realised some look quite different.
I’m starting my seven day rover on Saturday. I’ll create a version in Apple Wallet from the PRT and see how I get on. I’ll be carrying the original so any problems are easily solved.
I think that's the golden rule. It is on the passenger to ensure they have a valid ticket, and if you can't quite remember the Super Off-Peak time from your station, across London, to destination X routed via Y, then letting someone in 30 minutes early really isn't going to make much difference. The inspector on the train probably won't know either.
It is the lowest paying railway job as far as I am aware, but it needs similar ticket knowledge to others (ticket office, conductor, revenue protection), good customer service skills, patience, and the ability to remain calm and professional while being abused.
Except that the gateline just scanned the ticket. Why expect the member of staff to spend time scanning a ticket when the gateline could (with the right technology) just pass on its findings?
Does that technology exist, and does the member of staff have access to it? Because if not, then there's your answer. Either way, the problem is that in the scenario described the staff member is looking at the ticket and reacting to that rather than consulting the outcome of a scan to see why the ticket was rejected.
Ha, a brave assumption!
The ticket office staff at my station are very knowledgeable and would be willing to find out if they didn't know off the top of their heads. All of this info is documented somewhere, you just need to find a member of staff willing to spend time to search for it... time that is not available at a single-staffed gateline.
Unfortunately, your ticket office staff aren't at every station!
I don't know if it's a problem, but it's what some people are complaining about on this thread.
It's not a technology problem if the gateline assistant has an alternative means of scanning the ticket to establish why it was rejected. There's no need for that to prevent anyone else using the gates, passenger and assistant can simply move to one side.