Ask a programme officer in Kampala what they spend most of their week on and the answer is rarely programme work. It is reporting: quarterly narratives, indicator tables, log-frame updates, variance explanations, and the same three paragraphs rewritten for four donors who each want them in a different template. It is the most obvious candidate for AI in the entire development sector, and it is also the one where getting it wrong has the most immediate consequences, because the material is beneficiary data and the counterparty is an auditor.
Both things can be true. Here is where the line sits.
Key Takeaways
- The reporting burden is real and largely mechanical, which makes it a strong AI candidate on process grounds.
- Beneficiary data is personal data and frequently special personal data. It does not go into a general AI tool, and that single rule resolves most of the risk.
- Almost all of the useful work can be done on de-identified or aggregated data, which is what your report contains anyway.
- Check the grant agreement before the tool. Some donors now carry AI clauses requiring disclosure, and a few prohibit AI use on their material entirely.
- Fabricated figures are the specific failure mode that ends relationships here. Every number in a donor report is traced to its source, every time.
Start with the grant agreement, not the tool
This is the step almost everyone skips and it takes an afternoon. Read the AI and data clauses in every live agreement you hold. Donor practice has moved quickly and inconsistently, and the range of positions in circulation is wide: silence, a disclosure requirement, a requirement that personal data not be processed by third-party tools, and in a small number of cases an outright prohibition on AI use in producing deliverables.
Those obligations sit above any internal policy you write. The person managing the relationship is responsible for knowing them, and “we did not realise” is not a position anyone wants to be in during an audit. Where the agreement is silent, ask the programme contact rather than assuming. Most will answer, several will be glad you asked, and the exchange itself is a small credibility gain.
The line: aggregate yes, individual no
Nearly all of the reporting work an organisation wants help with concerns aggregates. How many people were trained. What the disaggregation by district and gender looks like. Why the figure is below target. What changed since the last quarter. None of that requires a single identifiable person to leave your systems.
| Safe to work on with AI assistance | Not without a tool cleared for it |
|---|---|
| Aggregate indicator tables with no names | Beneficiary lists, enrolment registers, attendance sheets with names |
| Your own previously published narratives | Case studies naming a real individual, before consent and de-identification |
| Donor templates and guidance documents | Photographs of participants |
| Draft variance explanations you have written | Health, disability, HIV status, gender-based violence records, or anything in the special categories |
| Restructuring the same content into a second donor’s format | Anything a partner shared with you under an agreement limiting its use |
The right-hand column is not a prohibition on ever using AI with that data. It is a prohibition on doing it casually, on a consumer account, without anyone having checked. The routes that exist are the same three as everywhere else: strip the identifiers first, use a tool with contractual commitments covering the category, or keep the work inside systems you control.
One caution on de-identification that is specific to this sector. Removing names is not sufficient when the remaining detail identifies someone anyway. A district, an age, a disability and a livelihood can identify one person in a small programme as effectively as a name. The test is whether someone who knows the community could work out who it is.
What actually saves time
In the reporting work we have seen, four tasks carry most of the saving, and none of them involves individual records.
Reformatting between donor templates. The same programme, the same quarter, four different structures. This is mechanical, high volume, and the outputs are easy to check because the content already existed.
First-draft variance narratives. You know the number missed target and you know why. Turning that into three paragraphs in the register a donor expects is drafting work, and a person edits it afterwards.
Consolidating field submissions. Six district reports in six styles into one house voice. Again, the content exists and the work is structural.
Proposal reuse. Finding what you wrote about a theme two years ago, in your own archive, and adapting it. This is search and synthesis over your own material, which is among the safest and most valuable uses available.
Notice what is absent: analysis that produces new figures. Which brings us to the failure mode.
The failure mode that ends relationships
These systems produce numbers, citations and references that look correct and do not exist. In most contexts that is embarrassing. In donor reporting it is a finding.
An indicator figure that was never in the data, a citation to a policy document that does not exist, a beneficiary total that does not reconcile with the enrolment register. Any one of those in a submitted report is the kind of thing that triggers a verification exercise, and a verification exercise triggered by a fabricated number is very hard to recover from, because the auditor’s next question is what else was fabricated.
The rule that prevents this is simple and non-negotiable. Every number in a donor report is traced to its source before submission. Not spot-checked. Traced. The same applies to every citation and every reference to a policy, a standard or a previous report. If a figure cannot be traced, it does not go in, regardless of how confident the sentence around it sounds.
This is not a burden AI created. Programme staff have always been expected to do it. What changes is that the drafting is now fast enough that the checking becomes the bottleneck, and organisations that do not notice this will report a time saving that is partly a shift of risk.
Disclosure, and why it is worth volunteering
Where a donor requires disclosure of AI use, disclose. Where the agreement is silent, consider volunteering it anyway, because the alternative position is worse. An organisation that mentions in its methodology note that drafting assistance was used, with human verification of all figures, is in a strong position if asked. An organisation that says nothing and is asked later is in a weak one, regardless of how careful it actually was.
The sentence does not need to be elaborate. Something to the effect that AI assistance was used in drafting and formatting, that all data and figures were verified against source records by named staff, and that no beneficiary personal data was processed by external tools. If all three of those statements are true, you have described good practice rather than confessed to anything.
The compliance floor for an organisation doing this
- Read the AI clauses in every live agreement. One afternoon.
- Write the red list, with beneficiary data and special categories at the top of it.
- Name a data protection owner. Uganda’s Data Protection and Privacy Act 2019 and its 2021 Regulations apply to your beneficiary records regardless of which tool touches them, and there is a registration obligation with the Personal Data Protection Office that carries a criminal penalty. Establish your position on it.
- Buy business-tier accounts for the staff who need them, so nobody has a reason to use a personal one.
- Adopt the tracing rule and put it in writing: every figure traced to source, every citation opened.
- Brief the team in person once, and again in three months.
That is roughly a fortnight of effort and it costs less than one quarter of the reporting time it protects.
The uncomfortable question worth asking anyway
If AI removes a third of the reporting burden across a programme team, what happens to that third? In an organisation that is genuinely stretched, it goes back into programme work, and that is the whole case. In an organisation where reporting had quietly become the job, the freed time will surface a harder conversation about what the team is for.
That conversation is not caused by AI, and it is better to have it deliberately than to have it arrive as an unexplained capacity surplus in a funding cycle where someone is already looking for savings. Decide in advance which it is, and say so when you present the numbers. A board or a donor will ask, and “efficiency” is not an answer.
Sources
- Data Protection and Privacy Act 2019 (Uganda) and the Data Protection and Privacy Regulations 2021, including the registration obligation under section 29 and regulation 15(1).
- Published guidance from Uganda’s Personal Data Protection Office on registration of data collectors, processors and controllers.
Position stated as at 21 August 2026. This is not legal advice, and donor requirements vary by agreement. Read yours.