How to Write a Grant Application: What Funders Actually Look For
A practical walk through the grant application itself: the questions every form asks, how assessors score them, and the mistakes that get decent projects rejected.
Most grant applications fail before an assessor reads a single word of the project description. They fail on eligibility, on budgets that do not add up, or on answers that describe the organisation when the question asked about the project. The good news is that grant forms are more predictable than they look. Almost every funder asks versions of the same five questions, and you can prepare strong answers to all of them before you open the form.
This guide covers the application itself. If you are a brand new group applying for the first time, start with our guide to winning your first grant, which covers the groundwork funders expect before any application.
Before you write anything
Read the eligibility criteria twice, then read the exclusions. Funders publish what they will not pay for, and that list rules you out faster than the aims page rules you in. Retrospective costs, activities that already have funding, and work outside the fund's area are the usual traps. An afternoon on a form you were never eligible for is the most common way applicants waste time.
Look at who they funded last year. Nearly all funders publish grantee lists. If every recent award went to organisations ten times your size, or to a different kind of work, believe the pattern over the prospectus.
Check the deadline and the decision date. If the money arrives after your project needs to start, the fund is wrong for you regardless of fit. Funders almost never pay for things that have already happened.
The five questions every form asks
Grant forms vary in length and layout, but underneath they ask the same things. Draft these answers in a document first, then paste and trim to fit each form's word limits.
| The question | What the assessor is checking |
|---|---|
| What will you do? | Is the plan specific enough to be real |
| Why is it needed? | Evidence of local need, not general statements |
| Who benefits, and how many? | Realistic reach, clearly defined beneficiaries |
| How much will it cost? | A budget that adds up and matches the plan |
| What changes as a result? | Outcomes you could actually check later |
What will you do?
Be concrete. Name the activity, the frequency, the place, and the people. "A weekly two-hour drop-in session at the village hall for carers of people with dementia, run by two trained volunteers" gives an assessor something they can picture and score. "Support for vulnerable people in the community" gives them nothing.
If the project has phases, list them in order with rough dates. You are showing the funder that the project will happen the way you say it will.
Why is it needed?
This is where most applications are weakest. General statements about national problems score poorly because they are true everywhere and prove nothing about your patch. Local evidence scores well, and it does not need to be a commissioned study:
- A number from your own records: a waiting list, attendance figures, enquiries you had to turn away
- A local statistic: ward-level data from the census, your council's needs assessment, local health figures
- Voices: two or three sentences from the people who want what you are offering
One good local figure beats three paragraphs of national context. If you use national data at all, use it once, then bring it home to your area.
Who benefits?
Define the group precisely and estimate numbers honestly. Assessors read inflated reach claims every day and discount them on sight. Forty people attending regularly, described honestly, reads better than "hundreds of community members reached". If some beneficiaries are indirect, say so and count them separately.
The budget
The budget is where trust is won or lost. Rules that hold across nearly every funder:
- It must add up. Check it, then have someone else check it. An arithmetic error undermines everything else in the application.
- Every line should trace back to the plan. If the project description mentions a trainer, the budget should show the trainer's cost. If the budget shows equipment the description never mentions, explain it or cut it.
- Get real quotes for anything significant. "Estimated" prices on big items invite doubt. Two quotes for the large costs show you have done the work.
- Ask for the right amount. Requesting the fund's maximum when your plan needs less is transparent and scores badly. So is shaving the request to look cheap and leaving the project underfunded.
Some funds expect you to bring part of the cost yourself. If you see that requirement, our guide to match funding explains what counts and where to find it.
What changes as a result?
Outcomes are the difference your project makes, not the activities you run. "We will run 40 sessions" is an output. "Twenty carers report feeling less isolated, measured by a short survey at the start and end" is an outcome. Pick two or three outcomes you could genuinely check, and say how you will check them. Funders do not expect a small organisation to run a research project. A sign-in sheet, a five-question survey, and a few quotes collected at the end are proportionate and credible.
Why decent applications get rejected
Assessors reject far more applications than they fund, and the reasons repeat:
- The application was ineligible, and nobody read the criteria closely enough to notice
- The answers described the organisation's history when the question asked about the project
- The budget did not add up, or did not match the activities described
- The need was asserted rather than evidenced
- The request did not fit the fund's size: too big for the pot, or oddly small for the plan
- Word limits were treated as targets, burying the answer in padding
None of these are about the quality of the underlying project. They are all avoidable in an afternoon of checking.
Frequently asked questions
How long does a grant application take to write? A short form for a small local grant might take an evening once your standard answers exist. A large application to a national funder can take several weeks. The standard-answers document is what makes the second application dramatically faster than the first.
Can I apply to more than one funder for the same project? Usually yes, and for larger projects funders expect it. Tell each funder who else you have applied to. If both say yes, you tell them and agree how the costs split. Honesty here protects your relationship with both.
Should I phone the funder before applying? If they invite contact, yes. A ten-minute call about whether your project fits can save you a wasted application, and assessors often remember a sensible early conversation.
What if we get rejected? Ask for feedback. Many funders give it, some encourage a revised application in a later round. A rejection from one fund says little about your chances elsewhere.
Your next step
Write your standard answers to the five questions before you pick a fund. Then browse live UK grants or the listings for your sector to find funds worth those answers. Every grant page on GrantMatch sets out the deadline, the award size, and who can apply, so you can rule funds in or out in minutes rather than evenings.