The Trip You Can Explain

The call came in on a Sunday evening in October, the kind of call a coordinator dreads because it contains almost nothing usable. A woman wanted to report her brother overdue from a day hike. He was fit, she said. He knew the area. She did not know which trailhead he had started from, only that he had said something about "the ridge" over dinner on Thursday, and that he had planned to be home by six. It was nine. She could not describe his truck beyond dark, maybe blue. She did not know whether he carried a map, a phone, or any sense of an alternate route.

We found him the next morning, cold and embarrassed, sitting beside a creek two drainages west of where anyone thought to look. He had taken a fork at a junction he did not remember seeing described, discovered his error an hour later, and decided that the sensible fix was to contour around a hillside rather than backtrack. The contour put him into terrain he could not get out of before dark. He spent the night pressed against a log with his jacket pulled over his knees, and he did everything else right: he stayed put, he kept warm, he waited for light. The search took eleven hours longer than it should have, not because he made a bad survival decision, but because nobody outside his head knew where his day was supposed to go.

That is who a trip plan is actually for. Not for you. You already know where you intend to walk. The plan exists so that a person sitting in a kitchen at nine at night, holding a phone, can tell a dispatcher something more specific than my brother went to the ridge.

I want to be plain about what I mean by a trip plan, because the phrase has been ruined by forms. It is not paperwork. It is a short, current description of where you are going, how you are getting there, when you expect to be out, and what a specific person should do if you are not. Some land managers publish a checklist for exactly this, and the ones I have seen ask for the same handful of items: who is going, what you are doing, your mode of travel, the route and any intended camps, identifying details of your vehicle or boat, and when you expect to be back. You can write that on one page. You can write it on half a page. What matters is not the completeness of the form but whether the person reading it could point at a map and say, start here.

The route is the part people write worst. I have read plans that said "up the valley and around" and plans that named nine peaks in an order that only made sense to the author. A useful route description is legible to someone who has never stood on it. Name the trailhead. Name the trail, using the name on the current map or the land manager's signage, not the name your friends use. Give the direction of travel. Give the expected camps or turnaround points. If there is an alternate you might take, say so, and say what would make you take it. "If the river is above the log jam, we will use the east-side trail instead." That one sentence has rescued more weekend trips than any piece of equipment I can name, because it lets your contact interpret silence.

Here is the thing that took me years to teach well: plans change, and a changed plan is not a failed plan. People treat a deviation as a confession of poor judgment, so they do not report it, and then the deviation sits in the gap between what the searcher expects and what the searcher finds. The plan does not need to predict your day. It needs to make your day interpretable. If your contact knows you had an alternate, then finding no sign of you on the intended route is a puzzle with two pieces instead of a hundred. If your contact knows nothing, every drainage in the area is equally likely, and a sensible decision looks identical to an emergency. A group I know well, three paddlers on a coastal route, changed their plan mid-trip last spring for a reason I would call unimpeachable: a forecast shift brought afternoon winds that would have put them broadside in open water. They came in a day early, by a different route and a different takeout, while their contact knew only the original plan. What followed was not a rescue, but it was two hours of a ranger's afternoon spent confirming that three people were not missing, because nobody had said who should hear about a change and how. The plan had a route, but it did not have a channel.

So build the change into the agreement. Tell your contact, in words, before you leave: if we are more than a few hours off the schedule, and we can get a message out, we will send one. Then agree on what silence means, because this is the uncomfortable part and I will not soften it. Silence means nothing by itself, since a party that is a day late and unable to communicate may be waiting out weather in a tent with a hot stove and no worries. The overdue trigger is the tool that turns ambiguity into a decision.

An overdue trigger has four parts, and I insist on all four: a location, a time, a date, and a named action. Not "if we're not back Sunday night." That phrasing gives the contact nothing to do and nobody to call. Write it as a sentence a tired, worried person can follow at ten at night: if we have not returned to the trailhead by ten in the morning on Sunday, call the county sheriff's dispatch at this number, and tell them where we planned to be, what we were wearing, what we were driving, and that we intended to be out by Saturday evening. One sentence. It converts the contact from a person who waits, increasingly certain something is wrong, into a person who acts.

*Figure 1.1. A plan is useful when it tells someone not only where you intend to go, but when and how to act if you do not return.* Now the part people get wrong in a way that genuinely costs hours. Filing a plan with an agency is not the same as being watched. Some parks ask for itineraries, and some do not, but I have never seen one where a filed sheet generates active tracking. The National Park Service is explicit about this on its own backcountry guidance: a submitted plan does not mean anyone is monitoring your progress. Rangers are not sitting over a map with your name on it, watching dots. Your safety net is a human being who knows your plan and has a deadline, not a drawer in an office. If a permit office or a lodge wants a copy, give them one, it costs nothing and sometimes helps, but do not let the paperwork give you the feeling of being looked after. That feeling is the hazard.

Choose the contact with the same care you choose the route. Not whoever answered the phone last. You want someone who will be reachable on the day, who can read your description without you there to explain it, and who will actually make the call. I have watched a sibling sit on an overdue report for half a day because calling felt like an accusation, like saying out loud that something might be wrong. Tell your contact plainly: calling is not panicking. You will not be embarrassed to be looked for. If we are late and fine, the cost of the call is a deputy's goodwill and your own apology at the trailhead. I have made that apology. It is a good trade.

Legibility works both directions, too, and this is where group planning earns its keep. The route that is clear to a searcher should also be clear to everyone walking it. If you are the one who scouted it, say the plan out loud to your companions before you start: the trail, the junction where the route turns, the time by which we should be at the lake, and the condition under which we turn around. Then set the turn-around before anyone is tired, because the decision you make about turning back at nine in the morning, in the parking lot, with coffee still warm, is a better decision than the one you make at four in the afternoon with a sore ankle and three hours invested in a summit. Fatigue and sunk effort are not moral failures. They are weather in the mind, and you plan for them the way you plan for rain, by deciding before they arrive.

The measure of the group is not its fastest member. I learned this by being the fastest member once, twenty years ago, on a route I picked for myself and invited two friends onto, and then watched them fall behind on a pitch I found easy. The plan said eight hours. The plan was about my legs. A route schedule should be built on the slowest person's pace, on the least experienced person's comfort, and on whoever has a knee that talks back after the second thousand feet of descent. If a member takes medication on a schedule, the schedule belongs in the timing of the day, in the same way a tide table does, and that is a conversation to have with a clinician who knows the person and the trip, not a paragraph in a book.

I will end where I started, because the point is small enough to hold. Your plan does not need to be impressive. It needs to be explainable. Before you leave, try this: describe your day to someone who is not going, and watch their face. If they can repeat the route back, the timing, and what to do if you are late, you have a plan. If they say "sounds good" and you suspect they could not tell a dispatcher which side of the river you are on, you have a feeling of safety, which is a different and cheaper thing. The ridge will not tell anyone where you went. The person holding the page will.

The weakest link in a group is not usually the person with the slowest legs. I want to be clear about that before I say anything else, because "weakest link" is a phrase people use to mean the one who cannot keep up, and that is almost never where a trip actually fails. A trip fails at whatever the group has not accounted for, and the group has not accounted for it precisely because nobody wanted to be the one who said it out loud.

I once helped look for a party of four that was two days overdue on a coastal route. Three of them were strong. The fourth, it turned out, had never carried a full pack for more than one night, had worn new boots on the advice of a salesperson, and had mentioned, once, at the trailhead, quietly, that her ankles were "not great." Nobody had asked what "not great" meant. By the second afternoon she could not keep her pack strapped to a swelling ankle, and the group split into pairs to move faster, which is how a slow party became two slow parties. They were all fine in the end, cold and embarrassed and three kilometers from where anyone expected them. The plan had not failed because of her ankle. The plan had failed because her ankle was not part of the plan.

When I teach trip planning now, I ask people to fill out a column of the route decision before they look at the route. The column has three lines in it. Who is going, and what can each of them actually do. What does each of them need, on a schedule, to remain functional. What happens to this group if it separates. The answers go into the route choice the same way snowpack goes into a winter route choice. You do not pick the line first and then hope the terrain cooperates.

The first line is honest capability, and honest capability is not fitness in the abstract. It is the specific distance this specific person has walked recently, with this much weight, on terrain like this, in weather like the forecast. The question "can you do a twenty-kilometer day" is worse than useless, because almost everyone answers yes. The question "when did you last do a twenty-kilometer day, and what did it feel like the next morning" gets you something you can build a plan on. People are not lying when they say yes. They are comparing the route to a version of themselves from some other year, often a year they remember through favorable weather.

I have a friend, a retired ferry engineer named Doris, who will not commit to a trip until she has walked the biggest hill near her house with her pack loaded, twice, on consecutive weekends. People tease her about it. She is seventy-one and she has never been the person a group waited for, and I have stopped teasing her. Her method is unglamorous and it works: she tests the specific claim before the specific trip depends on it. You do not need her exact ritual. You need the same honesty about what a person's legs and lungs have done lately, not what they intend to do.

The second line is the one people skip more often and regret more thoroughly: needs on a schedule. Medication is the obvious case. If someone takes something at fixed times, that schedule becomes part of the day's shape. It affects where you camp, when you start, and how much slack you have in the middle. A twelve-hour dosing interval does not care that the weather window was supposed to be at noon. I am not going to tell anyone how to manage their own medication, and neither should a book. That is a conversation for the person and a clinician who knows the trip: the length, the hours, the temperature range, the weight of the pack. What I can say is that the rest of the group should know what the schedule is and how it sits in the day's timing, in the same way they know the tide table. And the outside contact, the person holding the plan, should know what would matter in an emergency, without the whole group's medical history circulating at the trailhead. Share with the trusted contact what a responder could use. Do not laminate your privacy to a bulletin board.

Needs also include the smaller, more embarrassing ones. I have watched a woman decide not to say she was getting cold at a wet rest stop because two men in the group had stripped to their base layers and seemed comfortable. She got quiet, then clumsy, then she stopped offering opinions about the route, and her silence was read as agreement for another hour and a half down the wrong drainage. Cold, pain, hunger, a blister starting, an unfamiliar fear of a water crossing. These are capability data. A group that treats them as complaints will collect them anyway, later, in a less useful form.

That is why I tell every group I lead: state your condition out loud on a schedule, at rest stops, whether or not anything is wrong. Not "how is everyone feeling," which invites the answer "good." Rather "I am warm, my right foot is damp, my shoulders are fine." The first person to say something specific makes it specific for everyone after. It sounds stilted for about a day. Then it becomes the habit that keeps a group honest, and honesty is the cheapest safety equipment I know of.

The third line is separation, and here is where I will take a harder position than most trip planning allows. Do not split up. I mean that as a planning principle, not a law. If your route depends on the group splitting, then you are not actually one group, you are two groups who happen to share a ride, and each group has to be able to complete the route alone. That is a planning decision to make at the kitchen table, not at the switchback where one member is falling behind. Once you are out there, splitting to "move faster" almost always means the slower pair loses the faster pair's navigation, first aid, and judgment, and the faster pair loses all knowledge of where the slower pair actually is. Searchers, meanwhile, are given two overlapping puzzle boxes with half the pieces each.

If a split is genuinely necessary, and on some trips it is, then it is planned: which pair takes the map, the medical kit, the communication device, and the agreed meeting time and place, with a fallback time and place. Both halves of the party need to be able to answer for themselves if the other half does not arrive. If one half cannot, that is not a split, that is an abandonment with paperwork.

Now, the uncomfortable part. All three lines require someone to be the person who says the route is too big, and groups go out of their way to make sure nobody is that person. There is a quiet arithmetic in groups, and it runs on sunk effort and on not wanting to be responsible for other people's disappointment. A person who has trained all summer for a ridge crossing will not volunteer to be the reason the group turns around. A person with the newest gear will not say it is cold. A person who was invited last will not say their knee is wrong. The stronger the group's stated purpose, the harder it is to dissent from it, and the trip plan, written before any of this pressure exists, is the tool that lets you dissent in advance.

Write the limits into the plan as conditions, in the group's own words, before you leave. "We turn around at 1300 if we are not at the lake." "If the wind is above what we practiced in, we take the low route." "Nobody solo-loads the packs at the cache." The value is not that the paper enforces anything. It is that a tired person on the far side of the day can point at a sentence the group agreed to in good light and say "we said," instead of having to argue, from a position of exhaustion and embarrassment, that they are worth the group's time. I have watched that sentence do more for a struggling member than any pep talk, because it removes the requirement to be brave about being finished.

And decide, in advance, who calls it. Some groups give that to the leader, which is fine when there is a leader and everyone knows who it is. Some give it to anyone, which sounds generous until it dissolves into a negotiation on the trail. I prefer the version where any member can say the agreed stop condition out loud and the group goes, without a vote and without a recount. The strongest member may grumble, and you should let them, because grumbling is not a casualty. The plan that keeps its weakest link intact will disappoint someone, and if it does not disappoint anyone, I usually want to know what the group was not willing to say out loud.

One more thing, and it is the one I would keep if I could keep only one. Capability is not fixed, and a group is not the same at hour nine as at hour two. The weakest link is a moving target: after the ankle goes, it is the ankle; after dark comes early, it is whoever is navigating; after someone's water filter freezes, it is the water plan. This is why the strongest member checking their ego matters less than the whole group checking conditions on a schedule. The route decision is not made once, at the car. It is remade all day, and the plan you can explain to your outside contact is the one that tells them what you would plausibly decide at each point where the day could bend. Here is the check I use with groups before we commit to a route. I ask each person two questions and I listen for hedging. First: what would have to be true for you to have a bad day on this route, and how likely is it. Second: if you had to turn around at the halfway point, what would the walk out cost you. If someone cannot answer the second question, the route is not yet chosen, whatever the map says. The group's real route is the one everyone can walk back down.

*Figure 1.2. The route is a decision the group keeps making, not a line chosen once at the car.* ## Prepare for the forecast to be wrong

The forecast for the Sawtooth trip said clear, with light winds and a high near sixty. Three of us stood at the trailhead at seven in the morning under a sky that looked exactly like the forecast. By eleven there was graupel coming sideways across the basin, and by one we were back below the treeline, relearning the difference between a forecast and a promise. Nobody was hurt. One of us, a river guide named Frances who had paddled through worse weather than I will ever see on foot, said something I have repeated in courses ever since. She said the forecast had been correct for about forty miles in every direction except the one we were walking in.

That is closer to how forecasts work than most of us want to believe. A forecast is a statement about a volume of air, averaged across space and time, produced by people who know it will be wrong somewhere and who publish their own uncertainty if you go looking for the point forecast discussion instead of the cartoon sun on the app. The cartoon sun is a summary of a summary. In flat country it is often close enough that you can treat it as fact. In mountains, inlets, and canyon bottoms, it is a starting point, and the terrain will amend it. I have watched a calm marine forecast turn into a churning channel wind that arrived on no schedule any model predicted, because a headland funnels air in a way that no grid cell resolves. The fishers I grew up around did not distrust forecasts. They read them the way you read a chart, and then they looked out the window at the actual water.

So the habit I want to install here is small and unglamorous. Check an authoritative forecast close to departure, from the agency that manages the land or water you are on, and then plan for the forecast being wrong in the specific way your terrain allows it to be wrong. Not wrong in every possible way. Wrong in the way that particular drainage is wrong on that particular date.

The shape of the wrongness matters. On the outer coast in October, a forecast that misses usually misses toward wind and horizontal rain, and your contingency is shelter, insulation, and a shorter day than you planned. In the high country in spring, a miss can arrive as several feet of snow, and your contingency is not grit but the willingness to sit in a tent for a day, which requires carrying the food and fuel to sit there. In a river canyon, the miss that concerns me is water, either too much of it coming down or a wind line that makes a crossing unsafe, and the contingency is an exit route you identified before you needed it. A forecast is one input. The second input is knowing what your piece of ground does when the weather turns, and that knowledge comes from land managers, from local reports, and from people who have been there in the bad season, not from a general sense that you hike in all conditions.

This is where trip planning stops being paperwork and becomes a conversation with a place. The trail conditions page for a park like North Cascades, to name one I check often, will tell you things a national forecast never will: that a seasonal footbridge has been pulled for the winter, that new snow has arrived at elevation, that a crossing that was trivial in August is now a decision. Those notices change weekly. Checking them six weeks out is fine for choosing a route. Checking them the day before you drive is what keeps you from standing at a washed-out bridge at mile eleven with a plan that no longer exists. The same goes for fire closures, permit conditions, and seasonal advisories. They are not obstacles to your trip. They are the current facts of the ground, and the ground does not care what your reservation said.

Now, the supplies. Here is the mistake I watch people make most often, and I made it for years myself in the other direction. They hear plan for the worst and they pack for a week of unsupported survival, or they hear be light and they carry nothing but a filter bottle and confidence. Both errors come from the same confusion: they are packing against a general idea of disaster instead of packing for a specific, plausible delay.

So do this instead. Take your planned trip and ask one question: if everything goes modestly wrong, how long am I actually out here. Not if a plane crashes. Not if I fall into a crevasse. If the weather forces a camp, if an ankle slows the group to half pace, if the exit road is closed and I have to wait for a ride. For a summer day hike on a popular trail, that answer is often one unplanned night. Your load for that trip is what will keep you functional through one cold, wet, immobile night and a slow walk out the next morning: extra insulation beyond what the good weather requires, a way to keep the wet out, a headlamp, water and a little more food than the plan needs, the small repair and bandage kit, and the means to start a warm drink. That is not a survival kit in the mythological sense. It is a delay kit, sized to the delay that can realistically occur.

For a five-day traverse in shoulder season, the same question gives a different answer. If the weather closes the pass, I may be sitting two or three days. Now the food margin is real food, the fuel margin is enough to melt snow if I have to, and the shelter is chosen for the storm, not for the photographs. The load grows not because of a rule but because the plausible delay grew. If someone tells you there is a universal list, they are selling something. The list is a function of the route, the season, the group, and the forecast's ability to be wrong.

Two more things about that margin, because I have seen both go sideways. First, a delay margin is not a license to use the margin. Carrying a second day of food so you can push a one-day objective into two is planning in reverse. The margin exists to absorb trouble, and if you spend it on ambition, you are back at zero with more fatigue than you started with. When my groups start talking about using the buffer on the first night, I know the plan is drifting. Second, the margin must be carried by the group, not held by one person. If all the spare layers ride in the strongest hiker's pack and that hiker is the one who fords badly, the group's margin has gone for a swim. Distribute the redundancy like you would distribute water in a dry camp.

There is a subtler point, too, about what the forecast does to your trip length even when it is right. Suppose the forecast is exactly correct: rain from two in the afternoon until midnight. A group that treats that as an inconvenience will walk all day in it, get to camp soaked and cold, and spend the evening in a tent doing the slow work of getting warm. A group that treats the forecast as route information will note that the rain arrives at two, and will plan the exposed section for the morning, the sheltered section for the afternoon, and camp where the drainage does not collect water. The forecast did not change the terrain or the mileage. It changed the shape of the day, and the second group comes in drier for free. This is what I mean when I say planning is not paperwork. The forecast is only worth checking if you are willing to let it rearrange your schedule.

*Figure 1.3. Rain can leave the route unchanged and still change the order in which you travel it.* Then there is the matter of who knows what you expect. Everything in this section gets its full value when your outside contact knows the plan it might break. If your contact has your intended route, your expected return, and a stated overdue trigger, then a weather delay is a weather delay: you come off the mountain a day late, cold and annoyed, and the call you make from the trailhead is a cancellation rather than an apology. If your contact has none of that, a delay becomes an ambiguity, and an ambiguity is what starts a search that did not need to start, in weather that is actively bad, for a party that is fine and eating its second dinner by a lake. Tell the contact what weather you would plausibly wait out. Tell them the alternate route if you named one. Tell them that a night of rain, by itself, is not a reason to worry, and give them the time after which it is. The plan you leave behind is what lets a wrong forecast be a story rather than a report.

I want to close the chapter on the honest limit of all this. Preparation does not make you safe. I have watched a group with a beautiful plan, a printed itinerary, checked forecasts, and a fully registered locator beacon walk into a morning that was going to hurt someone no matter what they carried, because the snow came early and fast and the forecast, even checked twice, said otherwise. What the preparation did was give them a chance to recognize it by noon instead of by four, and dry clothes and a hot stove to think in once they recognized it. They turned around at the second viewpoint, which was the turn-around point they had agreed to at the trailhead while they were still capable of agreeing to anything. Every habit they had practiced did what habits are supposed to do. Nobody summited, and everyone came home.

The last check I teach is the one I would keep if I could keep only one question. The night before you leave, look at your route and your pack and your contact sheet and ask: what would I have to be wrong about for this to go badly, and what does the day look like if I am. If the answer is a night of discomfort and a slower walk out, you are packed for the right delay. If the answer is that a forecast held, a crossing stayed low, or the group held together when it had a bad hour in it, then you have not finished planning yet, and the cheapest time to find that out is still tonight, at the table, with the map dry.