Grant reporting: proving you did what you said you would

Grant reporting is the part of funded work that gets planned last and matters most to whether there is a next grant. A report is read by somebody deciding whether the money achieved what the application promised — and the usual problem is not poor writing but missing evidence, because nobody collected the figures the application committed to while the work was happening.

What grant reporting has to contain

• What was delivered against what was promised, in the funder's own terms rather than in yours.
• The numbers the application committed to, counted the way the application defined them.
• How the money was spent against the budget, including underspend, which funders mind less than being surprised by it.
• What changed and why, since almost nothing runs exactly as applied for and honest variance reads better than silence.
• Evidence rather than assertion: attendance records, case notes, feedback, photographs where permitted.
• What you learned, which is the section funders read most carefully and applicants write most carelessly.

Collect the evidence from day one

The commonest failure in this area is retrospective counting. An application promising to support eighty people in six months needs a record of who was supported, from the first week, in a form that can be counted at the end — and reconstructing that from memory and emails is both inaccurate and visibly so. Decide at the start what each committed number means, who records it and where, and the report becomes a summary of existing data rather than a research project in the final fortnight.

Diarise the reporting deadline when the grant is awarded, together with the date you will start writing. Funders generally care more about lateness than about imperfect outcomes, and a report delivered late sets the tone for every future application regardless of what it says.

Handling bad news

1. Tell the funder early rather than in the report — a problem disclosed at the time is a conversation, the same problem in a final report is a failure.
2. State what happened plainly, without euphemism, since experienced funders recognise the euphemisms.
3. Explain what you did in response, which is the part that builds confidence.
4. Give the honest revised number rather than a flattering one; the figures are usually checkable.
5. Say what you would do differently, concretely enough that it reads as a decision rather than as reflection.

Why underspend is worth raising early

Because the options narrow as the period ends. Raised in month three, an underspend can often be reallocated with the funder's agreement to something that extends the work; discovered in the final report, it is simply money returned and a doubt about planning. Most funders are far more flexible during a grant than they appear in their guidance, and almost none are flexible after it has closed.

Ettex Docs is a reasonable home for the report itself, with the version history showing what changed before submission and who approved it. The figures behind it belong in the records collected during the work, since the report should be assembled from those rather than written around them.