What to do after a proposal is rejected
A calm, practical routine for the days after a donor says no: thank them, ask one clear question, log the lesson and decide where to apply next.
Short answer
Take a day, then act. Thank the donor, accept the decision, and ask one or two specific questions: was it eligibility, fit or available funds, and may you apply again. Write the answer in a rejection log with what you think happened and what will change. Reuse your text, then move to the next funder.
Key points
- Rejection is normal. It is not a verdict on your organisation.
- Thank the donor and ask one clear question, once, in writing.
- Do not argue with the decision. It can cost you the relationship.
- Keep a rejection log. Patterns across several rejections teach more than one reply.
- Reuse your proposal text and go back to your donor list.
Why is rejection so common?
Most proposals are not funded. A donor may receive far more good applications than it can pay for, so a rejection often says nothing about quality. The reason can be eligibility, fit with this round's priorities, or simply a lack of money.
This is why strong organisations plan for rejection. They keep several applications moving at once, and they treat each "no" as information. A team that expects rejection recovers faster and learns more.
What should you do in the first 48 hours?
- Pause before replying. Read the message once and wait a day. A quick, upset reply can damage a relationship you may need later.
- Tell your team. Share the news clearly and kindly, and thank the people who worked on the proposal.
- Save everything. Store the final proposal, budget, annexes and the donor's message in one folder.
- Check for simple causes. Was a document missing? Was the file unreadable? Did you miss a requirement? These happen, and you can fix them next time.
How do you ask a donor for feedback?
Ask once, in writing, within a week or two. Keep it short and polite. A good message has four parts:
- Thank them for reviewing your proposal.
- Accept the decision without argument.
- Ask one specific question. The most useful is whether the proposal failed on eligibility, on fit with the programme, or only on available funds. Each answer leads to a different next step.
- Ask about the future. Ask whether you may apply again, and whether the donor can suggest other funders who may fit.
If the answer is short, accept it. Chasing a longer reason rarely produces one, and many donors do not have a detailed reason recorded. If you cannot reach a person, keep the lessons you can draw from the call's criteria.
What should you put in a rejection log?
Write three short lines in your pipeline or tracker for each rejection while the facts are fresh:
| Line | Question | Example |
|---|---|---|
| What the donor said | The exact reason, if given | "Many strong applications; limited funds" |
| What you think happened | Your own honest reading | "Our budget narrative was weak; target group very broad" |
| What changes next time | One action | "Ask a finance colleague to review the budget narrative" |
The third line is the point. One entry proves little. After five or six entries, you can see whether you are being turned down on fit, on eligibility, on quality or on luck. For example, if two donors in a row raise governance or finance, the next task is not another proposal. It is to strengthen those systems.
How do you reuse the work?
A rejected proposal is still valuable:
- Reuse text. Your problem statement, approach and results can be adapted for another donor. Keep your problem statement and results ready as standard blocks.
- Check your budget. Reuse the cost structure, but update it for the next donor's rules.
- Adapt, do not copy. Match each new proposal to the next donor's priorities and language.
- Update your profile. Add anything the process taught you about your own strengths and gaps.
Where do you go next?
Return to your donor list and choose the next best fit. This is a better use of a hard afternoon than rewriting the proposal that was just refused. Use donor mapping to find funders whose priorities match your work, and build a proposal pipeline and calendar so that one "no" does not stop your income plan.
Keep the relationship warm. Send the donor a short update on your work a few months later, share a result, or invite them to an event. Donors remember organisations that stay professional after a rejection.
What if rejections keep coming?
If you hear no several times in a row, step back from writing and look at the pattern:
- Fit: are you applying to donors whose priorities really match yours?
- Eligibility: are you meeting the basic rules, such as registration, track record and budget range?
- Capacity: do your finance, safeguarding and reporting systems meet donor expectations?
- Quality: is the proposal clear, consistent and specific?
Ask a trusted peer or a trainer to review one rejected proposal against the call. A fresh reader sees gaps that the writing team cannot.
How EMPO can help
EMPO is a trusted training and consultancy provider based in Yangon and one of Myanmar's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We offer proposal writing training and support, in English and Burmese, online or in person across Myanmar. If you want a fresh review of a proposal, see our services or contact us.
Sources
- What to do after your grant proposal rejection — Candid, 2023
- Rejected funding application: ask for feedback — CharityIQ, 2026
Questions people ask
Should we appeal a rejection?
Usually no. Most funders do not offer an appeal for a normal funding decision, and arguing can harm the relationship. If you believe a clear procedural error happened, such as a lost attachment, raise it politely and quickly.
What if the donor gives no feedback?
That is common. Thin feedback is normal. Still use the proposal: check it against the call's criteria yourself, and ask a colleague or peer organisation to review it with fresh eyes.
When can we apply to the same donor again?
Ask. Some donors set a waiting period, some welcome a new application, and some tell you what would need to change. Check the donor's guidelines and record the answer in your pipeline.
