
Read the decline for what it says and does not say
Decline letters range from a form paragraph to a detailed note from the program officer, and the difference matters. A generic decline often means the request was outside priorities, outside the budget range, or simply one of many strong applications in a competitive cycle. A specific decline that mentions a gap in the proposal, a concern about capacity, or an invitation to reapply is far more valuable, because it tells you what to fix. Read it twice before reacting.
Pay attention to phrasing. An explicit line encouraging you to apply in a future cycle is meaningful when a funder writes it and merely a courtesy when they do not. A statement that the request is not a fit with current priorities usually means stop applying until those priorities change. A note about limited funds this cycle can mean the proposal was fine and the timing was not. None of these are guaranteed readings, but they are the starting point for the follow-up conversation.
Keep reading: Why do nonprofits keep missing grant deadlines even when they have the funding lined up?, How should a nonprofit set up grant pipeline stages to track applications from start to finish?, Why does assigning a clear owner to every grant application prevent last-minute scrambles?. See how GrantWatchr helps you grant deadline tracking for nonprofits.
The follow-up that funders actually welcome
A brief, gracious thank-you email within a week is appropriate for every decline, and it should not argue. Thank the funder for their consideration, note that you value the relationship, and ask one question: whether they would be willing to share any feedback that would strengthen a future application. Many program officers will answer, especially for organizations they want to see succeed, and some will offer a call. Accept the call if offered and prepare two or three specific questions. Related: Why does assigning a clear owner to every grant application prevent last-minute scrambles?
Where feedback is offered, listen more than you explain. The temptation is to correct the reviewer's understanding, which rarely changes the decision and sometimes damages the relationship. Instead, take notes on what they perceived, even if you think the proposal addressed it, because the perception is the problem to solve. Ask directly whether reapplying is encouraged and when the next cycle opens. Then close the conversation without asking for anything else. Related: Why do nonprofits keep missing grant deadlines even when they have the funding lined up?
Record the decline where the team will find it
A decline that lives only in the writer's inbox will be repeated. Log it against the funder record with the date, the amount requested, the program, the stated reason, and any feedback received. Add your own assessment: was this a fit problem, a competition problem, a proposal quality problem, or a timing problem. That one line is the most useful piece of institutional memory your grants function can hold, because it shapes the next decision about this funder.
Update your pipeline stage to declined rather than deleting the record, so that the history stays visible when someone considers this funder again. Over time, the pattern of declines across funders tells you things no single decline can: that your budgets consistently run above the funder's range, that a certain program does not resonate, or that your applications are strong but your timing puts you in the most crowded cycle. Those patterns only appear if declines are recorded consistently. Related: How should a nonprofit set up grant pipeline stages to track applications from start to finish?
Deciding whether and when to try again
Not every decline deserves a reapplication. If the funder's priorities clearly exclude your work, or if you have been declined multiple times without encouragement, the honest move is to mark the funder inactive and redirect the effort. If the decline was competitive and the funder encouraged a future application, schedule the next cycle now, with a note about what to change, so the decision is not lost when the calendar turns.
If you do reapply, address the previous feedback visibly rather than hoping the reviewer will not remember. A short line in the narrative noting what changed since the last application signals that you listened. And if the funder gave no feedback at all, consider whether a smaller request, a different program, or a partnership with an organization they already fund might change the fit. A decline closes one application. It does not have to close the funder. Related: How can a nonprofit grow its grant program without the tracking descending into chaos?
- Read the decline carefully, because the specific wording usually hints at fit, competition, or proposal quality.
- Send a brief thank-you within a week and ask one question about feedback, without arguing the decision.
- Log every decline against the funder record with the reason and your own assessment so patterns become visible.
- Reapply only where the funder encourages it, and show clearly what changed since the last attempt.
Never Miss A Grant Deadline
Grant deadline tracking for nonprofits. GrantWatchr is built to help you put this into practice.
Start free trialGet the GrantWatchr playbook
Practical guides on grant management, straight to your inbox as we publish them. No spam, unsubscribe any time.



