Divide
Field guide/Platform docs

Creating a division

Platform docs · 5 min · Current as of Jul 2026

A division turns one route into a decision point with two conditional plans. The why is in the divisions essay; this is the how.

Turning a route into a division

01Open the route pill between the two cairns where the trip could fork
02Toggle Division on
03Answer What decides the branch? — the condition, e.g. “Cables permit drawn?”
04Name Plan A and Plan B and give each a direction — one line on what that branch is for
05Save once — both branch lanes appear, ready for cairns

In the itinerary the pill changes: it picks up the clay accent and reads Division · Cables permit drawn? with the two lanes below it.

Building the branches

Each branch holds its own ordered sequence of cairns, independent of the trunk. Add them with Add to branch, or drag existing cairns in. Branch cairns are full cairns — they can carry permits, weather, and all the usual details — but they draw with dashed borders everywhere, on the cards and on the map pins. Dashed means provisional: an idea, not yet a commitment.

A branch can also be marked open-ended — a lane for brainstorming rather than a finished alternate. Use it for “layover day ideas” and similar; the shared itinerary labels it as such so the group doesn't mistake a sketch for a plan.

When the decision lands

When the condition resolves — the lottery posts, the forecast firms up — drag the winning branch's cairns onto the trunk and delete the division, or keep it in place as a record of the call. Trips planned for clients usually keep them: the division is the documentation of why the trip goes the way it goes.

NoteOnly trunk legs count toward the trip's mileage totals and the elevation profile. A branch is an alternative — folding it into the totals would double-count the day.
Keep reading