The Problem Nobody Measures
Cruise lines have gotten very good at tracking the obvious cost of pier runners: delayed departures, port overage fees, emergency rebookings. But there's a second category of missed-time incidents that rarely shows up in a fleet P&L: missed excursions.
A passenger books a $150 snorkeling tour. They wander a bit too far from the meeting point, underestimate the walk back, and arrive eight minutes after the tour bus left. What happens next? A refund request, a complaint to guest services, a one-star review mentioning the cruise line by name, and a shore excursion partner who has to deal with an empty seat they could have filled.
Multiply that across a 4,000-passenger ship visiting five ports, and missed excursions become a real line item. The problem is that no one has ever given passengers the tools to prevent it.
Why Straight-Line Distance Lies
Cruise apps today show a map pin for the meeting point. The passenger looks at the screen, sees a pin that appears to be "a few blocks away," and decides they have plenty of time. But port towns aren't Manhattan grids. That pin that looks 500 meters away might require a 15-minute walk through winding streets, pedestrian detours, and one-way roads.
A meeting point that looks "5 minutes away" on a map pin could be 15 minutes of actual walking through port streets. Passengers make bad decisions based on bad data.
This is the same problem ShipSafe already solves for pier-return navigation. Our offline routing graphs map actual walkable roads in every port — not straight lines, not driving routes, but pedestrian paths. The infrastructure was already there. The question was whether to extend it to excursions.
How GoTime Works
GoTime extends ShipSafe SDK's pier-return tracking to monitor walking ETAs to excursion meeting points. When a passenger has booked excursions, the SDK tracks their walking distance to each meeting point alongside their distance to the pier. Each excursion progresses through a clear state machine:
- On Track — Plenty of time. The passenger sees a green status with their walking ETA and the excursion departure countdown.
- Leave Soon — Amber alert. Walking ETA is approaching the departure window. Time to start heading over.
- It's Go Time — Red alert. The passenger must leave now to make it. Walking ETA equals or exceeds the time remaining.
- You Made It — Arrived at the meeting point. Enjoy the tour.
The alerts are mathematically precise. GoTime calculates margin as the time remaining minus the walking ETA, and only escalates when the margin crosses a threshold. No arbitrary timers. No "you're 1 mile from your excursion" messages that mean nothing. Just: you need to leave now, or you'll miss it.
Intelligent Alert Priority
Here's the nuance that makes GoTime more than a simple timer: it knows when to shut up.
If a passenger is in pier-return RED or ORANGE status — meaning they're at risk of missing the ship itself — excursion alerts are suppressed entirely. The ship departure is always the highest priority. A missed excursion is a $150 refund. A missed ship is a $8,000+ incident.
But if the passenger is in pier YELLOW (heads up, you should start thinking about heading back) and an excursion is in GO TIME status, the excursion alert takes priority. Why? Because the excursion has a hard, imminent deadline. The pier yellow alert is a heads-up, not an emergency. GoTime is smart enough to know the difference.
Same Pipeline, New Dimension
GoTime doesn't require a separate system, a new SDK integration, or additional data downloads. It uses the exact same offline routing graphs that power pier-return navigation. The same A* routing engine. The same pace-adjusted ETA calculations. The same self-healing GPS.
The native binary that computes walking routes doesn't know or care whether it's routing a passenger to a pier or to a tour bus meeting point. It receives coordinates, computes the route, and returns an ETA. GoTime simply calls this pipeline once per active destination.
For cruise lines already running ShipSafe SDK, enabling GoTime means feeding excursion booking data into the SDK. No new infrastructure. No additional battery drain beyond what the existing tracking session already uses. One integration, two revenue-protecting capabilities.
Available Now in Navigator Plus
GoTime is included in the Navigator Plus tier at no additional cost — excursion-aware navigation alongside multi-route alternatives, route comparison, and the full offline routing experience.
We built GoTime because the infrastructure was already there and the problem was obvious. Passengers shouldn't need to guess whether they have time to make their excursion. And cruise lines shouldn't have to absorb the cost when they guess wrong.
Want to see GoTime in action? We'll walk you through the excursion tracking pipeline and show you exactly how it works in your passenger app.
Schedule a GoTime Demo →