Build a Two-Day Plan from Fixed Arrival, Overnight, and Departure Anchors
Use this process only when the first record says fits for one destination, origin, party, and exact two-day interval. Copy its confirmed arrival journey, overnight record, and return journey without changing their dates, endpoints, or sources. Those three items become fixed anchors. You may add at most one main visit on day one and one on day two, and each must already be named by you; the article does not supply attractions, food stops, neighborhoods, or detours. The task is to place those named visits between confirmed anchors using current opening or reservation evidence and complete transfers. If a mandatory link is unknown, the plan stops rather than growing an alternative branch. The output is one dated sequence and one later go-or-stop recheck, not a universal itinerary, spending recommendation, or promise of service, access, or total cost.
Copy the passed scope without reopening selection
At the top of a new sheet, copy the exact destination identity, origin, party, day-one departure boundary, day-two return boundary, and the timestamp of the fits result. Do not compare other destinations or rerun the earlier decision with relaxed limits. Then copy the identifiers and sources for the confirmed outward journey, overnight record, and return journey. If any copied value differs from the passed record, pause and reconcile the record before arranging activities. This step keeps scheduling separate from destination selection. The schedule may organize confirmed facts, but it cannot turn an unknown field into a pass or introduce another destination under the label of a nearby stop.
Place arrival, overnight, and departure as fixed anchors
Write the arrival endpoint and local time as the first destination anchor, the overnight check-in or access window as the middle anchor, and the first required return departure as the final anchor. Include any already confirmed transfer between them. Use these times as occupied boundaries, not flexible suggestions. An arrival at a station is not arrival at the overnight property or main visit unless the evidence says they share a boundary. Likewise, checkout is not the return departure. This three-anchor frame reveals the actual open intervals on day one and day two without inventing a fixed duration, recommended pace, or generic buffer for every traveler.
Insert at most one named main visit per day
If you already named a main visit for a day, verify its official identity, applicable opening window, reservation state, and entry conditions for that date. Place it only in an open interval between anchors. Do not browse for a replacement when it does not fit, and do not fill blank time with a catalogue of optional stops. A day with no named main visit can remain an arrival, overnight, or departure day. Keeping the maximum at one preserves a readable chain and makes every transfer visible. Record unknown when the responsible page does not confirm a mandatory field; photographs, reviews, and popularity do not replace the official record.
Verify every transfer in sequence
For each adjacent pair of anchors, record the responsible operator or authority, start and endpoint, date, local times, transfers, and check time. The National Rail planner demonstrates complete origin, destination, date, time, and connection fields for its own network; apply the same evidence boundary to the actual operators in your plan. Do not use the duration of a central segment as door-to-door time. If a transfer ends outside the next property's boundary, add the documented final connection. If a mandatory link is missing, conflicting, or outside an opening window, mark the sequence stop. Do not repair it by silently changing the visit, overnight property, route, or destination.
Freeze one version and define the recheck
Number the confirmed sequence from the original departure through the final return. Beside each changeable item, retain its responsible URL and last check time. Mark which fields need one fresh check shortly before departure: destination access, visit opening or reservation, overnight status, planned transport, and applicable alerts. The National Rail alert page distinguishes planned journey information from live service changes and provides a model for a current recheck; it does not certify other networks. Freeze the version after this list. Repeated polling, optional branches, and automatic substitutions would create a different system and are not required for this two-day record.
Run the go-or-stop check and close
At the chosen recheck time, open the same responsible sources and record a new timestamp for each mandatory changing fact. Mark go only if the fixed destination, arrival, overnight, named visits, transfers, and departure remain mutually consistent with the passed boundaries. Mark stop if any mandatory item now fails or becomes unknown. Do not jump to another destination, route, property, or visit; a replacement requires a new explicit record. Finish with the exact sequence version, go or stop, unresolved facts, and check time. This closes one schedule for one interval while preserving the difference between current published evidence and what may happen later.
Common questions
Must both days contain a main visit?
No. Each day may contain zero or one visit that you already named.
Can I add optional stops after freezing the plan?
Not to this record. A changed sequence should be opened and checked explicitly.
What happens if an alert changes one mandatory link?
Mark stop or unknown as supported; do not switch automatically to another route or destination.