Checking in on trail

Checking in while on trail is how you keep the auto-timer from firing an overdue alert. There is no separate "check-in" button — the check-in action is completing a day in the Trip Planner.

Completing a day (Pro check-in)

When you finish each day's stage on trail and have enough cell signal to sync:

1. Open the Trip Planner on your active trip
2. Find today's day in the itinerary
3. Tap Complete day (or the completion button on the day card)

The timer resets immediately. A new deadline is set: current time + your configured timeout window (24h, 36h, 48h, or 72h).

You do not need to complete days in order, and you do not need to complete a day every day — you need to complete a day within your timeout window. If you are taking a rest day, completing it still counts.

GPS location capture (optional)

Separately from completing a day, you can manually capture your current GPS location. This records your coordinates as "last known location" and displays them on:

• Your shared trip page
• The overdue alert emails sent to contacts and companions
• The Safety QR page in overdue state

To capture: open the active trip → tap the Capture location button → grant browser location permission when prompted.

GPS capture does not reset the timer. It is purely for location recording. You still need to complete a day to reset the timer.

If GPS signal is poor or unavailable, the capture may time out. You can skip it — a missed GPS capture has no effect on the timer or alert status.

Trip chat

The trip chat is a text channel that runs alongside an active trip. It is visible in your dashboard and on your shared trip page for the duration of the trip.

Its purpose is communication that does not fit the timer model — a route change, a weather delay, a shorter day than planned. Rather than your contacts receiving an unexpected overdue alert and having no context, you can send a message while you have signal and it is there when they check.

Who can read and write

• You (the trip owner) can send messages from the dashboard at any time while the trip is active
• Anyone with the shared trip URL can read all messages — this includes your emergency contacts, anyone you have shared the link with, and anyone who receives an overdue alert email (which includes the link)
• Reading and posting from the shared trip page: visitors can read messages; posting requires being logged in as the trip owner

Designed for bad connections

Most messaging apps — WhatsApp, iMessage, Messenger — are built for cities. They require a stable connection to send, and fail silently or queue indefinitely when signal drops. On a multi-day route in the UK hills or the Alps, that is not a reliable communication tool.

Trip chat uses a polling model: the page checks for new messages every 30 seconds rather than holding a persistent connection. A persistent connection (WebSocket) drops the moment you lose signal and has to re-establish from scratch. Polling does not — it simply tries again on the next interval. This means a message sent during a brief signal window at camp will reach your contacts the next time they load the page, regardless of what happened to your connection in between.

In practice: you get two bars on a ridge, send a quick update, put the phone away. Your contacts see it within 30 seconds of opening the shared page. No app required on their end, no account, no install.

What to use it for

• "Running about 2 hours behind, all fine, will check in from the next bothy"
• "Changed plan — skipping Day 4 ridge due to forecast, taking the valley route instead"
• "Starting descent now, should be at car by 17:00 not 15:00"
• Any update that would otherwise leave your contacts without context when the timer is ticking

Message visibility and privacy

All chat messages are visible to anyone who holds the shared trip URL — not just your registered emergency contacts. If the overdue alert fires and the link is shared more widely (with mountain rescue, with trail companions), those people can also read the message history. Do not include information in the chat that you would not want a stranger to see.

Messages are included in your trip data. They appear on the shared trip page for the full duration of the active trip.

Trip chat vs. collaborative editing

These are two separate features. Collaborative editing is for the planning phase only — it locks when the trip goes active. Trip chat is for the active phase only — it is not available during planning. They do not overlap.

If you miss a window (Free accounts)

On a free account, the alert fires when the trip end date passes. If you need more time on trail, update the trip end date from the dashboard before the current end date is reached. This requires a brief cell connection to sync.

Summary