The decline came in. You've read the reviewer comments, maybe twice, and you've had a day or two to be disappointed. Now someone on your team is asking the practical question: do we try again, and if so, what do we actually change?
This post is the operational plan. It covers a timeline from decline to next deadline, a change log that ties each comment to a fix, what to keep, how to write a response section when the funder allows one and how to decide whether to reapply at all.
First, decide whether to reapply here
Before you plan a resubmission, make sure this funder is still the right one. If you haven't yet worked through what the comments mean, start with our post on reading a rejection, then come back.
Reapply to the same funder when:
- Your scores were close. You landed near the funding line, and the comments point to fixable problems (thin evaluation, unclear budget, missing partner letters).
- The fit is real. The program's purpose and priorities still match your project, and the next notice is expected to look similar.
- The program officer is encouraging. A short call to ask whether a revised application would be competitive can save you months. Our post on talking to a program officer has tips.
Consider switching funders when:
- The core concept was the problem. Reviewers questioned the need, the approach or your eligibility, not the details.
- Priorities shifted. The program changed focus, lost funding or now favors a type of applicant you aren't.
- Another funder fits better. You find a program whose purpose matches your project more closely, even if it's smaller.
If you do switch, most of the plan below still applies. You'll just map your changes to a new set of scoring criteria.
Build a timeline from decline to deadline
Work backward from the next deadline. If the date isn't announced, use last cycle's dates and the funder's forecast, then adjust when the notice posts.
Here is a hypothetical timeline for a program with an annual deadline roughly six months after the decline:
| Weeks after decline | What happens |
|---|---|
| 1 to 2 | Read comments, request any missing scores or summary, call the program officer, decide pursue or pass |
| 3 to 4 | Build the change log, rank fixes by points at stake, assign owners |
| 5 to 10 | Do the substantive work: new data, partner commitments, revised evaluation plan, budget fixes |
| 11 to 16 | Revise the narrative section by section, write the response or introduction if allowed |
| 17 to 20 | Full read-through against the new notice, internal review, approvals |
| 21 to 22 | Final edits, registrations check, submit early |
The substantive work in weeks 5 to 10 is the part most teams skip. If reviewers said your evaluation plan was weak, rewording it rarely helps. You need an evaluator, a data source or a clearer measure. That takes calendar time.
Keep a change log tied to every comment
A change log is a simple table that turns reviewer feedback into a to-do list and later becomes the backbone of your response section. Make one row per distinct comment.
| Comment (paraphrased) | Criterion and points | Change we'll make | Owner | Status |
|---|---|---|---|---|
| Outcomes not measurable | Evaluation, 20 | Add baseline data and two measurable targets per objective | Program lead | In progress |
| Partner roles unclear | Capacity, 15 | Get signed commitment letters naming roles and hours | Executive director | Not started |
| Budget lacks detail on contractual line | Budget, 10 | Add vendor quotes and a cost basis for each contract | Finance | Done |
(These rows are hypothetical.)
A few rules make the log useful:
- Paraphrase fairly. Write what the reviewer said, not what you wish they'd said.
- Note where the comment came from. If two of three reviewers raised the same issue, it's a priority.
- Log disagreements too. If you think a reviewer misread something, note it and plan to make that section clearer. A misread often means the writing was unclear.
Fix the lowest-scoring criteria first
Your time is limited, so spend it where the points are. Look at your scores by criterion, if the funder provided them, and compare each to its maximum.
A criterion worth 25 points where you scored 12 has more room to grow than one worth 10 where you scored 8. Start there. Ask what a reviewer would need to see to score that section near the top, then build the evidence.
Common high-value fixes include:
- Evaluation: measurable objectives, a baseline and a named person or partner responsible for data.
- Need: current, local data with sources, plus a sentence on why the gap persists.
- Capacity: proof you've managed similar work, staff qualifications and partner commitments in writing.
- Budget: every cost tied to an activity, with a clear basis for the amount.
Check the new notice before you finalize priorities. Scoring criteria and point values can change between cycles, and the new version is the one that counts.
Know what to leave alone
Reapplicants often overcorrect. They rewrite everything, and sections that scored well get weaker.
Keep a section largely intact when reviewers praised it or scored it near the maximum and when it still matches the new notice. Update facts and dates, tighten where you can and make sure it connects to the parts you changed. But don't rebuild a strong section just because you're in revision mode.
Watch for ripple effects, though. If you add a partner or change an activity, the work plan, budget, budget justification, staffing and evaluation all need to reflect it. Use your change log to track those downstream edits.
Write a response or introduction when it's allowed
Some funders invite a short section that responds to prior reviews. Others don't, and some explicitly say not to reference past applications. Follow the notice exactly.
The National Institutes of Health (NIH) is a well-known example of a formal process. NIH accepts a single resubmission (called an A1) of a new, renewal or revision application, and it must be submitted within 37 months of the original. The resubmission includes an Introduction of one page or less unless the funding opportunity says otherwise, and NIH asks applicants not to mark up changes within the application attachments themselves. After an unsuccessful A1, the idea can come back as a new application.
Whatever the funder, a good response section:
- Opens with thanks and a summary. One or two sentences on what changed overall.
- Groups comments by theme. Answer the substance, not each reviewer line by line.
- States the change and where to find it. "We added baseline data for all three objectives (see Evaluation Plan, page 9)."
- Stays respectful when you disagree. Clarify, add evidence and move on. Never argue.
Here is a short sample paragraph:
We thank the reviewers for their careful reading. Reviewers noted that our outcomes were not clearly measurable. We have added baseline data from our 2025 intake records and set a numeric target for each objective, with our evaluation partner responsible for annual data collection (Evaluation Plan, section 3).
If the funder doesn't allow a response section, your change log still matters. It keeps the team honest that every comment was addressed somewhere in the narrative.
Your next step
This week, open your reviewer comments and start the change log. One row per comment, with the criterion and points beside it. When it's done, sort by points at stake and you'll have your work plan for the next round. If you want to see how winners handled the same criteria, our post on requesting funded applications shows how to get them.
When the next notice opens, SoliContraX can help you rebuild. Upload the notice, approve a concept and get a draft built from your own materials, checked against what the funder asked for, which you then review and finish. Start your next application.