How to write a grant application

A grant application is a persuasive document with a strict job: convince a funder that your project matters, that you can do it, and that their money will make a difference. It is judged by people who read many of them, so honesty and clarity win.

What it is

A grant application asks a funder to give you money for a specific project. It explains the need, your plan, your ability to deliver, and how you will use the funds — and it must follow the funder's guidelines closely.

How to write it

Follow the guidelines exactly. Every funder has its own format, word limits and questions. A grant that ignores the instructions is often rejected before the content is even read.

State the need clearly. Explain the problem you are solving, who it affects, and why it matters. Use real evidence — data, research, or your own experience.

Describe a specific project, not a vague goal. "We want to help writers" is vague. "We will run a twelve-week mentorship for fifty unpublished writers, with a monthly paid-opportunities newsletter" is specific and credible.

Show you can deliver. Explain your experience, your team, and any track record. A funder needs to believe you can actually do what you propose.

Give a realistic budget and plan. Show what the money will be spent on and a timeline. Be honest and reasonable; an inflated budget or a fantasy plan undercuts your credibility.

Show the impact. Explain what will change because of the funding — and how you will measure it. Funders want to know their money works.

Be honest, not inflated. Do not overclaim or promise what you cannot deliver. Honesty and realism are what make a funder trust you.

The structure to copy

1. The need — the problem and who it affects, with evidence.
2. Your project — what you will do, concretely.
3. Your capability — why you are the right one to do it.
4. The budget and plan — what it costs and the timeline.
5. The impact — what changes and how you measure it.
6. The ask — the amount and how it will be used.

Common mistakes

Ignoring the guidelines. A vague project or vague need. Over-claiming. No realistic budget. No plan or timeline. Not showing impact. Writing a generic statement about "helping people" rather than a concrete project.

Practical tips

• Read the guidelines twice before you start.
• Be concrete: numbers, names, methods.
• Be realistic — a funder trusts honesty over hype.

Checklist

• I followed the funder's guidelines exactly.
• I stated the need with real evidence.
• My project is specific and concrete.
• I showed I can deliver.
• My budget and plan are realistic.
• I showed the impact and how I will measure it.