How to Write a Grant Application: A Practical Guide for Charities

Published 2026-09-03 · Last reviewed 2026-09-03

A strong grant application is not about using grand language. It is about helping a funder see the need, understand your plan and trust your organisation to deliver it.

Writing a grant application can feel like trying to describe months of thoughtful work inside a rigid form and a tight word count. You know why the project matters. The challenge is making that case clear to someone who may be reading hundreds of applications.

A strong application is not the one with the most impressive language. It is the one that makes it easy for the funder to understand the need, see how your proposed work responds to it and trust that your organisation can deliver what it promises.

This guide takes you through the process step by step, from deciding whether a fund is genuinely right for you to checking the final application before it is submitted.

Before you write: check that the fund is a good fit

The fastest way to improve a grant application is to choose the right opportunity. Even an excellent proposal is unlikely to succeed if your organisation, project, location or costs fall outside the funder's priorities.

Read the published criteria before drafting anything. Then look beyond the headline. Review the funder's stated outcomes, exclusions, typical award size, decision timetable and examples of work it has supported before. If the funder offers a conversation before application, arrive with a concise description of your project and two or three specific questions.

• Eligibility: does your legal structure, annual income, location and beneficiary group qualify?
• Purpose: does the project directly support the outcomes the funder wants to achieve?
• Costs: will the fund cover the activities, salaries, equipment, overheads or capital items you need?
• Timing: can you wait for the decision before starting, and can you deliver within the funding period?
• Scale: is the amount you need realistic compared with the funder's usual awards?

Gather the evidence before drafting

Grant writing is a team activity, even when one person owns the form. Before you start writing, gather the facts that will support your case. Speak to delivery colleagues, finance staff, partners and, where appropriate, the people the project is intended to support.

Useful material may include attendance records, waiting lists, referral patterns, participant feedback, local data, evaluation findings and learning from earlier delivery. You will also need practical information such as the project timetable, staffing plan, safeguarding arrangements, budget assumptions and responsibilities of any partners.

This preparation prevents a common problem: an application that sounds convincing at the beginning but becomes vague when the funder asks how the work will happen, what it will cost and how you will know whether it succeeded.

Explain the need clearly

Your needs statement should describe the problem or opportunity the project will address, who experiences it and why action is needed now. Start with the people and place, not with your organisation.

Use evidence selectively. A relevant local figure, a pattern in your service data and a short summary of what participants have told you can work together. Numbers establish scale, while direct experience explains what the issue means in practice. Avoid filling the section with broad national statistics that do not tell the funder anything about the community you will serve.

Be careful not to portray people only through problems or deficits. Describe the barriers they face while recognising their strengths, ambitions and role in shaping the response.

• What is happening, and who is affected?
• How do you know this need exists?
• Why are current services or opportunities not enough?
• What have the people affected said they want?
• Why is your organisation well placed to respond?

Describe a specific and deliverable project

Once the need is clear, explain exactly what you will do. Replace general phrases such as "provide support" with a concrete picture of the activities, frequency, location, duration, staffing and route into the service.

A reviewer should be able to imagine the project operating. If you plan to deliver mentoring, say how participants will be recruited, how mentors will be prepared, how often they will meet, what each relationship will work towards and what support is available if a placement becomes difficult.

Keep the scale consistent throughout the application. The participant numbers, sessions, staffing, timetable and budget should describe the same project. Contradictions between sections make even a good idea feel underdeveloped.

Connect activities, outputs and outcomes

Funders want to know what their money will make possible. A simple results chain helps you explain that without overclaiming.

• Activities are what you will do, such as weekly mentoring sessions or financial advice appointments.
• Outputs are the direct record of delivery, such as the number of sessions held or people supported.
• Outcomes are the changes you expect, such as greater confidence, improved financial stability or progression into training.
• Impact is the broader or longer-term difference to which the project contributes.

Choose outcomes that are plausible within the grant period and within your influence. A six-month employability programme might reasonably expect participants to build skills, complete applications or enter training. It should not promise to solve unemployment across a whole borough.

State how you will recognise progress. Depending on the project, that might combine attendance, goal reviews, before-and-after questions, observations, interviews, referral outcomes and follow-up conversations. Use a small number of useful measures rather than collecting data that your team will struggle to maintain.

Show that participants helped shape the work

Funders increasingly want to understand how people with relevant lived experience influence a project. Avoid treating consultation as a sentence to add at the end. Explain what people said, how you heard from them and what changed as a result.

Involvement can take many forms: identifying the original need, designing activities, testing materials, sitting on a steering group, helping recruit staff or reviewing whether the project feels accessible. Be honest about the level of influence. Do not describe a feedback survey as co-production if participants did not share decision-making power.

Build a budget that tells the same story

A grant budget is part of the project plan, not a separate finance exercise. Every significant cost should connect to an activity, and every activity should have enough resource behind it to be credible.

Calculate staffing from realistic hours and rates. Include employer costs where relevant. Add delivery costs such as venue hire, travel, accessibility support, participant expenses, equipment, insurance, evaluation and a fair contribution to organisational overheads where the fund allows it.

Check the funder's rules on VAT, contingency, full cost recovery and in-kind contributions. Explain unusual or large items in the budget narrative. A reviewer should not have to guess why a cost is necessary.

• Make sure the figures add up and match every number quoted elsewhere in the form.
• Use evidence for estimates, such as quotations, previous delivery costs or published rates.
• Avoid making the project look artificially cheap by leaving out management and support time.
• Show confirmed and pending income clearly if the project has more than one funder.
• Explain what would change if you received less than the amount requested.

Demonstrate that your organisation can deliver

The funder is assessing both the idea and the organisation behind it. Give concise evidence of relevant experience, relationships, governance and delivery capacity.

Focus on what is most relevant to this proposal. Mention previous work with the community, what your team has learned, the expertise involved and the partnerships that make the plan stronger. Where a project involves children, vulnerable adults or sensitive information, explain the appropriate safeguarding, consent and data-protection arrangements.

Do not claim that everything has always gone perfectly. A brief example of learning and improvement can provide more confidence than a flawless success story.

Write for a busy reader

Answer the question being asked, in the order it is asked. Use the question wording to guide your first sentence. Short paragraphs, specific examples and plain language make an application easier to assess.

Avoid unexplained acronyms, internal programme names and promotional language. Words such as innovative, transformative and unique carry little weight without evidence. It is usually stronger to explain what is different, why it matters and how you know.

Draft to the word limit, then remove repetition. Do not shrink a complete project explanation into the final hour before the deadline. Leave enough time for someone who was not involved in writing it to check whether the argument is clear.

Use AI carefully when writing grant applications

AI can help organise notes, identify gaps, shorten a paragraph or turn project records into a first draft. It should not invent evidence, participant quotes, partnerships, costs or outcomes. Those details must come from your organisation.

Generic AI text often sounds polished while saying very little. The strongest application still depends on specific knowledge of the community, the funder and the proposed work. Treat AI output as a draft to verify and rewrite, not as a finished application.

Be especially careful with personal or sensitive information. Use approved systems, remove unnecessary identifying details and follow your organisation's data-protection policies.

Common grant application mistakes

• Applying because money is available, rather than because the fund genuinely fits the project.
• Describing the organisation at length before explaining the need.
• Listing activities without showing what will change for participants.
• Using ambitious outcomes that cannot be measured or achieved within the grant period.
• Presenting participant involvement as an afterthought.
• Submitting a budget that does not match the delivery plan.
• Copying old application text without checking it against the new funder's priorities.
• Making claims that are not supported by records, research or lived experience.
• Waiting until the deadline day to collect approvals, attachments or financial information.

Your final grant application checklist

• Every eligibility requirement has been checked.
• The opening makes the need and proposed response immediately clear.
• The evidence is relevant, current and connected to the people or place involved.
• Activities, participant numbers, outcomes, timetable and budget are consistent.
• The application explains how participants influenced the project.
• Outcomes are realistic and each has a proportionate way to measure progress.
• The budget includes the real cost of responsible delivery.
• Required policies, accounts, governing documents and approvals are ready.
• A colleague unfamiliar with the draft has reviewed it for clarity.
• The final version has been saved, named clearly and submitted before the deadline.

Keep the application connected to delivery

A successful application becomes a commitment. Save the final answers, budget, outcomes, conditions and reporting dates somewhere the delivery and finance teams can find them. The people running the project should know what was promised before the first session begins.

JENY connects grants to projects, activities, contacts, outcomes, evidence and reporting deadlines. Its Grant Writer can help organise a draft from information already held by your organisation, while your team stays responsible for accuracy, judgement and the final submission.

Keeping the application and delivery records together also makes the next report, renewal or funding bid easier. Instead of reconstructing the story at the deadline, you build the evidence as the work happens.