How to Write a Grant Budget That Gets Approved (2026)

The budget is the part of a grant application founders most often underestimate — and the part assessors scrutinise most closely. A brilliant project description paired with a vague or inflated budget raises immediate doubts, because reviewers read your budget as a proxy for how carefully you've thought through execution. A credible, well-justified budget signals a credible, executable project. This guide walks through how to build one that gets approved.

Why the budget matters more than founders think

Reviewers see hundreds of applications, and the budget is where wishful thinking becomes visible. Round numbers with no basis, costs that don't match the workplan, padded line items, or a total that conveniently equals the maximum available — all of these are red flags that experienced assessors spot instantly. Conversely, a budget where every cost is tied to a specific activity and justified with a clear rationale tells the reviewer you understand your own project. In competitive programmes where reviewers are looking for reasons to narrow the field, a weak budget is an easy reason to score you down.

Principle one: tie every cost to the workplan

The single most important rule is that your budget and your project plan must tell the same story. Every cost should map to a specific activity or work package in your plan, and every significant activity should have identifiable costs behind it. If your workplan describes six months of prototype development by two engineers, the budget should show those two engineers' time over that period. If a cost appears in the budget with no corresponding activity — or an activity has no visible cost — the reviewer notices the disconnect and trusts the whole application less.

A practical way to build this is to write your workplan first, break it into work packages, and then cost each package from the bottom up: who does the work, for how long, with what materials and equipment. This "bottom-up" approach produces a budget you can defend line by line, which is exactly what assessors reward.

Principle two: know what's eligible and what isn't

Every programme defines which costs it will and won't fund, and applying for ineligible costs signals you didn't read the rules. Broadly, most R&D grants cover the direct costs of doing the work: staff time for people working on the project, materials and consumables, certain equipment costs, subcontracting within limits, and a contribution toward overheads. What's typically not covered varies by programme but often excludes general marketing and sales, routine business operations unrelated to the project, and costs incurred before the project start date.

Read the specific programme's eligible-cost rules before you build the budget, not after. If something is ambiguous, ask the programme office. Building your budget around costs the funder won't pay is a common and entirely avoidable way to weaken an application.

Principle three: handle overheads and funding rates correctly

Two technical points trip up first-time applicants. First, overheads: many programmes let you add a standard percentage on top of your direct costs to cover indirect expenses like rent and administration, often calculated automatically. Understand how your programme treats overheads so you neither under-claim nor mis-state them. Second, and more importantly, the funding rate: grants rarely cover 100% of costs. Many programmes fund a percentage — for R&D grants, often up to around 70% for smaller companies, less for larger ones — and you contribute the rest. Some programmes, like certain early-stage research schemes, do fund 100%, but most expect co-funding.

Principle four: plan your match funding honestly

Because most grants don't cover everything, you usually need to show you can fund your share — the match funding. Assessors want confidence that the project will actually happen, which means demonstrating you have, or can raise, your contribution. Vague assurances aren't enough; be specific about where your co-funding comes from, whether that's revenue, existing cash, or committed investment. A project that wins a grant but can't fund its own share never delivers, and reviewers know it, so they weight this seriously.

The budget mistakes that sink applications

A few recurring errors do the most damage. Requesting the maximum available regardless of what the project needs looks like padding and invites scrutiny. Budgets that don't match the workplan destroy trust. Vague, unjustified line items ("miscellaneous: €40,000") read as poorly planned. Ignoring the funding rate and assuming 100% coverage leads to unrealistic asks. And forgetting to account for match funding leaves a hole reviewers will notice. Avoiding these is often the difference between a fundable and an unfundable application — and none of them require a better idea, just better discipline.

A simple pre-submission budget check

Before you submit, run through this: does every cost map to an activity in the workplan? Is every major line item justified? Have you confirmed all costs are eligible for this specific programme? Have you applied the correct funding rate rather than assuming 100%? Can you clearly show where your match funding comes from? Does the total reflect what the project genuinely needs rather than the maximum on offer? If you can answer yes to all six, your budget is in strong shape.

Practical next steps

A strong budget sits inside a strong application, so it's worth getting the whole picture right. Our guide to grant application mistakes that get you rejected covers the wider pitfalls, and our founder guides walk through specific programmes step by step. To find grants worth building a budget for in the first place, try the 60-second matching quiz or estimate your range with the funding calculator.

The bottom line

A grant budget that gets approved isn't about clever accounting — it's about discipline and honesty. Tie every cost to your workplan, use only eligible costs, apply the correct funding rate, plan your match funding credibly, and size the request to what the project actually needs. Assessors reward budgets they can trust, and a budget they can trust is one where every number has a reason behind it. Get this right and you remove one of the most common reasons strong projects get rejected.