Donation Integrity Investigation Program (DIIP)

Featured
to 2026 Data Engineering Data Analysis Case Study
PostgreSQL Apache Superset ETL Pipelines Python Geospatial Analysis

๐Ÿ” Project Overview: The $6 Billion Question

Every year, billions are pledged to global development and relief, but do these funds actually reach their intended destinations? This project exposes a staggering deficit between massive financial commitments (over 6.22Billion)andactualdisbursements(only1.23 Million). The core issues lie in a lack of transparency, funds evaporating into astronomical administrative overheads, and active manipulation through project fragmentation to evade audits.

โš™๏ธ Architecture & ETL Workflow

The project revolves around a robust data pipeline integrating ProPublica, World Bank, and AidData sources to uncover the truth.

Database Schema

  • Extraction: Fetched organizational financial filings and macroeconomic indicators via APIs, alongside massive geospatial CSVs.
  • Transformation (PostgreSQL): Data cleaning, type casting, and array conversions were handled entirely within PostgreSQL using the DIIP.sql script.
  • Risk Scoring Engine: Executed a Min-Max Normalization algorithm in SQL to calculate risk scores based on financial gaps, smurfing, geographic dispersion, and sectoral fragmentation.

๐Ÿ“Š Investigative Data Story & Key Findings

The analysis transitioned to Apache Superset to build an interactive dashboard that visualizes the global donation deficit.

1. Massive Pledges, Minimal Execution

We tracked 6.22Billionincommitmentsagainstamere1.23 Million in actual disbursements, highlighting a severe bottleneck before funds reach recipient countries.

Commitments vs Disbursements

2. Is the Money Following the Need?

Funding is often randomly distributed, ignoring the actual GDP per capita of recipient nations, indicating allocation is driven by factors other than pure economic need.

Economic Status vs Funding

3. The Intermediary Absorption

Organizations operating with astronomical administrative overhead ratios are absorbing millions into operational costs rather than executing promised projects.

Financial Efficiency

4. Active Manipulation Tactics

The system is actively gamed, with 61.34% of suspicious projects using โ€œFragmentationโ€ (splitting funds across confusing categories) and 36.93% using โ€œSmurfingโ€ (breaking large funds into micro-transactions).

Suspicion Metrics

Vague, repetitive terms like โ€œprojectโ€ and โ€œdevelopโ€ dominate project titles, obscuring specific, trackable deliverables.

Keywords Word Cloud

5. Spatial Reality of Risk

High-risk transactions cluster in specific global pockets, proving that risk is a systemic pattern concentrated in regions with compromised financial oversight.

Geographical Risk Map


๐Ÿšง Roadblocks & Data Caveats

  • Encountered cloud hosting constraints with Superset via Docker, shifting to a robust, Code-First Reproducible approach.
  • Engineered a robust retry mechanism in Python to mitigate unstable responses from the World Bank API.
  • Aggregation Caveat: The $6.22B vs $1.23M figure uses DISTINCT aggregations, which may silently drop legitimate duplicate rows and understate true totals.
  • Geospatial Caveat: Joining transactions on project_id alone can inflate geographic dispersion scores for projects with multiple locations.

๐Ÿ’ก Strategic Recommendations

  1. Cap Administrative Overhead: Enforce a strict maximum overhead ratio for all civil society partners.
  2. Milestone-Based Disbursements: Shift from bulk commitments to micro-releases tied strictly to verified, geolocated milestones.
  3. Algorithmic Auditing: Deploy this exact risk-scoring engine to flag anomalies like โ€˜Smurfingโ€™ before funds are approved.

๐Ÿ”— Project Repository: View Full Source Code on GitHub