The background to this
The information design geek in me took special notice of this post by Daniel Gray, about the excessive number of train tickets he received for a return journey. I was beaten to a visual response by a follow-up from Neil Martin with a solution to fit everything onto a single ticket.
My version of events
For my attempt I’ve attached a number of rationale:
- complex route (from my local station to the furthest significant point I could think of – apologies to those in Penzance)
- involves using London Underground system
- assumed the customer has specified the times they want to travel (the cheaper option)
Unlike Neil’s solution, the purpose of this design isn’t to get all the information into a single ticket, but to make the information on the ticket more useful to the customer and to provide some useful additional information.
To this end, you’ll see from the design that I’ve split it between what the customer needs to know, and the stuff that is for staff to check. Because staff of the rail companies look at these every day, they will soon become familiar with finding the information they need to check.
An equivalent ticket would be produced for the return journey, so whilst it’s not as environmentally sound as a single ticket for the whole journey, it is (I hope) more logical.
The example shown above is a sort of ‘worst case’ to show how the design would cope with a lot of information on it. The two images below show more realistic situations:
A booked return between two stations
An off-peak ticket