Minimum Viable Integrity Package for Relief and Social Funds

 

Minimum viable integrity package

Metro-level realities: drainage, debris, and “cash for work”

Urban floods require rapid municipal purchases—such as debris trucks, pumps, and renting excavators—as well as cash-for-work programs to clear silted drains. Evidence from multiple cities shows that even small abuses compound: a contractor bills for desilting that was never done; drain cleaning stops at the camera; PPE is invoiced but not delivered. The fix is to treat CFW and municipal buys as micro-contracts with the same disclosure defaults: unit prices, quantities, GPS-tagged photos, and quick citizen verification (OCP evidence on small-lot disclosure). 

When cities publish pre-monsoon work orders, silt volumes, and GPS-logged before/after photos (as Mumbai has begun to do for key nullahs and pumping stations, alongside fines for failed performance), it becomes feasible for civic groups to spot bottlenecks and verify work in real time (Times of India, 2025a; 2025b).

Minimum viable integrity package (MVIP) for relief & social funds

• Pre-season

• Vendor pools + ceiling prices for core items; beneficial-ownership checks at onboarding (IFRC DREF; OCP) (ifrc.org).

• Shock-module in social protection: registry “switch” to scale coverage; pre-tested payment rails; grievance SOPs (World Bank ASP/IEG). (Open Knowledge World Bank)

• Public playbook: criteria, appeal steps, data-protection notice (Sphere; CaLP/CHD). (spherestandards.org)

• First 10 days

• Publish all emergency awards in OCDS with delivery milestones and BO; assign a contract ID also used on delivery notes and dashboards (OCP). 

• Post ward-level beneficiary tallies (anonymized) and open the 48–72-hour appeal window (Sphere). (spherestandards.org)

• Activate complaints channels (hotline/SMS; IVR) with guaranteed response times.

• Weeks 2–6

• Randomized delivery audits and price-reasonableness checks; sanction non-delivery and publish penalties.

• CFW transparency: publish work orders, names (with consent) or anonymized IDs, days, wages, and GPS-tagged outputs; enable spot checks by CSOs.

• After-action learning starts immediately— capture procurement and targeting lessons while memories are fresh (IFRC ERF) (ifrc.org).

• 
  
• 
  

• Quarter 1 post-disaster

• Independent audit of relief funds; public hearing on findings (COA model) (coa.gov.ph).

• Registry cleanup: remove duplicates, deregister temporary addresses, and document corrections.

• Publish a lessons report: what worked, what didn’t, which vendors and processes improved outcomes.

Country-specific takeaways

Philippines. Institutionalize the COA disaster audit template for every major event with 30-, 90-, and 180-day public updates; require OCDS publication of all relief contracts; link to Ombudsman for criminal referrals when ghost deliveries are proven (COA, 2014; PhilStar, 2015). (coa.gov.ph)

Bangladesh. Leverage the country’s renowned early-warning and shelter system by adding transparent targeting dashboards, aggregation-safe data, and independent monitors at the union level; formally recognize CSOs as observers and set appeals SLAs (TIB, 2020; Daily Star, 2020). 

India. Continue investing in ASP plumbing—interoperable social registries, direct benefit transfers, and robust grievance systems—while designing equity-sensitive targeting that excludes neither migrants nor residents of informal settlements (World Bank, 2023; IEG, 2025; UNICEF, 2021) (Open Knowledge World Bank).

Citizen checklist: what to check in a tender notice or cash announcement

For emergency buys (tarps, chlorine, pumps):

• Is there a link to the procurement plan and the award notice with unit prices? (OCP guidance) (Open Contracting Partnership).

• Are beneficial owners disclosed? Are any vendors repeat awardees across many lots at identical prices? (EBRD/ProZorro) (ebrd.com).

• Are delivery milestones and photos posted? Are the GRNs (goods-received notes) cross-referenced to the contract ID?

For cash transfers:

• Are the eligibility criteria posted in simple language? Is there a 48–72-hour appeals process? (Sphere; UNICEF CVA targeting) (spherestandards.org).

• Is your data use explained? Can you opt out without losing other services? (CaLP/CHD) (data.humdata.org).

• Does the dashboard show how many people in your ward have already received payments this week?

For cash-for-work:

• Are task lists, rates, and days public? Is there PPE? Are outputs GPS-logged (drain meters cleaned, cubic meters desilted)?

Every monsoon or cyclone season tests not just engineering but institutional muscle memory. Preparedness is more than stockpiles; it is pre-negotiated contracts, practiced payment rails, pre-announced criteria, and complaint lines that people trust. The lesson from Haiyan and Amphan is not that speed inevitably breeds corruption; it is that ambiguity breeds corruption. Standards (Sphere), frameworks (IFRC ERF/DREF), open contracting, and adaptive social protection together form a workable shield if they are embedded before the storm. To truly bridge the gap between policy and practice, we must ask ourselves: What transparent actions will your jurisdiction take before the next disaster strikes?