Decide What the Weekend Can Hold

The first question I ever asked on a course was not "what do you want to learn." It was "what do you want this weekend to feel like on Sunday afternoon." People usually had an answer, and it usually wasn't the trip they had planned. A woman named Dana, who arrived at a June canoe course with a kayak paddle she'd bought for a canoe, told me she wanted to sleep somewhere she couldn't hear a highway. She had circled a route in a guidebook with four portages, one of them a kilometer and a half over a ridge, because the book called it a classic. She had also read a magazine article about friction-fire methods and packed a bow drill she'd never used, in case. I asked her to count the new things on the trip, and she got to six and laughed. The canoe itself, which she'd paddled twice, and the portage terrain she'd never walked. The new paddle, the bow drill, a campsite she'd never seen. And a companion, her sister, who had told her plainly that she wanted to swim and read, not walk a kilometer and a half with a pack.

Dana's trip wasn't doomed. It was planned for a different person than the one going on it. The route suited someone building a season of trips. The gear list suited someone rehearsing a survival narrative. And the whole thing was supposed to happen in a weekend that began with a five-hour drive on Friday night. What she wanted, sleeping out of earshot of traffic, was available on a lake eight minutes from the put-in, at a campsite you could reach before dark and leave late on Sunday. The classic route is still there. It will still be classic when she has twenty paddle days instead of two.

This is the first decision of any weekend in the woods, and it comes before the gear, before the destination, before anything you buy or pack. Name the trip you actually want. Not the trip that would impress the people at work, not the trip the guidebook is selling, not the trip you'd be capable of if the weather held and your knee cooperated and everyone else turned out to be as keen as you. The trip you want, held against the time and people you actually have.

I think of weekend trips as falling into three rough categories, and the categories matter because they pull in different directions. Rest trips exist to lower your heart rate and let you sit by water. Practice trips exist to make one or two familiar things more fluent, or to introduce one new skill where failing at it is an inconvenience rather than a crisis. Ambitious trips make the route itself the point, and you accept that the weekend will be organized around effort. A trip can blend these, but it can't fully serve more than one, and most bad weekends I've witnessed came from a leader who thought the group had agreed on one category while everyone else had privately assumed another.

The rest trip is the one people apologize for, and I wish they wouldn't. I once spent a season guiding trips where the itinerary said fourteen kilometers a day, and I watched clients come home more tired than they left. They'd wanted to nap. They'd wanted to swim in the afternoon and cook something slow. Instead they paddled, because the plan said fourteen kilometers, and the plan had the authority that printed numbers acquire without earning it. Now I tell people that if the point is rest, the plan should be aggressive about protecting it: short distance, early camp, no alarm, and a site chosen because it's pleasant rather than because it's at the far end of the route. Rest is a legitimate purpose, not a failure of ambition. The culture around camping keeps insisting a trip only counts if it was hard, and I consider that idea mostly a marketing artifact with some old masculine romance mixed in. The old woodcraft writers, whatever their other virtues, did tend to treat hardship as a credential. Some of that survives in the modern instinct to turn every weekend into a test. Notice the instinct in yourself and ask whose approval you're actually paddling toward.

The practice trip is the category I have the most affection for, because it's where people actually get better. The rule I taught, and still believe, is one new thing. One. If you're trying a new stove, the route should be one you've done before. If you're trying a new route, the stove should be the old one you can light in the rain without thinking. The reason is arithmetic more than philosophy: every unfamiliar skill has a failure mode, and failure modes stack. A new stove plus a new route plus a forecast you didn't read carefully gives you three ways for the evening to go sideways at once, and no slack to absorb any of them. I watched a group once try to inaugurate a new tarp setup, a new water filter, and a new campsite on the same night, in light rain, arriving at dusk. Two of the three worked. The tarp went up wrong and dripped onto the filter, which then needed to be backflushed, which nobody had practiced, so they boiled water instead, which took an hour, and they ate at ten. Nobody was hurt. But the trip had been advertised as relaxing, and by any honest accounting it was a rehearsal for a worse night than it needed to be.

Practice trips also want the right venue. A skill you haven't performed under pressure should be practiced somewhere a failure costs you comfort, not safety. That might mean a car-accessible site, or a lake you can see the far shore of, or a trip close enough to home that abandoning camp and driving back is a real option and not a humiliation. I've known people to treat the drive-home option as cheating. I've never understood this. The point of practice is repetition under mild stress, not under whatever stress the map happens to supply.

The ambitious trip is legitimate too, and I don't want to pretend otherwise. Some weekends are for the route you've thought about all winter, and effort is part of what makes them good. But an ambitious trip earns the name only when the group's actual capacity has been counted honestly, and by actual capacity I mean the least experienced, least fit, or most tired person in the boat or on the trail, on the worst hour of the trip. Park Service wilderness guidance I've read puts this plainly: plan your route and rate of travel around the weakest member. That's not sentimentality. It's the recognition that a group travels at the speed of whoever is struggling, and a plan written for the strongest member is a plan the group will fail to keep, which then forces exactly the rushed, late, exhausted decisions that cause trouble. The weakest member isn't a fixed identity, either. It can change by afternoon. Someone's knee, someone's blister, someone's cold hands, a person who didn't sleep. The plan should have room for the group to slow down without the day becoming an emergency.

There's a way to test whether you've named the trip honestly, and it's a question you can put to yourself before any gear comes out of the closet. Ask: on Sunday afternoon, what would make me feel this trip worked? If the honest answer is "I slept, I swam, I came home unhurried," then everything downstream of that answer should be chosen to protect those things, and a long portage is working against you. If the answer is "I can now set up that tarp in the dark," then pick a place where you can set it up twice, in daylight first, and let the distance be trivial. If the answer is "we reached the lake on the third portage," then count your days, count your group, and be conservative about the arithmetic, because a route that only works if everything goes right is a route that will eventually be done wrong.

The question also settles things between people before they have a reason to argue. Trips go bad socially for the same reason they go bad logistically: mismatched purposes. One person thinks it's a rest trip; one person thinks it's a training trip; nobody said so out loud, and by Saturday noon each is simmering with resentment at the other's pace. On guided trips I made the mismatch explicit early, sometimes by simply asking each person, in front of the others, what they wanted from the weekend. It took ten minutes and prevented most of the conflict I'd seen in earlier seasons. With friends it's the same conversation, just less formal. The person who wants to cover distance needs to hear that the person who wants to linger is not lazy. The person who wants to linger needs to hear that the distance isn't vanity. Then the route gets chosen for the group that exists, or the group agrees to split up for a day, which on water usually means it doesn't, which means the route bends.

A caution, because I'd rather be honest than tidy: naming the purpose doesn't guarantee the trip delivers it. Weather doesn't care what you wanted. A rest trip in three days of rain is still a rest trip if you've packed for it and chosen a site with somewhere dry to sit; it's a miserable one if you didn't. The purpose mainly tells you what to protect with the rest of your planning, which is what the rest of this chapter is about: choosing a route proportionate to the time, checking the conditions and rules that apply right now, and building in the margin that lets a trip absorb a delay without becoming a different, worse trip.

Dana and her sister took the short route. They paddled forty minutes and found a site on a point with a west view, and I got a note the following week saying the loudest thing she'd heard all night was a loon, and that the loon had been fine. The bow drill stayed in the closet. I took that as progress. She hadn't abandoned the harder trip; she'd sequenced it, which is a different act and a more patient one. Before you check a single forecast, try writing one sentence about what your weekend is for. If the sentence sounds like it belongs to someone else, you've just saved yourself two days of finding out.

The most useful planning document I ever saw was written on the back of a permit envelope by a man named Rourke, who had canoed the same lake chain for eleven summers and had, by his own account, "been stupid twice, which is once more than allowed." The envelope said where he was putting in, where he expected to take out, when he expected to be home, and what his wife should do if he wasn't. That was all. It was less paper than most people devote to a grocery list, and it contained the entire difference between a delay and a disappearance: someone who knew where to point the search.

I want to be careful here, because the phrase "trip plan" tends to summon either bureaucratic dread or, worse, a kind of talisman thinking. A written plan is not a tracking service. Nobody at any agency is watching a dot move across a map on your behalf. The plan exists so that a specific person, who is not on the trip, knows enough to start a sensible sequence if you don't come back: try your phone, and if that fails, call a named authority with the paper in hand. Search and rescue can take hours or days depending on weather, capacity, and what else is happening in the region. The plan doesn't promise help by a certain hour. It promises that looking for you starts in the right place, which is the only thing it can promise, and it is not a small thing.

So build the plan backward from the exit. This is the part of planning people skip, because the exit is the boring end of a trip and the put-in is the exciting beginning. But the exit determines almost everything else. Where do you intend to come off the water or off the trail? Is there another way off if the intended one becomes unusable, whether because of rising water, a blown tree across a portage, or a companion's twisted ankle? On a river, a secondary escape route matters more than on a loop trail, because current gives you fewer choices about direction. If your route has exactly one exit, you have planned a trip that cannot change its mind, and trips need to change their minds.

Then estimate how long the route will take, using your group's actual pace rather than a pace you found in a guidebook or a memory from a different decade. The honest method is unglamorous: take your slowest realistic day from a past trip, add time for breaks, route-finding, and setting camp, and treat that number as the planning figure. If you have no past trip, ask someone who does, and then slow their number down, because people systematically remember their fast days. A map distance is not a promise of anything. The same eight kilometers can be a morning on a gravel portage road or most of a day through blowdown, and the map will not tell you which, because the map was made before the storm.

The old woodcraft writers got one thing right on this subject, whatever else they got wrong: they planned small and left slack. Their trips were longer than ours and their gear was heavier, and they still budgeted days a modern camper would find embarrassingly unambitious. Some of that was the pace of travel in their era, but some of it was a habit of economy we've traded for optimism. I don't want to romanticize them. Their lists include items I'd tell you to leave home and omit things I'd tell you never to forget. But the underlying arithmetic survives scrutiny: hours needed, hours available, and a gap between them wide enough that a delay is an inconvenience rather than a crisis.

That gap is what I mean by margin, and margin is planning capacity, not spare time you're entitled to spend. Say you have Friday evening through Sunday afternoon, which on paper is two nights and about a day and a half of travel. Plan the route for one day of travel. The leftover half-day is not a bonus to be filled with a side trip; it's the container that absorbs a late start, a wrong turn, a wind that turns a lake into work, or the discovery that your companion's fitness was described in the past tense. If you finish on schedule, you get an afternoon of doing nothing at a campsite, which most people discover is the best part of the weekend. If you don't finish on schedule, you're still fine. The plan pays out either way.

Now the decision rule. Before you leave, agree with your companions on a specific, checkable condition under which you stop advancing and switch to the alternative. Not "we'll see how it goes." A time is the simplest version: if we haven't reached the second campsite by four o'clock, we take the alternate site short of it, or we turn back. A condition works too: if the wind is sustained enough that we can't hold a line, we get off the water. The rule has to be stated before the trip because it will be tested at the exact moment your judgment is worst, which is mid-afternoon, behind schedule, with the objective visible and your self-respect involved. Groups that set no rule default to continuing. That default is the single most reliable producer of bad weekends I know, and it has produced worse than bad weekends.

One honest limit: a turnaround rule can't anticipate every hazard. If thunder comes while you're on a ridge or the water turns ugly in front of you, you respond to the hazard, not to the schedule. The rule is a floor under your judgment, not a substitute for it, and it never overrides local official instructions or the plain evidence of danger in front of you.

The written plan itself can be one page, and for a weekend it should be. Names and phone numbers of everyone going. The route and the alternative, in language a stranger could follow: put-in, campsites, take-out. Vehicle description and where it's parked, which matters more than people expect; a searcher who knows to look for a gray pickup at the third boat launch has saved real hours. Expected return time, stated as a time and date, not "Sunday sometime." The communication method, including whether you'll have cell service, a satellite messenger, or nothing, because a contact who expects a text that can't be sent will burn the whole margin of the plan. And then the sentence people leave out: if we haven't checked in or returned by a stated time, try our phones, and if you can't reach us, call this named authority and read them this page.

Choose the contact deliberately. The person should be reliable, reachable on a weekend, and calm enough to actually make the call rather than wait another few hours out of politeness. Tell them plainly that the plan does not guarantee rescue or a response time, and that their job is narrow: try you, then report. My own contact for years was my neighbor Theo, a retired plumber who thought my trips were slightly ridiculous and took the responsibility with complete seriousness. He kept my plans in a drawer next to his seed catalogs. I never once needed him to act, and I never once left without giving him the page.

Before departure, recheck the conditions, and do it close enough to leaving that the check means something. A forecast pulled a week out is a rumor; pull the local forecast office's product a day or two ahead and again the morning you leave. Check the land manager's current notices for closures and fire restrictions, and for a water route, check the relevant gauge, because water levels can move faster than weather and a river that was friendly when you planned it can be a different animal after two days of rain upstream. None of this guarantees anything. Conditions can change after your check, which is the argument for the alternative route and the margin, not an argument against checking.

*Figure 1.1. Plan backward from the way out, then check that the plan still fits the conditions before leaving.* There's a rehearsal piece here too, and it belongs to planning rather than to gear. Whatever skill the trip depends on, whether that's pitching your shelter, running your stove, or treating water, try it once in a place where failure costs you nothing but embarrassment. The backyard is fine. The point isn't to become skilled; it's to keep the trip from depending on an untested technique. A weekend that includes a new cooking setup and an unfamiliar portage and a companion who has never paddled loaded is a weekend that has spent its margin three times before lunch. Introduce one unfamiliar thing per trip, maybe two, and let the rest be known.

I'll admit the part of this that I resist: all of it takes about forty minutes, and it's the forty minutes people are most determined to skip, myself included at various regrettable points in my past. On one trip in my thirties I didn't leave a plan because the route was one I'd done "a hundred times," which is a number I made up then and am embarrassed by now. The wind came up hard on the third crossing, I ran late, and I arrived at the take-out in the dark to find a note on my truck from the land manager, who had noticed it parked past closing and was deciding whether to call it in. Nothing bad happened. Everything could have. The note is still in my file box, filed under things that were cheap lessons.

A plan with an exit in it changes the texture of the trip itself. When you know there's a stated time at which you'll stop and a stated alternative if things go sideways, you stop negotiating with the day. The wind is no longer an argument you're losing; it's a fact that will either relent before your turnaround time or trigger a plan you already made peace with. That's the real return on the forty minutes. Not safety as an abstraction, but the specific freedom of a group that agreed, while dry and fed and unpressured, about what it would do when it wasn't.

Try it on paper before the season starts. Write a plan for a trip you've already taken, from memory, and see what you can't recall: the take-out's name, the gauge you should have checked, the time you actually got back versus the time you'd have written down. The gaps in the reconstruction are the gaps the plan exists to close.

The first time I taught a group to pitch a tarp in rain, I made the mistake of doing it in rain. It was June, the forecast had been honest, and I had decided that realism was a virtue. Six adults stood under dripping spruce while I demonstrated a knot I could tie but could not explain, and by the time the tarp stood, two of them had decided they were bad at camping. They weren't. I had taken a skill that needed a dry field and a slow afternoon and staged it as a test. I still think about that afternoon, mostly because the fix was so cheap: an hour in a backyard the week before, with the same tarp and the same knots, and nobody's weekend depending on the outcome.

The argument of this section is short. Skills that you'll need in the field should be rehearsed somewhere that isn't the field, and the best rehearsal happens as part of a trip whose main purpose is something else. Not a separate curriculum, not a course you take before you're allowed outdoors. A practice objective folded into an ordinary weekend, the way you'd fold in a swim or a long lunch.

The reason is mechanical, not moral. Under pressure, people revert to what their hands already know. A knot you've tied forty times in the garage is available at dusk in a drizzle; a knot you've read about is available in the book, which is at home. This is not a failure of character. It's how motor learning works, and it's why my old agency required its field crews to run their radio drills and their stove setups before the season rather than trusting the training binder to materialize at the moment of use. The binder never materialized. The hands did what the hands knew.

There's a planning consequence, too, and it connects to everything else in this chapter. A trip that includes a new skill is a bigger trip than its distance suggests, and you should budget it that way. If you're breaking in a new stove, a new shelter, a new water-treatment method, or your first year of paddling a heavier boat, that unfamiliarity costs time and attention just as surely as a portage does. The old woodcraft writers understood this in one direction; they were relentless about not carrying gear you hadn't used, because dead weight and untested equipment were the same problem to them. We've kept the principle and mostly dropped the moralizing, or at least I try to. The modern version is simpler: don't introduce more than one unfamiliar thing per weekend, and don't make the unfamiliar thing the one the whole trip depends on, like the stove you'll cook every meal on or the filter that's your only water.

The distinction that matters is consequence, not equipment. If your shelter fails in the backyard, you go inside and feel foolish. If it fails on the third night of a cold rain, forty minutes past the turnaround point you agreed to, it's an emergency. Same shelter, same flaw, entirely different outcome. So the rule for practice is to move the failure somewhere cheap. Choose a site where a botched attempt costs you an evening, not a night. A car-camping loop near home, a friend's field, a state forest with a road-accessible campsite and a short carry. Low-consequence doesn't mean fake. It means the stakes are small enough that you can afford to do it badly twice before doing it well.

I want to be specific about what deserves this treatment, because "practice everything" is the kind of advice that sounds rigorous and in practice discourages people from starting. For a weekend trip, the list is short. Your shelter, in whatever form you actually sleep in it, pitched once in wind if you can find wind. Your fire or stove kit, lit and cooked on at least once, including whatever fails on the first try. Your water treatment, run on actual water from an actual source rather than the tap, because the tap doesn't teach you what a silty intake does to a filter. And your packing: the load in the boat or the pack should be assembled once at home, in the daylight, by the person who will carry it. That last one sounds trivial until you've watched someone repack a canoe pack in a drizzle because the rain gear was at the bottom.

Everything else can be learned on the trip, in the ordinary way, with the ordinary amount of embarrassment. Practice the things whose failure is expensive; learn the rest as you go, and let the trip be the teacher for the low-stakes material. Knots for the food hang, yes, if you hang food. Identifying birds, no. Reading a rapid, yes, but only if you'll be reading rapids, and only after someone who knows them has walked you through the method.

Notice what that list has in common: each item is a thing you'd otherwise be doing for the first time in conditions you didn't choose. That's the whole test for whether something belongs on your practice list. Ask yourself, a week before the trip, "What will I be doing for the first time out there?" If the honest answer includes keeping yourself dry, warm, fed, and watered, you've found your practice objectives. If it only includes route-finding and a new dessert recipe, your preparation is already better than most.

A word about who practices, because this is where teaching goes wrong in both directions. In twelve seasons of instruction I watched two failure modes repeat. The first was the confident student who had read extensively and needed to be talked into touching the gear, because reading had made the skill feel completed. The second was the anxious student who believed that needing practice was itself a deficiency, that competent people just knew things. Both arrived at the same campsite unable to light a stove in a breeze, but the anxious one felt worse about it, and feeling worse made her slower to try again in front of others. If you're teaching a partner or a kid, the fix is to practice out of sight of an audience, name your own fumbles first, and treat the second attempt as the normal one rather than the redemption. The first attempt is just reconnaissance.

I'll admit my own version of the confident failure, since it's cheaper than pretending. For years I ran the same camp stove, a white gas model I could light in my sleep, and then I bought a canister stove the week before a trip because it was lighter. I did not test it. On the first morning the flame died halfway through boiling water because I hadn't seated the canister properly, and I diagnosed this with cold hands and an audience of one student who had, that same morning, carefully rehearsed her own gear. She was kind about it. She was also visibly warmer by lunch. I now light any new stove in the driveway before it earns a place in the pack, and I tell that story whenever anyone apologizes for practicing, which is often.

Practice fits into the plan you've built rather than floating beside it as a separate obligation. When you name the trip's purpose, before choosing the route, make practice one of the honest purposes available. A weekend can be for rest, or for a route you want to do, or for rehearsing two or three skills you'll need on a longer trip later in the season. If you choose the practice purpose, the route should be modest and known: a lake you've paddled, a campsite you've used, a distance that leaves slack in the afternoon for the slow, clumsy, unhurried version of the work. The mistake is trying to buy both at once, a demanding route and a set of new skills, because each one eats the margin the other one needs. The same principle that governs the whole plan governs this corner of it: one new variable at a time, and the least experienced person sets the pace.

Then pick your objectives with the same economy. Two is plenty for a weekend. Three is a curriculum. If the group is mixed, let the more experienced people practice something too, even if it's only patience, because the fastest way to poison a learning weekend is to have one person doing all the teaching and another doing all the being-taught. On the trips I ran, the best practice weekends were the ones where the veteran spent an hour figuring out a new way to rig his own tarp while the newcomer worked on the stove, and the two of them compared notes over dinner as equals in incompetence, which is a much better social arrangement than it sounds.

The conditions matter, and here I'll push back on my own younger instincts. Practicing in rain is not automatically better than practicing in fair weather, despite what I implied that June. What you want is graduated difficulty: first a dry run, then wind, then rain if rain finds you. A skill that only works in the conditions where you learned it has a very narrow home. But there's a difference between choosing a harder rehearsal and being ambushed by one, and the difference is whether you can stop. On a practice weekend, with a short carry back to the car and a stated turnaround time you actually respect, you can stop. That's what makes it practice rather than endurance, and I'd rather a hundred people rehearsed in easy conditions than ten who got "tested" and decided the woods weren't for them.

One more planning note, because it closes the loop with the trip plan itself. Put the practice objectives in the written plan, in the same place as your route and your overdue trigger. There are two reasons. The first is mundane: a plan that says "water treatment practice at the second campsite" tells your trusted contact roughly where you'll be and when, which costs nothing. The second matters more. Writing it down converts practice from an intention into a schedule, and intentions have a way of dissolving the moment the afternoon gets good. The lake goes flat, the loons show up, and nobody wants to unpack the filter. I have watched this happen with a group that then spent the following weekend, on a longer trip, discovering what an untested pump does on a silty intake. The loons were worth it. The pump was not.

And that's the last thing worth saying about practice, the thing I'd want a reader to carry out of this chapter. Rehearsal is not a tax on the weekend. It is one of the things a weekend can hold, alongside swimming and bad coffee and an early bedtime, and it takes about as much planning as any of them. The people I've watched become genuinely competent over a season or two were never the ones with the best gear or the most books. They were the ones who spent an hour on a Thursday night in April tying knots to a porch rail, badly, with a beer going warm beside them, until the bad version got boring and the good version arrived without ceremony. Competence looks like that from the inside: unglamorous, mildly repetitive, and entirely yours by the time you need it.

So pick one thing before your next trip. Pitch the tent in the yard tonight, or light the stove on the porch, or fill the filter from the creek behind the house if you have one, and time yourself without hurrying. If it goes badly, that was the cheap version. If it goes well, put the gear away and notice that the weekend just got roomier.