Most grant applications are not rejected because the writing is bad. They are rejected because the thinking behind the writing is unclear. This guide walks through how to write a grant application that wins — not with tricks or magic phrases, but by understanding what an assessor is actually doing when they read your form, and giving them exactly what they need to say yes.
Before a single word goes on the form, one reframe changes everything: you are not writing to impress. You are writing to be assessed. Somewhere, a real person — often a volunteer or an overworked grants officer with forty applications in their queue — will read your answers against a scoring framework. Winning applications make that person's job easy. Losing applications, however passionate, make it hard.
Not sure how fundable your project really is?
Take the free 3-minute scorecard: How Fundable Is Your Social Impact Idea?
Before you write: the three-question test
The strongest applications are decided before the writing starts. Run your project through three questions first:
- Is this funder genuinely a fit? Read their priorities, their last year of grants and their exclusions. If you have to stretch your project to fit their language, stop — misaligned applications lose, and they cost you weeks. (If your funder shortlist is thin, start with where to find grant funding in the UK.)
- Can I explain the project in one sentence? Who you help, what you do, and what changes as a result. If that sentence doesn't exist yet, the application isn't ready — funders consistently back the projects that are easiest to explain.
- Do the basics stand up? Governing document, bank account, safeguarding policy, unconnected trustees or directors, and accounts or a budget that add up. Assessors check these first, and no writing quality survives a failed eligibility check.
Think like the assessor, not the applicant
An assessor reads your application with two questions running in the background: will this project deliver the change we exist to fund? and can this organisation be trusted to deliver it? Every answer you write should serve one of those two questions. Most applications over-invest in passion and under-invest in trust — yet trust is where decisions are actually made, because funders don't reject ideas, they reject risk.
Your application is not competing against a blank page. It is competing against forty others on the same desk. Clarity is not a style choice — it is a competitive advantage.
The core sections, and how to win each one
The need: evidence, not adjectives
Weak applications describe need with adjectives — "desperate", "vulnerable", "crisis". Strong applications describe it with evidence: a local statistic, a waiting list, a quote from someone you support, a gap in existing provision. Two or three specific, sourced facts about your community beat a page of emotive language. Then connect the need directly to your project: this problem, in this place, is exactly what this project addresses.
The project: what you'll do, in plain numbers
Say precisely what will happen if the funder says yes: how many sessions, over what period, for how many people, delivered by whom. Vagueness reads as risk. "Weekly two-hour workshops for 25 young people over 12 months, delivered by two qualified youth workers" gives an assessor something they can picture, cost and score.
The difference it makes: outcomes, not activities
This is the section that separates funded from rejected. Activities don't get funded — outcomes do. Don't just say what you will deliver; say what will change because of it, and how you will know. "40 residents will complete the programme" is an activity. "At least 30 of the 40 will report improved confidence on a before-and-after survey, and 15 will move into work, training or volunteering within six months" is an outcome with a measurement plan attached. That single sentence pattern — how many, what changes, how you'll know — can be reused across almost every funder's form.
The budget: the most-read page you'll write
Assessors read budgets more carefully than prose, because budgets can't hide. Make yours boring in the best way: every line justified, every figure consistent with the project description, full cost recovery included (a fair share of rent, insurance and management time — most UK funders expect it), and no suspicious round numbers. If the form asks for £10,000 and your budget says £9,847, you have just told the assessor you did the work.
The consistency check that catches most applications
Where good applications go wrong
Even well-written applications fall into predictable traps: answering the question you wish had been asked instead of the one on the form; using sector jargon the assessor has to translate; leaving the strongest evidence in your head because "surely they know"; and submitting at the deadline with no one else having read it. We've covered the full list in the 7 biggest grant application mistakes — worth reading alongside this guide as a pre-submission checklist.
And one habit that quietly transforms results: wherever possible, talk to the funder before you write. A ten-minute call about fit can save a month of wasted work — and funders back organisations they know.
Great writing is downstream of fundability
Here is the truth that most "grant writing tips" articles skip: the application form is a window into your organisation, not a substitute for it. If your outcomes are fuzzy, your governance is thin or your story doesn't hold together, better prose won't fix it — assessors see through polish quickly. The founders who win consistently do the underlying work first: they make the organisation fundable, and then the writing becomes the easy part — a clear description of something genuinely worth funding.
So use this guide for your next application — but if you keep hitting near-misses and "strong application, not this round" letters, the answer usually isn't in the writing. It's in the readiness underneath it.
