Reporting to Funders After You Win: Narrative and Financial Reports

Many organisations put enormous energy into winning a grant, then treat reporting as an administrative burden to survive later. This is risky. After approval, your reports become the main evidence that your organisation can manage resources responsibly, learn from implementation and communicate honestly with a donor.

For African NGOs, social enterprises, startups, SMEs and research teams, good reporting is not about writing long documents or hiding problems. It is about answering three questions clearly: what did you do, what changed, and how was the money used? If your narrative and financial reports tell the same story, funders are more likely to trust your systems, even when the project faced delays or adjustments.

Start reporting before the first activity

The best reports are built during implementation, not written in panic two days before the deadline. As soon as you receive an award letter or grant agreement, read the reporting requirements carefully. Note the due dates, templates, eligible cost rules, branding requirements, currency instructions, supporting documents needed and who must sign off each report.

Create a simple reporting calendar and share it with programme, finance, procurement, monitoring and leadership staff. In smaller organisations, one person may play several roles, but the responsibilities should still be clear. A finance officer should not be discovering activity changes after the money has already been spent; equally, the programme lead should not be writing results that finance cannot verify.

At the start of the grant, set up folders for evidence and label them consistently. This can be as simple as separate digital folders for attendance lists, photos, procurement documents, receipts, bank records, activity reports and beneficiary feedback. For organisations working across states, counties or districts, agree how field teams will submit records and by when.

• Read the grant agreement and reporting template before implementation begins.
• List every report due date and set internal deadlines at least a week earlier.
• Agree who prepares, reviews and approves each section.
• Create one shared filing system for programme and finance evidence.
• Hold short monthly check-ins between programme and finance teams.

Writing a narrative report that tells the truth clearly

A narrative report should explain progress against the approved project plan. It is not a public relations brochure and it is not a place for vague claims. Funders want to understand what activities were delivered, who participated, what outputs were achieved, what early changes are visible and what challenges affected implementation.

Use the structure provided by the funder if there is one. If there is no template, organise the report around the approved objectives or work packages. For each objective, describe the planned activity, what actually happened, where it happened, who was reached and what evidence supports your statement. Replace broad phrases such as “many women were empowered” with specific descriptions such as “women entrepreneurs completed business record-keeping sessions and developed simple cashflow sheets for their enterprises”.

Do not hide delays or underperformance. A good narrative report explains the reason, the corrective action and the effect on the project timeline or budget. For example, if community mobilisation took longer than expected because local leaders requested additional consultation, say so and explain how the team adjusted. Honest reporting builds more trust than pretending everything was perfect.

• Link each update to the approved objectives and indicators.
• Use plain language and avoid excessive jargon.
• Include beneficiary voices only with consent and dignity.
• Separate completed activities from planned next steps.
• Explain challenges with actions taken, not excuses.

Building a financial report that matches the story

The financial report shows how grant funds were spent in relation to the approved budget. It should not be prepared in isolation by the finance team at the last minute. If the narrative report says three training sessions were held, the financial report should show reasonable related costs, such as venue, materials, transport, facilitation or refreshments, depending on the approved budget. If only one session happened, the spending pattern should reflect that reality.

Most funders expect expenditure to be reported by budget line, with a comparison between approved budget, amount spent during the period, cumulative spend and remaining balance. Some may also require reporting by activity, output, location or funding tranche. Follow the required format exactly. If the funder asks for local currency and grant currency, use the agreed exchange rate method and keep a record of how conversions were calculated.

Variance explanations are especially important. A variance is the difference between what was budgeted and what was actually spent. Small differences may be normal, but significant underspending or overspending should be explained. Avoid one-word explanations such as “inflation” or “delay”. Give enough detail for the funder to understand whether the change affects delivery and whether prior approval is needed.

• Check that every cost is eligible under the grant agreement.
• Keep receipts, invoices, payment vouchers and bank evidence together.
• Reconcile the report with bank statements and accounting records.
• Explain variances in clear, practical language.
• Request approval before moving funds if the agreement requires it.

Make narrative and finance teams report together

Many reporting problems happen because programme and finance teams work from different information. The programme team may report activities that finance has not paid for, while finance may charge costs to a budget line that the programme team cannot explain. This creates confusion and can raise questions about internal controls.

Before submitting any report, hold a joint review meeting. Compare the activity list with the expenditure report. Confirm dates, locations, participant numbers, procurement status and outstanding payments. If an activity was postponed, ensure the financial report does not show full delivery costs unless they are legitimate advance payments. If equipment was purchased, confirm that it appears in the narrative where relevant and is recorded in the asset register if required.

Leadership should review the final report for consistency, not just grammar. The authorised signatory is confirming that the organisation stands behind both the narrative and the numbers. For multi-partner projects, agree an internal cut-off date for partners to submit their reports, because late partner documents can delay the lead organisation’s submission.

• Do the activities reported match the costs charged?
• Do participant numbers align with attendance records and logistics costs?
• Are procurement documents complete and properly approved?
• Are budget lines used consistently with the approved budget?
• Are partner reports reviewed before consolidation?

Common mistakes that weaken funder confidence

One common mistake is submitting reports that are too general. A funder should not have to guess what happened. Statements like “stakeholders were engaged” need detail: which stakeholders, for what purpose, through which activity and with what result? Clear reporting does not mean writing pages of unnecessary background; it means giving enough evidence to support your claims.

Another mistake is treating financial reporting as a receipt bundle. Receipts are important, but they do not explain the financial position of the grant. A strong financial report summarises expenditure, shows balances, explains variances and connects costs to implementation. Supporting documents should be organised and available, not scattered across WhatsApp messages, personal email accounts or paper files no one can find.

A third mistake is waiting until the deadline to raise problems. If you need a no-cost extension, budget realignment or change in activity approach, communicate early and follow the funder’s approval process. Many funders understand that implementation environments can change, but they expect to be informed before major decisions are made, not after funds have already been spent differently.

• Do not copy proposal language without updating it to actual implementation.
• Do not exaggerate results or count the same participants carelessly.
• Do not submit figures that differ from your accounting records.
• Do not move funds between budget lines without checking approval rules.
• Do not ignore feedback from previous reports.

A simple report review checklist

Before you submit, give yourself time for a final quality check. This is where many avoidable errors can be caught: missing signatures, inconsistent totals, wrong reporting dates, unsupported claims or unexplained budget balances. If possible, ask someone not involved in drafting to read the report. Fresh eyes often notice gaps the project team has become too close to see.

Keep a copy of everything submitted, including email confirmations and any funder feedback. After submission, do not close the folder and forget it. Use the reporting process as a management tool. What did the report reveal about delays, cost pressures, community feedback, staffing gaps or procurement bottlenecks? Strong organisations learn from reports instead of treating them as compliance documents only.

• Have you used the funder’s latest template and correct reporting period?
• Do the narrative achievements match the approved objectives and indicators?
• Are challenges and changes explained honestly?
• Do financial totals add up across all sheets?
• Are variances explained and supported by records?
• Are all required annexes, signatures and partner inputs included?
• Has management reviewed and approved the final version?

Key takeaway

Reporting to funders after you win is part accountability, part communication and part organisational learning. A clear narrative report shows what happened and why it matters. A clear financial report shows how resources were managed. When both reports align, your organisation demonstrates seriousness, transparency and readiness for deeper partnerships. You cannot guarantee future funding, but you can protect trust by reporting promptly, accurately and honestly.