Most grant applications spend 80% of effort on the budget and 20% on the narrative. Funders read in the opposite order — narrative first, budget last. Here's what they actually look for.
Most grant applications spend 80% of effort on the budget and 20% on the narrative. Funders read in the opposite order — narrative first, budget last. Here's what they actually look for.
Most grant application drafts get prepared the wrong way around. The team starts with the budget — line items, supplier quotes, cost categories. Three weeks later they cobble together a narrative around the numbers. The budget is precise, the narrative is bland, and the funder rejects it without ever quite explaining why.
Funders read in the opposite order. Narrative first, alignment second, capacity third, budget last. By the time they reach the budget they've already decided whether you're a likely yes or no — and the budget is checked for plausibility, not used as the primary decision input.
A grant application is a structured proposal asking a funder (government, foundation, philanthropic body) to support a specific programme with specific outcomes for a specific cost. The deliverable is a written document, often submitted through an online portal, accompanied by financial statements, governance documents, and supporting evidence.
The four sections funders read in order:
The funder is reading this first. Three things have to land:
Funders read hundreds of applications. The narrative is the only part that distinguishes you from generic submissions. Vague problem statements ("there is a need") combined with generic interventions ("we will deliver workshops") get filed in the no pile within 90 seconds.
Every funder publishes priorities, strategic plans, theory of change. Your application needs to demonstrate it understands and maps to these — explicitly, with language that mirrors the funder's published terms.
| Funder language | Weak mapping | Strong mapping |
|---|---|---|
| "Community resilience" | "Our work helps the community." | "This programme builds three of the five community resilience pillars in your 2024 strategy: economic participation, social cohesion, and access to services." |
| "Outcome-based funding" | "We will deliver activities." | "We're applying for outcome-based funding because our model is structured around three measurable outcomes (listed below) rather than activity counts." |
| "Demonstrated impact" | "We have helped many people." | "Our previous programme delivered 312 beneficiaries with 67% sustained outcomes at 12 months — independently verified by [evaluator name]." |
Can you actually deliver? Funders need to believe the answer is yes. Four pieces of evidence:
This section is where most under-capitalised applications get caught — not because the idea is bad, but because the funder isn't confident in delivery.
By the time the funder reaches the budget, they've already mostly decided. The budget gets checked for:
Inflated budgets, vague line items, and over-allocated administrative costs are the budget red flags. A clean budget at 90% of what you actually need beats a padded budget at 130% of what you need.
| Week | Work |
|---|---|
| 1 | Read the funder's guidelines AND their last 3 funding rounds (what they actually funded — public on most funder websites). Identify the alignment language. |
| 2 | Draft the narrative — problem, intervention, outcome. 1,200–1,800 words. Avoid the budget entirely at this stage. |
| 3 | Write the alignment section. Map each funder priority to a section of your proposed work. |
| 4 | Document capacity — team, track record, governance, infrastructure. Pull existing materials rather than writing new ones where possible. |
| 5 | Build the budget. Now you've defined the work, you can cost it accurately. Code every line to a work package. |
| 6 | Internal review + external read-through (someone unfamiliar with your work — if they don't understand the narrative, neither will the funder). |
| 7 | Refine, submit. |
1,200–1,800 words for the narrative section is typical. Some funders give explicit word counts — follow those exactly. Going over is read as not respecting the format; going under raises capacity questions.
For a programme you already run: 4–6 weeks of focused work, ideally with one person leading and 2–3 contributors. For a new programme you're designing in tandem with the application: 8–12 weeks because you're doing both pieces of work in parallel.
Highly variable by funder. Government innovation grants: 8–18% success rate. Foundation grants (well-targeted): 25–40%. Local council grants: 35–55%. Application count alone doesn't matter — alignment + capacity + narrative drive the success rate.
Worth it for funders you don't have a track record with, or for grants above £150k where the application complexity justifies the cost (£3,000–£10,000 typical for a full application). Not worth it for repeat applications to funders you've already won from — the relationship knowledge in-house beats outside writing skill.
The narrative — specifically the problem-and-outcome pairing. Funders read the first 500 words and form a working judgement. Everything after either confirms or undermines that judgement; almost nothing reverses it.
Qwrki runs grant and programme operations as part of the operating layer — pre-grant narrative work, application drafting, capacity documentation, then delivery + acquittal. We don't write grant applications as a standalone service; we run the programme cycle end-to-end so the application reflects what'll actually be delivered. Book a call — if there's a specific funder you're applying to, the first session is a free read-through of your alignment.
What non-dilutive funding is, how it compares to equity and debt, who it suits, and what the operating burden really looks like.
A grant readiness checklist covering governance, financials, project definition and delivery capacity, so the application writes itself and the audit holds.
How to build a grant budget bottom-up: cost categories, justification lines, in-kind contributions and the admin caps question, with a worked structure.
Most grant application drafts get prepared the wrong way around. The team starts with the budget — line items, supplier quotes, cost categories. Three weeks later they cobble together a narrative around the numbers. The budget is precise, the narrative is bland, and the funder rejects it without ever quite explaining why.
Funders read in the opposite order. Narrative first, alignment second, capacity third, budget last. By the time they reach the budget they've already decided whether you're a likely yes or no — and the budget is checked for plausibility, not used as the primary decision input.
A grant application is a structured proposal asking a funder (government, foundation, philanthropic body) to support a specific programme with specific outcomes for a specific cost. The deliverable is a written document, often submitted through an online portal, accompanied by financial statements, governance documents, and supporting evidence.
The four sections funders read in order:
The funder is reading this first. Three things have to land:
Funders read hundreds of applications. The narrative is the only part that distinguishes you from generic submissions. Vague problem statements ("there is a need") combined with generic interventions ("we will deliver workshops") get filed in the no pile within 90 seconds.
Every funder publishes priorities, strategic plans, theory of change. Your application needs to demonstrate it understands and maps to these — explicitly, with language that mirrors the funder's published terms.
| Funder language | Weak mapping | Strong mapping |
|---|---|---|
| "Community resilience" | "Our work helps the community." | "This programme builds three of the five community resilience pillars in your 2024 strategy: economic participation, social cohesion, and access to services." |
| "Outcome-based funding" | "We will deliver activities." | "We're applying for outcome-based funding because our model is structured around three measurable outcomes (listed below) rather than activity counts." |
| "Demonstrated impact" | "We have helped many people." | "Our previous programme delivered 312 beneficiaries with 67% sustained outcomes at 12 months — independently verified by [evaluator name]." |
Can you actually deliver? Funders need to believe the answer is yes. Four pieces of evidence:
This section is where most under-capitalised applications get caught — not because the idea is bad, but because the funder isn't confident in delivery.
By the time the funder reaches the budget, they've already mostly decided. The budget gets checked for:
Inflated budgets, vague line items, and over-allocated administrative costs are the budget red flags. A clean budget at 90% of what you actually need beats a padded budget at 130% of what you need.
| Week | Work |
|---|---|
| 1 | Read the funder's guidelines AND their last 3 funding rounds (what they actually funded — public on most funder websites). Identify the alignment language. |
| 2 | Draft the narrative — problem, intervention, outcome. 1,200–1,800 words. Avoid the budget entirely at this stage. |
| 3 | Write the alignment section. Map each funder priority to a section of your proposed work. |
| 4 | Document capacity — team, track record, governance, infrastructure. Pull existing materials rather than writing new ones where possible. |
| 5 | Build the budget. Now you've defined the work, you can cost it accurately. Code every line to a work package. |
| 6 | Internal review + external read-through (someone unfamiliar with your work — if they don't understand the narrative, neither will the funder). |
| 7 | Refine, submit. |
1,200–1,800 words for the narrative section is typical. Some funders give explicit word counts — follow those exactly. Going over is read as not respecting the format; going under raises capacity questions.
For a programme you already run: 4–6 weeks of focused work, ideally with one person leading and 2–3 contributors. For a new programme you're designing in tandem with the application: 8–12 weeks because you're doing both pieces of work in parallel.
Highly variable by funder. Government innovation grants: 8–18% success rate. Foundation grants (well-targeted): 25–40%. Local council grants: 35–55%. Application count alone doesn't matter — alignment + capacity + narrative drive the success rate.
Worth it for funders you don't have a track record with, or for grants above £150k where the application complexity justifies the cost (£3,000–£10,000 typical for a full application). Not worth it for repeat applications to funders you've already won from — the relationship knowledge in-house beats outside writing skill.
The narrative — specifically the problem-and-outcome pairing. Funders read the first 500 words and form a working judgement. Everything after either confirms or undermines that judgement; almost nothing reverses it.
Qwrki runs grant and programme operations as part of the operating layer — pre-grant narrative work, application drafting, capacity documentation, then delivery + acquittal. We don't write grant applications as a standalone service; we run the programme cycle end-to-end so the application reflects what'll actually be delivered. Book a call — if there's a specific funder you're applying to, the first session is a free read-through of your alignment.
What non-dilutive funding is, how it compares to equity and debt, who it suits, and what the operating burden really looks like.
A grant readiness checklist covering governance, financials, project definition and delivery capacity, so the application writes itself and the audit holds.
How to build a grant budget bottom-up: cost categories, justification lines, in-kind contributions and the admin caps question, with a worked structure.
