Blog·

Field notes: the candidate list that named a refinery three suppliers swore didn't exist

A foggy mountain road curves through rugged, remote terrain with a single vehicle visible in the distance.

There's a particular flavor of email that lands in a compliance manager's inbox about once a quarter. It starts with "we've reviewed your findings" and ends with some version of "we have no relationship with this facility." Polite. Firm. Occasionally a little offended.

I've been on the receiving end of enough of these to notice a pattern that doesn't get talked about much outside the trade: the denial is often technically true and operationally useless. The tier-1 supplier really doesn't have a contract with the site in question. Nobody does, on paper. That's exactly why it shows up.

A few months back I was working a region where three separate suppliers, independently, told us the same refinery didn't exist in their chain. Not a disputed site. Not an alternate name for something already on the declared list. A facility their own procurement teams said they'd never sourced from, never heard of, had no commercial reason to acknowledge.

The refinery was there. It had been there, by the look of the roofline and the tank farm layout, for a while. It showed up on a candidate-site list generated from a pass over the region, flagged on the kind of signature that gives these places away: thermal plume patterns, the geometry of bulk storage, access roads cut for truck traffic rather than foot traffic, the seasonal rhythm of material stockpiled and drawn down. None of that requires anyone to have told us the site was operating. The equipment tells you.

What's interesting, and this is the part worth sitting with, is how the denials actually got resolved. Not through a fourth round of supplier questionnaires. Through a site visit prompted by the imagery, where it turned out the refinery was two degrees of separation further down the chain than anyone had mapped: a sub-supplier to a sub-supplier, moving material that eventually, after three more hops, landed in a shipment one of the three deniers had signed off on. Everyone had told the truth. Everyone had also been wrong about what was feeding their own supply chain.

This is the structural problem with declaration-based mapping in regions like this. A tier-1 supplier can only disclose what it knows, and what it knows is bounded by its own contracts. Tier-2 and tier-3 sites that never touch a purchase order don't appear in anyone's disclosure, not because of concealment, usually, but because the chain itself doesn't route information the way it routes material. The paperwork stops well before the smelters and mills do.

The thing I keep coming back to is that the refinery was never hidden. It sat in open country doing exactly what refineries do, in daylight, visible to anything looking from above with the right bands to read. The only thing missing was a reason for anyone to go looking. A candidate-site list built from a satellite pass over the region gives you that reason before a journalist, an auditor, or a customer's customer does.

I don't think this changes the supplier relationship much, honestly. You still have the same conversation, the same slightly offended email. What's different is what you bring to it: a location, a coordinate, a date stamp on when the imagery first picked up activity there. "We have no relationship with this facility" lands differently when you can answer with where it is and when it showed up.

If your own site list is built entirely on what suppliers have told you, there's a gap in it the size of this one. The annual candidate-site list is built to find what sits in that gap before someone else does, so the next denial email arrives with a location attached rather than a question mark.

Request early access

← Back to the blog