How to write a grant evaluation plan UK funders can trust

The grant deadline is close. Your delivery lead is checking the budget, someone is chasing a partner letter, and the form asks how you’ll prove the project worked. Your grant evaluation plan can’t be the bit you write after everyone else has gone home.

You need a plan your team can deliver and a funder can believe. Start with the change you’re promising, then work backwards to the evidence you’ll collect.

How do you write a grant evaluation plan UK funders can trust?

A grant evaluation plan explains how you’ll track delivery, measure results and use what you learn. It should name your outcomes, the evidence you’ll collect, when you’ll collect it and who is responsible.

Start with the funder’s requirements, including any specified measures or key performance indicators. Then connect each promised outcome to a realistic measure, a starting point and a reporting date. Keep the work proportionate to the grant: a plan only builds trust if your team can follow it whilst delivering the project.

Why this matters to funders

A funder wants to know what their money will support and how you’ll recognise progress. If you promise to “transform lives”, you may mean it. The assessor still needs something they can assess.

A credible plan gives them a clear line of sight: who will take part, what you’ll deliver and what should change. Evaluation helps show whether the funded work is progressing and how you’ll check. It also helps your team spot problems whilst there’s still time to act.

That matters once the good news has arrived and the celebrations are over. The project starts, the reporting dates become real, and everyone is back to their day job. The strongest plan is one your team can pick up and use on an ordinary Tuesday.

Government evaluation guidance makes the same practical point: evaluation works best when it’s considered early. The Magenta Book guidance on evaluation covers how to plan, carry out and use an evaluation, rather than treating it as an end-of-project exercise.

Start with the funder’s actual requirements

Read the live guidance, then the award terms

Does the application ask for a separate plan? Does it request outcomes in a form field? Are there required indicators, milestones or report dates? Check the live guidance before you build a template.

Requirements vary between a charitable trust, a public grant and a research award. The National Lottery Community Fund, for instance, publishes terms for awards over £20,000. Compare the award terms with the application guidance, as reporting requirements can differ between programmes. Read the terms for your programme and award rather than assuming last year’s reporting arrangements still apply.

Some proposals won’t ask for a document called an evaluation plan. You’ll still need to explain how you’ll know the project is on track if the funder asks about results.

Match the measures to the funding decision

Look at the funder’s priorities and assessment questions. If the grant is intended to improve access for a defined community, a count of social media views won’t tell the funder much. A measure of who reached the service, and whether access improved, will be stronger.

Keep the same outcomes across the grant proposal, workplan and reporting plan. For a closer look at this connection, see how to align a grant application with funder priorities.

Map the work before you choose measures

Build a simple logic model

A logic model is a short map of how your project is expected to work. It links the need you’ve identified to the resources you’ll use, the activities you’ll deliver and the results you expect.

Imagine a funded digital skills project. Staff time and venue space support classes. The classes and places offered are outputs. Learners being able to complete an online form without help is an outcome. These are different claims, so they need different evidence.

The Magenta Book’s evaluation guidance includes advice on building a logic model and other ways to map how an intervention is expected to work. A one-page version is often enough to reveal a missing link before you submit.

Name the assumptions you depend on

That digital skills project may rely on a referral partner, accessible travel and learners having time to attend. Include those assumptions in your plan.

If referrals slow down, you can check the route into the project before concluding that people don’t need the service. Funders are comfortable with an honest account of what could affect your results, and far less comfortable with an outcome that seems to rely on everything going to plan.

Write objectives an assessor can check

A useful objective names the group, expected change, measure and deadline. SMART objectives make project objectives specific enough for an assessor to check.

“Improve digital confidence” leaves too much open. A stronger objective might set a target for learners to complete a defined online task independently by the end of the course. Make sure it follows from the activities and intended change in your logic model. If a funder uses its own label for outcomes, mirror it in the form, then explain the change in plain English. Base your targets on your capacity, referral evidence and starting position so you can defend them if asked.

For each outcome, ask four questions:

• Who should experience the change?
• What will they be able to do, know or access?
• How will we recognise that change?
• When will we check?

You don’t need a dozen outcomes to look serious. Two or three that connect clearly to the need and delivery plan may give the funder a better account than a long list nobody has time to measure.

Choose evidence your team can collect

Use numbers for reach and progress

Your evaluation plan should use data collection methods your team can manage. Attendance records provide quantitative data, showing how many people came, how often they attended and where drop-off happened. A short question at the start and end can show change against the same measure. Referral records may help explain who the project reached.

Choose baseline data, the starting position, before you settle on a claim of improvement. If participants already feel confident completing an online form, a final survey alone won’t show what changed during your classes.

Be clear about missing data too. If 40 people join but only 18 complete a follow-up question, report both figures. Don’t present 18 responses as the experience of all 40 people.

Ask people what the figures miss

Interviews, short feedback questions and staff observations provide qualitative data that can explain why a result changed. Perhaps attendance dipped because sessions clashed with school pick-up, and the team needs to move them. Perhaps people completed the course but still needed help with unfamiliar forms.

During data collection, use questions that relate to your outcomes. “Did you enjoy the workshop?” may be useful for delivery, but it won’t show whether someone gained a skill.

The National Lottery Heritage Fund’s evaluation good practice guidance is a useful example of a funder asking projects to think beyond activity counts towards benefits and longer-term effects. Your own funder’s guidance should decide what you report.

Make collection safe and fair

Collect only what you can use

A grant isn’t permission to gather every detail someone is willing to share. Plan data collection around what you need, who can access it, where it will be stored and when it should be deleted. Agree your approach with whoever handles data protection in your organisation.

Explain to participants what you’re asking and how their information will be used. Be careful with sensitive accounts, especially in health, safeguarding or community work. You can often report a useful pattern without including a person’s identifiable story.

Check whose experience is missing

A final survey can over-represent people who stayed until the last session. Those who left early may tell you the most about barriers to access.

Build in a respectful way to understand drop-off, where appropriate. You might compare attendance over time, ask a brief exit question or review feedback from referral partners. Record what you couldn’t find out as well as what you could.

That honesty makes the findings more useful. A neat percentage loses value if nobody knows who had the chance to respond.

Set a timetable people can deliver

Review progress during the project

Monitoring is the regular check on delivery: sessions held, places filled, spending, referrals and milestones. A formative evaluation uses information gathered during delivery to help you improve it.

For a small project, a monthly review of attendance and a short discussion with staff may be enough. If numbers fall, decide whether to change the session time, speak to referral partners or remove an access barrier. Record the decision and check whether it helped.

Name the person responsible for each measure. “The team will monitor outcomes” sounds reassuring until everyone assumes someone else has the spreadsheet.

Decide what you’ll assess at the end

A summative evaluation looks at results at a defined endpoint. It brings together delivery figures, outcome measures, participant experience and the limits of what the evidence shows.

For a multi-year award, don’t wait until the final month. If you’re making claims about longer-term change, an impact evaluation may need follow-up after people leave. Set review points that match project milestones and funder reporting periods. Check each point against your logic model, from activity through to intended change.

If you intend to follow people after they leave, decide your evaluation design first. Explain how you’ll contact them, what data collection will involve and how you’ll account for those you can’t reach.

Longer follow-up can show whether change lasted, but it takes staff time, so cost it before you promise it.

Keep the work proportionate to the grant

If you’re applying for £5,000, the evaluation shouldn’t eat into the money meant for delivery. A short question at the start, an attendance record, some participant feedback and a final review may be enough, depending on the funder’s rules and how much could go wrong.

A larger or longer project may need regular milestones, partner evidence and a fuller assessment of outcomes. The right level depends on what you’re claiming, how much is at stake and what the funder asks you to report.

Check the cost in real terms. Who enters the data? Who follows up? Who analyses it and writes the report? If those hours aren’t in the workplan and budget, the plan is relying on time nobody has.

Promise the evidence you can collect whilst doing the work. If the method needs extra time or specialist help, put that cost in the budget.

Turn the plan into a reporting routine

Give every measure a home

For a small award, a well-kept spreadsheet and a shared calendar are usually enough, as long as one person owns them and you control who can edit them.

Keep everything about each measure in one place, from what it means and its target to where the data comes from, who collects it and when. Store the evidence where the person writing the report can find it. If you’re juggling several awards, grant management software can help with deadlines and records, and it’s worth looking at once the spreadsheet starts creaking.

Your reporting routine should also say who reviews the findings and when. Feedback only improves the service if someone looks at it and decides what to change.

Report shortfalls before they become surprises

Most projects miss a target at some point, because referral partners change, costs rise and people have lives outside your project plan. Funders need a clear account of the position and your response.

Use a simple update: original target, actual result, reason, action taken and next review date. If attendance is low, show the numbers. Then explain what you’ve checked, whether you’ve changed session times or referral routes, and when you’ll test the result.

Raise material changes in line with the award conditions. Waiting until the final report or summative evaluation to mention a problem you’ve known about for months makes the relationship harder than it needs to be.

Avoid the mistakes that weaken a plan

The most common problem is measuring activity and calling it change. Thirty workshops delivered may prove you delivered thirty workshops. Your evaluation should test whether that activity led to the change set out in your logic model.

Another is choosing the measure after the project starts. Without a baseline or a consistent question, even good work becomes hard to evidence, so agree your measure and how you’ll use it before the first participant arrives.

Watch for targets that depend on people or partners you haven’t confirmed. Watch, too, for a plan that only gathers praise from those who finished. An assessor is more likely to trust balanced evidence than a stack of glowing quotes with no context.

Finally, keep the plan readable. If an evaluator has to search across five attachments to find your target and evidence method, bring them together.

Check the plan against the whole application

Before submission, compare your evaluation plan with the delivery timetable and budget. Do the numbers match? If you promise 100 participants, is there enough capacity to reach and support them? If you’ll survey people twice, has anyone been given time to do it?

Get the delivery lead, finance lead and bid writer looking at the same version. Check that the route from activities to outcomes in your logic model matches the delivery plan, and that the evidence you’ve promised has the resources to collect it. Can the data be gathered during normal work, or will you need specialist help? Do the report dates fit the funder’s timetable?

This is where a fresh pair of eyes helps. Bidsmithery™ provides an independent grant application review that checks whether the outcomes, evidence and funding case hold together before an assessor sees them. Nobody can promise you a win, but a review can help you find a weak link whilst there’s still time to fix it.

Frequently asked questions

Key takeaways

• Start with the live funding rules and keep your targets consistent across the bid.
• Connect each activity to a defined outcome, measure, starting point and review date.
• Use numbers and participant experience together, within your team’s capacity.
• Name who collects, reviews and reports the evidence.
• Tell the funder early when results change, with a clear plan for what happens next.

A plan your team can stand behind

When that evaluation question appears late in the bid, go back to the work you’re promising. Decide what change you can reasonably show, how you’ll check it and who will keep the evidence in order.

If you want an honest check before submission, book a free fit call to discuss whether Bid Win Rate Accelerator Training or ongoing review support would help your team. An external red review gives you a second pair of eyes on the plan while your team gets on with delivery.