Grant Reporting After You Win

The sector spends enormous energy on writing grant applications and almost none on what happens after one succeeds. Reporting is treated as an administrative obligation, delegated to whoever has capacity, and completed close to the deadline from whatever records exist.

That is a missed opportunity and a quiet risk. Grant reporting is one of very few moments when a funder is guaranteed to read something you wrote, and it is the single largest determinant of whether they fund you again.

Why reporting decides the next grant

Funders make renewal decisions on evidence, and the report is the evidence. An organisation that reports clearly, on time, with honest treatment of what did not work, builds a track record that makes the next application substantially easier.

The reverse is equally true and less visible. A vague, late or defensive report rarely produces a confrontation. It produces a declined application eighteen months later with a polite explanation about a competitive round, and the organisation never learns why.

There is an internal reason too. Reporting forces an organisation to look at whether the programme actually achieved what was intended, which is a question that otherwise gets deferred indefinitely. Organisations that report well tend to deliver better, because the reporting closes the loop.

Setting up on day one

The single largest determinant of report quality is what was collected during delivery. Organisations that begin thinking about the report in the final month can only describe what happened to be recorded, which is rarely what the funder asked about.

1. Read the reporting requirements before the work starts, not before the deadline. They are in the agreement.
2. Map each required outcome to a data source. If a required figure has no source, you have found the gap while there is still time.
3. Set up collection inside delivery, so attendance, feedback and outcomes are captured as they happen.
4. Diarise the deadlines, including interim reports, and set an internal date two weeks earlier.
5. Name one owner. Reports that belong to everyone get written by whoever is least busy in the final week.
6. Start a running log immediately, capturing changes, decisions and anything notable as it occurs.

That running log is worth more than any template. Six months later nobody remembers why the delivery model changed in March, and the log turns a defensive explanation into a considered one.

What funders are actually looking for

Funders read reports with a small number of questions in mind, and answering them directly is most of the job. Did the work happen as described. Did it achieve what was intended. Was the money spent as agreed. What did you learn. Can we trust this organisation with more.

Answer in the funder’s structure and terminology. Reorganising their questions into your preferred narrative makes a reader work to find what they asked for, and it reads as avoidance whether or not that is intended.

Writing the narrative section

The narrative should be specific, structured against the agreed outcomes, and readable by someone who does not know your organisation. Assume the reader has not looked at your application since it was approved.

Lead each section with the answer. “We delivered 34 of the 40 planned sessions” followed by explanation is far stronger than three paragraphs of context arriving at the number. Funders read many reports and value directness.

Use one or two concrete examples rather than several general claims. A single participant’s trajectory, described specifically and with consent, does more to evidence outcome than a paragraph of adjectives, which we cover in our guide to impact reporting.

“Funders are not persuaded by adjectives. They are persuaded by numbers with denominators and by one story specific enough that it could only be true.”

The financial report

The financial section should show budget, actual and variance by line, with explanation for material differences. Two errors recur across the sector and both are avoidable.

The first is a financial report that does not reconcile with the narrative. If the narrative says a workshop series ran at reduced scale and the budget shows full spend on facilitation, the reader now has a question you did not answer, and the whole report is read more sceptically.

The second is allocating costs differently from the application without saying so. Moving spend between lines is often perfectly reasonable and it is not reasonable to do silently, because it can appear as though funds were used for a purpose the funder did not agree.

Where restricted funds are involved, ensure your accounting has tracked them separately throughout. Reconstructing restricted spend at reporting time is difficult, error-prone and exactly the situation good financial management exists to avoid.

When things did not go to plan

Programmes deviate from plan. Funders know this, have read hundreds of reports, and are considerably more concerned by a report that claims everything went exactly as intended than by one describing genuine difficulty.

Report variance in three parts: what differed, why, and what you did about it. The third part is what converts a problem into evidence of competence. A programme that under-recruited and responded by changing its outreach approach demonstrates something valuable.

Tell them early where the variance is significant. A funder who learns in the final report that the programme changed shape in month two will reasonably ask why they were not told, and that question is harder to answer than the original change.

Underspend, and what to do about it

Underspend makes organisations nervous and it is usually manageable. What causes problems is not the underspend itself but discovering it late and handling it silently.

Raise it as soon as it is apparent. Many funders will agree to a variation, an extension, or a redirection of the remaining funds to a related purpose. Almost none will agree to any of that after the grant period has ended.

Be prepared to return unspent funds if that is the outcome, and treat it as a normal event rather than a failure. An organisation that returns money cleanly and explains why is in a considerably better position than one that finds a way to spend it in the final fortnight.

Reporting as relationship management

The report is the formal moment in a relationship that should have informal moments too. Organisations that only contact a funder at reporting deadlines are managing a transaction; those that maintain light contact are managing a relationship.

Include something the funder cannot get elsewhere. Frontline organisations see changes in community need long before published research does, and funders value that intelligence highly. A short section on what you are observing turns you from a grantee into a source.

Ask one specific question in every report. Not a general offer to discuss, but something concrete: whether they would be interested in a longer-term proposal, whether they know others working on this, whether a particular finding is useful to them. It invites a reply, and replies are how relationships develop.

Systems for organisations with several grants

Once an organisation holds three or four grants simultaneously, reporting becomes a coordination problem. Different funders want different formats, periods and outcome definitions for work that overlaps considerably.

The mapped outcomes framework is the item that saves the most work. Collecting data once and reporting it in several formats is dramatically easier than running parallel collection for each funder, and it also stops the same programme being described inconsistently.

Interim reports, and why they are the useful ones

Interim reports get treated as a lesser version of the final one, completed quickly because nothing has finished yet. They are actually the more valuable document, because they arrive while there is still time to change something.

Use them to surface difficulty early. A programme recruiting below target at the halfway point is a conversation. The same fact in a final report is a result, and the funder’s only available response is to note it when considering the next application.

Interim reports are also where you build the relationship that makes the final one easy. A funder who has already heard about a challenge and your response reads the final report as confirmation rather than as news, which changes how it lands entirely.

Where a funder does not require an interim report, consider sending a short one anyway. Half a page at the midpoint, unprompted, is unusual enough to be remembered and costs almost nothing.

Consent, privacy and participant stories in reports

Grant reports frequently include participant stories, and the consent behind them is often thinner than it should be. A person who agreed to a photograph at an event has not necessarily agreed to their circumstances being described in a document sent to a funder.

Get consent specific to the use. Explain who will read it, whether it will be published, and for how long it will be held. Offer control over wording and make declining genuinely easy, particularly where the person is a current service user who may feel obliged.

Anonymise or use composites where the detail is what matters rather than the identity, and label composites clearly as such. A funder is persuaded by a situation being real, not by a name being attached to it.

Handle the data side too. Participant information used in reporting is personal information, and the obligations that apply elsewhere apply here. Collect only what the report needs and keep it no longer than required.

“A story that required someone to describe their worst month, for a document they will never see, deserves more consent than a signature on an event form.”

When a report leads to a decline

Sometimes a good report is followed by a declined renewal. It is disorienting and it is usually not about the report at all: funder priorities shift, rounds become more competitive, or a strategy changes above the level of your relationship.

Ask for feedback anyway, specifically and briefly. Not why were we declined, which invites a general answer, but whether there was anything in the reporting or the proposal they would have wanted differently. Program officers frequently answer that question honestly.

Keep the relationship regardless. A funder who declines this year is a warm prospect in two, and organisations that respond to a decline by disappearing lose the accumulated familiarity that made them credible in the first place.

And check your own diversification. A decline that threatens the organisation is a concentration problem rather than a reporting one, which is the argument in our guide to revenue diversification.

Outputs, outcomes and the difference funders care about

Most weak reports are weak because they count activity rather than change. Outputs are what you did: sessions delivered, people served, meals distributed. Outcomes are what changed as a result: participants housed, confidence increased, isolation reduced. Funders fund outcomes and receive outputs, and the gap between the two is where reports lose their persuasive power.

The practical fix is to decide, before the program starts, what change you expect and what would count as evidence of it. That decision determines what you collect, and collecting the right thing from day one is the difference between writing a report and reconstructing one.

Designing data collection people will actually do

Reporting systems fail for a predictable reason: they are designed by whoever writes the report and used by whoever delivers the service, and those are different people with different pressures.

1. Collect at the point of delivery, not retrospectively. A short form completed at the end of a session is accurate. The same information reconstructed at quarter end is a guess.
2. Ask for the minimum. Every extra field reduces completion. If you would not use a data point in a report or a decision, do not collect it.
3. Use one system, not four. Attendance in a spreadsheet, feedback in a form, case notes in a document and finances elsewhere guarantees that nothing reconciles.
4. Make it possible on a phone, because frontline staff are rarely at a desk.
5. Explain why to the people collecting it. Staff who understand that the data secures next year’s funding for their own role complete it. Staff who see it as administration do not.
6. Build in a quality check, a monthly ten minutes to spot gaps while they can still be filled.
7. Store it lawfully. Personal information about service users carries privacy obligations that vary by jurisdiction, and consent for data collection is not the same as consent to publish a story.

Reporting to several funders at once

Once you hold more than two grants, reporting becomes a scheduling problem as much as a writing one. The organisations that handle it well do one thing differently: they maintain a single internal source of truth and generate funder reports from it, rather than maintaining a separate data trail per grant.

1. Keep one master dataset covering all activity, tagged by funder, program and period, so any report is a filtered view rather than a fresh collection exercise.
2. Build a reporting calendar with every deadline for the year, plus an internal deadline a fortnight earlier.
3. Write a reusable core narrative describing the program, the need and the approach, then tailor the outcomes and figures per funder rather than rewriting from scratch.
4. Watch for double counting. If two funders support overlapping costs or the same participants, be explicit about how you are apportioning, because discovering it later is far worse than declaring it now.
5. Track restricted balances continuously, not at report time, so an underspend is a decision you make in month eight rather than a problem you discover in month twelve.

Closing a grant properly

The final report is the last impression a funder has of you and the first thing they will look at if you apply again. It deserves more care than it usually gets, because by that point the program has ended and everyone has moved on.

1. Reconcile the finances fully before writing, so the narrative and the numbers describe the same project.
2. Handle any underspend explicitly. Ask about carry-forward or return well before the deadline rather than mentioning it in the final report.
3. Include what did not work. Funders read hundreds of reports where everything went to plan and trust the ones that describe a difficulty and what was learned.
4. Say what happens next. Whether the work continues, how it will be sustained, and what would be possible with further support. This is where the next application quietly begins.
5. Thank people specifically, naming the program officer if they were helpful. Relationships are held by individuals.
6. Archive everything in one place: the application, the agreement, all reports, the data and the finances. In three years, someone will need it and nobody will remember where it was.

Getting more out of what you already wrote

A completed grant report contains most of the raw material for several other things your organisation needs, and it is almost always filed and forgotten. Before archiving it, spend an hour extracting the reusable parts.

1. The impact numbers belong in your annual report, your website and your next application.
2. The participant stories, where consent allows, become social content, newsletter items and case studies. Check the consent covers the new use, because consent to report to a funder is not consent to publish.
3. The lessons learned section is the honest core of your next application’s approach narrative.
4. The budget variance analysis tells you what your programs actually cost, which improves every future budget you write.
5. The description of need can be updated and reused rather than rewritten under deadline pressure.
6. The photographs and quotes, gathered during delivery and used once, are usually the scarcest asset you have.

Organisations that build this habit find that applications get faster and better at the same time, because they are assembled from evidence already gathered rather than composed from memory the week before a deadline.

Working with your program officer

The single most underused asset in grant management is the person at the funder assigned to your grant. Organisations treat them as an inbox for reports, when they are usually the one person in the building who can tell you what will and will not be a problem.

The pattern that works is straightforward. Make contact early, before there is anything to report. Ask what a good report looks like to them and whether they can share an example. Then keep them informed when something changes, particularly when it changes for the worse. A program officer who learns about a delay from you in month four can usually help. The same officer learning about it from the final report in month twelve has been made to look uninformed internally, and that is the thing that damages a relationship.

Two boundaries are worth respecting. Program officers cannot promise renewal, and asking repeatedly puts them in an awkward position. And they are usually managing a large portfolio, so contact should be substantive rather than frequent. A short update at meaningful moments, a heads-up when something changes, and a genuine thank-you at the end is the right cadence for most grants.

Where to start

If your reporting currently feels like an emergency each time, change two things before the next deadline. Set up the data collection at the start of the grant rather than the end, deciding then what change you expect and what evidence would show it. And build a single reporting calendar covering every funder, with an internal deadline two weeks ahead of each real one. Those two changes convert reporting from a recurring crisis into a routine task, and everything else in this guide becomes easier once they are in place.

One last thing

Reporting is not administration you do after the work. It is the record of whether the work achieved what it set out to, and it is the only evidence a funder will ever have. Organisations that treat it as a compliance chore write reports that are true and unconvincing. Organisations that treat it as the story of what changed, told honestly including the parts that did not go to plan, build the relationships that fund the next five years.

A note on honesty

The temptation in every report is to present things as having gone slightly better than they did. Resist it consistently. Funders read enormous numbers of reports and develop a reliable instinct for the ones that are managed rather than reported. An organisation that says plainly that recruitment took three months longer than planned, explains why, and describes what it changed, reads as competent. The same organisation reporting full delivery against every target reads as either unusually lucky or not looking closely. Over several grant cycles, honesty is not just the right thing, it is the better strategy.

Frequently asked questions

When should we start preparing a grant report?

On day one of the grant. What you can report is determined by what you collected during delivery, so read the reporting requirements before the work begins and map each required outcome to a data source.

What do funders most want to see?

Delivery against plan, outcomes rather than activity counts, honest explanation of variance, what you learned, and a financial report that reconciles with the narrative.

Should we report things that went wrong?

Yes, with the reason and what you did about it. Funders read many reports and are more concerned by one claiming everything went exactly to plan than by one describing genuine difficulty handled well.

What if we underspend the grant?

Raise it as soon as it becomes apparent. Many funders will agree a variation, extension or redirection during the grant period, and almost none will after it has ended.

How detailed should the financial section be?

Budget, actual and variance by line, with explanation of material differences. It must reconcile with the narrative, because contradictions between the two undermine the whole report.

Can we move money between budget lines?

Often yes, and never silently. Reallocating spend without explanation can appear as though funds were used for a purpose the funder did not approve, which is a trust problem rather than an accounting one.

What if the outcomes turned out to be unmeasurable?

Say so, report what you can evidence, describe what you observed, and explain how you would measure it next time. Redefining the outcome to match what was achieved is considerably more damaging.

How do we manage reporting across several grants?

One shared deadline calendar, one folder per grant, a named owner with a backup, and a single outcomes framework mapped to each funder’s indicators so data is collected once and reported several ways.