The email arrives and the answer is no. Weeks of work, a team that stretched for the deadline and a budget gap that was counting on this money. Then a second decline comes, and the mood in the office changes. People start asking whether anyone should bother applying again.
If you lead a grants team or run the organization, how you respond in the next few days sets the tone for the next application. This article covers how to put a decline in perspective, how to talk to your team, how to run a debrief that teaches something and how to get moving again.
Put one decline in perspective
Competitive funding is built on more demand than money. One public example comes from the National Institutes of Health, which publishes its success rates. For research project grants, the share of reviewed applications that were funded stayed between about 19 and 21 percent in each fiscal year from 2018 through 2023. NIH funds research, not community programs, so the number doesn't transfer to your field. It does show how a long-running competitive program can work: most applications receive a no, including strong ones.
Your own programs will have their own odds, and some are far better or worse. Ask the funder or read past award lists to find out what is typical for the one you applied to.
That context supports one point: a decline tells you the application didn't win in that round. It doesn't say your organization is weak, your cause is unimportant or your team can't write. A decline can reflect a funder with a small budget, a priority that shifted or a pool of strong applicants. Sometimes it does point to a fixable problem, which is what the debrief is for.
Talk to the team honestly and quickly
Silence after a decline lets people fill in their own explanations, and those are usually harsher than the truth. Tell the team within a day or two.
- Say it plainly. "We weren't funded this round" is better than a long cushioning speech.
- Thank people for specific work. "The community survey data made the need statement stronger" lands better than "great job, everyone".
- Separate the process from the people. Talk about the application, the timeline and the funder's decision. Don't talk about who wrote which section as if someone is to blame.
- Share the full picture of the year. If the organization has had other awards, mention them. One loss is easier to carry beside the wins.
- Let people feel it. Disappointment after real effort is normal. A day of lowered expectations is fine. A week of silence isn't.
If you're the one who wrote the application, you're likely the one taking it hardest. Burnout in the funding cycle covers how to build recovery into the year, and a decline is a reasonable time to use some.
Run a blame-free debrief
A debrief turns a decline into information. Schedule it after the first sting has passed but while memories are fresh, within a couple of weeks.
Keep it to an hour and ask the same five questions each time:
- What did the notice ask for, and where did we answer it well?
- Where was our application thinnest or least clear?
- What got in the way of our process: time, missing information, late sign-offs?
- What did we learn about the funder that we didn't know?
- What will we do differently next time?
The rule is that every comment is about the work, not a person. "The budget narrative was written last, in a rush" is useful. "Dana's budget was late" isn't, and it teaches people to hide problems.
Write down the answers and keep them where the next application team will see them. If the funder offers reviewer comments or a conversation, request it. Reading a rejection looks at how to read the response you receive.
Here is a hypothetical example. Say a small environmental nonprofit sends out eight applications in a year, three are funded and five are declined. At the year-end debrief, the team notices that all three funded applications began six weeks before the deadline, while four of the five declines began in the last two. Nobody did anything wrong in the declined ones. The pattern points to the schedule, and the fix is a rule about start dates, not a conversation about talent.
Keep leadership and the board informed
Your executive director and board will want to know what a decline means for the budget. Bring three things: what the application would have covered, what the plan is to cover that gap and what the debrief found. A short, factual update shows a team that is learning, and it makes the next request for time or support easier to win.
If the decline leaves a real hole in the budget, say so early. A gap that leadership hears about now can be managed. One that surfaces at the end of the quarter feels like a surprise, and it makes the grants team look like the cause.
Decide what happens next
Once the debrief is done, act on it before enthusiasm drains away.
- Decide whether to reapply. Some funders welcome a second try and some don't. Check the funder's guidance and ask the program officer. A go/no-go check keeps the decision honest.
- Reuse the work. The needs data, program description and budget you built are not wasted. They can anchor the next application with changes for a new funder.
- Line up the next opportunity. Having something concrete to work on helps a team move on faster than reflection alone.
- Revisit your pipeline. If declines cluster with one type of funder, shift effort toward funders where your fit is stronger.
Your next step
Put a debrief on the calendar now, even if you haven't had a decline yet, and write the five questions above into the invitation. When the next decline comes, you'll have a routine ready and nobody will have to decide how to handle it in the moment.
When the next opportunity is ready to pursue, SoliContraX can help the team get moving again. Upload the notice, refine the concept you approve and redraft from your organization's own materials. Start your next application.