Security Intelligence

Case Study: Verifying Delivery Where Staff Cannot Travel

Third-party monitoring in an area international staff could not reach, sampling, unannounced visits, geotagged evidence and a rule against monitoring your own work.

By Mowlid Ali 06 Sep 2026 7 min Security Intelligence
Source

Originally reported by INGO ADVISORY. INGO ADVISORY analysis is attributable to our intelligence desk; the underlying reporting remains the property of the publisher.

Read the original publication View all 5 citations
Author
Mowlid Ali
Source
INGO ADVISORY
Publication date
06 Sep 2026
Location
Client locations withheld
Country
Sudan
Category
Security Intelligence
Threat level
SUBSTANTIAL — An attack is likely.
Analytic confidence
High
Verification status
Verified
Listen · 2 minReady to play · about 2 min

Anonymised practitioner case study. The organisation, precise locations and dates are withheld to protect the client and its staff. Internal metrics are not published, and none has been invented in their place.

The client

A donor-funded programme distributing assistance in an area of Sudan that international and most national programme staff could not safely visit.

The problem

Reporting came exclusively from the implementing partner. It was plausible, internally consistent and impossible to test. Neither the organisation nor its donor could state with confidence what had reached whom.

Remote management is not an absence of verification. It is verification designed for distance.

The method: independent third-party monitoring

  • Engaged monitors with no contractual or personal relationship to the implementing partner, separation of duties first, everything else second.
  • Drew a random sample from the beneficiary list rather than accepting a partner-selected sample.
  • Ran unannounced visits within agreed safe windows, alongside scheduled ones.
  • Required geotagged, timestamped photographs and short structured forms rather than narrative reports.
  • Conducted independent post-distribution telephone interviews with a second, separately drawn sample.
  • Triangulated three streams, monitor observation, beneficiary interview, partner report, and treated any divergence as a finding requiring explanation, not as an error to reconcile.
  • Recorded monitor safety limits explicitly, so a location not visited was shown as not visited rather than assumed compliant.

What changed

The organisation could distinguish what was confirmed by independent observation from what was reported by the implementer and from what remained unverified. Findings were used to correct process, not to punish partners, which is why monitors continued to receive cooperation.

Transferable lessons

  • Nobody monitors their own delivery.
  • You draw the sample, not the party being monitored.
  • Show unverified locations as unverified. Silence reads as compliance.
  • Divergence between sources is information; do not average it away.
Africa Risk Brief

Get the weekly Africa Risk Brief

Analysis like this — on security intelligence and Africa's highest-risk operating environments — delivered every Monday. Free.

No spam. Unsubscribe anytime. We never share your email.