Blog Summary
1. Unmet needs data tracks the help people asked for but couldn’t receive, whether because a service was unavailable, full, inaccessible, or didn’t fit their needs.
2. It gives organizations evidence of actual community demand, helping make a stronger case for more funding, staff, or new programs, not just showing how many people were already served.
3. Unmet needs can come from different gaps, including limited capacity, missing services, access barriers, eligibility restrictions, and referrals that don’t successfully connect someone to support.
4. Good tracking needs to be simple and built into everyday workflows, using structured categories and recording information at the point of contact so staff and volunteers can capture it consistently.
5. The data can strengthen grant applications and planning decisions by showing funders not only what an organization accomplished, but where demand remains unmet and where future resources could have the greatest impact.
Reading Time: (8 Minutes)
What is unmet needs data?
Unmet needs data is information about the requests, gaps, and barriers a person faced when they tried to get help but couldn't because a service didn't exist, was full, was inaccessible, or didn't match what they actually needed. It's the difference between "what we provided" and "what was asked for," and it's one of the most underused datasets in the nonprofit sector.
Most organizations are very good at tracking what they did: calls answered, referrals made, clients served. Far fewer systematically track what they couldn't do. National information-and-referral networks like 211 are an exception, they've built formal tracking for exactly this gap, logging both the services people ask for and the "unmet need" flag when no resource could meet that request.
Why does unmet needs data matter?
Unmet needs data matters because it's the clearest evidence an organization has for why it needs more funding, more staff, or a new program and it's evidence that's very hard for funders to dispute, because it comes directly from the people you serve.
The scale of this data at a national level makes the case well. United Way's most recent 211 Impact Survey, covering 2025 data, found the 211 network made 19 million referrals that year — up from 18 million in 2024 averaging 37 referrals every minute. Housing assistance was the single largest category, reaching an all-time high of 6 million referrals and accounting for roughly one in three of all referrals nationally. Local 211 leaders also named housing as the single biggest unmet need in their communities not because people stopped asking, but because local resources couldn't keep up with demand.
A few reasons unmet needs data carries so much weight:
- It shows demand, not just capacity. A report that says "we served 500 people" tells a funder what you could afford to do. A report that documents how many people were turned away for lack of shelter beds tells them what the community actually needs.
- It justifies new programs before you launch them. If dozens of callers each month ask for a service you don't currently offer, that's a data-backed case for starting one — instead of guessing at community need.
- It's harder to dismiss than anecdote. A specific, tracked count of unmet requests is much more persuasive to a board or funder than a general sense that staff feel overwhelmed.
- It reveals systemic gaps, not just organizational ones. Housing has shown up as the single largest category of both requests and unmet need across the 211 network for several years running, a pattern that points to a regional and national housing shortage rather than any one organization's shortfall. Patterns like this are exactly what advocacy campaigns and funding coalitions are built on.
What does unmet needs data actually look like?
In practice, unmet needs data usually falls into a few recurring types. There are capacity gaps, where the service exists but couldn't accommodate the request — a shelter was full, a counselling waitlist was closed, no volunteer was available to take the call. There are service gaps, where the organization simply doesn't offer what was asked for, whether that's legal aid, financial counselling, or youth-specific support. There are access barriers, where a service technically exists but the caller couldn't reach it, no interpreter was available, the service only operates during business hours, or there was no accessible transportation to an appointment. There are eligibility gaps, where a caller doesn't meet the criteria for the program that fits their need, due to age, location, income, or documentation status. And there are referral failures, where a referral was successfully made but the caller couldn't follow through, whether because of a lack of transportation, no childcare, or the receiving service declining them.
Each of these tells a slightly different story, and separating them matters. "We don't have capacity" is a funding-and-staffing argument. "We don't offer this service" is a program-development argument. "People can't access what we do offer" is an equity and design argument. Lumping them all into one bucket makes the data much less useful when it's time to act on it.
Research into information-and-referral call systems backs this up: a widely cited study of 211 callers found that problem-resolution rates varied enormously by need type — food assistance requests were resolved at a much higher rate than employment-related requests and that overall, only about half of callers reported their problem was resolved when followed up with a month later. That kind of category-level breakdown is only possible when unmet needs are logged with enough structure to separate need type from outcome.
How do you actually collect unmet needs data?
The biggest reason organizations don't track unmet needs data isn't that they don't value it — it's that it's hard to capture consistently, especially for frontline staff or volunteers who are focused on the person in front of them, not data entry. A few practical approaches:
1. Build it into the intake or call log workflow, not as a separate step. If a caller's need can't be met, that should be a required field to close out the interaction — not an optional note.
2. Use structured categories, not free text. A dropdown for "reason unmet" (no capacity, not offered, access barrier, ineligible, referral failed) produces reportable data. A paragraph in a notes field usually doesn't. Large-scale networks classify calls using a defined taxonomy of need types for exactly this reason — it's what makes trend reporting possible at scale.
3. Capture it at the point of contact, not after the fact. Trying to reconstruct unmet needs from memory at the end of a shift loses most of the detail and most of the volume.
4. Make it low-effort for staff and volunteers. If logging an unmet need takes five extra clicks, it won't get logged consistently under pressure. This is really a software and workflow design problem as much as a data problem.
5. Review it on a cadence, not just at grant-reporting time. Some regional 211 systems now publish real-time dashboards of met and unmet needs by area, which lets programs and funders see shifts in demand as they happen rather than waiting for an annual report.
How can unmet needs data support grant applications and funding conversations?
Funders increasingly want more than output numbers — they want to understand the need behind the request. Unmet needs data lets an organization make a forward-looking case instead of a purely historical one:
Instead of "we served 1,200 people last year," an organization can say "we served 1,200 people and identified 340 additional requests we couldn't meet, primarily for after-hours support."
It supports needs-based grant applications, where funders specifically ask organizations to demonstrate a documented service gap.
It strengthens collaborative or coalition funding requests — 211 resource data, for example, is routinely shared with local governments and partner agencies to avoid duplicating research and to build a shared, regional picture of need.
It gives boards and EDs a concrete way to prioritize where the next dollar of unrestricted funding should go.
Unmet needs data vs. outcomes data: what's the difference?
These two are often confused, but they answer different questions:
Outcomes data answers: Did the help we provided work? (Did the client feel safer, access housing, complete counselling?)
Unmet needs data answers: What help did we fail to provide, and why?
Both matter, and a mature reporting system tracks both. But unmet needs data tends to get far less attention, largely because it requires deliberately tracking a "no" instead of a "yes" — which runs against the instinct of teams who are focused on getting people help, not logging when they couldn't.
FAQ
What's a simple definition of unmet needs data? It's data on requests for help that an organization couldn't fulfill because of capacity, service gaps, access barriers, or eligibility limits, as opposed to data on the help that was successfully provided.
Who uses unmet needs data? Program managers use it to justify staffing and new services; executive directors and development teams use it in grant applications and funder conversations; coalitions, regional 211 networks, and advocacy groups use it to make the case for system-level or policy change.
Is unmet needs data hard to collect? It doesn't have to be. The main barrier is workflow design, not the concept itself — building a required, structured field into intake or call-closing steps makes it far easier to capture consistently than relying on staff to remember and report it separately.
How is unmet needs data different from a waitlist? A waitlist is one form of unmet needs data (a capacity gap), but unmet needs data is broader — it also captures service gaps, access barriers, eligibility issues, and failed referrals that a waitlist alone wouldn't show.
Want to see how Izzy helps helplines and case management teams capture unmet needs alongside every call, text, and chat — without adding extra steps for staff and volunteers? Book a demo.
References
United Way Worldwide. "211 Helpline Data Reveals Housing as Most Pressing U.S. Community Need." United Way Worldwide News, March 31, 2026 (covering 2025 survey data — most current at time of writing). https://www.unitedway.org/news/211-helpline-data-reveals-most-pressing-us-community-needs-0
United Way Worldwide. "211 Impact Survey Results." United Way Worldwide, 2024 data. https://www.unitedway.org/211Data
United Way Worldwide. "2-1-1 Impact Survey Uncovers Widespread Unmet Community Needs Nationwide." United Way Worldwide News, 2023 (used only for the food/employment resolution-rate context below; superseded for volume stats by source 1). https://www.unitedway.org/news/2023-211-impact-survey-uncovers-widespread-unmet-community-needs-nationwide
ActivateCare. "How Do Your 211 Referral Outcomes Compare to St. Louis?" ActivateCare Blog. https://blog.activatecare.com/211-referral-outcomes
United Way of Greater Kansas City. "211." Accessed 2026. https://unitedwaygkc.org/211-2/
United Ways of Texas. "2-1-1 Texas: Local Information and Referral." Accessed 2026. https://www.uwtexas.org/2-1-1-texas
National Center for Biotechnology Information (NCBI). "Indications of Food Insecurity in the Content of Telephone Calls to a Community Referral System." PMC.https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10118074/
Health Resources & Services Administration (HRSA). "Unmet Need Score (UNS) User Guide." https://data.hrsa.gov/Content/Documents/topics/UNS_User_Guide.pdf
Social Impact Solutions. "A 5-Step Needs Assessment Template for Nonprofits." https://socialimpactsolutions.com/dev/a-5-step-needs-assessment-template-for-nonprofits/
Magic Lamp Consulting. "Why a Community Needs Assessment Is Imperative to Nonprofits." https://blog.magiclampconsulting.com/blog/why-a-community-needs-assessment-is-imperative-to-nonprofits