What to Do If Someone Does Not Arrive on Time

Quick Answer

If someone doesn't arrive when expected, the first step is to attempt direct contact — call, text, try any messaging app you have in common. Give it 15 to 30 minutes beyond the expected window before moving to the next escalation level, depending on how high-risk the journey was. If you have live tracking access, check their last known position and direction of travel. If you can't reach them and their position is frozen or unknown, escalate to local emergency services with all available information: their last known position, their planned route, their departure time, and their destination.

The hard truth is that most missed arrival situations are explained by mundane causes — phone battery died, coverage dropped, they forgot to message, they stopped somewhere unexpected. But the protocol should be the same regardless: escalate methodically and don't wait too long because you don't want to look like you're overreacting.

The Anxiety of a Missed Arrival

You know the feeling. You're expecting someone at a certain time. That time passes. You check your phone. Nothing. You tell yourself they're probably fine — traffic, a slow stop, a dead battery. You wait a little longer. Still nothing. The window stretches from ten minutes to thirty, and your mind starts moving in directions you don't want it to go.

This is one of the most common and most underaddressed safety experiences that families, partners, and friends deal with regularly. It happens in low-stakes situations — a teenager who was supposed to be home by 11 — and in genuinely high-stakes ones: a hunter who went out solo three days ago, a partner driving mountain roads in a storm.

The anxiety is similar in both cases. The appropriate response is very different.

The problem is that most people don't have a protocol. They have a habit: wait, try to call, worry, wait some more, eventually call someone else or not know who to call. Without a protocol, the decision of when to escalate is always made in the worst possible state — anxious, uncertain, afraid of overreacting.

A protocol removes that paralysis. It doesn't make the situation less frightening, but it tells you exactly what to do and when — so you can act instead of spiraling.

Why the Protocol Matters More Than the App

There's a common misconception that having a good tracking app solves the missed arrival problem. It helps — significantly. But it doesn't replace the protocol.

Here's why: a tracking app shows you position data. It does not tell you when to act on it. An app can show you that someone's position froze two hours ago and they haven't moved. But it can't tell you whether that means they're at a campsite with no coverage, or whether something is wrong. That interpretation requires context — the planned route, the expected arrival time, the nature of the terrain, the risk profile of the journey — and a protocol for acting on it.

The app is the tool. The protocol is the system. Both are necessary. Neither works without the other.

A tracking app with no agreed-upon check-in window and no escalation plan gives you information but no framework for acting on it. A protocol with no tracking app gives you clear steps to take but limited information to work with. The two together — clear protocol supported by good tracking — is what actually enables fast, effective response when something goes wrong.

Step-by-Step: What to Do When Someone Doesn't Arrive

This is the core of the article. Here is a practical, ordered protocol for a missed arrival situation.

Step 1: Confirm the Window Has Passed

Before taking any action, confirm that the check-in window you agreed to in advance has actually passed. Not just the expected arrival time — the window. If you agreed that a missed check-in was only a concern after 30 minutes beyond the expected arrival, make sure 30 minutes has passed, not just 5.

This step sounds obvious, but in the anxiety of a missed arrival, it's easy to start escalating before the agreed window has expired. Premature escalation creates unnecessary alarm and erodes trust in the protocol over time.

If you did not agree on a check-in window in advance: use your best judgment based on the journey risk level. For a low-risk urban drive, 30-45 minutes is reasonable. For an outdoor trip in challenging terrain, 1-2 hours is more appropriate.

Step 2: Attempt Direct Contact

Try to reach the person directly through every available channel:

• Phone call — leave a message if they don't answer. This matters: if they pick up later, they know immediately that you were trying to reach them and why.
• Text message — even if they have no coverage, the message will deliver when they reconnect.
• Any secondary messaging apps you know they use.
• Any other people who might have been with them — travel companions, people at the destination.

Do not skip to calling emergency services without attempting direct contact first. In the large majority of missed arrival situations, the explanation is benign and direct contact resolves it quickly.

Step 3: Check Their Last Known Position

If you have tracking access, check it now:

• Where was their last known position?
• When was the last update?
• Which direction were they heading (if the app shows heading)?
• Is the position consistent with their planned route?

A frozen position that is on the planned route and consistent with a coverage gap is different from a position that is off-route or has been static for an unusually long period. This context matters for both your interpretation and for what you tell emergency services if you escalate.

If you don't have tracking access and didn't set up a session, note this for future trips. Having the last known position is one of the most valuable pieces of information in a non-arrival situation.

Step 4: Contact People at the Destination

If the person was traveling to a specific location where others are present — a family member's house, a campsite with other people, a workplace — contact someone at the destination. They can confirm whether the person has arrived, was expected, or was seen.

This step is easy to skip because it feels like admitting you're worried. Don't skip it. The person at the destination either confirms arrival (and you stop worrying) or confirms non-arrival (and you have important confirmation for the next step).

Step 5: Contact People Who May Have Seen Them En Route

Depending on the journey, there may be people who were likely to encounter the traveler along the way — a trailhead attendant, a campground host, a gas station the traveler mentioned planning to stop at, other members of a group who departed from the same location.

Any of these contacts can either confirm a sighting or confirm that the traveler hadn't passed through, which narrows the window of uncertainty.

Step 6: Reassess Based on What You Know

By now, you have: attempted direct contact, checked last known position, contacted the destination, and tried any intermediate contacts. What do you know?

• Did any of these steps resolve the situation? If yes, the protocol ends here.
• If not: What is the last confirmed position or contact? How long has it been? What is the risk profile of the journey? What terrain or conditions were involved?

Use this information to make the call on escalation. The higher the risk profile of the original journey, the sooner you escalate.

Step 7: Call for Help

If direct contact has failed, you have no position update for an extended period, and the risk profile of the journey warrants it — call for help.

In most situations, this means:

• Local police — for urban or suburban travel, highway travel, or any situation where the person may have had a vehicle incident.
• County sheriff — for rural travel, and typically the agency that coordinates search and rescue in most US jurisdictions.
• Search and rescue — if the person was in backcountry or wilderness terrain, the sheriff can connect you to search and rescue resources.

When you call, have all available information ready. (See the section below on what to tell them.)

Adjusting the Response by Risk Level

Not all missed arrivals warrant the same urgency. The right time to escalate depends on the risk profile of the specific journey.

Low-Risk Journey

Characteristics: Urban or suburban travel, consistent cell coverage, predictable routes, person in good health, short duration, familiar environment.

Escalation timeline: 30-60 minutes beyond the agreed window before calling for help. Direct contact should be tried first and given a realistic chance to succeed — most low-risk missed arrivals resolve with a callback.

Moderate-Risk Journey

Characteristics: Rural or highway travel, some areas with reduced coverage, longer duration, less familiar routes, solo travel on a predictable route.

Escalation timeline: If direct contact fails and last known position hasn't updated in 2+ hours, escalate. Don't wait to see if they show up on their own.

High-Risk Journey

Characteristics: Remote or backcountry terrain, significant coverage gaps expected, challenging conditions (weather, difficult roads), solo outdoor travel, medical factors, or any situation where a significant incident is meaningfully possible.

Escalation timeline: If the check-in window passes and direct contact fails, escalate quickly — within 1-2 hours, not overnight. The earlier search and rescue is activated in a genuine emergency, the better the outcome. The cost of a false alarm is embarrassment. The cost of a 12-hour delay in a real emergency can be someone's life.

What Information to Have Ready Before Calling for Help

When you call for help, the quality of information you provide directly affects the speed and accuracy of the response. Prepare this before you call:

Who:

• Full legal name
• Date of birth
• Physical description (height, weight, hair, clothing last seen in)
• Any relevant medical information
• Phone number and carrier

What they were doing:

• Purpose of the trip
• Mode of travel (vehicle — make, model, color, plate number — or on foot, if hiking)
• Solo or with others? If others, who?

When:

• Departure time and location
• Expected arrival time
• Your agreed check-in window
• Time of last confirmed contact

Where:

• Departure location (specific address or coordinates if possible)
• Destination (specific address or coordinates)
• Planned route (as specifically as possible — which roads, which trails, which trailhead)
• Any known waypoints or stops along the route

Last known position:

• Coordinates or description of location from tracking app
• Time of last position update
• Direction of travel if known
• Screenshot of the map if you can share it

What you've already done:

• All contact attempts and their results
• Anyone you've already spoken to
• What they reported

Having this information organized before you call means the dispatcher can immediately start building a picture rather than asking basic questions while time passes.

How Live Tracking Changes the Response

If the person was sharing live position before contact was lost, the response protocol changes significantly — and for the better.

Instead of "we don't know where they are, they were somewhere between point A and point B," you have a starting point. You know where they were the last time the app updated. You know the direction they were heading. If they were on a planned route with marked waypoints, you know how far they were from the destination.

This information doesn't guarantee a fast resolution, but it dramatically narrows the search window. For search and rescue operations, the difference between "we know they were at this location heading this direction at this time" and "we have no idea, they could be anywhere in this county" is the difference between a focused search and an open-area search that could take days.

This is one of the most concrete arguments for using a tracking platform before any high-stakes trip: not just for peace of mind while the trip is happening, but for the actionable information it provides if something goes wrong.

Learn about NAVTRL's arrival awareness features

The value compounds when you've also marked waypoints, danger zones, and planned route details in advance. If a hiker's last position was near a river crossing that was flagged as a hazard, that's where you look first. If a vehicle's last position was on a specific forest road, that's where you send the first unit.

Contextual information saves time. Time saves lives.

Common Explanations for a Missed Arrival

Before going further into escalation, it's worth acknowledging that most missed arrivals have mundane explanations:

Dead phone battery — The most common single cause. The traveler is fine but can't communicate. Usually resolves when they find a charger or arrive somewhere with power.

Coverage gap — They're in an area with no signal. The app has stopped updating. They're moving normally and will reconnect when coverage returns.

They forgot to message — Completely benign. They got absorbed in something and the check-in slipped their mind.

They stopped unexpectedly — A detour, an opportunity, a delay that seemed minor enough not to warrant a message.

Traffic or road conditions — Longer than expected, but entirely safe.

Device issue — App crash, software glitch, phone fell and broke the screen.

They're fine, at the destination, and just missed the check-in — More common than you'd think.

Knowing these common explanations doesn't mean you shouldn't escalate — it means you escalate with the right emotional state. You're not panicking; you're following a protocol. The protocol says: do these steps, in this order, escalate at this threshold. You follow the protocol whether the explanation turns out to be a dead battery or something more serious.

When to Call Search and Rescue vs. Local Police

This is one of the most confusing points for people who have never dealt with a genuine emergency, because the right answer depends on where the trip was and what kind of emergency is likely.

Call Local Police (or 911) When:

• The person was traveling by vehicle on public roads
• The journey was urban or suburban
• You suspect a vehicle accident, medical event in an urban area, or criminal incident
• You're not sure which agency to contact — 911 dispatchers will route you appropriately

Call the County Sheriff When:

• The person was traveling in rural areas
• The journey was on unpaved roads, remote highways, or logging roads
• The county sheriff's office coordinates search and rescue in most US jurisdictions
• You need to initiate a missing person report for an adult (wait times and requirements vary by jurisdiction)

Contact Search and Rescue Directly When:

• The person was in wilderness or backcountry terrain — a national forest, wilderness area, backcountry trail
• The sheriff's office can connect you to search and rescue, or they may already be involved
• The person was hiking, hunting, or otherwise on foot in remote terrain

Important note about timing: Many people hesitate to call for help because they're afraid of looking like they're overreacting, or because they've heard that police won't file a missing person report for 24 hours. The 24-hour rule is a myth for high-risk situations — you can report a missing person immediately if the circumstances warrant concern. And for wilderness search and rescue, earlier activation almost always leads to better outcomes. Don't wait.

Preventing the Missed Arrival: Building a Better Protocol

The most powerful thing you can do is build the protocol before you need it. The conversation about what to do if someone doesn't arrive should happen before every high-stakes trip — not during a crisis.

The Pre-Trip Safety Conversation

This doesn't have to be long or formal. It covers five points:

1. "I'm leaving at [time] from [place]."

Sets the clock. Your contact knows when the session started.

2. "I expect to arrive at [specific destination] around [time]."

Concrete. Named. Confirmable.

3. "If I haven't checked in by [time], here's what I want you to do."

Explicit escalation instruction. Not "call someone," but who to call and when.

4. "I'll be out of coverage through [section] for about [estimated time]."

This prevents expected silence from triggering premature alarm.

5. "Here's my route and any stops I plan to make."

Context for interpretation if something looks wrong on the map.

This conversation takes less than five minutes. It changes the response from anxious guesswork to structured protocol. It also means that if you don't arrive, the person waiting has actual information to act on rather than just fear.

Learn more about setting up trip sharing sessions

Mark the Map in Advance

Before a high-stakes trip, use your tracking platform to mark the destination, key waypoints, and any terrain features that matter. This serves two purposes:

1. It gives your contact a shared picture of where you were planning to be.

2. If something goes wrong, it gives search and rescue actionable starting points.

Five minutes of map work before departure can be the difference between a focused search starting at the right trailhead and an open search across a 50-mile wilderness area.

Set a Realistic Check-In Window

The window should be long enough that normal travel variability doesn't trigger false alarms — but short enough that a genuine emergency gets a fast response. For most outdoor trips, 1-2 hours beyond expected arrival is a reasonable window. For high-risk solo travel, some people set a shorter window and commit to checking in at intermediate waypoints.

Practice the Protocol

The best way to make sure a protocol works is to use it. Even on low-stakes trips, practice the check-in habit: share a session, message at a waypoint, confirm arrival, end the session. When it becomes routine, it doesn't feel burdensome, and your contacts know exactly what to expect.

How NAVTRL Is Designed for Arrival Awareness

NAVTRL, the platform behind Stalkr, is being designed around exactly this problem. The session-based architecture gives every trip a defined start, a defined destination, and a defined endpoint — which means "didn't arrive" is a concrete, detectable condition, not an ambiguous interpretation of a position feed.

Within a session, the key features supporting arrival awareness include:

Named location markers — The destination, camp, vehicles, waypoints, and hazard zones are all marked in advance and shared with the whole group. Arrival at the destination is arrival at a named, confirmed place — not a position change near a vague area.

Group-wide arrival visibility — When a member arrives, the whole group knows. When everyone has arrived, the picture is complete. This matters for multi-person trips where individual members may arrive at different times.

Heading and direction indicators — Not just where someone was, but where they were moving. If a position freezes, knowing the last heading gives context: they were moving toward the destination, or they had turned around, or they had stopped and appeared to be setting up camp.

Check-in window support — The session architecture is designed to surface alerts when expected arrival windows pass without confirmation. The platform supports the protocol, not just the map.

Last known position with context — If something goes wrong, the information available isn't just a coordinate — it's a coordinate within a session that has the destination, the planned route, the waypoints, and the danger zones already marked. That context is what turns "they didn't arrive" from raw anxiety into actionable information.

Explore all of NAVTRL's outdoor awareness features

Build safer arrival awareness with NAVTRL

Mistakes That Delay Emergency Response

These are the patterns that most commonly delay response when someone genuinely doesn't arrive:

Waiting Too Long Before Escalating

The fear of overreacting is real and understandable. But the cost of overreacting is embarrassment. The cost of under-reacting in a genuine emergency is someone's safety. When in doubt, escalate.

Not Having a Protocol Before the Trip

If there's no agreed-upon check-in window, no designated contact, and no clear escalation threshold — the person waiting has no framework for making decisions. They end up making subjective judgments about ambiguous information in a state of rising anxiety. This reliably delays escalation.

Assuming a Frozen Position Means Fine

A position that stopped updating an hour ago might mean the traveler is fine in a coverage gap. It might mean something else. Without additional context — their planned route, the terrain, whether coverage gaps are expected there — a frozen position is ambiguous. Don't assume either way. Follow the protocol.

Not Having Information Ready When Calling for Help

When you call 911 or the sheriff, they need specific information immediately. Not having the planned route, the vehicle description, or the departure time organized means precious minutes are spent on basic questions while resources wait.

Calling the Wrong Agency

Calling local police about a backcountry wilderness missing person and calling the county sheriff about a highway vehicle incident are both suboptimal. Know in advance which agency is appropriate for the type of travel involved.

Not Setting Up Tracking Before the Trip

The single most impactful preparation step for a non-arrival response is having tracking data to share with emergency services. If a session was running and you have last known position and heading, you dramatically improve response speed and accuracy. If no tracking was set up, you're starting from zero.

Conversations to Have Before Every High-Stakes Trip

These conversations feel awkward to initiate. Have them anyway. They are the difference between having a protocol and not having one — and they take five minutes or less.

With the Traveler

"Before you head out — what's your expected arrival time, and if you're not checked in by [reasonable window], who should I call?"

This question opens the protocol conversation without making it feel ominous. Most people will answer it thoughtfully and be glad it was asked.

With Your Own Emergency Contact

"If I'm ever not back when expected and you can't reach me, here's what I'd want you to do." Then give them: your preferred tracking platform, your usual emergency contact (family member, close friend), which agency to call for the types of trips you typically take, and any relevant medical information.

This is the kind of conversation that feels morbid before you have it and feels like obvious common sense after.

With Group Members

For any group outdoor trip: "Here's the plan for what we do if someone doesn't make it back to camp on time." Establish the window, who's responsible for monitoring, and what the escalation path is. For hunting parties, overland groups, and extended backcountry trips, this is a basic safety briefing that should happen before departure.

See how NAVTRL handles group outdoor coordination

Frequently Asked Questions

How long should I wait before calling for help when someone doesn't arrive?

It depends on the risk profile of the journey. For low-risk urban travel, 30-60 minutes beyond the agreed window. For outdoor or remote travel, 1-2 hours maximum if direct contact has failed. When in doubt, escalate. The cost of calling too early is a false alarm. The cost of calling too late in a genuine emergency is much higher.

Can I call search and rescue before 24 hours?

Yes. The 24-hour waiting period is a myth. You can report a missing person — and request search and rescue activation — immediately if the circumstances warrant concern. For backcountry travel, earlier activation leads to better outcomes consistently.

What's the most useful information to give emergency services?

Last known position and time, planned route (as specifically as possible), departure time, expected arrival time, vehicle description and plate number (if applicable), any relevant medical information, and whatever tracking data you have.

What should I do if I have live tracking and the position is frozen?

Check when the last update occurred, what direction they were heading, and whether the position is consistent with a coverage gap in their planned route. If the freeze is extended, they deviated significantly from the route, or the position is in a hazard area, treat it as a concern and escalate.

What's the most common reason someone doesn't check in?

By a wide margin: dead or lost phone battery. The second most common: poor coverage. Both are benign. This doesn't change the protocol — you still follow it — but it helps maintain a measured response rather than immediate panic.

Should I track family members all the time to prevent this?

Permanent continuous tracking is one approach but it has significant privacy tradeoffs and doesn't necessarily provide better emergency response than a well-structured session with a clear protocol. A session-based approach for high-stakes trips, combined with a clear pre-trip protocol conversation, is often more effective and more appropriate.

Understand when to use temporary vs. permanent tracking

How does NAVTRL help in a non-arrival situation?

NAVTRL's session architecture provides last known position, direction of travel, planned route context, and named location markers — all of which are immediately useful when escalating to emergency services. The group visibility feature means other group members know the situation simultaneously, not just one designated watcher. The platform is designed to provide actionable information, not just a dot on a map.

What's a satellite communicator and do I need one?

A satellite communicator (Garmin inReach, SPOT, etc.) is a dedicated hardware device that communicates via satellite rather than cell networks. It works in areas with zero cell coverage and can send SOS signals directly to rescue coordination centers. For serious backcountry travel, many experienced outdoorspeople carry one in addition to an app-based tracker. They complement each other — app tracking for group awareness when coverage allows, satellite for emergency communication when it doesn't.

Final Thoughts

A missed arrival is one of the most common safety situations that families and outdoor groups face. Most resolve without incident. Some don't. The difference between a fast response and a delayed one is almost always the same thing: whether a protocol was established in advance.

The protocol doesn't need to be elaborate. It needs to be agreed upon, specific, and known to everyone involved before the trip starts. What is the expected arrival time? What is the check-in window? Who calls whom, and when? What information do they have to work with?

A good tracking platform — one built for the real conditions of outdoor travel, with session-based sharing, named location markers, and group visibility — gives that protocol its best possible informational foundation. When something goes wrong, you want every piece of information already mapped, already shared, already available to give to the people who respond.

Learn about NAVTRL's approach to outdoor safety

NAVTRL is being built to provide exactly that foundation. Not just a tracking dot, but a session with context: the destination, the route, the waypoints, the danger zones, the group positions, the arrival status. Everything you'd want to hand to a dispatcher or a search team — already there, already organized, already in the platform.

If you want to build that kind of arrival awareness for your trips, your group, or your family — the waitlist is open.

Build safer arrival awareness with NAVTRL