Community Grants & Projects

Grant impact reports: how to prove your project works

For community groups in Grimsby, Cleethorpes, Immingham and across North East Lincolnshire, a grant impact report is more than the final piece of administration after the money has been spent.

Grant impact reports: how to prove your project works

It is the document that shows whether a safer street, a better-used youth space, a revived community venue or a new partnership has made a practical difference.

That distinction matters. A report that says a project held 12 meetings, installed new lighting or reached 80 residents describes activity. It does not, on its own, show what changed for the people the project was meant to support. Strong community safety grant impact reporting requirements increasingly ask for that next step: the connection between the work funded, the experience of residents and the outcome the grant was intended to deliver.

For a grassroots organisation, this need not mean turning a neighbourhood project into a corporate performance review. It means gathering the right evidence from the beginning, agreeing what success will look like, and telling the story of the work with enough structure that a funder can see its value.

Moving beyond activity counts

Activity counts are useful. They establish that something happened and help a funder understand how a budget was used. The difficulty comes when those counts are treated as proof of impact.

A community safety project might report:

  • 15 evening sessions delivered;
  • 40 young people attending a youth club;
  • 25 residents taking part in a street clean-up;
  • six new volunteers recruited;
  • improved lighting installed at a troublesome passage;
  • three local organisations joining a partnership.

These are outputs. They sit close to the work itself. They show delivery, reach and, in some cases, good stewardship of the grant. But the more searching question is what those outputs produced.

Did young people return regularly, rather than attend once? Did the street clean-up lead to more residents using the area? Did the lighting change how safe people felt walking home? Did local groups become better able to share concerns and respond quickly? Did the youth club create a reliable alternative to spending unsupervised time outdoors?

Those are outcomes. They describe a change in behaviour, confidence, access, relationships or conditions.

The difference can be expressed simply:

What the project didWhat the report should explore
Held youth sessionsWhether young people attended consistently, felt more connected and had access to a safer evening activity
Installed lightingWhether residents used the route more confidently or reported a change in perceived safety
Ran a residents’ meetingWhether concerns led to agreed action, referrals, environmental improvements or stronger local coordination
Delivered a clean-upWhether the area remained better maintained and whether residents became more willing to use or look after it
Recruited volunteersWhether volunteers remained active and whether the project gained lasting capacity
Created a partnershipWhether organisations shared information, avoided duplicated effort and responded more effectively

A good report includes both sides. Without outputs, the account becomes vague. Without outcomes, it becomes a receipt.

A busy project is not automatically an effective project. The report needs to show what became different because the work took place.

This is particularly relevant when groups are seeking renewal or hoping to apply for another Community Wallet allocation, Safer Streets funding or a related local safety grant. Future funding decisions are rarely based only on whether an activity was popular. Funders want to see a credible line between investment and improvement.

Choosing five to eight measures that fit the work

The strongest reports usually concentrate on a small group of key performance indicators rather than attempting to measure everything. A practical range is five to eight KPIs for one grant report, chosen to match the project’s aims and budget headings.

That number is large enough to show more than one dimension of the work, but small enough for a volunteer-led group to collect consistently. A long list of weak or irregular measures creates the appearance of detail without giving a clear view of performance.

For a community safety initiative, the most useful measures often fall into several families.

Reach and participation

These measures show who engaged with the project and how consistently.

Examples include:

  • number of individual participants, rather than only total attendances;
  • number of repeat participants;
  • age groups or neighbourhoods reached, where appropriate and lawful to collect;
  • attendance or completion rate;
  • number of volunteers who remained active after initial recruitment.

A project that records 100 attendances may have reached 100 people once, or 20 people five times. Those describe different forms of engagement. If the project depends on trust and continuity, repeat participation may be more meaningful than the headline attendance total.

Changes in confidence and perception

Community safety work often aims to alter how residents experience a place. This can be measured through short surveys, structured conversations or regular feedback forms.

Possible measures include:

  • the proportion of participants reporting greater confidence using a route or facility;
  • changes in residents’ perception of safety at a particular time of day;
  • the number of people who say they know where to report a concern;
  • participant confidence in accessing support;
  • changes in young people’s sense of belonging or connection to the area.

A simple before-and-after question can be useful if it is asked in the same way at both stages. The wording does not need to be elaborate. What matters is consistency.

Practical environmental change

Some projects make physical improvements to a place. In that case, the report should record what changed and whether the improvement was maintained.

Measures might include:

  • number of sites improved;
  • completion of agreed repairs or environmental works;
  • number of hazards, obstructions or areas of poor visibility addressed;
  • frequency of follow-up maintenance;
  • resident use of the space before and after the work.

The report should avoid claiming that a new bench, light or cleared area caused a reduction in crime unless the project has evidence capable of supporting that conclusion. It is entirely reasonable to report improved visibility, increased use or stronger perceptions of safety without making a larger claim than the data allows.

Strength of partnership and local capacity

Grassroots safety work often succeeds because several organisations contribute different kinds of knowledge. A residents’ group may understand the street-level concerns, a youth organisation may have trusted relationships with young people, and a local venue may provide a dependable base.

Partnership measures can include:

  • number of active partner organisations;
  • number of joint actions completed;
  • referrals made and followed up;
  • shared training or volunteer development;
  • response time between an identified concern and agreed action;
  • evidence that the partnership will continue after the grant period.

A list of logos is not evidence of partnership by itself. The report should explain what each organisation contributed and what became possible through the collaboration.

Continuation and sustainability

Long-term impact is often less visible at the point when a grant closes. Still, a report can record early signs of continuation.

Useful measures include:

  • whether the activity continued after grant funding ended;
  • number of volunteers or organisations carrying the work forward;
  • additional funds or in-kind support secured;
  • whether a venue, session or service became part of a regular local offer;
  • whether the project was adopted or repeated elsewhere.

These measures should be proportionate. A small East Marsh residents’ project does not need to demonstrate systemic change across North East Lincolnshire to have delivered meaningful value. It needs to show the scale of change that was realistic for its funding, timescale and purpose.

Building the evidence framework before the project begins

The easiest time to decide how success will be measured is before the first session, clean-up or installation. Once a project is underway, groups are often busy delivering the work, and the baseline information that would have made the final comparison useful may no longer be available.

A straightforward evidence framework has four parts:

1. The starting point: what was happening before the grant?

2. The intervention: what did the project change or provide?

3. The immediate result: what happened during or shortly after delivery?

4. The continuing effect: what remained in place after the funded activity ended?

The starting point does not need to be a large research exercise. It might consist of attendance records from an existing service, a short resident survey, a map of reported problem locations, photographs taken before environmental work, or a simple count of how many people were using a space at particular times.

The baseline should match the project. If the grant is for a youth club, record existing attendance, opening hours and the number of young people who can currently access the provision. If the project is focused on a poorly used public area, document its condition, use and residents’ views before work begins. If the project is about local coordination, record which organisations are already involved and how concerns are currently passed between them.

A report can then compare like with like. The comparison may be numerical, descriptive or both.

Use consistent units

Small inconsistencies can make otherwise useful evidence difficult to interpret. Decide in advance how the project will count:

  • people versus attendances;
  • sessions versus hours delivered;
  • referrals made versus referrals completed;
  • sites improved versus individual improvements at each site;
  • bags of waste collected versus an agreed volume or weight;
  • volunteers recruited versus volunteers still active at the end.

If a funder asks for a particular unit, use that unit throughout the report. Where a conversion is necessary, record the method used rather than changing figures informally. Even something as ordinary as reporting waste removed can become confusing if one part of the record uses bags, another uses vehicle loads and another uses estimated volume.

The same principle applies to money. Each KPI should connect to a budget heading where possible. A report is more persuasive when it shows not only that an outcome was achieved, but how the funded resources supported that outcome.

Separate evidence from interpretation

A photograph of a cleared alleyway is evidence of a physical change. A resident survey may provide evidence of perceived safety. An attendance register shows participation. The conclusion that the project improved confidence is an interpretation drawn from those pieces of evidence.

That interpretation may be well supported, but it should not be presented as if every piece of evidence proves the same thing. A careful report explains the link.

For example, a project could state that improved lighting was installed at an agreed location, that evening use of the route increased during the observation period, and that residents who completed the follow-up survey reported greater confidence. It should then acknowledge that other factors may also have influenced how the route was used.

This is not weakness. It is credible reporting.

Measuring community project success without overclaiming

Community organisations sometimes feel pressure to present every project as an unqualified success. In practice, funders are more likely to trust a report that distinguishes between what was achieved, what is promising and what remains uncertain.

A strong account of measuring community project success can include three levels of result.

Short-term results

These are visible during delivery or soon afterwards:

  • planned sessions completed;
  • equipment or improvements purchased and installed;
  • participants reached;
  • volunteers trained;
  • budget spent against agreed headings;
  • partnerships meeting as planned.

Short-term measures answer the question: did the project deliver what it set out to deliver?

Mid-term results

These appear after participants have had time to engage with the work:

  • repeat attendance;
  • improved confidence;
  • greater awareness of support routes;
  • more consistent use of a facility;
  • residents taking part in follow-up activity;
  • organisations working together on specific concerns.

Mid-term measures answer: did the activity make a meaningful difference to the people and place it was intended to serve?

Longer-term results

These may take months to emerge and may require follow-up after the grant period:

  • a youth service continuing through volunteer effort or new funding;
  • a public space remaining maintained;
  • stronger local reporting and referral routes;
  • a partnership becoming part of normal neighbourhood practice;
  • a project model being adopted by another area;
  • changes in the way local stakeholders respond to recurring concerns.

Longer-term measures answer: did the project leave behind capacity, confidence or a safer pattern of use?

Not every grant can demonstrate all three levels. A short project may be able to show delivery and early outcomes but not sustained change. The honest approach is to state what the reporting period can support and identify how continuation will be monitored.

Bringing numbers and resident experience together

Numbers provide structure, but they do not explain what the change felt like on the ground. A resident’s experience can show why an intervention mattered, what barrier it addressed or why a particular approach gained trust.

That evidence should be gathered carefully. Do not invent direct quotations or present a polished personal story as representative of the whole neighbourhood if it is based on one conversation. Instead, describe the feedback accurately and make clear how it was collected.

For example, a report might explain that residents who completed a follow-up survey commonly described the area as easier to use in the evening, while several participants also raised concerns about maintenance. That is more useful than claiming that everyone felt safer.

Qualitative evidence can come from:

  • short participant feedback forms;
  • recorded comments from a residents’ meeting;
  • reflective notes from youth workers or volunteers;
  • case studies with consent;
  • photographs showing a change in the environment;
  • observations recorded at agreed intervals;
  • partner feedback on referrals or joint work.

The most effective narrative follows a simple line:

1. What was the local concern?

2. Who helped shape the response?

3. What did the grant make possible?

4. Who took part?

5. What changed?

6. What evidence supports that conclusion?

7. What still needs attention?

This keeps the human story connected to the grant’s purpose. It also reflects the way community work actually happens in North East Lincolnshire: through trust built over time, practical collaboration and residents who often notice a problem long before it appears in a formal dataset.

The strongest evidence is not the most dramatic evidence. It is the evidence that can be traced from a real local need to a funded action and then to a change that residents can recognise.

Reporting safety initiative outcomes in a way funders can follow

A funder should not have to reconstruct the project from scattered notes, photographs and invoices. The report needs a clear route through the work.

A useful structure is:

The original need

Describe the issue in local and practical terms. Identify the street, facility, group or pattern of use involved where it is appropriate to do so. Explain how the concern was identified and who contributed to understanding it.

Avoid turning the opening into a catalogue of crime. Community safety is broader than crime figures alone. It includes confidence, visibility, relationships, access to support, positive use of public space and the resilience of local networks.

The funded response

Set out what the grant paid for and why that response was chosen. Link expenditure to the project’s aims. If the approach changed during delivery, explain why.

A change is not automatically a failure. A venue may become unavailable, a partner may need to adjust its role, or residents may identify a more urgent location for a small environmental improvement. The report should show how the decision was made and what effect it had on delivery.

The results

Use the selected KPIs rather than reproducing every note collected by the project. For each measure, state:

  • the baseline, if one was available;
  • the target or intended result;
  • the actual result;
  • the evidence used;
  • any limitations in the comparison.

A compact table can make this easy to read:

IndicatorStarting pointResultEvidenceWhat it suggests
Repeat participationRecorded before deliveryAttendance tracked across the projectSign-in recordsWhether engagement became regular
Perceived safetyInitial participant feedbackFollow-up feedback after activityShort surveys or structured conversationsWhether confidence changed
Local coordinationPartners and referral routes identified at launchJoint actions completedMeeting records and action logsWhether collaboration became practical
Environmental conditionPhotographs and site notesFollow-up site reviewDated photographs and inspection notesWhether the improvement was completed and maintained
ContinuationNo agreed activity beyond grant periodFollow-up activity or new support securedPartner confirmation and recordsWhether capacity remained after funding

The next step

Close by explaining what will happen after the report. Will volunteers continue? Will partners meet again? Is further funding needed? Will the group collect another follow-up measure?

This is where a report becomes useful to the community as well as to the funder. It turns a completed grant into a learning record for the next piece of grassroots work.

Evidence gathering for grant renewal

When a group is seeking renewed funding, the previous report becomes part of its case for continuity. The new application should not simply repeat the old project description. It should show what was learned and how the next phase responds.

Evidence that can strengthen a renewal application includes:

  • a clear comparison between the original baseline and later findings;
  • participant retention or repeat engagement;
  • examples of partnership activity that continued beyond the funded period;
  • evidence that residents helped shape changes;
  • a record of what did not work and how the approach was adapted;
  • a realistic plan for collecting the next set of measures;
  • a direct connection between the proposed budget and intended outcomes.

For example, if a project found that one-off community events attracted attention but did not lead to regular engagement, the next application might propose a smaller number of recurring sessions with a named volunteer or partner responsible for follow-up. If an environmental improvement was completed but maintenance became a problem, the new plan might include a stewardship arrangement rather than only more installation work.

This is the difference between repeating an activity and developing a project.

Funding accountability in North East Lincolnshire should not be understood as a demand for paperwork detached from local life. Proper accountability protects the credibility of community organisations and helps funders direct resources towards work that is useful, trusted and capable of lasting. It also gives residents a clearer voice in deciding what progress looks like.

Being open about challenges strengthens the report

A project rarely proceeds exactly as planned. Attendance may be lower than expected during the first few sessions. A partner may have less capacity than anticipated. An installation may be delayed. A survey may receive too few responses to support a firm conclusion.

Leaving these details out can make a report appear neat, but it also leaves the funder with less confidence in the account. Transparency is more persuasive than a claim of effortless success.

A constructive explanation should cover:

1. What happened: state the difficulty without disguising it.

2. Why it happened: give the relevant context, avoiding excuses.

3. What the project did: describe the adjustment or corrective action.

4. What changed as a result: show whether delivery or outcomes were affected.

5. What will be done differently: turn the experience into a practical lesson.

Suppose evening attendance was lower than expected because the original venue was difficult for participants to reach. A credible report can explain the attendance figures, record the move to a more accessible location and show whether participation improved afterwards. That is more valuable than presenting the total attendance without context.

The same applies to data gaps. If no baseline survey was completed, the report should say so and use the evidence that is available, such as attendance records, site photographs, partner observations and follow-up feedback. It can then commit to collecting baseline information at the start of the next phase.

No community project can isolate every cause of a change. Wider policing activity, seasonal patterns, school holidays, economic pressures and other local initiatives may all affect how residents experience a place. A good report recognises that context while still making a measured case for the project’s contribution.

A practical reporting rhythm for small community groups

The work becomes much easier when reporting is treated as part of delivery rather than a task left until the final week.

A manageable rhythm might look like this:

  • Before launch: agree five to eight KPIs, define the units, record the baseline and decide who will collect each measure.
  • During delivery: keep attendance, spending, volunteer and activity records as the work happens.
  • At the midpoint: review what the early evidence shows and adjust delivery if participation or reach is not developing as expected.
  • At completion: collect follow-up feedback, photograph completed work, reconcile the budget and record outcomes against the baseline.
  • After completion: check whether the activity continued, whether the improvement was maintained and whether partners or volunteers remained involved.

Responsibility should be shared. One person may hold the financial records, another may manage attendance, and a partner organisation may gather participant feedback. The group does not need a specialist evaluator, but it does need an agreed method and a named person who can bring the information together.

Keep consent and privacy in view, particularly when working with children, young people or people in vulnerable circumstances. Use only the personal information needed for the reporting purpose, store it securely and avoid including identifying details in a public report unless there is clear permission to do so.

The report as part of the neighbourhood’s memory

A well-written impact report does more than protect future funding. It records the collective effort behind a change that might otherwise be easy to overlook.

The improved route through Cleethorpes, the better-used youth space in Grimsby, the partnership connecting residents and voluntary organisations in Immingham, the small intervention that gives people a reason to use a neglected place again: these are not isolated transactions. They are part of the steady revitalisation of neighbourhood life.

That is why the most useful report combines precision with warmth. It should contain figures that can be checked, dates and records that explain what happened, and resident experience that shows why the work mattered. It should distinguish activity from outcome, immediate progress from lasting change, and evidence from assumption.

For groups preparing their next application, the first step is straightforward: choose the measures before the work begins. Keep them few enough to manage, local enough to mean something and closely tied to the grant’s purpose. Record the starting point. Review progress while there is still time to act. Then report not only what the project delivered, but what the community was able to do because the project existed.

That is the clearest proof of a community safety project’s value: not a perfect story, but a credible account of shared work, measurable change and the resilience to keep improving the place together.

FAQ

What is the difference between an output and an outcome in a grant report?
An output describes the activity itself, such as the number of sessions held or lighting installed. An outcome describes the resulting change in behavior, confidence, or conditions for the people the project supports.
How many performance indicators should a community project track?
A practical range is five to eight key performance indicators. This number is large enough to show different dimensions of the work while remaining manageable for a volunteer-led group to track consistently.
Why is it important to establish a baseline before starting a project?
A baseline provides a starting point for comparison, allowing you to measure what changed because of your project. Without it, it is difficult to demonstrate the specific impact of the grant intervention.
Should I include project failures or challenges in my final report?
Yes, being open about challenges strengthens a report. A constructive explanation of what happened, why it happened, and how you adjusted your approach is more persuasive to funders than claiming effortless success.
How can I prove that a physical improvement, like new lighting, reduced crime?
You should avoid claiming that a specific improvement caused a reduction in crime unless you have evidence to support that conclusion. It is more accurate to report on improved visibility, increased use of the space, or changes in residents' perceptions of safety.