How to Request Feedback After a Grant Rejection and Rebuild Your Application in 5 Steps

Step 1: Follow the 48-Hour Protocol to Process the Rejection

The moment you open that rejection email, your instinct will be to fire off a response. Maybe to ask why. Maybe to argue your case. Do not hit send. What you do in the next 48 hours will determine whether this rejection becomes a learning opportunity or a wasted experience.

Give yourself permission to stop

Put the laptop down. Close the email. Step away entirely. The 48-hour protocol exists because you need to let the emotional spike pass before you do anything strategic. Feel the disappointment-that's human. Acknowledge it. Then release it. You are not allowed to contact the funder until you can do so with genuine gratitude, not grievance.

Reframe rejection as data

Here is the number that should take the sting out: the national success rate for well-targeted grant proposals sits at 10-30%-and some sources place it as low as 10-20%. That means 70% to 90% of strong, well-written applications get rejected. The most common cause is not poor writing but poor fit with the funder's priorities. Rejection is a data point, not a verdict. It tells you something about alignment, strategy, or timing. It does not tell you your organisation lacks value.

What to do during the buffer

Use the two days to process, not to act. Walk. Talk to a colleague. Jot down your initial reactions in a private note-then set it aside. Do not draft a reply. Do not circulate the rejection internally with commentary yet. Let your mind settle. When the 48 hours are up, you will be ready to approach the funder as a professional, not as someone still smarting from the blow.

Step 2: Professionally Request Feedback from the Funder

Once you’ve let the initial disappointment settle, it’s time to make a move that separates professionals from amateurs: asking for feedback. Most organisations skip this step entirely. Don’t be one of them.

How to Ask - The Right Way

Your message needs two things: gratitude first, then a clear request. Never apologise for applying. Never argue. Here’s a template you can adapt:

Subject: Feedback request - [Proposal Title] - [Your Organisation]

Dear [Program Officer’s Name],

Thank you for your time reviewing our recent proposal. We appreciate the consideration.

I’m wondering if you would be able to share any feedback about our application? Is there anything you recommend doing differently for future submissions?

If scoring sheets or reviewer comments are available, we’d be grateful for those too.

Thank you for your support.

[Your Name] | [Title] [Your Organisation]

Send this within 48 hours of receiving the rejection. That window signals professionalism, not desperation.

What to Ask For

Be specific. Request:

Some funders won’t provide detailed feedback. High-volume programmes in particular may simply lack capacity. That’s okay. The act of asking still does something important: it builds a relationship. You become a recognisable name, someone professional and coachable. That can pay off on the next submission.

If a funder does respond with detailed notes, treat that as gold. They’ve invested time in your growth. Thank them warmly, implement their suggestions, and let them know when you do. That turns a rejection into the start of a mentoring relationship.

Step 3: Analyse the Rejection with an Internal Audit

You’ve requested feedback and maybe received a few comments - or you haven’t heard back at all. Either way, the next move is yours. Run a structured internal audit on the application. No guesswork. No gut feelings. Just honest answers.

The Self-Checklist

Work through these five questions. Be brutally honest.

1. Was your mission truly aligned with the funder? Poor fit is the single most common reason grants get rejected - not bad writing, not weak outcomes. Did you match the funder’s stated priorities, geography, and grant size? Or did you stretch to fit?

2. Did you have prior contact with the program officer? Applications sent cold perform worse. Did you speak to the program officer before submitting? If not, that silence itself is a clue.

3. Did you comply with every rule? For government grants especially, compliance is the #1 killer. Check page limits, formatting, attachments, deadlines. One wrong PDF can sink you.

4. Was the narrative logical and clean? Read the proposal aloud. Does the need statement lead naturally to your approach? Does the budget match the activities described? Are there typos or unclear sections?

5. Did the budget align with the narrative? A common red flag: the budget lists expenses that the narrative never explains. Check for gaps or mismatches.

Track Every Rejection

Create a master spreadsheet (Google Sheets works fine). Record each application with:

Over time, patterns emerge. You might discover: “Three funders questioned our budget clarity” or “We keep getting rejected for poor fit with education foundations.” That’s data you can act on.

Don’t collect rejection letters in a folder and forget them. Turn them into a feedback system. Every “no” becomes a signal that points toward the next “yes.”

Step 4: Rebuild the Application Using Feedback

Now the real work begins. You've processed the rejection, requested feedback, and run your internal audit. You have a list of problems - maybe a score sheet, maybe a paragraph from a program officer, maybe just your own honest notes. Time to turn those findings into a stronger application.

Address feedback point-by-point

Treat every piece of feedback as a direct instruction. If a reviewer said your project timeline was vague, rewrite it - include specific milestones with dates and deliverables. If they flagged a mismatch between your budget and narrative, reconcile every line item. In your resubmission, you can acknowledge the change directly: "Based on previous reviewer comments, we have added a detailed Gantt chart and connected each activity to a budget line." This signals you listened and improved.

Update your data and restructure weak sections

Old statistics weaken your case. Refresh all numbers, citations, and sources for the new cycle. If the programme officer hinted your Statement of Need lacked depth, consider restructuring it entirely - lead with a stronger data point or a more vivid community testimony. If the logic chain from problem → activity → outcome was unclear, rebuild the flow section by section.

Bring in an external reviewer

After three rounds of edits, you'll miss your own blind spots. Ask a colleague who hasn't seen the proposal - or better yet, hire a grant consultant - to read it cold. They'll spot gaps you've looked past, like an unstated assumption or a missing connection in your evaluation plan. Their fresh eyes catch what yours no longer can.

Check the funder's latest guidelines before resubmitting

Funders shift priorities between cycles. A topic they prioritised six months ago may now be secondary. Read the new RFP as if you've never seen it before. If your application doesn't match their current focus, no amount of polishing will save it. Adjust your narrative to align with what they're asking for today - not what they asked for last time.

Do not resubmit the same document

This is the most common mistake - and the most avoidable. Unless the funder explicitly invited you to resubmit with minor tweaks, you must rebuild. Treat the rejection as data, not defeat. Every revision makes your next application sharper.

Step 5: Decide Whether to Re-Apply or Move On

Not every rejection deserves a second attempt. Some do. Some don’t. The smart move is to decide with your head, not your pride. Use this simple decision tree:

If the funder explicitly invited you to re-apply - Move them to the top of your re-submission list. A direct invitation signals interest, assuming you address their concerns. Prepare your revised application for the next cycle and make sure every change responds point-by-point to the feedback you received.

If you have a solid relationship but no invitation - Don’t rush a re-submission. Instead, schedule a brief call with the program officer to discuss where your proposal fell short. Send them a short impact report or a success story from the current year to stay on their radar. Funders remember organisations that stay engaged, not those who disappear after a rejection.

If you received no feedback and have no relationship - Deprioritise this funder. They’ve shown you’re not a priority for them either. Monitor their guidelines for changes, but spend your energy on prospects where you have a stronger connection or clearer alignment.

If the same weakness appears across rejections - Stop applying and fix the problem. If two or three different funders say your programme isn’t developed enough or your budget lacks clarity, no amount of rewriting will help. Pause grant writing, strengthen the underlying programme, and return when you have something stronger to pitch.

What you must never do - Re-submit the exact same proposal to the same funder. Even if they don’t remember the details, the odds are stacked against you. Unless they explicitly ask for the same document, you must revise it.

And if this funder really isn’t the right fit, broaden your search. Explore other foundations, corporate giving programmes, government grants, or even smaller entry-level awards from the same institution. A no from one door is often a redirection to a better one.

Grant funding for charities

GrantGunner finds charity grants and drafts the application from your own documents. See charity grants

More from the GrantGunner blog