Grant application need statements that prove local demand

What is a grant application need statement?

A grant application need statement explains the problem your project will address, who is affected, and why funding is needed in your area now. It turns a good idea into a case a funder can assess.

Strong statements use local facts, lived experience and service evidence. They do not rely on broad claims about “need” that could apply anywhere. You need to show the size of the issue, the gap in current support and the difference your work will make.

The aim is simple: give an assessor enough proof to believe the need is real, local and worth funding.

On this page

• Why a need statement matters
• Start with the funder’s question
• Define the place and people
• Find local evidence that holds up
• Turn evidence into a strong argument
• Use lived experience properly
• Link need to delivery and outcomes
• A practical evidence checklist
• Common mistakes to avoid
• Review before you submit
• Frequently asked questions

Why a need statement matters

Funders receive plenty of applications with worthy aims. What separates a stronger one is proof.

Your need statement tells the assessor why your project should sit higher on the pile than another sensible proposal. It shows that you understand the people, the place and the problem beyond a few familiar phrases.

A good answer makes the connection between local conditions and your planned activity feel obvious.

Need is not proved by saying a community is deprived. It is proved by showing how deprivation affects the people you will support, and why your project is a practical response.

For senior leaders, this is often where pressure builds. You know the need is there because your team sees it every day. The challenge is putting that knowledge into a format that earns marks.

Start with the funder’s question

Before opening Nomis or searching for a statistic, read the guidance again.

What does the funder mean by “need”? They may care about health inequalities, youth unemployment, rural isolation, community safety, skills, early intervention or access to services. Those are different cases, and they need different proof.

Read the scoring criteria first

Look for the words that repeat across the guidance, application form and funder’s strategy. They often tell you what the assessor will look for.

Some funds ask for local demand. Others want evidence of unmet need, a defined beneficiary group, geographic disadvantage or a gap in provision. If they score outcomes and value for money, your need evidence must also lead naturally into those sections.

The grant application criteria and evidence should shape the case you make. Do not write a generic need statement first and try to squeeze it into the questions later. That is how good evidence ends up doing no scoring work.

Set boundaries around the answer

Decide your geography before collecting data. Is the project for one ward, several postcode areas, a borough, a district or a rural catchment?

Then define the people within that place. “Young people” is too wide if you are supporting 16 to 24-year-olds who are out of work. “Older residents” tells an assessor little if your service is for people over 75 who cannot access local activities without transport.

Precision helps. It also stops your figures drifting away from the project you are asking the funder to support.

Define the place and people

The strongest local case answers three questions early: where, who and what is happening.

Name the area. State the group. Explain the issue in plain language. An assessor should not have to hunt through three paragraphs to find the point.

Make geography do useful work

A borough-wide statistic may be useful, but it can hide sharp differences between neighbourhoods. If your project is based in two estates or a particular town, use data at that level where possible.

Census 2021 data, local authority profiles and deprivation data can help you show population size, age profile, disability, employment, overcrowding or household circumstances. Nomis is often useful for local labour-market data, whilst a Joint Strategic Needs Assessment, usually called a JSNA, can provide the local health and inequality picture.

The UK deprivation data collection can help you identify where area-based disadvantage is concentrated. Use it with care. A deprived area is context, not the whole story.

Name the people behind the numbers

Numbers give scale. They do not tell an assessor why your service is needed by this group.

Add relevant detail. Perhaps local young carers miss activities because caring responsibilities limit their time. Perhaps older residents live within a bus route on paper but cannot use it after early evening. Perhaps small businesses need digital skills, but local providers only offer courses during standard working hours.

Keep the focus on facts you can support. You are not trying to write a sad story. You are showing a real barrier and a credible response.

Find local evidence that holds up

A useful grant application need statement usually draws from more than one source. One figure can be challenged. A small body of evidence that points in the same direction is much harder to dismiss.

Start with reliable public data. Then add what your organisation and local partners know.

Use public data for scale and context

ONS Census 2021 data can show who lives locally. Nomis can support employment, claimant count and population evidence. Your council’s JSNA, director of public health report and local health profiles can show priorities, trends and inequalities.

If safety is part of the issue, police.uk data may help you describe local crime or anti-social behaviour patterns. For a health-related project, NHS and public health data may show prevalence, access issues or service pressure.

Do not collect every available statistic. Pick the figures that support the exact problem your project addresses.

Evidence source	What it can prove	Best use in an application
Census 2021 and Nomis	Population, age, work, health and housing patterns	Describe the local population and scale
JSNA and public health reports	Health priorities, inequalities and service gaps	Explain why the issue matters locally
Deprivation data	Area-level disadvantage and unequal access	Add geographic context
Your own service records	Referrals, waiting lists, unmet demand and outcomes	Show what is happening now
Partner feedback	Gaps, referral patterns and shared priorities	Confirm the issue is not yours alone

A local evidence pack does not need to be enormous. The Mayor’s Community Fund evidence guide is a useful reminder that evidence should be proportionate to the funding and project size.

Use your own evidence for the gap

This is where many applications become more convincing.

Your waiting list, referral numbers, enquiries, attendance data and exit feedback can show demand that public data cannot. A youth service might report a rise in referrals from schools. A community organisation may have 43 people waiting for advice appointments. A business support programme may show that most enquiries come from firms with fewer than ten staff.

Keep records tidy. State the timeframe, source and sample size.

For example:

“Between April 2025 and March 2026, we received 186 referrals for debt advice from residents in the project area. We supported 121 people within existing capacity, leaving 65 unable to access an appointment within four weeks.”

That is far stronger than saying demand is increasing.

Turn evidence into a strong argument

Data without explanation can feel like a box of receipts tipped onto the kitchen table. There may be useful things in there, but nobody can see the total.

Your job is to guide the assessor through the logic.

Use the claim, evidence, meaning structure

Start with a direct claim. Follow it with evidence. Then explain what that evidence means for the people you will support.

It can look like this:

“Residents aged over 65 make up 24% of the local population, above the England average. The council’s JSNA also identifies social isolation as a priority for older residents in the area. Our weekly transport-supported groups will give 80 isolated residents regular access to social activity, peer support and local advice.”

The structure is simple:

• State the problem in the target area.
• Give a recent, relevant source or figure.
• Explain the effect on the named group.
• Show how your project responds to that effect.

The VCSE guide to applying for a grant makes the same practical point. Funders need evidence that the need exists, alongside a clear view of the outcomes the project will deliver.

Put the strongest proof first

Lead with your most relevant evidence, not the national context.

A national statistic can support your point, but it rarely proves why your local project needs funding. Use it later, if it adds useful comparison.

Avoid piling up figures in one sentence. Give each important number room to land. An assessor has limited time, and nobody awards extra marks for making them decode a spreadsheet in paragraph form.

Use lived experience properly

Local voices can make your evidence more grounded. They should not be decoration.

Use service-user feedback, consultation findings, partner letters and community surveys to explain barriers that data alone cannot show. A parent may explain why a free activity is still inaccessible without transport. A local employer may identify a skills gap that does not appear in a national report.

Keep evidence ethical and specific

Do not include identifiable personal details without permission. Do not use a single emotional quote to stand in for a whole community either.

Instead, show the method. Say how many people took part, when the feedback was gathered and what themes came through.

For example, “In a January 2026 survey of 57 local parents, 39 said cost and transport stopped their children attending holiday activities.” That is clear, proportionate and easy to understand.

The National Lottery Community Fund’s guide to generating evidence is helpful on keeping evidence activity proportionate to the size of the project.

Link need to delivery and outcomes

A need statement is only half the case. The other half is showing your project can meet that need in a realistic way.

If the local issue is rising demand for advice, explain how many additional people you will support. If access is the barrier, explain what changes access. If the gap is a lack of early help, explain why your model reaches people sooner.

Set a sensible baseline

Start with what is happening now. Then state the practical change you expect to make.

You might have 65 people unable to access support within four weeks. The funded project may create capacity for 120 extra appointments, with an aim that 85% of referrals are offered an appointment within ten working days.

Those figures should be credible. Funders can spot wishful thinking a mile off, particularly when the budget and delivery plan say something different.

Your outcomes do not need to promise the moon. They need to show a reasonable change, backed by the right people, process and resources.

A practical evidence checklist

Before you submit, test the evidence behind your case for funding.

• Check that every major claim has a source, date and geographic area.
• Use data that matches the people your project will support.
• Include at least one source that shows the scale of need.
• Add your own service data, referrals, waiting list or consultation findings.
• Explain the gap in current support, rather than assuming the funder knows it.
• Confirm your evidence is recent enough for the issue you describe.
• Link each need point to a project activity and intended outcome.
• Read the answer against the funder’s scoring criteria, word limit and guidance.

A broader grant application checklist can help your team test readiness before the deadline starts looming.

Common mistakes to avoid

Poor need statements are rarely poor because the organisation does not understand its community. They lose strength because the evidence is too broad, too old or disconnected from the project.

Relying on generic deprivation language

“our area is deprived” is not a need statement. It does not tell the assessor which people are affected, what happens to them or why your service is the right response.

Name the actual issue. Use deprivation figures as supporting context. Then show the local impact through health, employment, service demand, access or safety evidence.

Data dumping without a point

Five statistics in a row are not automatically persuasive.

Every number should answer a question. What does it show? Why does it matter? What will your project do about it?

If a fact does not change the funder’s understanding of the need, cut it. It may be interesting, but interesting is not the same as scoreable.

Treating demand as proof of impact

A full waiting list proves people want something. It does not prove your project will improve outcomes.

Show demand, then describe the activity, delivery capacity and intended result. Keep those links visible across the application, including the budget.

Ignoring existing provision

Funders often want to know what already exists locally. Do not pretend no one else is working on the issue if they are.

Explain the gap. Perhaps current provision has a long waiting time, is not accessible to your group, ends at age 18, lacks specialist support or has no evening delivery. Collaboration looks better than pretending you are the only show in town.

Review before you submit

Read your need statement as if you have never met your organisation.

Can you find the problem, place, people, proof and proposed response within the first few lines? Can every key claim be checked? Does the evidence match the funder’s definition of need?

A strong review looks at what an assessor can actually award marks for, not what the team meant to say. That is where an independent pair of eyes can save a submission that is nearly there, but not yet convincing.

Put local proof at the heart of your application

The best grant applications do not sound louder. They sound more certain because the evidence is relevant, current and tied to a practical plan.

Your local knowledge matters. Give it structure, support it with proof and make the route from need to outcome easy to follow.

If you want a candid, evaluator-focused check before submission, explore grant funding support, the Bid Win Rate Accelerator Training or a fit check call. Bidsmithery™ can help you spot where your case is strong, and where it still needs work.

Frequently asked questions

How much evidence should a grant need statement include?

Use enough evidence to prove the issue without burying the point. For most applications, two or three strong public sources, plus your own local service evidence, will be more effective than a long list of statistics.

Match the level of detail to the grant size, the funder’s criteria and the available word count.

Can we use national statistics in a UK grant application?

Yes, but national figures should support local evidence rather than replace it. A national statistic may explain the wider issue, but the funder still needs to know why the problem matters in your area.

Bring it back to your geography, target group and delivery model.

What if there is no recent data for our ward or neighbourhood?

Use the smallest reliable geography available, then add current evidence from your organisation and local partners. Referral trends, waiting lists, surveys, case records and consultation feedback can show what has changed more recently.

State the area and date clearly, so the assessor understands the limits of the evidence.

Should we include quotes from service users?

A short quote can help if it adds a barrier or insight that data cannot show. It should be anonymous, used with permission and supported by wider evidence.

Do not rely on one quote to prove a community-wide problem.

How often should we update our evidence bank?

Review it before every significant application. Keep dated copies of key local reports, service data, referral patterns, outcomes and partner feedback.

The best time to build an evidence bank is not two days before a deadline. Sadly, that is also when most teams discover they need one.

Key takeaways

• A strong grant application need statement proves a local problem, not simply a worthy ambition.
• Use public data for scale, then add service demand and community insight to show the gap.
• Make every statistic earn its place by explaining what it means for the people you will support.
• Link need directly to delivery, outcomes and a realistic budget.
• Write so an assessor can find the proof and award the marks without doing detective work.