How to build a convoy routing plan when ground reports conflict

When the radio net and the WhatsApp group don't match

Two days into a response, you've got a logistics officer on the ground calling in that the Route 4 bridge crossing is passable at low clearance, and a partner NGO's field team texting the exact opposite from the same general area twelve hours earlier. Both reports are probably honest. Neither one is wrong on purpose. The gap usually comes down to timing, who was standing where, and whether the person reporting drove the span themselves or just saw it from a distance.

This happens in the first week of almost every response involving washed-out roads or a damaged bridge network. A routing plan built on the first report you get will fall apart the moment a third one arrives, so the plan has to be built to handle disagreement from the start, not patched after the fact.

Rank reports by what they saw, not who sent them

A lot of cluster coordinators default to trusting whichever partner has the bigger radio network or the longer history in-country. That's a reasonable tiebreaker, but it's not a method. What matters:

• Did the reporter cross the segment themselves, or relay what someone else told them?
• When was the observation made, relative to the last rainfall event or aftershock?
• Does the report name a specific segment, a km marker or village-to-village stretch, or just "the road to X"?

Build a simple log, even a spreadsheet, with those three fields next to each report. You'll find that half your "conflicting" reports aren't conflicting at all. One crew was talking about the northern approach and the other was talking about the span itself.

Where the ground reports genuinely disagree

Sometimes you end up with two credible, specific, recent reports that flatly contradict each other. A bridge one convoy crossed Tuesday morning, and another convoy was turned back from that same afternoon. This happens more than planners like to admit, usually because something changed in between, a secondary collapse, a flood crest moving downstream, debris shifting, or because the two parties were describing different crossing points on the same river without realizing it.

At that point, an independent look at the segment itself resolves the dispute. A fresh image pass over the network, compared against the last one taken before the event, shows what changed and where, without relying on anyone's memory of which bridge they meant.

Write the plan so it survives the next conflicting report

A convoy routing plan that depends on today's reports being final will break again next week. Build in a standing method instead of a one-time fix:

1. Log every status report with segment, timestamp, and whether it's a first-hand crossing or a relay.
2. Treat any report older than the last rainfall or seismic event as provisional, not current.
3. When two first-hand, recent reports disagree on the same segment, hold it as unconfirmed rather than picking a side, and route around it until there's independent confirmation.
4. Re-check unconfirmed segments against the next available imagery pass before committing a convoy to them.

That last step is the one most response plans skip, mostly because nobody wants to wait on a satellite tasking cycle that might take weeks. An event-driven pass, one that comes in as soon as usable imagery is available after the damage event, changes that math. It arrives tied to when the bridge went down, rather than on a fixed revisit schedule.

None of this replaces the field reports. A convoy still needs drivers who know the local terrain and partners who know which checkpoints are open today. What it gives you is a tiebreaker that isn't another phone call, something you can check the change map behind a disputed segment against before you commit a convoy and a driver to it.

If two reports on the same bridge don't agree, Route Disruption Mapping flags what changed between passes and hands you the image pair that proves it.