Make the journey
part of the day.

The planner has three manual checks: last trains, ticket and checking ahead. Each is false or true, giving two cubed, eight possible combinations. Bars compare three checked items and zero at one hundred fifty pixels per item. The summary counts checks. Exactly three displays Ready to travel, but this is a label driven by user ticks, not a verified ticket, train service or safe trip. Route text does not change this count. The actual form contains From, To, travel date and place to watch. Bars compare four entered fields and three check booleans at one hundred pixels per item. Source change handlers save them locally without trimming. Empty route fields can coexist with all three checks and the Ready label because the source has no validation requirement. The page does not search stations or venues, fetch live rail status, reserve a ticket or determine a departure. The actual JSON document has nine fields: the seven stored inputs, a real physical export timestamp and a fixed scope boundary. Bars compare nine document fields with seven stored inputs at fifty pixels per item. Raw timestamps are retained in verification evidence. Reload restores the saved route and ticks. Reset writes seven empty or false defaults back to storage instead of removing its key. The scope says live rail, ticket and venue information must be checked separately; exporting does not submit a booking.