What exactly did the funder say-and what did they leave out?
The first thing you do after your grant rejection lands is probably groan, close the email, and swear off funders forever. Don't. Instead, read that letter again-carefully. What did they actually say? And what did they leave out?
Most rejection letters are masterpieces of vagueness. "Not competitive at this time." "The committee felt the proposal didn't quite align." These phrases aren't helpful-they're code. But that code contains clues if you know how to decode it.
Look for specific phrases like these:
- "Lack of fit" → Your project didn't match the funder's priorities. That's fixable if you re-read their mission and adjust your framing.
- "Weak outcomes" → Your outcomes were vague or unmeasurable. This is a huge one: 83% of rejected proposals fail on this exact point, not on need statements.
- "Eligibility concerns" → 62% of rejections stem from basic eligibility mismatches-you didn't qualify but applied anyway. Check your eligibility before your next application; it'll save you 20-60 hours.
Now look for what's missing. Many funders auto-generate generic responses. They use templates because they're swamped. That's not malice-it's efficiency. But it leaves you guessing.
Your next move: ask for the real feedback. Fewer than 30% of rejected applicants ever request specifics. That means those who do are memorable. The funder knows your application-they spent time on it. A polite, brief email asking for one or two points of constructive criticism often gets a surprisingly detailed reply.
Don't sit on that email. Send it within 72 hours while the application is still fresh in the reviewer's mind. Be specific: "You mentioned 'lack of fit.' Could you share which priority area my proposal didn't address?" That turns a vague "no" into actionable intelligence.
Did I ask the funder for feedback-and how do I make that request?
Most funders won't volunteer feedback. They'll send a polite "we received many strong applications" and call it a day. But here's the thing: many of them will share insights if you ask-respectfully and specifically.
According to Williams Grant Writing, fewer than 30% of rejected applicants proactively request feedback. That means by simply asking, you immediately join a minority that funders remember. You're signalling something important: you're serious, you're teachable, and you respect their time.
Timing matters. Don't wait a month. Send your request within 72 hours of the rejection email. That window keeps your application fresh in the reviewer's mind and increases the chance they'll give you something useful beyond boilerplate.
Here's a simple script you can adapt:
Dear [Name], Thank you for the careful consideration of our application. We're committed to strengthening future proposals and would genuinely appreciate 2-3 bullet points on what was missing or could have been stronger. Any insight you can share would be invaluable. Warm regards, [Your name]
Keep it short. Don't ask for a re-evaluation or imply the decision was wrong. You're asking for guidance, not a second chance.
What if they still say no? It happens. Some funders have strict policies. But even a non-response teaches you something: that funder isn't invested in your growth. That's useful intel for where to invest your energy next cycle.
Your goal here isn't just closure. It's raw material for your next application.
Was my proposal really aligned with the funder’s priorities, or just close?
The stated priorities on a funder’s website are a starting point. But they’re not the full picture. What actually gets funded often lives in the gap between what they say they want and what they’ve historically backed.
Look at the recent grant list-not just the mission page
Pull up the funder’s last 12-18 months of awarded projects. Do the titles and abstracts match the language in your proposal? Or are you seeing a pattern they didn’t advertise?
Example: A funder says they support “community health.” But their recent grants all focus on maternal health in rural areas. If you submitted a proposal about urban diabetes prevention, you weren’t misaligned-you were in the wrong niche.
That’s exactly what happened to a PhD applicant in the 7 Lessons post. They applied to a program whose stated priorities matched their research. But after contacting faculty, they discovered the department’s active projects were completely different. The “no supervisor availability” feedback wasn’t about their qualifications-it was about real-world capacity. They rewrote their narrative around actual ongoing work and got in the next cycle.
Vague outcomes are the fastest way to look misaligned
Here’s a hard stat: 83% of rejected proposals fail because outcomes are vague or unmeasurable (GrantGunner, Stop Reporting Activities). Even if your topic aligns, if your results section reads like a wish list-“improve community wellbeing”-funders can’t connect your project to their tracked priorities. They’ll assume misalignment and move on.
Your action plan
- Download the funder’s recent grantee list. Compare their project titles, methods, and outcome language to your proposal. Highlight every difference.
- Map your wording to their actual funded language. If they say “reduce hospital readmissions” in their awarded projects, use that exact phrase-not “improve patient discharge outcomes.”
- Run the ‘So What?’ test on every outcome. If you can’t finish the sentence “so that…” with a specific, measurable result, your alignment is weaker than you think.
Did my narrative sound like me-or like a template?
You've written your proposal in your own words. But honest question: would a reviewer be able to swap your organisation's name with any other applicant's and barely notice the difference? If the answer is close to "yes," you've got a voice problem.
A 2025 survey of 47 UK trust officers found something telling: 41% of AI-assisted proposals were rejected precisely because they used generic language that lacked organisational voice. Funders are trained to spot phrases like "transformative impact," "tackling systemic inequality," or "leveraging community assets." They've read those words hundreds of times. They don't tell a unique story. They signal you're filling a template-not speaking from experience.
Run your narrative through a 'Template Test'
Print your proposal and grab a highlighter. Mark every phrase that could appear in any other grant application from any other organisation. Then ask yourself: "Is this something my team actually did, or something I read in a sample proposal?" Phrases like "we are committed to" or "our holistic approach" are almost always generic noise.
Replace buzzwords with concrete proof
Instead of "transformative impact," try: "Twenty-two parents who hadn't read a single book aloud now read 15 minutes daily to their children-verified via home visits." Instead of "community-driven," try: "We co-designed the programme with 14 local residents who'd been homeless, then hired three of them as paid peer navigators."
Quick audit checklist for your next draft
- Read it aloud. If it sounds like a press release, cut it.
- Check for "we believe" statements. Replace them with "we have evidence that…"
- Ask a colleague who knows nothing about your project: "What three things make this organisation unique?" If they can't answer from the proposal, you haven't written yourself into it.
- Look at your nouns. "Stakeholders" is a red flag. "Parents, teachers, and local business owners" is specific.
Funders don't just fund good ideas. They fund your good idea, executed by your people, in your community. Make sure your proposal sounds like it came from nowhere else.
What one action can I take right now to prove I’m ready for next time?
Stop treating that rejection letter like a dead end. Treat it like raw material. Many of the most competitive applicants don't wait for the next cycle to prove themselves-they repurpose their rejected proposal into something tangible now.
Turn your 'no' into published work
As the GrantGunner article 7 Lessons from a Rejected PhD Application shows, one early-career researcher turned a rejected fellowship proposal into two published pieces-an original article and a commentary-within six months. Her next application opened with a killer line: “I have already tested this idea-the results are promising.” Reviewers stopped seeing a high-risk bet. They saw a proven line of inquiry.
You can do the same. Strip the proposal down to its core argument and submit it as a preprint, a blog post, or a case study on your website. It doesn't have to be peer-reviewed. It just has to exist. That single piece of evidence-showing you executed, not just intended-shifts you from hopeful applicant to credible partner.
Build proof with small actions
Don't have time to publish? Gather partner letters of support. Run a pilot workshop. Collect even raw data from a small test. Funders fund execution, not promises. Showing you've already started the work makes your next application dramatically harder to reject.
Track every rejection like a scientist
Here's the simplest thing you can do right now: open a spreadsheet. Create columns for date, funder name, ask amount, feedback received, and action taken. Every time a rejection comes in, log it and assign one concrete next step. Over time, this tracker becomes your institutional memory-and your win rate climbs.
Your next 'yes' isn't hiding in a perfect proposal. It's built in the margins of your last 'no.'
Grant funding for charities
GrantGunner finds charity grants and drafts the application from your own documents. See charity grants