Why do donors reject proposals?

Donors may reject proposals because the project does not fit their priorities, the applicant is not eligible, the budget is unclear, the evidence is weak, the objectives are vague, the format is not followed, or the organisation does not show enough capacity and accountability.

How should small community-based organisations approach donors?

Small organisations should start with clear documentation, local credibility, evidence of results, financial records, references, realistic budgets and local networks before approaching larger donors.

Should a proposal always follow the same format?

No. Donor instructions should come first. A generic structure is useful only when the donor has not provided a required format.

Programme management

Fundraising Documents for Humanitarian Programmes

Q: What should be included in a funding proposal?

A funding proposal normally includes a title page, summary, organisation background, needs assessment, objectives, activities, work plan, monitoring and evaluation, community participation, safeguarding, sustainability, budget and relevant appendices.

This page is about the paperwork behind fundraising: donor proposals, tenders, grant applications, project budgets, logframes, monitoring plans, supporting evidence and the documents that help an aid programme show it is credible, organised and ready to deliver.

Proposal Format Budget Guidance Submission Checklist

What is a humanitarian fundraising proposal?

A humanitarian fundraising proposal is a structured programme document that explains a need, the planned response, the people who will benefit, the activities, budget, evidence, risks, monitoring arrangements and the organisation’s capacity to deliver responsibly. It is not just a request for money. It is a case for trust.

Why fundraising documents matter

Community-based NGOs, local organisations and humanitarian teams often do important work with limited resources. Many are close to affected communities and understand the practical problems better than distant institutions. Yet raising funds can be difficult, especially for smaller organisations without long donor histories or large administrative teams.

Donors may be cautious about funding small organisations directly because of perceived accountability risks, limited references, difficulty transferring funds, tax and compliance issues, or the workload of managing many small grants. Larger organisations may appear easier for donors to assess, even when smaller organisations are closer to the people who need support.

This creates a difficult cycle. An organisation may need funds to improve financial systems, reporting, policies and documentation, but donors may want to see those systems before they release funds. Strong fundraising documents help break that cycle by showing the organisation’s purpose, evidence, capacity, controls and realistic plan.

Core idea: a good fundraising document makes the donor’s decision easier. It shows the need, the plan, the cost, the evidence, the risk controls and the result in a clear and credible way.

Basic fundraising concepts for programme teams

Successful fundraising is often an extension of successful networking, credibility and documentation. A proposal rarely works in isolation. It works best when it sits behind a relationship, a clear programme idea, evidence of need and a record of responsible work.

Start as locally as possible. Local businesses, employers, faith groups, professional associations, diaspora networks, community leaders and local institutions may be able to provide support, introductions, endorsements or in-kind help. Even small local support can make a project more credible to larger donors because it shows that the organisation is known and trusted.

For all donors, remember that relationships are not built by sending documents alone. When appropriate, arrange a meeting, call, briefing or short discussion. Be ready to explain how your work fits the donor’s priorities, what difference it makes, and why your organisation is well placed to do it.

Strong fundraising usually combines

A clear mission and specific aims.
Evidence of community need.
Local credibility and references.
Realistic project design.
Financial records and budget discipline.
Measurable outcomes and outputs.
Safeguarding and accountability controls.
A relationship with the donor or funder.

Before writing a proposal

Before opening a proposal template, make sure you understand your own organisation, the donor, the project, the evidence and the practical delivery requirements.

01Know yourself

Be clear about who you are, why your organisation exists, what you do, who you serve and what results you can show.

02Know the donor

Understand the donor’s priorities, eligibility rules, preferred formats, funding limits, timelines and reporting requirements.

03Know the need

Use assessment findings, local evidence, community input, data, maps, case examples and field observations to explain the problem.

04Know your capacity

Be honest about staff, systems, finance, safeguarding, logistics, partnerships and what your organisation can realistically deliver.

Do not start with the donor form. Start with the problem, the people affected, the solution, the evidence and the cost. Then fit the strongest version of that story into the donor’s format.

A practical proposal format

Always follow the donor’s instructions first. If the donor provides a format, use it exactly. If no format is given, the structure below can help you prepare a clear and professional proposal.

Title page

Include the organisation name, logo if available, project title, donor name, funding window or budget line, date, location, contact person and requested amount.

Executive summary

Summarise the project in one page or less: the problem, target group, location, planned response, expected results, total budget, amount requested and implementation period.

Organisation background

Explain your organisation’s history, legal status where relevant, experience, staff capacity, local relationships, previous work and why you are credible for this project.

Needs assessment and justification

Show the need your project will address. Explain who identified the problem, what evidence supports it, how affected people were consulted and what will happen if no support is provided.

Goals, objectives and outcomes

Explain the change you want to create. Objectives should be clear, realistic and measurable. Avoid vague promises that cannot be tracked.

Activities and methodology

Describe what you will do, where, when, how and by whom. Include expected outputs such as wells built, households supported, workshops held, staff trained or supplies distributed.

Monitoring, evaluation and learning

Explain how progress will be measured, who will collect information, how community feedback will be handled and how lessons will improve the programme.

Staffing and key personnel

List roles rather than only names. Explain responsibilities, reporting lines and the experience needed to deliver the project.

Community participation and capacity building

Explain how affected people, local organisations or community structures will be involved. If capacity building is included, explain why it is needed and what it will change.

Sustainability and exit

Explain what happens when the funding ends. Will activities continue? Who will maintain assets? How will knowledge, systems or local ownership remain?

Budgets and budget narratives

The budget is often where a good project becomes weak. Show costs clearly and explain them. A donor should be able to see what is being bought, why it is needed, how the cost was calculated and which costs the donor is being asked to fund.

Avoid vague headings such as “miscellaneous” unless the donor allows them and you can explain them. Separate direct project costs from administration, support costs, staffing, transport, supplies, monitoring and overhead. If the donor requires a specific currency, use it. If working locally, it may help to show local currency and donor currency where appropriate.

A budget narrative is not decoration. It explains the assumptions behind the figures: unit costs, quantities, time periods, exchange rates, procurement assumptions and why each cost is necessary.

Budget lines to make clear

Personnel and consultant costs.
Supplies, kits, materials or equipment.
Transport, fuel, vehicle hire and logistics.
Training, meetings and venue costs.
Monitoring, evaluation and data collection.
Communications and visibility where required.
Security, safeguarding and risk management costs.
Administration, audit and support costs.
Co-funding or in-kind contributions.

How donors read proposals

A donor is not only asking whether the cause is worthwhile. They are asking whether this organisation can deliver this project, with this budget, in this place, at this time, with acceptable risk.

Donor question	What your document should show	Common weakness
Does the project fit our priorities?	Clear alignment with donor themes, geography, target groups and funding rules.	Generic proposal sent to the wrong donor.
Is the need real and well evidenced?	Assessment data, community input, local knowledge, relevant context and practical examples.	Emotional claims without evidence.
Is the plan realistic?	Activities, timeline, staffing, logistics and outputs that match the budget and capacity.	Too many activities for the time and money available.
Can the organisation manage funds?	Financial controls, records, authorisation, audit, procurement and reporting arrangements.	Unclear budget or weak accounting evidence.
How will results be measured?	Indicators, monitoring plan, feedback mechanisms and learning process.	Objectives that cannot be measured.
What are the risks?	Security, safeguarding, delivery, finance, access, procurement and mitigation plans.	No serious discussion of risk.

Supporting documents and appendices

Attach only documents that help the donor understand the proposal or assess the organisation. Too many weak appendices can make the submission harder to review.

Useful appendices may include a work plan, schedule, logframe, map, organisation chart, letters of support, registration documents, annual accounts, audit reports, relevant policies, previous project summaries, technical designs, procurement plans or staff CVs.

Do not overload the donor. Appendices should support the case, not bury it. Every attachment should have a reason to exist.

Useful supporting documents

Work plan and implementation schedule.
Logframe or results framework.
Detailed project budget and budget narrative.
Map of the project area.
Needs assessment or baseline summary.
Letters of support from partners or authorities.
Organisation profile and structure chart.
Safeguarding, finance and procurement policies.
Previous donor-funded project summaries.
Technical designs or specifications.

Submission checklist

Before sending a proposal, check the basics slowly. Many proposals are weakened by avoidable mistakes: missing signatures, wrong formats, inconsistent budgets, unclear dates or attachments that do not match the text.

Donor eligibilityThe organisation, country, theme, budget size and project type fit the donor’s requirements.

Format followedThe donor template, page limits, font rules, naming conventions and submission instructions have been followed.

Budget consistentThe figures in the summary, main text, budget and budget narrative all match.

Need evidencedThe proposal shows why the project is needed and how affected people or local stakeholders informed the design.

Objectives clearThe project has realistic goals, measurable outputs and a clear connection between activities and outcomes.

Risks addressedSecurity, safeguarding, financial, access, procurement, delivery and reputational risks are acknowledged and managed.

Attachments completeOnly useful appendices are included, named properly and referred to in the proposal where needed.

Authorisation completeSignatures, board approval, partner letters or legal documents are included if required.

Final review: ask someone outside the project team to read the summary, budget and activities. If they cannot understand the project quickly, the donor may struggle too.

Common proposal mistakes

Fundraising documents fail when they make the donor work too hard. A proposal should not hide the project behind jargon, vague benefits or unexplained costs.

Writing about the organisation more than the people affected.
Using vague phrases instead of clear activities and outputs.
Ignoring the donor’s format or eligibility rules.
Including a budget that does not match the project plan.
Promising long-term impact without a way to measure it.
Leaving safeguarding, accountability or risk until the end.
Submitting the same generic proposal to every donor.

What strong documents do

Strong fundraising documents show judgement. They are clear about need, honest about risk, realistic about capacity, careful with budgets and respectful towards the people the project is meant to serve.

A donor should finish reading with confidence that the organisation understands the problem, has designed a realistic response and can account for the funds responsibly.

Related programme and career resources

Fundraising document FAQs

What is a humanitarian fundraising proposal?

A humanitarian fundraising proposal is a structured document that explains a need, planned response, target group, activities, budget, evidence, risks, monitoring plan and organisational capacity.

What should be included in a donor proposal?

A donor proposal normally includes a title page, summary, organisation background, needs assessment, objectives, activities, work plan, monitoring and evaluation, community participation, safeguarding, sustainability, budget and appendices.

Should every proposal follow the same format?

No. The donor’s instructions come first. A generic format is useful only where the donor has not provided a required template.

Why are small organisations often rejected by donors?

Small organisations may be rejected because of eligibility rules, weak documentation, limited references, unclear financial systems, insufficient evidence, or because donors prefer to manage fewer larger grants. Good documentation can reduce, but not remove, these barriers.

What makes a proposal more credible?

Clear evidence, realistic activities, local participation, accurate budgets, financial controls, relevant experience, safeguarding, monitoring plans and honest risk management all strengthen credibility.