Your guides leave camp in four directions before light.

How an outfit gets spread out

An outfitting operation is a fixed point with trips radiating off it. The camp, the lodge or the trailhead stays put; everybody else scatters at first light and is independent until they come back.

• A hunting outfit drops guides and clients in separate drainages before dawn and picks them up in the dark, often at a different road than the one they left from.
• A fishing outfit has boats on different reaches and a shuttle to run, so the truck and the boat are separated by a day's float and a bad road.
• A horse outfit has a string moving on the trail while camp crew stay behind, and the two are hours apart within an hour of leaving.
• River trips have a takeout time, which is the only real deadline of the day and the one thing water level can change.
• Backcountry hiking and ski guiding puts one guide in charge of a group in terrain where the phone in their pocket is cold, dark and irrelevant most of the day.
• Between seasons, somebody scouts alone — pre-season trail clearing, camp setup, spotting — which is the highest-risk, lowest-visibility work the outfit does all year.

The guide is the lone worker, not the client

Outfitters plan around client safety, because that is where the liability and the duty of care sit. But the person who is genuinely working alone is the guide: they are the one with the responsibility, the one moving between groups, and the one whose absence is the hardest to interpret.

It also inverts when something happens to them. A guide who goes down is a guide whose clients now have to describe an unfamiliar place to somebody on a radio, in the dark, and get it right. A last known position with a time on it is a far better starting point than a client's best recollection of how far up the drainage they walked.

So the accounting problem worth solving is staff-shaped: which of my guides is where, when did I last hear from each of them, and is a missed radio check a flat battery or a real problem. That is the question STALKR answers, within the coverage it has.

What it covers, trip by trip

Everything below is in the current iOS beta, described as it behaves.

• One Crew for the outfit. Staff join by entering a Crew code and asking; an owner or admin approves. Admins can issue temporary codes carrying an expiry and a request limit, which suits seasonal hires, and changing the persistent code takes the old one out of circulation.
• Seasonal turnover is handled the same way it was created: an owner or admin removes a member, and that person loses the Crew's map. Only the owner can delete a Crew or transfer ownership.
• Live Crew sharing shows each member's current position, facing direction, accuracy, status and battery while they are sharing, and Crew member trails draw where somebody has recently been from the positions they already published.
• Presence is labelled live, stale, or unknown, with the time of the last update on the member card. The direction cone appears only when the heading is trustworthy.
• Markers carry the types this work already uses: Camp, Vehicle, Danger, Safe Zone, Animal Sign, Supply Cache, Waypoint and Custom — with photos attached, so the crossing that is passable at this water level is a picture with a coordinate rather than a description.
• Zones, as circles or polygons, alert on Enter and Leave. A Zone on a takeout or a trailhead is how camp learns a party is off the water without anybody making a call. There is no dwell or overstay alert — Zones report the transition, not the duration.
• A Journey shares one specific run with chosen watchers and an expected arrival, and its watch link opens in a browser for an office manager or a family member who is not in the Crew. Journeys are a Pro capability, and a Journey needs a destination and service access to start.
• A check-in timer or dead-man switch for the guide who is out scouting alone. A missed acknowledgement escalates by push notification and email to the Crew and the selected recipients, with the last known location attached.
• SOS is a press-and-hold action scoped to the active Crew. It creates a panic incident, attempts to alert that Crew, and opens a pre-filled message the sender has to send themselves.

A Track walked once outlasts the guide who walked it

The quiet operational problem in outfitting is that the route knowledge lives in one head. The line up to the saddle that avoids the deadfall, the spring that is still running in August, the crossing that is safe below a certain flow, the place where the horses always want to turn — a senior guide knows all of it, and might not be back next season.

STALKR handles this in the order that keeps it truthful. A Track records where somebody actually walked, with duration, distance and movement statistics. When that Track is finished, it can be deliberately saved as a Route, which copies its Checkpoints so later edits do not alter the original recording. The Route can then be opened and followed later with progress and next-Checkpoint context, and Checkpoints can carry photos and arrival alerts.

Two honest notes on that. A Route is not created automatically when a Track ends — somebody decides to keep it. And STALKR has no route planning intelligence: it will not generate a line across terrain for you, because a Route here is a record of a path a person already covered, which for this use is the only kind worth having. Following a Route is foreground map guidance, not background turn-by-turn navigation.

The coverage limit, stated properly

Most of a good hunting drainage has no data service, and an app that needs one is useless there. Being specific about where the line falls is more useful than a claim.

STALKR publishes and receives positions over a data connection. Where there is none, a member's position ages to stale and then unknown, a check-in timer cannot escalate, a Track cannot be started, and a Journey cannot begin. Geometry that was already loaded may stay drawn from memory, but there are no downloadable offline maps and no offline outbox holding writes until service returns.

There is no satellite transport and no mesh networking, and neither is planned into the beta. For the parts of the day that are genuinely off-grid, an outfit still needs a satellite messenger or a beacon, and STALKR does not replace one.

What is left is still most of the day for most outfits: camp, the road, the trailhead, the ridge with a bar of service, the drive back. That is where the accounting actually happens, and where a stale marker with a timestamp gives someone a place to start.

What an outfitter should not expect from it

The gaps that matter to a business, rather than to a person on a hill.

• You cannot equip clients with it. STALKR is an iOS TestFlight beta: there is no public App Store release and no Android release, so a mixed group of guests cannot install it. Plan around staff devices.
• There is no supervisor or web dashboard. A Journey watch link is the only browser-facing surface, and it shows one trip to its chosen watchers.
• There is no monitoring centre and no professional response. SOS and missed check-ins reach your own Crew and the recipients that person selected, by push notification and email. It never sends an SMS on your behalf, and it does not contact emergency services or a rescue coordination centre.
• There is no man-down or fall detection. A horse wreck, a fall, or a capsize raises nothing on its own.
• There is no compliance export or reporting for a permit file, a land agency, or an insurer, and no regulatory certification of any kind.
• There are no recurring scheduled check-ins and no configurable escalation policies. Each timer is armed by the person it covers.
• Plan limits are real: the Free plan allows up to 2 Crews and up to 5 members per Crew, so an outfit with more staff than that needs Pro. Journeys, Zone alerts, Tracking Enforced and emergency contacts are Pro capabilities.
• Background location is implemented and OS-controlled, with physical-device validation still an open release gate. Force-quitting the app stops ordinary background work, and background execution on iOS is never guaranteed.
• Overdue and arrival alerts depend on scheduled server functions and push delivery, so they are neither instant nor guaranteed.

Related NAVTRL Systems