How to write a grant project plan UK funders can follow

The deadline is getting closer, you’re still waiting for delivery figures, and someone keeps asking whether the budget is “nearly there”.

You need a grant project plan that makes sense to a funder, without turning another evening into an unpaid planning meeting.

How do you write a grant project plan UK funders can follow?

A grant project plan explains what you’ll deliver, who will do it, when it will happen and what it will cost. It links an evidenced need to the funder’s priorities, activities and costs in your grant application, with measurable results and clear responsibilities.

Start with the funding rules. Define your scope, break delivery into manageable stages, assign owners and build the budget around that work. Then check that your timetable, outcomes, risks and application answers agree.

Why this matters

You know your organisation inside out, including why the service matters, and you could probably explain the project whilst making tea.

The assessor has none of that background, so the plan has to do the explaining for you.

They need to understand the need, follow your decisions and judge whether the proposed work is credible. Missing links make that harder, even when your team could explain them in seconds.

A clear plan also protects your organisation after the award. Winning feels brilliant until recruitment starts, reporting dates arrive and someone asks who agreed that target.

That is when the promises in your application become your team’s working commitments.

For Innovate UK, eligibility checks come before assessment. Its published assessment process explains that competitions can use one, three or five assessors.

Independent assessors need enough detail to judge the application without a conversation with you.

Make the plan understandable outside your organisation. That helps the funder assess it and gives your delivery team something dependable to work with.

Check the funder’s rules and define the project

Before drafting, bring finance, delivery and the application lead into one short discussion. Agree whether this funding programme deserves your team’s time.

Read the current guidance, application questions, assessment criteria and funding conditions. Check who can apply and where, the project dates and eligible activity, and any grant limits or partnership requirements.

For innovation funding, Innovate UK’s pre-application guidance is a useful starting point. The live competition rules still govern your application.

A grant can offer non-dilutive funding, unlike equity, and isn’t a loan. Check the specific award terms, as repayment conditions may apply.

Record any unanswered questions. Ask the funder where clarification is available.

Resolve uncertain eligibility before proposal writing. Better wording won’t repair an ineligible project, however many people have already contributed to the draft.

Write the funder’s intended change in one plain sentence. Write your project’s intended change underneath.

Can you explain the connection without stretching either sentence?

A project may improve wellbeing, strengthen community connections and reduce hardship. Choose the strongest match as your lead. Let the other benefits support it.

Our guidance on aligning with funder priorities helps you test that connection before committing to the application.

Keep the project honest. Your team will eventually have to report against the outcomes you promise.

A broad ambition creates a difficult writing job. A defined project gives everyone something concrete to agree.

State who the work supports, where it happens and why it is needed now. Use reliable waiting-list information, referral patterns, participant feedback or local needs assessments to evidence the need.

Record each source and its date. Explain any limitations, so old or incomplete data isn’t presented as certain.

Then agree what the funded project includes and excludes. Separate existing services from additional activity, development or expansion.

This also helps you explain what the grant makes possible and what could proceed without it.

Your business plan covers the whole organisation. Your grant proposal only needs to make the case for this one investment, so pull across what’s relevant and leave the rest where it is.

Reuse relevant evidence and financial assumptions. Rewrite the delivery case around the funder’s questions.

For research and development applicants, UKRI’s core application questions show how assessment considers the proposed work and the team’s ability to deliver it.

The funded work should be distinct, whilst showing how it fits your organisation’s strategy.

Build a workplan with named owners

Break delivery into work packages: groups of related activities with a defined result. Use that terminology only if the funder uses it.

Otherwise, “delivery stages” does the job nicely.

Use basic project management to assign each stage an owner, timing, expected output and link to its project costs. Avoid rows such as “ongoing engagement” that leave everyone guessing what will happen.

Use this structure to build an operational plan the team can follow after an award.

Delivery stage	Define the result	Confirm before proceeding	Link the costs
Set-up	Agree access, resources and procedures	Approvals and partner commitments	Staff time and set-up costs
Recruitment	Establish staff and participant routes	Capacity and referral arrangements	Recruitment, training and outreach
Delivery	Specify the funded activity	People, venues and equipment	Delivery hours and direct costs
Evaluation	Collect and review agreed evidence	Measures and data arrangements	Evaluation and reporting time
Closure	Complete reporting and next-step decisions	Award conditions and notice periods	Closure and reporting costs

The table should expose decisions your team still needs to make.

Add durations and dependencies, meaning the things that must happen before another activity can start. Recruitment may depend on award confirmation. Delivery may depend on training or approvals.

Set milestones around completed results, rather than activity alone. A completed recruitment stage gives the funder more confidence than “recruitment underway”.

Use a Gantt chart if requested or helpful. Keep the written explanation clear enough to stand without it.

“We have an experienced team” needs supporting detail. Show who is responsible, what they bring and how much time they have available.

Name the project lead and delivery owners. Set out their relevant experience, project responsibilities and allocated time.

Check these commitments against current services and other funded work. Staff cannot provide unlimited hours just because several applications describe them as essential.

If you need to recruit, explain when recruitment will happen and how you’ll manage delays.

Research applicants should check UKRI’s project roles guidance for relevant responsibilities and costing requirements.

Explain who approves spending, reviews progress and authorises changes. Keep arrangements proportionate to the project’s scale and risk.

For partners, confirm the activity they will deliver, their resources and evidence of their commitment. Their letters of support should reflect a delivery commitment you’ve already agreed with them.

Healthcare or research work may also need ethical, clinical or organisational approvals. Check which requirements the funding body sets for your project.

Give each approval an owner and a place in the timetable. “We’ll sort that after award” can leave a substantial gap in delivery readiness.

Build the budget around the work

Start with the delivery stages. Estimate the project costs for each one, then check them against the funding rules.

That way, the budget reflects the real workload your team will carry.

For staffing, record the eligible rate, project time and permitted employment costs. For external services, record the quantity, rate and basis of the estimate.

Keep quotes and calculations available, with clear budget details and assumptions. You may need to explain them during assessment or award checks.

Include accessibility, supervision, evaluation and grant management where eligible. Volunteer-led activity still needs support, coordination and sometimes training.

Check whether VAT is recoverable and how the funder requires it to be treated. Apply the programme’s rules to overheads, equipment and capital expenditure.

Every significant line should point back to a delivery requirement.

Show total project costs, the amount requested and each additional contribution. State whether funding is confirmed, pending or subject to approval.

Check restrictions on existing funds. Don’t count the same contribution twice, or assume donated space and volunteer time qualify as match funding.

Funding rates and eligible costs differ between programmes and competitions. Previous awards are useful experience, but their rules aren’t transferable.

A balanced budget can still leave a cash-flow gap. Compare your cash forecast with payment dates and when wages, suppliers and delivery costs must be paid.

Agree who will cover any permitted contribution and how the organisation will manage payment timing.

Connect delivery to measurable change

Outputs describe what you deliver, such as sessions, equipment, research findings or people reached.

Outcomes describe what changes as a result. Impact is the broader or longer-term difference your project contributes to.

Keep those distinctions clear. Attendance proves participation, but it doesn’t automatically prove improved wellbeing. If you use impact statements, describe the broader change your project contributes to.

A simple logic model maps the identified need, resources, activities, outputs and expected outcomes.

Use it as a planning tool to test how activities connect to the need and expected outcomes. Follow a particular format only if the funder requests one, as there’s no universal requirement to submit a logic model.

For every important outcome, agree a measure, starting point, collection method, review date and responsible person. Make sure each measure is useful and matches what your grant application promises.

Participant experience can sit alongside numbers. Follow-up evidence may help show whether a change lasted, provided your team can collect it responsibly.

UKRI’s grant reporting terms include end-of-grant reporting on outputs, outcomes and impacts achieved to date.

Build evaluation into delivery now. Give someone time to collect evidence, review missed targets and report honestly. A reporting promise without resources becomes a late problem for somebody already carrying a full workload.

Make risks and dependencies visible

A credible risk section explains what could affect delivery and what your team will do about it.

Identify the risks that genuinely matter: recruitment delays, weak referral numbers, supplier availability, approval timing or unconfirmed funding.

For each, record its likelihood, delivery consequences, prevention measures, response and owner. Add a review date or trigger for action.

Avoid “we will monitor closely” as the whole response. Say what you’ll monitor and what decision follows a concern.

Innovation funding applications also need an honest account of technical uncertainty. Explain the current evidence, what testing will establish and how results will shape the next stage. For Innovate UK competitions, check guidance on technical merit, commercial risk and route to market. Include a commercialisation plan where relevant, supported by market analysis to assess commercial risk.

For community delivery, test access assumptions with the people and partners involved.

Plan the award ending too. Set decision dates for continuation, replacement funding or responsible closure. Allow time for staff, participant and partner communications.

You can describe uncertainty clearly without pretending it has disappeared.

Check the plan and avoid common mistakes

A shared spreadsheet, Microsoft Planner or Trello can help organise tasks. Use what your team already understands.

The useful part is having one controlled version, clear owners and visible unresolved decisions. Another platform won’t make an unconfirmed partner commitment more definite.

Bring delivery, finance and the application lead together for a final reconciliation. Make sure everyone is working from the same documents, because three versions with similar filenames is how mistakes slip through.

Use these questions:

• Does each promised activity have an owner, time allocation and budget?
• Do the delivery dates allow for recruitment, approvals and partner dependencies?
• Can we evidence each important outcome using the resources provided?
• Are funding contributions, assumptions and unresolved decisions clearly identified?
• Does the cash forecast match the workplan and budget?
• Do the form, workplan, budget, executive summary and attachments tell the same story?

Then give the draft to someone who wasn’t involved in building it. Ask them to test it against the actual questions and criteria, as grant reviewers would. A fresh reader can show how it may come across to independent assessors.

Bidsmithery™ combines proposal writing and evaluator experience, with more than £103m in contracts secured. Our independent grant application review tests whether the funding case, evidence and delivery commitments hold together.

Leave time in the submission process to act on that feedback. A useful review needs room for changes, so book it well before the portal closes.

One frequent mistake is starting with the amount available, then expanding the project until the budget reaches it. Cost the work you can justify.

Another is promising more activity than the resources support. Check staffing hours, venue bookings, supervision and evaluation against the narrative.

Reusing a previous plan unchanged can also create problems. Dates, criteria, funding conditions and partner availability may all have moved on.

Watch for impact statements that sound impressive but lack a baseline or credible measure. Tighten the promise until your team can explain how it will be evidenced.

Don’t hide pending match funding, recruitment or approvals. State the position and the action needed.

Finally, keep acronyms and internal shorthand under control. An assessor shouldn’t need your induction pack to understand the project.

Before uploading, check attachment names, required formats, word limits and portal access. Protect time for the submission itself, as the final five minutes of writing is rarely enough.

Frequently asked questions

Key takeaways

• Begin with the live funding rules and a genuine fit.
• Connect activities, owners, milestones and costs in one working plan.
• Give evaluation and reporting enough time and resources.
• State assumptions and pending contributions honestly.
• Review the whole application against the funder’s questions before submission.

Protect your next submission

A clear delivery plan gives the funder confidence and your team a workable starting point after the win.

If the same gaps keep returning, Bid Win Rate Accelerator Training or ongoing bid review support can help reduce the load. Book a free fit call to discuss what would help.

An external red review is a sensible way to protect your team’s energy, confidence and headspace before the next deadline arrives.