Flagoak Studios

The Rest Between Trips

The fastest return team in Winter Storehouse comes into the depot just as a second wagon needs a driver. It is easy to put the arriving team straight back on the road. The handoff screen should show why that choice changes the next trip. Fatigue concerns the team and its work schedule, while weather and load limits concern the route. Keeping those facts separate helps the player understand why a familiar road takes longer this time.

Three parallel readiness tracks for team, wagon, and load
Three parallel readiness tracks for team, wagon, and load.

Open with the handoff

One clerk checks in the empty wagon. Another checks the team in a separate column. This matters because the wagon could be prepared for a different team while the returning crew rests. The schedule gives readiness times for the equipment, crew, and load separately. Set up the opening so the next possible departure depends on the crew rather than wheel fittings. The test then reveals whether players read the readiness time as a property of the right object.

Use only three states on the first board. A team can depart immediately, depart after a rest interval, or remain assigned to a crossing until it returns. In the last case, the diary can show the forecast without letting the player select that team. The first two states remain selectable when the decision is legal. Show the expected arrival with and without a rest stop, and mark which part of the timing changed.

Plan the next interval

When the receiving yard needs a small load, an available team with a light wagon can carry it past the first marker. A larger consignment can wait until the previous crew has recovered enough to make the longer route. A player can also accept a later arrival if the depot has enough stock and the next interval will suit the crew. All three choices share the same road report. The trade becomes visible through the schedule and how much slack remains at the receiving yard.

One interface version displays a colored band across the rest interval. The alternative leaves a ruled blank in the team schedule and writes the next available time at its right edge. Ask players to name when the team can leave. If they try to drag a departure into the blank interval, that interaction may signal a constraint that needs a nearby explanation. Do not rely on color; the blank can be useful even if printed without ink.

Read the receipt at the other end

Send the team out and let another load arrive at the receiving yard first. The diary should show whether the later dispatch began after a wait or was slowed on the road. This matters when a player tries to improve the next delivery. Rest can shift a planned departure. A soft road can shift an arrival. The receiving yard will care about the same deadline in both cases, but a field officer can change different things.

Repeat the position with a departure that has already been recorded. If the officer changes their mind at that point, move the next available action to the handoff station instead of quietly rewriting the record. A clear history explains why the team is still committed while the plan changes around it.

What to carry into the next test

Record whether a player mentions the team, the wagon, or the road when asked what delays departure. A useful handoff screen lets the player describe the right cause before looking at the final receipt. In The Crossing Ledger, the return schedule competes with a narrow span. Dispatch After Dusk applies the same separation of times to observations rather than teams. The two related tests can show whether the ledger’s design survives a change in subject.