Convoy mode: making Maps work for group road trips
Group road trips run on WhatsApp live location because Google Maps doesn't know the cars are travelling together. A proposal for route-aware convoy tracking that stays honest when the signal drops.
Views are my own, based on public information and my own use of Google Maps. I don't work at Google and have no inside knowledge of its plans.
Google Maps can already share your location with other people. What it can't do is understand that three cars are one trip.
The problem
A shared location answers one question: where is that car? A group driving together is asking different ones. How far behind us are they, measured along the road? Are they still on our route? Is that dot old because they've stopped, or because their phone has lost signal? Where should we wait for them?
Today those answers come from WhatsApp live location, phone calls that drop on hill roads, and guesswork. Someone in each car ends up coordinating from the passenger seat, switching between apps. Maps is open on every dashboard in the convoy, yet it's the one app that doesn't know the cars are travelling together.
Who it's for
The main user is the person organising a group road trip: two to four cars of family or friends, driving a few hundred kilometres on highways and hill roads where mobile data comes and goes. The second group is motorcycle riders travelling together, who can't look at a screen while riding and need voice updates instead.
It isn't for commercial fleets, which already use dedicated tracking tools, or for trips across a city, where cars rarely lose each other for long.
The proposal
A convoy session
A convoy starts from a route someone has already set up. The organiser shares a link, and anyone who opens it joins the same route. Nobody has to set up the trip again on their own phone.
Positions along the route, not dots
Instead of separate dots on a map, each car is shown by where it is on the shared route: "Car 3, 6 km behind, on route." Distances and arrival times are measured along the road, not in a straight line. On a hill road, a car two kilometres away as the crow flies can be twenty minutes behind.
Live, estimated, stale
Every car's position carries one of three states, so the group always knows how much to trust what it sees.
- LiveUpdated in the last minute. Shown as a solid marker.
- EstimatedThe car has lost data. Its position is projected along the route from its last known speed, and shown hollow with a range that widens the longer the gap lasts.
- StaleNo update for long enough that an estimate isn't useful. The car is greyed out at its last known point, with the time it was last seen.
The point is to show uncertainty, not hide it. A frozen dot that looks current is worse than an honest "last seen 22 minutes ago."
Off route, and where to regroup
If a car leaves the shared route, the group sees "Car 3 is off route." That's a different problem from falling behind, and it needs a different response. When the gap between cars grows past a limit the organiser sets, Maps suggests a stop ahead that the trailing car can reach, such as a fuel station or a dhaba, with the time each car needs to get there.
Drivers and navigators
The driver should never need to touch the convoy panel. Drivers hear short voice updates at natural moments, such as a long straight stretch, never in the middle of a turn. The panel itself is for a passenger, who becomes the navigator for that car, or for the driver once the car has stopped.
Privacy
Sharing lasts only as long as the session. It ends on arrival or after 24 hours, whichever comes first, and everyone in the convoy sees an indicator while it's on. Locations are only visible inside the group, and leaving takes one tap.
How I'd measure it
| Type | Metric | Why |
|---|---|---|
| Primary | Share of convoy sessions where every car stays in the session until arrival | If groups drop out to WhatsApp, the feature hasn't replaced the habit |
| Supporting | Regroup suggestions accepted | Shows the suggestions are useful, not noise |
| Supporting | Gap between estimated and actual position when a car reconnects | Estimates are only useful if they're roughly right |
| Counter | Driver touches on the screen while the car is moving | Must not rise. This is the safety line |
| Counter | Battery used per hour of convoy session | Long trips can't afford a drained phone |
| Counter | Sessions abandoned in the first 15 minutes | Signals setup friction or confusing states |
Risks
| Risk | Why it matters | What I'd do |
|---|---|---|
| Distraction | Alerts arrive while someone is driving | Voice only for drivers, timed to safe moments; the panel is for passengers |
| Everyone has to join | One car outside the session breaks the picture | Join from a link, with no setup |
| Wrong estimates | A bad projection causes a false alarm | Show a range, widen it over time, and switch to stale rather than guess |
| iPhone background limits | iOS can limit how often apps update location in the background | Test early; iPhones may report less often |
| Privacy | Continuous location sharing in a group | Session-only sharing, a visible indicator, an automatic end |
Isn't this just location sharing? Partly, and that's the point. Maps already has the pieces: location sharing, routes and offline maps. What's missing is the idea that several people are on the same trip. Convoy mode doesn't need a new data source. It puts what Maps already knows onto the route the group is actually driving.
Next in this series: multi-day planning, and why a trip that looks fine as one long route often falls apart once it's split into real days.