How to Share Trip Details With Someone Who Isn't a Backpacker

When I ask a non-backpacker to keep my trip details, I assume they won’t know the difference between a trailhead, a topo map, and a campsite marked “probably here.” That’s not a problem. An emergency contact doesn’t need to understand backpacking. They need clear information, sensible time thresholds, and permission to ask questions.

A useful trip plan should help someone answer three questions:

Where were you supposed to be?
When should they become concerned?
What information can they give responders?

The goal isn’t to create a perfect prediction of your trip. Backcountry plans change. The goal is to make your intended route and likely alternatives understandable to someone who has never carried a pack beyond the car.

Start With a Plain-Language Summary

Begin with a short overview before adding maps, coordinates, or gear lists. Write it as if you’re explaining the trip to a friend over coffee.

Include:

Your name and the names of everyone in the group
The trip start and end dates
The general area, park, forest, or trail system
The trailhead or access point
The planned route in everyday language
The number of nights you expect to be away
Whether you’ll have mobile service, a satellite communicator, or neither

For example, instead of writing “loop via the north fork and alpine bench,” write: “We’re parking at the south trailhead, walking north along the valley, camping near Lake A on night one, crossing the ridge on day two, and returning to the same parking area on Saturday.”

You can include official trail names in brackets, but don’t rely on them alone. A person unfamiliar with the area may not know whether “North Fork Trail” is a short side path or the only road out.

Keep the summary near the top of the document. If your contact has to make a phone call during a stressful situation, they shouldn't need to search through six pages to understand the basic plan.

Include Dates, Times, and Flexibility

Give your contact more than a departure and return date. Include the details that establish when your plan is still normal and when it has become overdue.

List:

The time you expect to leave the trailhead
Your intended campsites or overnight areas
Your expected return time at the trailhead
The time you expect to be home or back in service
How much flexibility you have built into the schedule

A simple table can make this easier to scan:

Day	Planned activity	Expected location	Flexibility
Friday	Hike from trailhead to first camp	Lake A campsite	Could stop earlier if weather is poor
Saturday	Cross the ridge and camp near the junction	Junction campsite	May use lower route if snow or wind is bad
Sunday	Return to vehicle and drive home	South trailhead	Expected at vehicle by 3 p.m.

Be honest about uncertainty. If you could reasonably finish any time between 2 and 5 p.m., don’t give your contact a false precision that turns a normal delay into an emergency.

At the same time, avoid making the whole plan sound vague. “We’ll be out for a few days” is difficult to act on. A better description is, “We plan to return Sunday afternoon, but a delay of up to three hours wouldn't be unusual. If you haven’t heard from us by Monday at 9 a.m., start making calls.”

Explain the Route Without Assuming Map Skills

Attach a map, but don’t expect the map to explain itself. Mark the following if they apply:

The vehicle and trailhead location
The planned route
Overnight locations
Bailout routes or alternate exits
Water crossings and major junctions
Possible alternate campsites
The nearest road, community, ranger station, or staffed facility

Use both names and descriptions. “Camp at kilometre 12” may be useful to you, but “the flat campsite beside the small lake, approximately 12 kilometres from the trailhead” gives your contact a second way to identify it.

If the route isn't fixed, describe the decision points. For example: “If the ridge is clear, we’ll take the high route. If weather is poor, we’ll stay in the valley and return the way we came.” This helps your contact understand why your location might differ from the itinerary without assuming something has gone wrong.

For remote areas, include coordinates for the trailhead, planned camps, and any important junctions. Label the coordinate format and datum if you know it. A coordinate that can't be interpreted isn't much help.

Write a Clear Check-In Plan

“Call if you can” isn't a check-in plan. Decide in advance what communication you expect and what happens when it doesn’t occur.

Tell your contact:

How often you expect to check in
Which method you’ll use first
Whether a brief or delayed message is normal
What an emergency message from you might look like
When they should try to contact you
When they should escalate the concern

A check-in might be a text message from the trailhead, a satellite message each evening, or a message only when you reach service. Choose something realistic. If you know there will be no signal for three days, don’t promise daily texts.

Give your contact a sequence rather than a general instruction:

Wait until the agreed check-in deadline has passed.
Try the agreed contact methods.
Contact the other members of the group or their emergency contacts.
Check the planned vehicle location and route information.
Contact the relevant park, land manager, local authorities, or emergency service for advice if concern remains.

The appropriate response depends on the area, the length of the delay, weather, your experience, and the information available. A missed message in a service dead zone is different from a missed return after severe weather, an injury report, or an overdue vehicle.

Confirm the Check-In Thresholds
Before you leave, read the plan aloud with your contact and make sure they can identify the exact time a normal delay becomes a concern. Confirm which number or service they should use for local emergency advice, since procedures and available resources vary by area.

Tell Them What “Uncertainty” Looks Like

Non-backpackers often imagine an itinerary as a promise. Backpackers know it is closer to a working plan. Explain the changes you might make without contacting anyone.

Common examples include:

Stopping early because of rain, heat, snow, or fatigue
Waiting for safer conditions at a river crossing
Taking a signed alternate route
Spending an extra night because the group is moving slowly
Leaving the route to reach a road or staffed facility
Returning to the trailhead without completing the loop

Then explain which changes are important enough to report. You might say, “If we can send a message, we’ll report any major route change or extra night. If we can’t, the alternate route marked on the map is the most likely option.”

This distinction prevents two opposite problems: your contact panicking over a reasonable decision, or dismissing a serious change as part of the plan.

Add Information Responders May Need

Your contact may need to pass information to people who know the area but don’t know you. Include a short emergency profile for each group member:

Full name and emergency contact
Relevant medical conditions or allergies
Medications that could be important
Significant injuries or mobility limitations
Outdoor experience and relevant skills
Clothing and pack colours
Recent photograph, if appropriate

Also list group equipment that could affect a response, such as a satellite communicator, personal locator beacon, water filter, shelter, or vehicle. Include device details and instructions only if your contact can use them. A complicated equipment list is less helpful than a clear note saying where the device is, whether it is switched on, and who knows how to access the account.

Describe the vehicle accurately, including its make, model, colour, licence plate, and parking location. If the vehicle will be left somewhere that requires a permit or registration, give your contact the confirmation details.

Make the Document Easy to Find

A perfect itinerary is useless if nobody can locate it. Give your contact a digital copy and, where practical, a paper copy. Store it somewhere they can access when you may be unreachable.

Name the file clearly, such as “Smith group—Lake A trip—return Sunday.” Avoid relying on a link that requires your phone to be online or an account your contact can't access.

Tell your contact when the plan is final and when you will update it. If you change the route, dates, group members, vehicle, or communication plan, send a revised copy and ask them to delete or clearly mark the old one.

Keep the information current without turning it into a full expedition report. A few accurate pages are better than a long document containing several abandoned plans.

Talk Through the Plan Before Departure

The handoff matters as much as the document. Ask your contact to explain the plan back to you in their own words. This quickly reveals confusing trail names, missing dates, or assumptions you didn’t realize you were making.

Explain what kind of help you would want. Some people would rather be contacted early; others might wait too long because they don’t want to overreact. Agree that asking the local park office, land manager, or emergency service for advice is reasonable when the agreed threshold has been reached.

You should also tell them when the trip is complete. Send a final message when you reach the trailhead or another reliable point of contact. If the group finishes early, close the loop rather than assuming everyone knows the plan changed.

Practical Next Steps

Before your next trip, create a one- or two-page itinerary using this order:

Plain-language trip summary
Dates, times, and acceptable flexibility
Map with route and alternatives
Check-in schedule and escalation plan
Group, vehicle, and equipment details
Contact information for relevant local services

Then review it with someone who doesn't backpack. If they can tell you where you’re going, when you should return, and what to do if you don’t check in, the plan is doing its job.