Writing Donor and Progress Reports with an AI Assistant: A Step-by-Step Workflow

For civil society organisations, non-governmental organisations (NGOs), and community groups, donor reporting is vital for maintaining funding relationships and ensuring institutional accountability. Yet consolidating fieldwork observations, quantitative indicator datasets, and logframe milestones into a polished narrative is often time-consuming for overstretched field teams. Generative artificial intelligence assistants can streamline this reporting workflow, acting as drafting aids that structure content, turn bullet points into cohesive paragraphs, and rephrase complex indicator tables into plain English.

Using an AI tool for official reporting, however, carries operational risks. If unmanaged, automated tools can distort findings, generate plausible-sounding falsehoods ("hallucinations"), or expose sensitive community data. Establishing a disciplined, step-by-step workflow ensures your organisation retains editorial control, protects beneficiary safety, and submits reports of high factual rigour.

Establishing Data Hygiene and Safeguards

Before entering any monitoring notes into an AI platform, programme managers must enforce strict data protection protocols. The International Committee of the Red Cross (ICRC), in its Handbook on Data Protection in Humanitarian Action (third edition, November 2024), emphasises that data protection is essential for safeguarding human dignity and physical safety in vulnerable contexts. Commercial public AI models frequently store user inputs to train future models, meaning sensitive internal text could inadvertently become accessible outside your organisation.

Civil society teams must clean all raw documentation beforehand. Never upload identifiable beneficiary names, biometric details, phone numbers, precise home addresses, or confidential safeguarding and protection disclosures into an external AI tool. Replace names with pseudonyms or generic roles (for example, "Community Leader A"), round GPS coordinates to broad district levels, and remove any identifiable case study data before drafting begins.

Six Steps for Drafting with an AI Assistant

1. Gather and validate primary data locally: Assemble your monitoring and evaluation sheets, attendance registers, training pre- and post-tests, and financial ledgers in your local office software first. An AI assistant cannot know what took place in your project communities; it can only work with evidence you provide. Completing internal data verification before involving AI ensures you build from verified facts.
2. Structure the document to the donor's template: Load the donor's exact reporting template, word counts, and section instructions into the prompt. Instruct the assistant to generate an empty report outline matching these headings (such as executive summary, context analysis, planned against achieved activities, challenges and adaptations, and indicator progress) to ensure compliance with funder guidelines.
3. Draft narrative sections from field notes: Feed the assistant short, bulleted notes from field monitoring visits, stakeholder meetings, and post-distribution reviews. Instruct the model to draft descriptive paragraphs strictly within the boundaries of those notes. A prompt such as: "Synthesise these five field bullet points from September 2026 into a 150-word narrative paragraph for Section 2. Do not invent any additional activities, dates, or outcomes" keeps the model focused.
4. Translate indicators into plain-language findings: Progress tables filled with baseline values, quarterly targets, and percentage reaches can confuse non-technical reviewers. Provide the indicator data to the model and request a clear prose explanation of what the numbers indicate. Direct the assistant to describe trends without guessing the underlying causes, leaving diagnostic commentary to the programme officer.
5. Cross-examine every number against source sheets: AI models are designed for text sequence generation, not arithmetic verification. As the UK Fundraising Regulator underscored in its artificial intelligence guidance (published in December 2025), institutions remain fully responsible and accountable for all outputs generated by AI tools, including subtle inaccuracies. Cross-check every single figure, budget variance, percentage calculation, and milestone date in the draft by eye against your primary spreadsheets.
6. Log prompts, models, and modifications: Keep a clear institutional record documenting where AI assistance was utilised in the report. Save a text log containing the prompt instructions, date, model version, raw output, and the identity of the staff member who reviewed the final draft. Storing this file in your project archive guarantees transparency should questions arise during an audit or donor evaluation.

Verification, Audit Trails, and Accountability

Human judgment must govern the entire reporting cycle. Non-profit trustees and programme directors carry legal and contractual duties toward funding partners; an algorithm cannot bear accountability for inaccurate progress reporting.

When reviewing the compiled draft, programme teams must edit out generic development platitudes, ungrounded optimism, and excessive adjectives. A high-quality progress report presents an honest assessment of both milestones reached and operational bottlenecks encountered. Ensure that operational delays, supply-chain interruptions, or community pushback are accurately contextualised in your own voice rather than smoothed over by automated phrasing.

Checklist

• Primary monitoring records, financial ledgers, and participant numbers are consolidated and vetted locally before any AI interaction.
• All personally identifiable beneficiary information, GPS coordinates, and sensitive case notes are thoroughly removed or anonymised.
• The assistant is provided with the donor's exact template headings and instructed to operate solely within the supplied notes.
• Every numeric figure, percentage, and expenditure amount in the text has been reconciled against original source databases.
• The narrative has been edited by programme staff to remove vague buzzwords, ensure balanced reporting of setbacks, and preserve organisational voice.
• An internal audit log recording the AI model used, prompt texts, generated drafts, and reviewing staff member has been archived.