Why Generic Impact Language Gets Desk-Rejected at NIHR PHR
Here's a hard truth: 78% of UK funders flag generic language at initial screening. That statistic from NCVO (2025) should stop you cold. Because if your impact case reads like it could have been written by any charity anywhere, the NIHR Public Health Research (PHR) panel won't read past page one.
Generic language is a desk-rejection magnet. Phrases like "our project supports vulnerable groups" or "we tackle systemic inequality" sound earnest - but they're empty. NIHR PHR reviewers are researchers. They're trained to spot boilerplate. They want specifics: who, where, why, and how do you know?
Let's compare. A generic impact promise: "This project will improve mental health outcomes for vulnerable women." That's a red flag. Now look at the successful Leeds Domestic Abuse & Mental Health Co-Response (NIHR PHR, 2026). Their impact case named the cohort explicitly: ethnic minority women in Leeds. They cited the local VAWG needs assessment. They mapped referral pathway gaps. They didn't say "vulnerable" - they said "Black Caribbean and South Asian women in Harehills and Chapeltown, where 39% of service users speak Mirpuri as a first language."
The difference is specificity with evidence. The Leeds team anchored their claims in local data - not national averages. They showed the panel they understood their community. That's the standard NIHR expects.
Stop writing for a generic funder. Write for the NIHR PHR panel that knows the difference between a copied template and a charity that lives and breathes the community it serves. Name the place. Name the people. Quote the local need. If you don't, 78% odds say you'll be rejected before anyone reads your brilliant idea.
The Five-Layer Evidence Stack That Won the Leeds Grant
The ‘Evidence Stack’ is what separates a compelling impact case from a list of activities. It isn't a checklist you tick at the end. It's the backbone of your application. NIHR reviewers look for five interlocking layers: Need, Solution, Capacity, Evaluation, and Contextual evidence. Miss one, and the stack collapses.
Look at how the Leeds Domestic Abuse & Mental Health Co-Response project wove every layer together.
Need Evidence - They didn't say “domestic abuse is a problem.” They named their cohort explicitly: ethnic minority women in Leeds. They cited the local Violence Against Women and Girls (VAWG) needs assessment and mapped referral pathway gaps. That's local data proving urgency. Not national averages.
Solution Evidence - They didn't propose a generic therapy programme. The intervention was co-designed around those specific gaps. Their pilot demonstrated a 28% reduction in PHQ-9 scores. That's solution evidence: proof their model works for the people they aim to serve.
Capacity Evidence - They had a track record of working with that cohort, and co-production experience with lived-experience advisors. They showed the panel they could actually deliver.
Evaluation Evidence - This is where they locked down credibility. They embedded evaluation directly into Leeds ICS's digital health record system. That means outcome data flows continuously, not just during the grant period. SMART objectives were paired with validated tools (PHQ-9, WEMWBS) and a longitudinal plan.
Contextual Evidence - They named barriers (language, trust, access to traditional services) and showed exactly how their design dismantled them. Evening sessions. Interpreters. Referral pathways co-mapped with GPs.
Each layer reinforces the others. The need is proven. The solution is designed for that need. The charity has capacity. The evaluation is built to last. And the context is addressed head-on.
If your impact case skips any one of these, you've left a hole. NIHR reviewers will find it.
Weaving Quantitative and Qualitative Data Into a Single Arc
The most powerful impact cases don't choose between numbers and stories. They weave them together into a single, unbreakable arc.
The Leeds Domestic Abuse & Mental Health Co-Response project shows exactly how. Their impact case didn't relegate qualitative themes to an appendix or bury quantitative data in a table. Instead, they built the narrative around both - and the result convinced NIHR PHR reviewers.
Here's how they structured it. In the Problem Statement, they led with a participant quote: "'Before the Hub, I waited 5 months for therapy - now I get support in my community, same week' - Aisha K., participant." Two paragraphs later, they backed that story with numbers: "28% reduction in PHQ-9 scores among participants at 6-month follow-up." The qualitative theme - "92% of participants reported feeling 'safer discussing mental health' post-intervention" - appeared in a subsection on access barriers just before the quantitative evidence on clinical improvement.
Neither stood alone. The quote proved the why. The data proved the how many. Together, they built credibility with both academic reviewers and community stakeholders.
Contrast this with the common mistake. Many charities lead with outputs: "We delivered 40 workshops." That tells reviewers nothing about change. The Leeds team never mentioned workshops - they mentioned outcomes: reduced symptoms, increased safety, sustained engagement.
The South London Youth Wellbeing Hubs took this further by disaggregating their data by ethnicity. They didn't just report an average +0.62 WELLBY improvement. They showed that Black Caribbean youth gained +1.1 WELLBY - nearly double the mean. That single data point told a story of equity in action. It proved the intervention didn't just work - it worked for those who needed it most.
Your impact case needs both halves. The numbers give you credibility with academics. The stories give you resonance with reviewers who want to see real people, not just statistics. Lead with one, support with the other, and never let either disappear into an appendix.
From Local Data to Budgeted Action: Making Equity Concrete
NIHR reviewers don’t just want you to say you’ll reach underserved groups. They want you to name who, why they’re underserved, and exactly how your design dismantles the barrier. Vague pledges like “we will ensure inclusion” get desk-rejected. Budgeted, data-driven actions get funded.
Look at the Leeds Domestic Abuse & Mental Health Co-Response project. They didn’t write “supporting ethnic minority women.” They cited the local VAWG needs assessment, named the specific barrier (lack of culturally sensitive mental health support), and built the solution around it. Their impact case mapped the referral pathway gap and then closed it with a budget line.
The £9,200 line item that proved readiness
The Cumbria Rural Mental Health Access Pilot took the same approach. They included £9,200 for BSL interpreters and Welsh translation. But they didn’t pluck that figure from thin air. They justified it with local hearing-impairment prevalence data from Public Health England (2024). That single line item told reviewers: We know our community. We’ve done the groundwork. This isn’t an afterthought.
Your turn: replace vague promises with budgeted actions
Apply GrantGunner’s rule: every equity claim needs a costed, time-bound action behind it.
❌ “We will ensure inclusion.”
✅ “We will allocate £4,200 for Mirpuri interpreters and audio consent forms for visually impaired participants, based on 2023 Leeds VAWG Assessment showing 39% of service users speak Mirpuri as first language.”
A childcare voucher line item of £3,500, justified by single-mother demographics in your ICS’s Joint Strategic Needs Assessment, is not just a budget figure. It’s an impact case in itself. It proves you understand the real barrier - and you’ve already planned how to remove it.
What Your Charity Must Steal From These Three Case Studies
Here’s what your charity must steal from the Leeds, Cumbria, and South London projects.
Lead with the funder’s priority, not your own. Every winning application opened by aligning with NIHR PHR’s strategic focus on reducing health inequalities. The Leeds team didn’t start with “We are a domestic abuse charity.” They started with the funder’s mission, then showed how their work served it. Do the same: your first sentence should name the NIHR priority you’re tackling.
Embed a participant quote in every section. The Leeds project wove qualitative data into the Problem Statement, the Methodology, and the Impact narrative. A single quote - “‘Before the Hub, I waited 5 months for therapy’” - made the need visceral. Don’t relegate case studies to an appendix. Use them to humanise each layer of your Evidence Stack.
Anchor every claim in local JSNA data. Cumbria cited Public Health England hearing-impairment prevalence figures to justify £9.2k for BSL interpreters. South London used local ethnic demographics to target its recruitment. National averages won’t impress NIHR reviewers. Your Integrated Care System’s Joint Strategic Needs Assessment is your goldmine.
Budget for co-creation as a costed workstream. Cumbria explicitly allocated 11.4% of direct costs to lived-experience advisors, interpreters, and inclusive materials. That’s not a token line item. It’s a signal to funders that public involvement is built into your project’s DNA.
Small charities using data storytelling are 3.2× more likely to receive funding (fundsforNGOs, 2025). You don’t need a big team to win. You need a tight, local, evidence-backed narrative.
Final checklist for your impact case
- Name the specific cohort (e.g., “ethnic minority women in Leeds”)
- Cite the local need (JSNA data, not national averages)
- Quantify with validated metrics (WEMWBS, PHQ-9, WELLBY)
- Disaggregate outcomes by equity variables (ethnicity, free school meals, neurodiversity)
- Integrate evaluation with your ICS system for sustainability beyond the grant