How to Write a Grant Proposal (Free Template)

What Is a Grant Proposal?

A grant proposal is a formal request for funding submitted to a foundation, government agency, or corporate giving programme. Unlike a business proposal, you are not selling to someone who wants your service — you are competing for a fixed pool of money against applicants who are often just as deserving as you are. The proposal is the only thing standing between your work and their decision.

That competitive frame changes how you should write. A commercial proposal can win on charm. A grant proposal wins on fit, clarity, and the reviewer's confidence that you will actually deliver what you describe and be able to prove it afterwards.

Why Grant Proposals Get Rejected

Program officers read a lot of applications, often quickly, often against a scoring rubric. The most common reasons a good organisation loses:

• Wrong funder. The single biggest waste of effort. If the foundation funds early-childhood literacy and you run a youth sports programme, no amount of writing saves it. Read what they actually funded last cycle before you write a word.
• The need is described with adjectives, not evidence. "There is a desperate need" is not a need statement. A cited figure about your specific service area is.
• Need and methods do not connect. The proposal describes a transport problem and then requests funding for a website.
• Unmeasurable outcomes. "Raise awareness" cannot be evaluated, so it cannot be funded by anyone who has to report upward.
• The budget contradicts the narrative. You promise to serve 200 people and the budget only staffs for 40.
• Guidelines ignored. Page limits, fonts, attachment lists, and deadlines are a competence test. Failing it is an easy way for a reviewer to shorten the pile.

Most grant writing advice focuses on prose. Most grant rejections are structural — wrong funder, unmeasurable outcomes, or a budget that does not match the promise. Fix those three and average writing will still get funded.

Section-by-Section Breakdown

Funders vary, and their guidelines always win over any generic outline. That said, nearly every application asks for these components under some name:

Our free grant proposal template follows this order with prompts under each heading, so you can draft against a structure instead of a blank page. If you need related documents — a partnership letter, a project proposal for a co-applicant — the full proposals template library covers those too. Everything is free, no sign-up, no watermark on the export.

Writing the Statement of Need

This is where proposals are won and lost. Three principles:

1. Be local and specific. National statistics establish context; data about your county, neighbourhood, or population makes the case. A reviewer funding your area wants to see your area.
2. Cite honestly. Use public data you can point to — census figures, health department reports, school district records, your own service records. Never estimate a number and present it as research. If your own intake data is the source, say so plainly: it is legitimate evidence and reviewers respect the transparency.
3. Describe a gap, not a tragedy. The need is not that people are suffering. The need is that a specific service is missing or insufficient, and you can name what fills it.

One useful test: the need statement should make the reader think "so something should be done about that" before you have described your programme. If you have to introduce your solution for the problem to make sense, the problem is not yet on the page.

Presenting the Budget

Reviewers often go to the budget second, right after the summary. It is the fastest way to tell whether a proposal is serious. Make the numbers legible and defend every line:

Do not deflate the budget to look modest. An underfunded plan reads as a plan that will fail, and experienced reviewers have watched it happen. If the funder's maximum is below what the work costs, say what the grant covers and name the other sources — that is a partnership, not a weakness.

Step-by-Step Process

1. Research the funder properly. Read their guidelines, their recently funded list, and their reporting requirements. Confirm you are eligible before anything else.
2. Make contact if they allow it. Many program officers take a short call. A ten-minute conversation can save you forty hours on a proposal that was never going to fit.
3. Build the budget before the narrative. The numbers discipline the promises.
4. Draft the need statement and evaluation plan next. They are the hardest sections; do them while you are fresh.
5. Write the project description to bridge them. Every activity should trace back to a stated need and forward to a measured outcome.
6. Write the executive summary last. It is a summary, not an introduction.
7. Check the guidelines line by line. Page limits, margins, attachments, submission portal, deadline time zone.
8. Have someone outside the programme read it. If they cannot explain your project back to you, a reviewer will not either.

Follow-Up and Reporting

After submission, respect the process. If the funder states a decision timeline, wait it out. A short, courteous confirmation of receipt is fine; chasing is not.

Subject: [Organisation] — application submitted for [Program Name]

Dear [Program Officer],

We submitted our application for [Program] on [date] via [portal].
Reference: [number].

If anything is missing or you need clarification on any section,
I am glad to provide it. I understand decisions are expected
around [their stated date] and will wait to hear from you.

Thank you for considering the request.

[Name], [Title]

If you are declined, ask for feedback. Many funders will share reviewer comments, and some invite strong near-misses to reapply. That feedback is the cheapest grant-writing education available. If you are funded, treat the reporting requirements as seriously as the application — the next grant from that funder is decided by how well you handled this one.

Common Mistakes to Avoid

• Recycling a proposal without re-tailoring it. Reviewers can tell, and mission-fit language is not decoration.
• Jargon and acronyms. Assume an intelligent reader who does not work in your field.
• Confusing goals with objectives. A goal is the direction; an objective is measurable and time-bound.
• Passive, hedged language. "It is hoped that participants may benefit" tells a reviewer you do not believe it either.
• Ignoring sustainability. Funders do not want to be your permanent budget line.
• Submitting at the deadline. Portals fail. Submit a day early.

Grant writing rewards preparation far more than eloquence. Pick the right funder, build an honest budget, connect the need to a measurable outcome, and write it plainly. Start from the grant proposal template and spend your saved time on the research instead of the formatting.