Survival and Travel Logs That Stay Human

Use resource tracks and weather pressure without turning the solo journal into punishment, dread, or exhaustion math.

A humane travel log table with weather tokens, route map, resource beads, dice, notebook, and a small rest marker.
Travel pressure works best when resource loss is paired with rest, help, and choice.
On this page

Survival and travel logs can create meaningful pressure, but pressure need not become punishment math. Food, weather, fatigue, light, and distance matter when they change a choice. Leave room for rest, help, luck, and care, too.

Track Few Resources

Choose two or three: food, light, warmth, morale, time, or equipment. Too many tracks can bury the story. Each resource should create a decision: press on, rest, trade, detour, ask for help, or change the goal.

Give each track a visible marker, a way to recover it, and a consequence at zero. Food at zero might mean the next scene must be about finding help. Light at zero might mean travel stops until morning. Morale at zero might mean the character pauses to remember someone before continuing. Avoid penalties that only make future turns slower unless that slowness is the point of the game.

Decide what a mark represents and when to change it. A single supply track might cover food, water, and small necessities in broad strokes; a mark need not represent one meal. If you use a game’s existing travel rules, follow those first and treat the procedure below as an optional alternative, not an extra cost on top.

Run a Travel Turn

Choose a destination and divide the route into a few meaningful legs, such as the road to a bridge and the path from the bridge to a village. A leg can be a hex, a path between map points, or a stretch of time. The hexcrawl and pointcrawl guide can help you choose a scale.

For a lightweight game of your own, try this procedure:

  1. Choose a leg. Name where you hope to arrive and one thing you know about the route.
  2. Pay the travel cost. Reduce supply by one, if you have any. At zero, pause to seek help, trade, or change the plan before setting out; don’t subtract below zero.
  3. Roll once for the leg. Use the table below or choose a result that fits. Interpret it within your content boundaries.
  4. Resolve the choice and update the log. Mark your location, any changed resource, what you discovered, and your next action.

Start supply at 3 out of 3. This is an example scale, not a measure of real-world provisions. Skip the roll for an uneventful leg if the trip has no interesting uncertainty.

d6Travel result
1Obstacle: choose a detour or stop and seek help.
2Bad weather: reach the next point, but arrive late or leave an item needing repair.
3Quiet road: reach the next point and notice a useful landmark.
4Discovery: reach the next point and find a clue, view, or promising side path.
5Shelter: reach the next point; you may rest there before the next leg.
6Help: reach the next point and meet someone willing to trade or share a useful warning.

The table adds no automatic supply cost beyond the one paid for the leg. A detour can become another leg if you decide to travel it. Once at a plausible source of provisions, such as a settlement or a helpful camp, spend a scene trading, gathering, or accepting help to restore one supply, up to 3. Rest in shelter can restore morale or warmth if you track it; decide what it costs in time or obligation before continuing. If the fiction leaves an important question unanswered, use an oracle or make a choice rather than rolling repeatedly for the same answer.

Add Recovery

A pressure table can include shelter, kindness, cached supplies, better weather, repair, memory, or safe road. Put recovery alongside danger so mercy is not an afterthought. A storm result can include a dry barn. A lost-road result can include a stranger’s marker. A broken-tool result can create a repair scene.

Recovery need not erase consequence. A barn offers warmth but may delay arrival; a trader may ask for a favor. Make the offer clear enough that the character can accept it, look for another option, or continue with the cost.

For a published example of a different approach, the Ironsworn rulebook includes travel, resupply, and camp moves. Use its own rules when playing that game; the small table above is a separate method.

Keep Hardship Bounded

Set content notes before harsh travel. Decide whether injury, starvation, isolation, animal harm, or despair are in scope. Choose human stakes without making misery the whole game.

If a result crosses the line, translate it. Starvation can become running low on supplies. Graphic injury can become a sprain and a slower pace. Hopeless isolation can become missing home and looking for company. You can also replace or skip a result altogether. The emotional safety guide offers ways to pause and reset if the tone stops being enjoyable.

Log the Journey

Write route, weather, cost, discovery, and next question. That is enough to resume. A useful entry can be five lines: where I started, what blocked me, what I spent, what I found, and what I will decide next. Add a small map mark if it helps.

For example, a courier starts with supply 3 and travels from the mill to the bridge. The player pays one supply and rolls a 5. The courier reaches the bridge and finds an empty shelter; the player decides to rest until morning. Rest does not restore supply in this example, because there is no established source of provisions.

Route: Mill to bridge; now at bridge shelter.
Weather and obstacle: Rain; the bridge is passable, but the road beyond is muddy.
Cost: Supply 3 to 2; rested overnight.
Discovery: A dry shelter beside the bridge.
Next: Choose the muddy road or ask at the nearby farm about another path.

The next line is a decision, not a full retelling. If counting becomes tiring, replace a track with a note such as “supplies low,” or save only the location and next action. The campaign log template guide has more ways to make a session easy to resume.

Written By

JJ Ben-Joseph

Founder and CEO · TensorSpace

Founder and CEO of TensorSpace and the editor of Fondsites: an engineer working across software, AI, cybersecurity, and biosecurity who builds the site's games and tools.

Keep reading