The Late Train and the Locked Form: Designing Rail Compensation as a Decision Tree
Photo: Carlos Delgado, CC BY-SA 3.0, via Wikimedia Commons
A delayed train produces a familiar sequence of emotions: irritation, resignation, then a vague sense that something might be claimable. The obstacle is rarely the arithmetic. It is the branching. UK rail delay compensation schemes ask passengers to establish how late they arrived, whether their ticket type qualifies, which operator is responsible, what evidence is acceptable and whether an exclusion applies. Presented as continuous prose, those conditions read like a locked form. Presented as a decision tree, they become a journey.
The real barrier is branching, not bad maths
Most delay compensation pages explain the principle adequately. Trains are late; passengers may claim; payment is a proportion of the ticket price. The difficulty arrives in the qualifications. A 15-minute threshold is not the same as a 30-minute threshold. A return ticket may be assessed on one leg. A split ticket may require more than one booking reference. A season ticket may be calculated differently from a single. An operator-specific exclusion may sit several screens below the cheerful headline.
For an information designer, this is not a reason to simplify away the complexity. It is a reason to expose the structure. A decision tree is honest about conditionality. It says: start here, answer this, then move left or right. It does not pretend that every passenger is the same passenger.
A ticket-style grammar for a claims journey
The visual language should borrow from the ticket itself. A ticket already carries the fields that matter: origin, destination, date, ticket type, price paid and reference. A claims graphic can reuse that grammar so the passenger recognises the information being requested. The first panel should not be a legal notice. It should be a journey summary: where you travelled, when, on what ticket, and how late you arrived at your destination.
The second panel should show the delay bands as a ladder, not a paragraph. Fifteen minutes, thirty minutes, sixty minutes and longer should be visually ordered, with the applicable compensation proportion attached to each band. The third panel should ask about ticket type. The fourth should list evidence: ticket, booking confirmation, receipt, screenshot of a journey record. The fifth should show the likely payout range and the route to claim.
This is not decoration. It is a reading order that matches the decision order.
What changes between operators in 2026
In 2026, the contrast between operator schemes remains material. Some operators use a 15-minute trigger; others retain a 30-minute threshold. Some accept a booking reference; others expect a scanned ticket or a clear photograph. Some make provision for split tickets; others require each leg to be evidenced separately. The precise rules change, so a national graphic cannot be a single fixed poster. It needs a configurable core: a stable decision tree with operator-specific layers that are dated and sourced.
The design implication is important. Do not bury the operator name in a footer. Put it at the top of the tree, because it changes the branches. Do not present a universal compensation table as though it were a statute. Present it as a map with a visible edition date. In a field where conditions move, the date stamp is part of the information, not an editorial afterthought.
Show likely payout without implying a guarantee
A decision tree can do something prose struggles to do: it can show a likely payout at the point of decision. That is valuable, but it must be framed carefully. Use a range where the calculation depends on ticket price or journey leg. Use the word 'likely' rather than 'you will receive'. Show the assumptions in a small, readable panel: ticket price, delay band, operator scheme, evidence supplied.
A ticket-style graphic can also distinguish between the amount claimed and the amount paid. Delay compensation is not a refund of the whole journey in every case. It is a proportion, sometimes subject to a minimum or a scheme-specific calculation. The graphic should not flatten that distinction. It should show the proportion, the base to which it applies and the evidence that supports it.
Accessibility is a design requirement, not a final check
A decision tree that works only as a large landscape poster has failed. It must survive a phone screen, a printed leaflet and a screen reader. That means a logical reading order: question, answer options, consequence. Colour cannot be the only carrier of meaning; each branch needs a label and a shape. Text must remain legible at mobile size. The printable version should fit on one or two sides of A4 without turning into a maze.
The same discipline applies to the ticket-style panels. Use clear field labels, generous spacing and plain language. Avoid abbreviations that only regular travellers recognise. Where an operator uses a term such as 'advance ticket' or 'split ticket', explain it in a short note rather than assuming familiarity.
The editorial test
A good test is whether a passenger can answer three questions from the graphic alone: Am I probably eligible? What evidence do I need? What should I do next? If the graphic cannot answer those questions without a second document, it is still prose in disguise.
Delay compensation is a public information problem before it is a customer service problem. The claim may be small, but the decision tree is the contract. Draw it clearly, date it honestly and let the branches do the work that paragraphs have been doing badly.
