StackExchange Travel - user's ticket printed with inappropriate restriction code

[Muzer]

Just thought this might be of interest to some on here:

https://travel.stackexchange.com/qu...th-restriction-forcing-use-of-specific-trains

I have an Off-Peak Day Return ticket from Hull [HUL] to Leeds [LDS]. When I purchased this ticket through the Northern app, I also reserved seats for both legs. When I collected the tickets, I was surprised to see that the restriction code TD. The key part of this restriction (as I read it) is "Seat reservations are compulsory." for outward travel, and "Not applicable" for return travel.
Does this mean that I must travel on the reserved train for one or both of the legs (and not on another service)?
Note: I contacted TransPennine Express about this, and they claim this restriction code does not apply to an Off-Peak Day Return, and I am free to use any service. This is one possible answer, preferably with an explanation of to why tickets might have incorrect restriction codes, and some references as to how to tell the restriction can be ignored.

Why would an off-peak return have printed with a restriction code that's clearly more suited to an advance?

 

[hairyhandedfool]

There have been an awful lot of errors cropping up on tickets in recent times, most notably since the fares change in May. I suspect this is just another one of them, the restriction should be I1 ("not valid on trains timed to depart after 0429 and before 0930", which in itself is stupid wording for "not valid on trains timed to depart between 0429 and 0930"). I'll see if I can get this passed on, but without knowing where the ticket was collected it might be difficult to resolve. I would assume Hull, but i don't know who has what machines there and all the important information is covered up in the picture.

 

[Muzer]

From StackExchange:

in reply to the comment there (I don't have an account, so perhaps you would be kind enough to add it), the tickets were collected in Hull from one of the TPE machines there.

 

[hairyhandedfool]

Thank you kindly, I'll pass that on.

 

[tspaul26]

("not valid on trains timed to depart after 0429 and before 0930", which in itself is stupid wording for "not valid on trains timed to depart between 0429 and 0930")

The latter wording invites the question of whether the prohibited time period is inclusive or exclusive of the start and end times. The former wording is clearer because it does not have this ambiguity.

 

[furlong]

Why would an off-peak return have printed with a restriction code that's clearly more suited to an advance?

Cross-check by asking what price was paid / printed on the ticket - covered up in the photo - and ask for the 4-digit code after the / following the ToD CTR.

 

[hairyhandedfool]

The latter wording invites the question of whether the prohibited time period is inclusive or exclusive of the start and end times. The former wording is clearer because it does not have this ambiguity.

I would have thought the word "between" would be enough for most people as 0930 isn't between 0429 and 0930. However, if that is such an issue you could equally have "not valid on trains timed to depart between 0430 and 0929 inclusive"