NGO Project Report Format: Report Activities, Results, Finance and Evidence

Editorial responsibility: Vekho P. Ringa · Sources and corrections policy

Documents

Report activities, outputs, utilisation and evidence.

India-focusedEvidence-ledPractical workflow

On this guide Browse sections

Writing a project report a funder can check

Short answer: An NGO project report tells the funder what the project set out to do in the period, what actually happened, what it cost and what changed as a result. Put a one-page summary first, then planned versus actual for each activity, outputs and outcomes with evidence, spending against the approved budget, problems and how you handled them, and the plan for the next period. Always use the funder’s own format if the agreement gives one.

Planned versus actual: how one row should read

Activity	Planned (half-year)	Actual	Variance and reason	Evidence held
Teacher training sessions	6 sessions, 120 teachers	5 sessions, 104 teachers	One session moved to next quarter: exam schedule clash; agreed with funder by email	Attendance sheets, photos with consent, trainer reports
Reading kits distributed	400 kits	400 kits	None	Delivery challans signed by school heads
Spend on training head	₹1,80,000	₹1,52,000	Lower because of the moved session; balance carried forward as agreed	Ledger extract, vouchers

The figures are an illustration. What makes the row useful is the last two columns: a reason the funder can check, and evidence you can produce on the day of a monitoring visit.

Narrative or utilisation certificate?

A project report is the story with numbers. A utilisation certificate is a formal statement of how the money was used, usually in a prescribed form. Many government and CSR funders ask for both, and the two must agree line for line. See the utilisation certificate (UC) format and the wider utilisation and reporting process.

Before you write, re-read the original project proposal; your report should answer the targets it promised. Ready-to-fill report and UC templates are in the grant reporting and utilisation templates, and evidence for beneficiaries is covered in beneficiary records. Looking for the next grant? Browse current funding opportunities.

By Vekho P. Ringa, Editor. Last verified 22 Oct 2026. Sources: the reporting clause of your grant agreement or sanction order, which prevails; the table values are illustrative. General information only, not legal advice.

NGOGrant rule: The free page should give the reader a genuinely usable format and explain how to use it correctly. Paid value comes from deeper registers, trackers, workflows and integrated office systems—not from hiding the basic format.

A project report should allow the reader to understand what was approved, what was actually done, what was spent, what evidence exists and what remains unresolved.

It should reconcile with the project budget, accounts and monitoring records.

1. Recommended project report structure

Project identity
Executive summary
Approved objective
Geography / beneficiaries
Activities planned vs completed
Outputs
Outcomes / progress
Monitoring evidence
Financial utilisation
Variances
Challenges
Safeguarding / grievance / data issues where relevant
Assets
Sustainability / next steps
Annexures

2. Project identity

Project:
Funder:
Agreement / Sanction No.:
Implementation period:
Reporting period:
Location:
NGO:
Project manager:
Report date:

3. Executive summary

One page:

purpose;
period;
major activities;
actual reach/output;
expenditure;
key result;
key challenge;
next action.

4. Planned vs actual

Activity	Planned	Actual	Date / location	Evidence	Variance

Do not hide incomplete activities.

5. Beneficiary reporting

Define the metric.

Separate:

unique beneficiaries;
households;
attendances;
institutions;
repeat services.

Explain how counted.

6. Outputs

Examples:

trainings delivered;
kits distributed;
infrastructure completed;
consultations;
services provided.

These are outputs, not necessarily impact.

7. Outcomes

Where evidence exists, describe changes.

Include:

indicator;
baseline;
target;
actual;
data source;
limitation.

Avoid claiming causation beyond the evidence.

8. Project narrative

For each major activity explain:

purpose;
implementation;
participation;
adaptations;
results;
evidence.

9. Financial utilisation

Use a table:

Budget Head	Approved	Actual	Variance	Explanation

Reconcile to finance records.

10. Releases and balance

Report:

opening balance;
grant received;
interest if relevant;
expenditure;
advances;
closing/unspent balance.

The agreement controls exact treatment.

11. Challenges

Be specific:

access/weather;
recruitment;
procurement;
delayed release;
participant attendance;
permission;
price variation;
data quality.

Explain mitigation.

12. Changes to project

Document:

original plan;
proposed change;
reason;
funder approval;
date;
effect on budget/timeline/outcome.

13. Monitoring and evidence

Index:

attendance;
service records;
photos;
assessments;
invoices;
bank evidence;
asset records;
beneficiary feedback;
partner records.

Do not attach sensitive raw data unless required and secure.

14. Stories

Use case stories with consent/appropriate identity protection.

Do not use one story to claim project-wide success.

15. Assets

Report assets bought from project funds and their current location/use.

16. Next period / closeout

State:

pending actions;
next activities;
risks;
approvals needed;
reporting due;
closeout/refund if project ending.

17. Free project report template

PROJECT REPORT

1. Project Information
2. Executive Summary
3. Project Objective
4. Geography and Beneficiary Definition
5. Activities: Planned vs Actual
6. Outputs
7. Outcomes / Evidence
8. Financial Utilisation
9. Variances / Approved Changes
10. Challenges and Mitigation
11. Monitoring / Safeguarding
12. Assets
13. Next Steps / Closeout
14. Annexures

18. Common mistakes

Planned targets shown as actual.
Beneficiary count has no definition.
Financial figures do not reconcile.
No variance explanation.
Photos used as only evidence.
Challenges omitted.
Project change not linked to approval.
Sensitive data attached unnecessarily.
No report period/version.

Utilization Certificate
Grant Utilisation Guide
Annual Report
M&E Guide
Impact Measurement

Project report questions

How long should an NGO project report be?

Long enough to cover every activity in the agreement, and no longer. For a half-year report on a small project, six to ten pages plus annexures is usually enough (an editorial suggestion).

What if we missed a target?

Say so plainly, give the reason, say what you did about it, and say whether the funder agreed. Funders forgive delays; they rarely forgive surprises.

Can we include beneficiary stories and photos?

Yes, with recorded consent and without identifying children or vulnerable people. One specific story tied to an outcome is worth more than five general ones.

Should the report include the full accounts?

Usually a statement of spending against each approved budget head, with a note on variances. Attach audited statements only when the funder asks.

What is the difference between outputs and outcomes?

Outputs are what you delivered: sessions held, kits given. Outcomes are what changed: reading levels improved, attendance went up. Report both and keep them apart.

Who should sign the report?

The person your agreement names, usually the chief functionary, after the finance lead has checked the figures against the books.

NGOGrant boundary

A project report should reflect genuine programme and finance records. NGOGrant can help organise the report but should not manufacture results.

Practical next steps

Continue with the related task or checklist that fits your organisation. Verify current official requirements before submitting anything.