Rejected Again? How to Make Your Next Grant Application Stronger

A rejected grant application can feel personal, especially when your organisation is doing important work and the need in your community is clear. But in most cases, rejection is not a judgement on your mission. It is a decision made under pressure, against specific criteria, with many applications competing for limited funds.

The useful question is not only “Why were we rejected?” but “What made it easy for a reviewer to say no?” A strong proposal reduces doubt. It shows fit, clarity, credibility and value for money. Whether you are an NGO in Nigeria, a social enterprise in Kenya, a community-based organisation in Uganda, an SME or a research team, the same principle applies: make the reviewer confident that you understand the problem and can deliver the work responsibly.

1. The application did not clearly fit the funder’s priorities

One of the most common reasons for rejection is poor fit. An organisation may be eligible on paper, but the proposed project may not match the funder’s theme, geography, target group, type of intervention or expected results. Reviewers rarely have time to “interpret” your fit. If they cannot see the connection quickly, the proposal becomes easy to score low.

For example, if a call is focused on improving livelihoods for young women, an application about general youth entrepreneurship may be too broad unless it explains how young women are specifically reached, what barriers they face and how the project is designed around them. Similarly, a community health project may be relevant to a broad development agenda, but not to a call that is specifically asking for policy advocacy, systems strengthening or innovation.

To avoid this, create a simple alignment check before you write. Copy the funder’s stated priorities into a table and write one sentence showing how your project responds to each one. If you struggle to complete the table honestly, the opportunity may not be the right one, or the project design may need adjusting.

• Use the funder’s language naturally, without copying whole sections.
• State the target group, location and problem early in the proposal.
• Avoid forcing your usual project into a call that is asking for something different.
• If only one part of your work fits, apply with that focused component, not the whole organisation’s wish list.

2. The problem statement was too broad or unsupported

Many proposals are rejected because the problem is described in general terms but not made specific enough for action. Statements such as “poverty is high”, “youth unemployment is a major challenge” or “women lack opportunities” may be true, but they do not tell the reviewer exactly what gap the project will address, who is affected, why the issue persists and what will change through the grant.

A stronger problem statement narrows the issue. Instead of saying that farmers need support, explain which farmers, in which communities, facing which barriers. Is the issue poor access to quality inputs, weak market linkages, climate-related crop losses, lack of storage, limited finance, or low technical knowledge? Each problem leads to a different project design.

You do not need to overload the application with data. Use a balanced mix of credible evidence: community consultations, organisational experience, needs assessments, programme records, government or sector reports where available, and short examples from the field. The key is to show that the project is based on reality, not assumptions.

• Define the problem in one clear sentence before expanding it.
• Separate symptoms from root causes.
• Show why your target group is particularly affected.
• Avoid dramatic language that is not backed by evidence.
• Explain what will happen if the problem remains unaddressed.

3. The proposed solution felt vague, oversized or disconnected

A proposal can identify a real problem and still fail because the solution is unclear. Reviewers look for a logical chain: problem, objective, activities, outputs, outcomes and budget. If the application jumps from a big problem to a list of activities without explaining how those activities create change, the project may appear weak.

Another common mistake is trying to do too much. A small grant cannot realistically train thousands of people, build platforms, conduct research, change policy, provide equipment, run media campaigns and establish new offices at the same time. Ambition is good, but an overstretched project raises concerns about delivery capacity.

Keep the project tight. If your goal is to support adolescent girls to remain in school, the activities might include mentoring, parent engagement, teacher coordination and referral support. Do not add unrelated business training, environmental clubs and digital literacy unless they are essential to the outcome and resourced properly.

• Write one main objective and a few specific outcomes.
• Check that every activity contributes directly to an outcome.
• Remove attractive but non-essential activities.
• Explain your delivery approach, not just what you will do.
• Show who will do the work and what experience they bring.

4. The budget weakened confidence in the proposal

Budgets often reveal whether a project has been properly thought through. A reviewer may like the idea but lose confidence if the budget is unrealistic, unclear or inconsistent with the narrative. Common issues include missing costs, unexplained lump sums, inflated-looking items, weak justification for staff time, or activities in the narrative that have no budget line.

A budget should tell the same story as the proposal. If you plan to conduct community workshops across several districts, the budget should reflect venue, facilitation, transport, materials, participant support where appropriate and staff time. If the budget includes equipment, explain why it is necessary for the project and how it will be managed after purchase.

Value for money does not always mean choosing the cheapest option. It means the cost is reasonable for the result. For organisations in Nigeria, Kenya and Uganda, it is also important to consider local realities such as transport distances, security, translation, mobile data, accessibility and field supervision. Under-budgeting these items can make the proposal look neat but impractical.

• Match each budget line to a project activity.
• Avoid vague lines such as “miscellaneous” or “project support” without explanation.
• Check calculations, units and totals carefully.
• Include realistic operational costs; do not hide them.
• Use a budget narrative to explain items that may not be obvious.

5. The application created doubts about organisational capacity

Funders do not only assess the project; they assess whether the applicant can manage funds, people, risks and reporting. Applications are often rejected when the organisation does not show enough evidence of capacity. This can happen even when the team is experienced, simply because the proposal fails to present that experience clearly.

Capacity is not only about being a large organisation. A smaller community-based group can be credible if it shows strong local presence, relevant experience, clear governance, basic financial controls, partnerships and practical systems for monitoring work. If you have delivered similar projects, say so briefly and specifically. If you are new to a type of grant, show what support structures or partnerships will reduce risk.

Be honest about gaps. Reviewers understand that organisations grow. What creates concern is when an application pretends that capacity challenges do not exist. If you need technical support, safeguarding training, financial management strengthening or a specialised partner, include it in the design.

• Add short examples of past work related to the proposed project.
• Describe roles for key staff, volunteers, board members or partners.
• Show how funds will be approved, tracked and reported.
• Mention relevant policies, such as safeguarding, finance and procurement, if required.
• Do not exaggerate experience; make your real strengths visible.

6. The proposal was hard to review

Sometimes applications are rejected not because the idea is poor, but because the proposal is difficult to read, incomplete or non-compliant. Reviewers may be assessing many submissions against a scoring template. If your answers are scattered, too long, full of jargon or missing required information, you make their work harder.

Clarity is a competitive advantage. Use headings that match the application questions. Answer the question asked before adding context. Keep sentences direct. Define technical terms. If there is a word limit, treat it as part of the assessment, not a suggestion. If attachments are required, label them clearly and ensure they are the correct versions.

Build in a review process before submission. Ask one person who understands the project to check accuracy, and another person who is less familiar with the work to check clarity. If they cannot explain the project back to you after reading it, the proposal needs revision.

• Follow formatting, naming and submission instructions exactly.
• Complete every required section, even if the answer is brief.
• Use plain English instead of internal organisational language.
• Cross-check names, dates, locations and figures across all documents.
• Submit early enough to avoid portal, internet or power problems.

Key takeaway

Grant rejection is part of the funding journey, but repeated rejection should prompt a careful diagnosis. Look for patterns: weak fit, broad problem statements, unclear logic, unrealistic budgets, hidden capacity gaps or poor presentation. Before your next application, review the proposal as a stranger would. Is the need specific? Is the solution practical? Does the budget match the work? Can the organisation deliver and account for the funds? You cannot control how competitive a call will be, and no proposal can guarantee funding. But you can make it much easier for reviewers to understand your value and much harder for them to dismiss your application for avoidable reasons.