The meals map — where they'll land, and why we show it.

LADLE has a page at /meals-map that shows regions where hunger is most acute. Marker size roughly scales with the severity of need. The intent is to give subscribers a geographic sense of where their contribution will land once the pooled meal fund crosses the $50,000/year partnership threshold and meals begin shipping through the partner we select ([context here](/blog/the-fifty-thousand-threshold)).

This post is about what the map shows, what it deliberately doesn't, and why we don't overreach on the attribution question.

**What the map shows.**

Regions where large-scale hunger relief operates today, drawn from public food-security assessments. Bigger markers = more acute need in that region. Hovering shows the region name and a short note of general context (emergency response, prolonged drought, displacement, and so on).

The data isn't real-time — it updates as public assessments are published. What you see is a recent snapshot, not a live feed of "meals being served right now."

**What the map DOESN'T show, and why.**

A named partner. We haven't selected one yet; the criteria are public at /impact/choosing-a-partner. The map is about where the need is, not about any specific organization's footprint.

Individual attribution. Even post-partnership, we won't be able to say "your $8 in June funded three meals in Yemen and two in Ethiopia." Aggregated donation models don't work that way. Your earmark is pooled into the aggregate LADLE contribution, then into the partner's operational budget, then allocated by their planning across programs and geographies based on need.

Pretending otherwise would be marketing fiction. "You fed a specific child in a specific place" is emotionally powerful but factually not how humanitarian food aid works. Hunger-relief organizations allocate by need, urgency, and logistics — not by donor attribution.

**Why we show the map anyway.**

Two reasons.

One: subscribers reasonably want to know where their money geography-goes, even if not person-specifically. The map answers that: large-scale hunger relief operates in these regions, at these approximate scales. Your contribution will land somewhere on this map, weighted by the partner's operational allocation at the time of transfer.

Two: it's a check against the abstract. "$8 buys meals for people who need them" is true but distant. Seeing the specific regions — school feeding here, emergency response there, resilience programming across multiple continents — grounds the abstraction in specific places.

**A subtlety about "where the meal is served."**

There's a meaningful gap between where donations are raised (mostly rich countries) and where hunger is most acute (mostly countries in acute humanitarian need). This gap is intentional — humanitarian aid moves resources from where they can be raised to where they're needed. If we ONLY showed the countries where meals are served, someone might wonder why "their" meals appear in places they haven't heard of. Because that's where the need is.

**What we would add if we had more data:**

Per-region breakdown of the partner's monthly disbursement, so subscribers could see the specific mix of countries their donation batch supported. That depends on what the partner we select publishes at monthly granularity. If they do, we'll add it.

Program-type breakdown (emergency vs. school feeding vs. resilience). Same story — depends on the partner's reporting.

**Where the map is now.**

It's a static-ish view sourced from public food-security assessments, refreshed when new data publishes. Good enough to answer "where is the need" and "where will meals I've reserved land, geographically." Not enough to answer "which meal was mine." And, as above, that second question doesn't have an honest answer anyone can give.

Once a partner is signed, we'll link to their own transparency reports (financial breakdowns, per-country allocations, program strategy documents) rather than reproduce them. The LADLE meals map is a summary. The partner's own reporting will be the depth.