Back to blog

What a flagged trip actually means, and what it does not

The first time a fleet manager sees a flagged trip on their dashboard, the instinct is usually the same: something went wrong, and someone needs to be confronted about it. Most of the time, that instinct is wrong, and treating every flag as an accusation is the fastest way to make a rider stop trusting the system entirely.

What actually triggers a flag

A trip gets flagged when the GPS data shows a meaningful deviation from what was expected: a route that departs significantly from the assigned path, a stop that runs far longer than the delivery should reasonably take, or movement recorded outside an approved shift window. None of these, on their own, prove anything about intent.

• Route deviation: the rider's actual path differs substantially from the road-snapped expected route between two points.
• Extended stop: the vehicle is stationary for longer than a typical delivery or pickup should take at that location.
• Off-shift movement: GPS activity recorded on a vehicle when no shift is currently open.

The traffic problem

Lagos traffic alone explains a large share of what would otherwise look like an anomaly. A rider stuck on a bridge for forty minutes is not idle by choice, and a route that takes an unusual detour is often the only way around a road closure that a map does not know about yet.

This is why raw GPS deviation is not enough on its own. Good flag detection needs to account for road-snapped routing, so what counts as "off route" is measured against actual streets rather than a straight line between two points, and it needs a large enough time threshold that ordinary hold-ups do not trigger a flag on their own.

How to actually review a flagged trip

Before reaching out to a rider about a flag, three quick checks usually settle whether it needs a conversation at all:

1. Check the time of day. A deviation during known peak traffic hours is far more likely to be genuine congestion than one at 6am on a Sunday.
2. Look at the GPS replay. Watching the actual movement, rather than reading a single flag summary, usually makes the explanation obvious, whether that is a road closure, a legitimate second stop, or something that genuinely needs a conversation.
3. Check the pattern, not the incident. One flagged trip in a month tells you very little. The same rider flagged repeatedly, on the same kind of deviation, is a very different signal.

Why this matters for how riders see the system

Riders who feel like every hold-up gets treated as suspicious will start avoiding the fastest route in favour of one that "looks better" on a map, even when it is slower. A flagging system that cannot tell the difference between traffic and a genuine problem trains people to work around it rather than trust it.

The businesses that get the most out of flag detection use it as a starting point for a quick, low-pressure check-in, not as evidence presented at a confrontation. That approach catches the real problems without burning trust with everyone else.