How to leave a hiking trip plan, with a fill-in template

Agree the handoff before you set out

Start with a direct request: “Can you be my contact for this hike, from [departure] until I confirm I am back at [endpoint]?” Ask while there is time to choose someone else. A friend who cannot look at their phone during your return window may care about you but still be unavailable for this particular outing.

The National Park Service recommends giving a trip plan to a trusted person who is not joining the trip. Its guidance also calls for communicating changes and completion. This page offers an original template for that conversation; it is not an official NPS form or a substitute for required permits.

Check access to the information. If you send a map, open the same link with your contact before leaving. If a file needs permission, resolve that now. Keep a copy the contact can refer to without waiting for you to respond. The safety contact guide explains how to turn receiving a link into an agreed responsibility.

Fill in a hiking itinerary someone else can read

Use the following prompts in a document, email or message. Keep the route description specific enough to identify the intended trail and access, but easy to read. Avoid burying the return commitment at the bottom of a long packing list.

Review personal information before sharing. Only include details that are useful for the task, and keep the plan with the intended contacts. A location link or a marked map can be forwarded, so discuss who should receive it if help is needed.

Separate the intended route from evidence of where you are

Your itinerary describes an intention. A location update records where a device reported being at a particular time. These can complement each other without being interchangeable. If the phone stops transmitting, the last point is still an old report; it does not prove that you stayed there or explain why updates stopped.

Give trail names or a marked route that your contact can interpret. State which direction you intend to travel around a loop and whether you expect to return to the same trailhead. For a one-way hike, include the finish access and transport arrangement. The map should answer “what was planned?” without requiring someone to reconstruct it from earlier messages.

Keep your navigation preparation separate. The hiking-alone guide covers the broader outing decisions. A contact holding your itinerary cannot navigate for you when neither of you can communicate, and a live sharing page is not a replacement for a navigation method you can use on the trail.

Define a finish that includes the walk out

Choose the event you are promising to report. “Back by four” could mean back at the viewpoint, trailhead, campsite or home. Write “I will message when I reach the west trailhead, by [date, time and time zone]” or another endpoint you can actually check in from. Include breaks, packing up and the return leg when deciding whether that commitment is realistic.

For a fictional afternoon hike, the agreed plan might be a start at 1 p.m., a loop back to the same trailhead and a check-in by 4 p.m., all on the written date in the named time zone. Those times illustrate the wording only. Choose your own times from the route, conditions and your preparation; this example does not establish a safe pace or margin.

Use the return-time planning tool as a planning aid, then make the actual agreement with the contact. Calculating a time does not start a live outing or save an alert. If you are using Holler for the check-in, confirm the saved deadline separately while connected.

Tell the contact what an absent message means. The NPS guidance advises trying the person’s listed number when the expected return is missed and contacting authorities if there is no response. There is no universal extra waiting period in this template. Seek emergency help promptly when circumstances indicate it is needed, even before the agreed time.

Add the details that change with the activity

The same basic questions apply to several outdoor activities, but the locations and endpoints change. A fishing session may move between banks; a photographer may finish shooting before beginning a long walk back; a campsite can be the start of a separate day hike. Write the event your contact should be expecting, rather than labeling all of these simply “outdoors.”

For hunting, use the hunting trip-plan worksheet to describe the area, entry and planned stationary periods. For paddling, the kayak and canoe float-plan guide addresses craft and launch/landing details. Those additions belong with the activity-specific plan so this general template remains readable.

For a camping trip, distinguish arrival at camp, any side outing and the final return home. The solo camping check-in guide walks through those commitments. One message saying you reached camp does not establish the plan for a later hike from it.

If several people are traveling together, state who is responsible for the completion message. If the group splits, update the plan so the person at home is not waiting for a single all-clear that no longer represents everyone. Changes in companions can matter as much as changes in the route.

Use a saved alert for the commitment it actually supports

A document is useful because it preserves details for the person handling a missed return. A saved overdue alert can prompt that person to look. Treat the difference between location sharing and a safety check-in as part of the setup conversation, particularly if they are used to watching a dot without an agreed finish.

Holler’s current return setting allows up to 23 hours from the time it is set. It does not establish a weekend-long or recurring check-in schedule. A saved deadline can be processed on the server after the phone goes offline, but saving or changing it needs connectivity. Verify acceptance rather than assuming that a tap during poor reception completed the request.

Continuous browser location sharing needs the page open and the screen on. That can affect whether the setup suits the hike. The iPhone app is in private beta. Explain the arrangement you will actually use, and do not promise your contact an uninterrupted trail record.

No alert replaces an available person making a judgment. If a message is delayed or missed, the written response agreement still matters. A Guardian should not read an app acknowledgment as proof that emergency services have been contacted or that the person outdoors is safe.

Update, finish and reuse the plan carefully

When the route or finish changes, send a clear replacement: “Updated plan at [time]: [change]. The new check-in is [date, time and time zone]. Please confirm you have this version.” If you also use an app deadline, update and verify that separately. Keep the person’s received plan and the saved setting consistent.

At the agreed endpoint, send an explicit completion message and close the relevant app outing. If the contact has already sought help, communicate directly so they can pass on the new information. A location near your parked vehicle is not the same as a message confirming you reached it.

For the next trip, reuse the structure and replace the details. Old dates, an unavailable contact or last month’s entrance can make an otherwise careful form misleading. The outing-plan tool can help organize the information; sharing it with someone who accepts the role is still part of the task.