FCDO donor reporting: what an annual report must contain
Oct 12 2026 · Donor reporting
What FCDO annual reports must cover, the mistakes that get them returned, and a pre-submission checklist that catches them first.
An FCDO annual report is written against the logframe: results for each output and outcome indicator, a short narrative per output, disaggregated data, the means of verification actually used, a risk and assumptions update, and a value for money note. Most reports are returned for the same few reasons: a result with no named source, a narrative that contradicts the table, a target changed without explanation, or aggregate figures that hide who was reached. Keep one source of truth, the indicator tracker, write the prose from those numbers, and flag underperformance with a corrective action rather than dressing it up.
How does an FCDO annual report relate to the logframe?
Most FCDO contracts and grants are managed against a logframe agreed at inception. The annual report is not a separate document; it is that logframe read back to the donor with evidence attached.
Each output and outcome gets a row. Each row carries its indicators. Each indicator carries a baseline, a target, an actual, and the source of the number. If the logframe is out of date, the report will be too, so reconcile the two before you write a word of narrative.
The layout guide at /blog/logframe-template-google-sheets covers the structure, and /store/builder generates a logframe you can reuse across reporting rounds.
What must be in an FCDO annual report?
- Results against every active logframe indicator, with baseline, target and actual.
- A short narrative per output explaining what changed and why.
- Disaggregated data for the groups the logframe already names.
- The means of verification used for each result, named rather than implied.
- A risk and assumptions update, including anything that materialised.
- A value for money note tied to spend and results.
- An honest record of underperformance and the corrective action agreed.
Which mistakes get a donor report returned?
In practice the same handful of problems accounts for most of the back-and-forth between a programme team and a donor desk officer.
| What went wrong | What the reviewer sees | What to do instead |
|---|---|---|
| Result with no named source | An unverifiable claim | Name the means of verification and where the dataset sits |
| Narrative contradicts the table | Two versions of the same year | Write the prose from the tracker figures |
| Target changed with no comment | A question mark over data integrity | Footnote the revision and who approved it |
| Aggregate-only reporting | No evidence of who was actually reached | Disaggregate by the categories in the logframe |
| Everything reported as on track | A report the reviewer cannot trust | Flag shortfalls with a corrective action and a date |
Written for M&E professionals. Not a guarantee of accuracy — always verify every claim against its source, and let a named human sign off. Get the free handbook.