Requesting and Using Feedback

A rejection letter tells you the outcome. Feedback tells you the why. Not every funder provides it, and not every funder will respond to a feedback request. But when you can get it, funder feedback is some of the most valuable intelligence available to your grant program. The challenge is asking in a way that actually gets a response — and then using what you hear.

When and How to Ask

Timing and tone matter. A feedback request that feels defensive, entitled, or premature will get ignored. One that feels genuine and professional often gets a thoughtful response.

Wait at least two weeks after the rejection

Give the funder time to close out the review cycle. Immediate requests can feel reactive. A deliberate pause signals that you've processed the decision and are asking from a place of genuine learning.

Keep the request brief and specific

Don't write a long email. Three to four sentences: acknowledge the decision gracefully, express that you'd value their perspective, and ask a specific question. 'Were there areas where our proposal could have been strengthened?' is better than 'Can you tell us why we weren't funded?'

Make it easy to respond

Offer a brief phone call or say that even a few sentences by email would be helpful. The lower the effort barrier, the more likely you'll get a response.

Thank them regardless

Whether they provide feedback or not, thank them for their time and consideration. This is a relationship, not a complaint process.

Watch out

Some funders have policies against providing individual feedback. Government grant programs in particular may only release reviewer scores without commentary. Don’t push back if a funder declines your request — accept it gracefully and look for other ways to assess your application.

What Funder Feedback Typically Looks Like

When you do get feedback, it usually falls into a few categories:

Reviewer scores or rankings

Government grants often provide numerical scores by criteria. These are gold — they tell you exactly which sections were strong and which were weak. A low score on 'organizational capacity' means something different from a low score on 'project design.'

General thematic comments

Foundation program officers might say something like 'The proposal didn't clearly articulate the connection between activities and outcomes.' This is directional — it tells you what to strengthen without a specific prescription.

Alignment feedback

'The project was outside our current funding priorities' or 'We funded organizations with a stronger track record in this area.' This is fit information, not quality feedback — and it's just as valuable.

No response

Silence is also data. It may mean the funder doesn't provide feedback, they're too busy, or the rejection was routine. Don't read too much into it, but don't ask a second time either.

Turning Feedback Into Action

Getting feedback is only useful if you systematically apply it. Most organizations read the feedback, nod, and file it away. The disciplined ones change their process.

Write down the feedback immediately

Record it verbatim, not your interpretation of it. Your interpretation may soften the message or miss the point. Keep the funder's actual words.

Look for patterns across rejections

One reviewer's opinion is an anecdote. Three reviewers saying the same thing is a pattern. Cross-reference feedback from different funders to identify recurring weaknesses.

Assign specific changes to specific proposals

Don't just resolve to 'write better proposals.' Identify the exact section, the exact weakness, and the exact revision. 'Strengthen the evaluation section with measurable indicators and a data collection timeline' is actionable. 'Improve the proposal' is not.

Test the change

Apply the revision to your next proposal and see if it scores better. If multiple reviewers flagged your evaluation plan, revise it and track whether the next application scores higher in that area.

Pro tip

If you work with a team, hold a brief “feedback review” after each rejection where you discuss what was said, what patterns you see, and what specific changes you’ll make. This turns individual feedback into organizational learning.

Funder feedback is a gift, even when it’s hard to hear. The organizations that improve fastest aren’t the ones with the most talent — they’re the ones with the shortest feedback loops. Every piece of feedback you receive and act on makes your next proposal measurably stronger.

In Grantable

In Grantable, you can store funder feedback alongside the proposal it relates to, making it easy to reference when revising for the next cycle — instead of searching through old emails.

Check your understanding

You receive reviewer feedback on a federal grant application. Two of three reviewers gave high marks overall but noted that your evaluation plan lacked specific data collection methods. The third reviewer gave a low score across all categories. How should you prioritize this feedback?

Key Takeaways

Wait two weeks after rejection, then ask for feedback with a brief, specific, gracious request
Record feedback verbatim — your interpretation may soften or miss the point
Look for patterns across multiple rejections, not just one funder's opinion
Turn feedback into specific, actionable revisions and test whether they improve results

Next Lesson

You have the feedback. The question is: should you apply again, or move on? Next, we’ll cover the framework for deciding when to reapply and when to redirect your energy.