Food Bank Dashboard: Pounds and Families Served

A food bank dashboard should center on two numbers that move together: total pounds distributed and the count of unique families served, both reported weekly. Pounds tell funders and food sourcing partners how much food moved. Families served tell your board and your community whether that food reached enough households. When both sit at the top of one weekly view, an operations lead can answer the two questions every stakeholder asks before any meeting starts.

The trap most pantries fall into is tracking one without the other. A week with high poundage and flat family counts usually means larger boxes per household, which can be a planning win or a sign that distribution slowed. A week with rising families and falling pounds means you are stretching inventory thinner per home. Neither number is meaningful alone. The dashboard exists to keep them in the same frame.

The two-number rule, and why pounds per family is the third

Start with the discipline of reporting both headline numbers every single week, even when one is flat. The moment you let "families served" lag or get estimated, your data stops being defensible to a funder who wants to see reach.

The single most useful derived metric is pounds per family, calculated as total pounds divided by unique families that week. This ratio surfaces problems the two raw numbers hide. A typical food box for a household of three to four lands in a working range of 30 to 50 pounds, depending on whether you distribute fresh produce, shelf-stable goods, or both. If your pounds-per-family suddenly drops to 18, you are either serving smaller households or running short on inventory. If it spikes to 75, you may be over-allocating and burning through stock that next week's families will need. Track the ratio as a line over time and the anomalies announce themselves.

This three-metric core, pounds, families, and pounds per family, is the spine of the two-number rule: two headline numbers reported together, with pounds per family as the ratio that watches the gap between them. Everything else on the dashboard supports it.

A weekly food bank metric framework

Use this layered structure so the board reads top to bottom: headline first, then the cuts that explain it.

• Headline KPIs: total pounds distributed this week, unique families served this week, pounds per family, and households new this week (first-time visitors).
• Trend lines: pounds and families plotted week over week for the last 12 to 16 weeks, so seasonality and the gap between the two curves are visible at a glance.
• Source breakdown: pounds in by source (food bank network, retail rescue, purchased, community donation) so you can see how resilient your supply is.
• Distribution channel split: families served by channel (walk-up pantry, drive-through, home delivery, partner site) to show where demand concentrates.
• Returning vs. new: the share of households that are repeat visitors, a proxy for whether you are serving an ongoing population or a churning one.

Six elements is enough. A weekly operational board that tries to show twenty things gets ignored. The framework above answers "how much, to how many, how efficiently, from where, through which channel, and to whom" without crowding.

What counts as a "family served" (define it before you report it)

The fastest way to lose a funder's trust is an inconsistent denominator. Decide, in writing, what a unique family is and apply it the same way every week. Most pantries count a household once per distribution week regardless of how many times they visit, and size it by number of people in the home so you can also report individuals served when a grant asks for it.

This mirrors how food insecurity is measured at the national level. The USDA Economic Research Service treats the household as the unit and classifies it from a standardized set of questions, so the same household is counted the same way every time. The USDA ERS guide to measuring food security lays out why a consistent household-level definition matters once your numbers get aggregated upward into grant reports or network rollups.

Separately, as a MyDashBorg rule of thumb, report reach, the number of distinct households and people served, as your primary outward-facing figure rather than raw visit counts, since reach is what funders and your community ask about first. Lock your per-household definition once, document it next to the dashboard, and your weekly numbers stay comparable across months and ready to submit to any grant or feed into any network rollup without re-cutting. If the denominator drifts, that comparability drifts with it.

Sizing community need is a separate exercise from counting your own clients. Large hunger-research programs like Feeding America estimate food insecurity county by county, which describes the population around you rather than the households you actually serve.

A mini-case: the box-size blind spot

Consider a mid-size pantry running a single Saturday distribution, serving roughly 220 families a week. For two years the operations lead reported only total pounds, which hovered around 9,000 pounds weekly, and leadership felt good about a stable, large number. When the team finally added unique families and pounds per family to the same view, the two-number rule caught it: families flat, pounds per family climbing. The ratio had quietly risen from 38 to 52 over six months, not because households grew, but because volunteers were packing increasingly heavy boxes to clear incoming produce before it spoiled.

The dashboard made the trade-off visible: they were moving more food per home while families served stayed flat at 220, meaning the pantry had capacity to reach more households but wasn't. Within a quarter they adjusted box sizing back toward 42 pounds, redirected the surplus to a second weekday distribution, and lifted families served past 290 without sourcing a single extra pound. The insight was not in any one number. It was in seeing the ratio move.

Building it without a spreadsheet you have to maintain

Most pantries run this on a volunteer-maintained spreadsheet, which works until the volunteer who built it leaves. The weekly cut, the pounds-per-family formula, and the rolling 16-week chart all live in someone's head. A purpose-built dashboard moves that logic out of a fragile workbook and into a view your whole team can read.

The practical path is to keep your intake however you already capture it (a sign-in sheet, a Google Sheet, an intake form) and connect that to a dashboard that does the weekly rollup, the ratio, and the trend lines automatically. MyDashBorg builds that view for you from a nonprofit template rather than asking your team to learn a reporting tool, and the "Ask your data" feature lets a coordinator type "how many new families did we serve last month" and get an answer without writing a formula.

The discipline matters more than the tool: report pounds and families together every week, with pounds per family watching the gap between them. Get that right and your board meetings, your grant reports, and your weekly planning all read from one honest source.

Ready to set up a weekly board your whole team can read? See the pricing tiers, including a free self-serve option to start.

Frequently Asked Questions

What are the most important metrics for a food bank dashboard?

The two headline metrics are total pounds distributed and unique families served, both reported weekly. The most valuable derived metric is pounds per family, which divides total pounds by families served and reveals whether box sizes or reach are shifting. Supporting cuts like supply source and new-versus-returning households explain what drives the headline numbers.

How do you define a "family served" consistently?

Decide on one rule and document it next to your dashboard before reporting. Most pantries count a household once per distribution week regardless of visit frequency, and record household size so they can also report individuals served when a grant requires it. Consistency in the denominator is what makes your weekly numbers comparable across months and defensible to funders.

How often should a food bank update its dashboard?

Weekly is the right cadence for operational tracking, since distribution patterns and inventory shift week to week. Reporting both pounds and families every week, even when one is flat, keeps the data honest and lets you catch trends early. Monthly or quarterly rollups can be built from the weekly data for board and grant reporting.

Can a food bank dashboard pull from a sign-in sheet or spreadsheet?

Yes. The cleanest approach is to keep capturing intake the way you already do, whether that is a paper sign-in sheet entered into a spreadsheet or a digital intake form, and connect that source to a dashboard that handles the weekly rollup and ratios. This avoids forcing volunteers to learn new software while still moving the reporting logic out of a fragile workbook.