How to be a safety contact for a runner, rider or hiker

Agree on a role you can actually take on

A safety contact is the person expected to notice when an outing does not end as planned and help start a response. You might be a partner at home, a friend in another city or a family member near the trail. What matters is that the person going out knows who is available and what you have agreed to do.

Be specific about your availability. If you will be driving, in a meeting, asleep or without a connection, say so before the outing. Being listed as a contact does not make you available automatically. Ask the person to select someone else or agree on a clear handoff if your availability will change.

You do not need to watch a map continuously unless you have explicitly agreed to that. You do need an independent understanding of the expected finish and a way to notice it. Notifications can be missed, so avoid making the whole arrangement depend on a sound you assume the phone will play.

For a recurring run, keep a familiar routine but confirm today's details. “Usual loop” is only useful if you both mean the same route and endpoint. A changed trailhead, detour or walk home can change the plan even when the main activity sounds routine. The guide to asking for a safety contact can help start that conversation.

Keep a short outing plan somewhere you can find it

The National Park Service recommends leaving trip information with a trusted contact who is not on the trip. Use the outing-plan tool or an ordinary message to collect the relevant details. An elaborate document that you cannot find quickly is less useful than a clear note that you actually have.

Agree on the finish of the whole outing. Returning to the trailhead, reaching the car and arriving home may be different moments. Ask what the person is promising to confirm, then record the time and time zone. If you are in different places, do not rely on “seven tonight” without checking whose clock that means.

Keep personal details private and collect what is relevant with the person's knowledge. You do not need to distribute a full medical history to every contact. If they want responders to know particular medical information, ask how to find and share that information if needed.

• Name and contact number, plus who is going with them.
• Route, start point and intended endpoint, with a usable place name or map reference.
• Expected finish and the method they will use to confirm completion.
• Planned breaks, known reception gaps and the changes they will tell you about.
• Useful identifying details, such as current clothing and a trailhead vehicle, when relevant.
• The response you have agreed on if they are overdue and unreachable, and who else is involved.

Read the map as a record with a timestamp

With Holler, you can view the private live link in a browser without an app or account. It shows the last reported position and the route traveled. Open the current outing, check when its location last updated, and then compare it with the route and timing you agreed on.

An old update does not establish why reporting stopped. The phone may have lost power, connectivity or the ability to keep the sharing session active. The person may also have continued moving after that point. Avoid telling another contact that someone is definitely still at a place when the only evidence is an older position.

Even fresh updates are phone-location estimates, not direct observations of a person's condition. A cluster of similar positions can suggest a pause, but it cannot tell you whether the person is drinking water, waiting at a crossing or needs help. Use the information as context rather than turning a dot into a medical conclusion.

For a hypothetical example, imagine the last point is near a bridge and the update is old. Record the bridge location and the time of that report. Do not fill the gap by assuming the runner crossed the bridge or stayed there. The dead-phone answer explains why saved information can remain visible after updates stop.

Understand the alert without ranking urgency by its name alone

The alert type explains what triggered a notification. It does not establish the person's condition. A missed return in difficult conditions can be urgent; an unanswered stillness prompt can happen during an ordinary stop. Read the message, use the outing context and respond to the situation rather than assigning a fixed seriousness to every label.

Holler sends alerts through the configured email or supported app/browser push channels. It does not contact emergency services. Check the delivery arrangement before the outing, and keep the agreed return plan even if no notification has appeared. The absence of an alert is not confirmation that someone has finished.

Acknowledge attention, then coordinate a real response

An acknowledgment is useful because it tells others that someone has picked up the alert. It is not the same as reaching the person, sending a rescuer or confirming that they are safe. After using an available acknowledgment control, continue the response and communicate what you have actually done.

The live link can offer a response control, while a signed-in Guardian response can be associated with that Guardian's account. Follow the flow shown to you. An entered display name or a response marker is not proof that the named person has verified the situation. If a response cannot be recorded, contact the person directly rather than repeatedly retrying the button.

When several people are involved, assign concrete jobs. One person can contact the runner while another keeps the route details ready. Say “I have called and have not reached them” instead of “I have got it,” which can leave others unsure whether help has actually been requested. Do not assume everyone can see your private calls or messages.

If someone else is contacting emergency services, confirm who is doing it and share new information with them. If you have reason to believe urgent help is still needed and no one has made the call, act. A response icon should not become a reason for everyone else to stop thinking about the situation.

Use the circumstances to decide what to do next

For an unexplained missed finish, try to contact the person and compare what you know with the plan. The National Park Service advises a trusted contact to contact authorities when the person is overdue and cannot be reached. Do not keep extending the agreed deadline simply because an ordinary delay is possible.

If there is an SOS, a reported injury, a credible threat or another immediate emergency, contact emergency services promptly. In the United States, call 911. Outside the United States, use the local emergency number. Do not wait for a set number of failed calls before acting on evidence that help is needed.

There is no useful universal rule that a stationary alert is always more urgent than an overdue alert. Consider the route, weather, darkness, how long the person has been unaccounted for and any information they gave you. Report observations and uncertainty clearly; you do not have to diagnose what happened before seeking assistance.

Do not assume a 24-hour waiting rule prevents reporting someone missing. For example, California's Department of Justice explicitly says reports there have no waiting period. Follow the appropriate local reporting route and explain any immediate danger. Our overdue-person response guide covers this decision in more detail.

A nearby friend may have useful information, but do not send an unprepared person into a hazardous area. Let trained responders advise on a search or rescue. Your useful contribution may be keeping the phone free, locating the trip plan and passing on what you know.

Give responders the place, the time and the uncertainty

911.gov advises callers to be ready with the emergency location, callback number and nature of the emergency, and to follow the call-taker's instructions. If you are calling about someone elsewhere, say that early and identify the location involved. Do not assume your own phone location is the location where help is needed.

Have the last reported position and its update time ready. If the map provides coordinates, read or copy them accurately and tell the call-taker that they are a last known position. Also provide the intended route and start point. The map and the plan can help explain different parts of the situation.

Use a plain template such as: “I am calling about [name], who was [activity] on [route]. Their last location report was [place or coordinates] at [time and time zone]. They were expected at [finish time]. I have [the alert or other observation], and I have not been able to reach them. My callback number is [number].” This is a suggested structure, not a script to read instead of answering questions.

Keep a brief log as things happen. Note when you received an alert, when you tried contact and what was said. Distinguish what you personally observed from something another person reported. If the person returns or you receive new information, tell the authorities you contacted so they can update their response.

• Keep the current link and route note available.
• State the age of location information whenever you pass it on.
• Answer the call-taker's questions and follow their instructions.
• Stay reachable for callbacks and updates.

Close the outing and improve the next plan

Once the person has confirmed they are safe, make sure everyone involved hears that update. Ask them to finish or resolve the outing in the service they used. A personal message can reassure you, but it may not close an app alert or tell another Guardian what happened.

After an ordinary missed check-in, discuss the practical cause without blame. Perhaps the expected finish covered the run but not the walk home, or the contact was not available for the last part of the outing. Fix that specific mismatch rather than choosing an increasingly long buffer to avoid all notifications.

Practice the ordinary flow together: receiving the link, finding the update time, understanding the selected alert channel and confirming the finish. A short practice is useful, but record its limits. Seeing one message arrive does not establish that every future alert will be delivered under different phone settings or coverage.

If you need to step away during an outing, arrange a direct handoff and tell the person heading out when possible. Give the replacement contact the plan and confirm that they accept the role. Adding another name somewhere is not the same as someone agreeing to take over.

Keep the arrangement proportionate and usable. If the current setup creates confusion, use the tracking versus check-in guide to decide which signals you actually need. Clear expectations make the contact role easier to repeat across regular runs, rides and hikes.