The supplier who disputed every alert, and was right twice

Every sustainability team that runs a dispute queue has a version of this supplier. The one who contests every single flag that comes in against their concession, every week, without fail. Not a reasoned challenge here and there. All of them.
The temptation is to write that supplier off as noise. A box-checking exercise where someone on their compliance desk hits "dispute" on autopilot because that's cheaper than reading the alert. For a while, that's exactly what one trading desk assumed about a mill supplier in their program. Forty-some alerts over a season, forty-some disputes. The analyst running the queue started triaging them in batches of ten without much more than a glance.
Two of those disputes turned out to be right.
The first was a cloud-shadow artifact over a steep ridge line that the detection flagged as canopy loss. The supplier's forester sent back drone stills from the same week showing standing timber, full canopy, nothing cut. The second was a firebreak, cleared under a provincial permit the supplier had on file, that looked from above exactly like the start of a clearing front. Both were legitimate catches. Both also sat inside a pile of thirty-eight disputes that went nowhere, where the supplier pushed back on a real clearing and lost the argument every time.
That's the part worth sitting with. A supplier who disputes everything as a matter of policy will land on the right side of the argument sometimes just by volume, and twice out of forty times, the policy paid off. Most queue managers would call that a wash at best, and move the supplier into a lower-trust bucket for review. The lower-trust bucket misses what the two correct disputes were telling the desk about where their own detection pipeline runs thin: steep terrain with afternoon shadow, and permitted firebreaks that read the same as the first week of an illegal clear. Those are pipeline problems. Sorting the supplier into "less trustworthy" fixes neither one.
The analysts who get the most out of a dispute queue treat it less like a credibility ledger and more like a sensor for their own blind spots. Every dispute, win or lose, gets logged with the reason the supplier gave, not just the outcome. Over a season or two a pattern shows up: certain slope classes misfire more, certain crop calendars around dry-season burns get flagged for clearing when they're routine field prep, certain permit types never make it into the reference layer the detection runs against. None of that shows up if the queue is scored purely on who was right.
It also changes how the desk talks to the supplier that disputes everything. Instead of treating the ratio as a verdict on their reliability, the next conversation starts with the two cases that landed, and asks what else the supplier's own forestry team is seeing on the ground that the weekly pass from orbit doesn't catch yet. That's a more useful call than "your dispute rate is high," and it tends to get better information out of the supplier the next time something genuinely wrong shows up in their blocks.
A desk still needs a weekly list it can act on, routed to the people who chase it down, with a record of what got disputed and why that holds up when a buyer or a regulator asks. A clearing alert that lands the week it happens is only worth running if someone reads the disputes as carefully as the alerts themselves.
The supplier who fights every flag is still worth the argument. Just read the two wins, not only the ratio.