A windsock stretches across a quiet field, an imagined reminder to assess the conditions before choosing the next move.
Read the evidence, repair what matters and know when to choose another opportunity
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
A grant rejection often arrives after the work has already become real in the applicant’s imagination. Staff have planned the activities. Partners have discussed their roles. Someone has pictured the people who might benefit. Then a short message changes the immediate future of all that preparation.
The disappointment deserves space. So does the decision that follows it.
An organization can spend the next month defending the old application, rewriting every paragraph or looking for a completely different funder. Any of those responses can consume scarce time without addressing the reason the proposal was unsuccessful. The useful question is more precise: what does the available evidence tell us to do next?
Sometimes the answer is a substantial redesign. Sometimes it is a clearer explanation of work that was already sound. Sometimes the project belongs with another funder. And sometimes the responsible decision is to stop pursuing a proposal whose costs now exceed its value.
Begin with the decision you actually received
Keep the submitted application, the notice in force when it was submitted, the decision letter, any scores and every official comment together. Preserve the submitted version. Quietly correcting that file afterward makes it harder to distinguish what reviewers saw from what the team intended to say.
Establish whether the application was ineligible, returned without review, reviewed but not selected, or still awaiting a funding decision. A portal score is not necessarily a final rejection. A submission error requires a different response from a concern about the research design. Limited funds and weak technical merit are also different explanations, even when both produce an unfunded application.
Record what the funder actually says. If the message gives no reason, write “reason not provided.” Do not turn silence into a verdict about the project, the community or the applicant’s reputation.
Feedback practices differ. Some funders provide detailed critiques; others offer a short explanation or no individualized comments. Check the published procedure before requesting a conversation. Where feedback is available, ask a focused question about the decision or the next application rather than demanding an argument with reviewers.
A specific system, not a universal rulebook
The National Institutes of Health provides a useful worked reference because it publishes detailed guidance on peer review, resubmission and appeals. The discussion here uses NIH instructions checked on November 10, 2026, together with a historical career-development application released by the National Institute on Aging.
NIH supports research and research training under specific funding opportunities. Its rules are not automatically the rules of a community foundation, a local authority or another federal agency. Nor does the example establish that Feel Worldwide Foundation is eligible for, has applied to or has received any NIH award.
At NIH, a summary statement can include reviewer critiques, criterion scores, administrative comments, budget recommendations and a summary of the panel discussion. For discussed applications, the final overall impact score runs from 10 to 90, with lower scores indicating greater assessed impact. Applications designated Not Discussed do not receive that numerical final score. A score is an assessment within this review system, not a percentage probability of funding. See NIH’s first-level peer review guidance.
Read the actual opportunity’s current review criteria as well. A historical sample may use criteria or forms that no longer govern the next submission.
Read for the central concern before counting comments
Start with the official decision and, where available, the panel’s summary. Then read the individual critiques. A page containing ten minor suggestions may be less important than one unresolved question about whether the central activity can work.
Keep strengths visible. If reviewers valued the problem, the team or the partnership, a revision should not accidentally remove those assets while trying to satisfy every suggestion. Likewise, apparent disagreement deserves examination. One reviewer may have understood a section that another found unclear. That can reveal a communication problem, a substantive disagreement or both.
Use the official program contact for interpretation within the agency’s process. At NIH, applicants must not contact reviewers to influence the review or send information directly to them. Its peer review guidance directs applicants toward the listed program official for advice after review.
The purpose of that conversation is to understand the evidence and available routes. An encouraging conversation does not become a funding commitment.
What an actual unfunded review can teach
NIA’s sample application collection includes Elizabeth Luth’s K99/R00 application from the Weill Medical College of Cornell University. NIA identifies the 2019 initial application as unfunded and the 2020 resubmission as funded. These are historical teaching examples shared with the applicant’s permission, not a representative sample of all applicants or a current template.
The 2019 summary statement, page 2, praised the candidate’s preparation and mentoring team. It also questioned whether the first aim could be completed in one year, noted that later aims depended heavily on it, and found the justification for a proposed goal-attainment tool unconvincing. Other concerns involved sampling and differences among clinician types.
Those observations point to distinct decisions. A scheduling concern calls for evidence of feasibility. Dependence on an early aim calls for a credible response if that aim stalls. Doubt about a measurement tool calls for a methodological justification or a different choice. More enthusiastic language would not resolve those questions.
The case demonstrates how specific feedback can guide revision. It does not prove which change caused the later award, that all the concerns were equally important or that another applicant would obtain the same result. The original documents credit Dr. Luth, her institution and NIH NIA; their research plan should not be borrowed as someone else’s work.
Separate repairable weakness from poor fit
A team benefits from naming the kind of problem before assigning someone to rewrite it.
A clarity weakness exists when the underlying work is credible but the application does not explain it well. Perhaps a partner’s confirmed contribution was omitted, or the timeline never showed when recruitment would begin. The repair may be a concise explanation supported by the existing record.
An evidence weakness is different. If the application promised access to participants without a confirmed recruitment route, the missing item may be an agreement or a feasibility test. Adding a confident sentence would conceal the uncertainty rather than resolve it.
A design weakness concerns the work itself. Activities may not address the stated problem, the evaluation may not measure the intended change, or the schedule may depend on resources that are unavailable. These concerns require decisions about scope, methods, staffing or timing before the prose can improve.
Poor fit occurs when the applicant, activity, population, geography, career stage or requested support does not match the opportunity. Some mismatches are threshold eligibility issues. Others concern program priorities or what kind of evidence the funder expects at a particular stage.
Ask whether addressing the mismatch would still leave a project worth doing. A service organization should not invent a research purpose merely because a research opportunity is open. Nor should a small exploratory project promise a definitive evaluation simply to resemble a larger funding mechanism.
Fit can also change between rounds. Recheck the live notice, amendments and agency announcements. Last year’s eligibility or permitted cost is not a permanent entitlement.
Turn feedback into a small set of decisions
For each important concern, write a short record containing five things: the official comment, the team’s interpretation, the proposed response, the evidence needed and the person responsible. Add a date for deciding whether the response is ready.
Keep the comment separate from the interpretation. “Recruitment feasibility is unclear” does not necessarily mean “double the recruitment budget.” It might mean that the applicant failed to provide an existing referral agreement. It might also mean that the available population is too small. Those possibilities lead to different work.
Test the response with a question: what would a careful reader now be able to verify that they could not verify before? A new paragraph is useful only if it removes a real uncertainty or explains a defensible choice.
Disagreement can be handled respectfully. An applicant may retain a method if there is a sound reason, explain the reason and strengthen the supporting evidence. Accepting every suggestion mechanically can produce an incoherent project. Ignoring difficult comments can leave the main barrier untouched.
Be especially careful with promises made by other people. A revision cannot quietly commit a community partner to more work, an employee to additional hours or participants to new data collection. Confirm changes through the appropriate organizational and ethical processes.
A hypothetical decision with real opportunity costs
Consider an entirely fictional community learning organization. No facts in this example describe an actual funder, applicant or Foundation program. Its unsuccessful application proposed a year-long pilot. Written feedback questioned recruitment, the proposed outcome measure and whether the work matched the funder’s geographic focus.
The team estimates 80 staff hours for a serious revision and values those hours internally at an assumed fully loaded $45 each. That is $3,600 of staff time. An additional $900 for specialist methodological advice would bring the planning cost to $4,500. These are invented assumptions, not recommended rates, allowable grant costs or a prediction of financial return.
The arithmetic helps make the decision visible. The same 80 hours might also be needed to complete a promised program evaluation. Management must decide whether it has capacity for both, whether work can be reassigned and what would otherwise be delayed.
The organization can probably repair its recruitment plan and improve its outcome measure. But suppose the published geographic rule excludes its intended service area. Spending the full $4,500 polishing an ineligible application would be difficult to justify.
A more useful response would be to retain the methodological improvements, document the fit problem and assess a different opportunity before committing the remaining time. If the geographic concern is ambiguous rather than explicit, a permitted clarification with the funder comes first.
This example also shows why a universal “always resubmit” policy is weak management. The quality of the next decision depends on the problem, the rules and the cost of responding.
Know what an NIH resubmission requires
NIH currently permits one A1 resubmission following an unfunded A0 application, within 37 months of the application it follows. The applicant must first receive the previous summary statement, and the funding opportunity must allow resubmissions. An unsuccessful A1 may be followed by a new application. Rules on overlapping applications still apply.
The resubmission includes an introduction summarizing substantial changes and responding to the critiques. It is generally limited to one page, with specified exceptions. NIH says changes should not be highlighted or otherwise marked within the application attachments. Changing activity codes or moving between a program announcement and an RFA generally requires a new application, subject to the stated exceptions. Check the current resubmission policy, the notice and the applicable application guide before choosing a route.
These are administrative limits, not a recommendation to use the next available deadline. A revision should be ready because the important work has been completed, not because the calendar makes another attempt possible.
Reserve appeals for the issue they can address
NIH’s March 2026 Grants Policy Statement, section 2.4.2, distinguishes a flawed review process from disagreement about scientific merit. Its allowable grounds concern reviewer bias, conflicts of interest, missing appropriate expertise or factual errors that could substantially alter the review outcome. Differences of scientific opinion alone do not qualify. The policy does not provide an appeal of the funding decision itself, and initial-review appeals are not accepted for RFA applications as stated in the notice.
Start with the program official. A formal appeal requires the applicant organization’s authorized representative’s concurrence and must meet the applicable timing requirements. The general policy specifies receipt after the summary statement and up to 30 calendar days after second-level review; confirm the institute’s submission deadline and current instructions promptly. NIH will not review the resubmission while an appeal on the original is pending. A successful appeal can lead to re-review of the original application without added material, not an automatic award.
For other funders, use their own procedure. Keep any challenge factual, specific and proportionate. Disappointment by itself does not identify a procedural flaw.
Make the next commitment explicit
Before authorizing another submission, ask whether the opportunity still fits, the central weaknesses can be addressed, the necessary evidence will be ready, and the organization can deliver the revised promise. Review the cost of applying alongside the cost of delivery. A grant that requires an unaffordable contribution or creates an unsustainable obligation may remain unsuitable even after the application improves.
There are several legitimate outcomes. Resubmit when the case is stronger and the route is permitted. Delay when essential evidence is not ready. Pursue another opportunity when the project is useful but the match is poor. Redesign when the review exposes a deeper problem. Close the proposal when continuing would divert resources from more valuable work.
Record the decision, its reasons and any condition that would justify revisiting it. If another funder is selected, build the new application around that funder’s criteria rather than merely changing the name on the old draft. Carry useful learning forward without carrying every old promise with it.
A rejection cannot guarantee a better result next time. It can, however, become a reason to ask better questions, protect scarce resources and make a more honest commitment. That is worthwhile progress even when the next decision is to go somewhere else.
For a possible collaboration on evidence-informed community initiatives or organizational learning, use Feel Worldwide Foundation’s partnership inquiry form. Describe the proposed purpose, roles, location and resources so that fit and capacity can be considered. An inquiry does not establish a grant-writing service, an award relationship or a promise of funding. To support the Foundation’s broader mission, visit the donation page and review the available purposes and terms before giving.
