Reading a fund report.
JULY 2026 · IMPACTThe reports page is at /impact/reports. Every month has a document. Here's how to read one field by field — month earmark, cumulative fund balance, per-plan breakdown, and what the reference-number field means today vs. post-threshold.
LADLE's core promise is a monthly artifact for the meal fund. Every month has one. They live at /impact/reports on the marketing site. This is the field-by-field guide.
Framing note: our future hunger-relief partner is our **target** partner. Formal corporate partnerships at that scale typically start around a $50,000/year commitment. Until we cross that threshold, the monthly artifact is a **fund report** — a LADLE-issued document about the pooled meal fund. Once we cross the threshold, real partner receipts publish alongside every fund report. See [the-fifty-thousand-threshold](/blog/the-fifty-thousand-threshold) for the full context.
**The header.**
Month name and (once available) reference number. Today the reference-number field states plainly that a our future hunger-relief partner reference number will populate once the $50,000/year partnership threshold clears. Post-threshold, it'll be a real partner identifier — usually a short prefix + a letter — that anyone can look up on the partner's side to cross-verify.
**Total meals reserved this month.**
The count of meals that this month's aggregated earmark represents at $0.80/meal. Today these are reserved in the pooled fund; post-threshold they ship as funded meals via the partner we select.
The floor: this number is at least (subscriber count × 10 meals × months paid). Annual subscribers who paid in that month contribute their whole year's meal count in that month's total, so annual-heavy months look bigger.
**Total USD posted to the meal fund.**
The raw dollar amount posted to the pooled fund for the month. Total reserved meals × $0.80.
**Cumulative fund balance and distance from threshold.**
Two lines that only exist while we're pre-partnership: the running balance of the pooled meal fund since launch, and how far it is from the $50,000/year commitment that unlocks the partnership with the hunger-relief charity we select. These lines retire once the partnership activates.
**Batch identifier.**
Every month's posted total gets a LADLE batch identifier so we can trace ledger rows to the report. Post-threshold, each batch identifier also carries the partner reference number for the same aggregate — the two sit side by side.
**Subscriber-level breakdown (optional).**
Some reports include an aggregate per-plan breakdown: how many meals came from Ladle subscribers, from Max 5x subscribers, from Max 20x subscribers, and (when there are any) from gift subscriptions. This is useful for verifying the plan mix and per-plan meal counts (10 / 50 / 100). We don't publish per-user info — that would be a privacy violation. Aggregate only.
**Reference to the previous month.**
Every fund report links to the prior month's. Continuity is part of the trust — a missing month would be visible.
**What the report DOESN'T include.**
Distribution details. That's the partner's operational decision, not ours, and it only becomes meaningful once meals actually ship (post-threshold). If you want to see the partner's country-level activity, their own transparency reports will be the source once the partner is announced.
Individual per-subscriber records. Your specific meals aren't personally traceable in the report — they're pooled into the monthly aggregate. This is intentional: aggregating protects privacy and, post-threshold, operational efficiency for our future partner.
Refunded amounts. If subscribers refunded within the 7-day window in a given month, those meal accruals are reversed BEFORE the batch is posted. The report total already accounts for reversals.
**The escape hatch.**
If we ever can't publish a monthly fund report on time, we say so in the changelog with the reason. If the report total is materially different from what the subscriber count and plan mix would predict (say, off by more than 5%), we owe an explanation. This has never happened as of publication but we've written the escape hatch policy in advance so we know how it goes if it does.
**Where the reports live.**
The full archive is at /impact/reports. Every month is there. Batch identifiers are permanent — they don't rotate. Reference numbers, once the partnership activates, will be too.
If you're new to LADLE, spending five minutes reading a few months of fund reports is the fastest way to verify the promise isn't marketing polish. That's the whole point of publishing them.