NGO Programme Reporting in Kenya: Make the Evidence Traceable

A funder asks how many unique people your programme reached. One county submits attendance totals, another counts households, and a third sends photographs of registers. The immediate problem is not the absence of a dashboard. It is that the numbers answer different questions.

For a development programme operating across sites or funders, a reporting system should make evidence traceable from field record to approved indicator. Start there before deciding to replace Excel or build a custom platform.

Agree the indicator before designing the form

Create an indicator sheet with the definition, unit, inclusion and exclusion rules, reporting period, source, owner, review steps and required disaggregation. Explain whether repeat participation counts once or on every occasion. If partners contribute data, agree the definition together.

Keep activities, outputs and outcomes distinct. Training delivered, people trained and a subsequent change in practice answer different questions. The OECD's 2023 evaluation glossary provides a shared vocabulary; a dashboard does not by itself establish that the programme caused an outcome.

Example indicator sheet: “Unique adults completing the full training during the quarter.” Define what completion means, how repeat attendance is identified, how missing information is handled and which evidence supports the count. This is a design example, not a prescribed donor indicator.

Check whether the real bottleneck is collection, review or reporting

Trace one reporting cycle and record the time used for collection, corrections, approval, compilation and export. Count submissions received late, returned for correction or missing agreed evidence. Also record the time staff spend answering clarification requests after submission.

A well-controlled spreadsheet can remain adequate for a small programme with stable indicators and clear ownership. A new system becomes more compelling when re-entry, version conflicts, access control or recurring reconciliation cannot be managed reliably.

Illustrative business case: three staff each spend two days per month reconciling reports. That is six staff-days per month, or 72 per year if the pattern continues. Multiply by an appropriate internal day cost, then compare plausible savings with implementation, support and training costs. Not every day can be eliminated or turned into a cash saving.

Specify the controls that protect the numbers

• Collection: use required fields, valid ranges and clear definitions. Test offline capture where staff need it, including failed sync and conflict handling.
• Review: flag duplicates and missing evidence for a person to assess. Matching names alone can wrongly merge different people.
• Approval: distinguish pending and approved submissions. Preserve the original record and the reason for corrections.
• Reporting: record the reporting cutoff and dataset version. Totals should reconcile with the approved source records.
• Access: show managers and funders only the information their roles require. Prefer appropriately aggregated views for external reporting.

GPS and photos should serve a defined evidence need. Do not collect them simply because the technology allows it. Confirm the lawful basis, explain the purpose, minimise identifiable information and set retention and sharing controls. Use ODPC's principles and its relevant sector guidance; assess high-risk processing before rollout.

Compare configuration and custom development fairly

A configurable tool may support complex programmes; a custom build may still require substantial manual work. Ask both approaches to demonstrate the same real workflow rather than judging a sales presentation.

Your procurement brief should specify forms, roles, approvals, offline requirements, exports, migration, hosting, support, training and acceptance tests. Ask who owns the data, how it can be exported, what happens when the contract ends and how backups are restored. Include recurring licences and integration maintenance in the budget.

Request a written quote for the agreed scope. There is no defensible universal “NGO system cost” without those requirements, and a system's eligibility for programme funding depends on the funder's rules.

Pilot through a complete reporting cycle

Choose a representative site, including the connectivity and staffing conditions you need to handle. Run the pilot long enough to cover collection, review, approval and a real reporting deadline. Agree in advance who resolves discrepancies between old and new totals.

Track completeness of required fields, on-time submissions, correction rate, time from submission to approval and compilation hours. State the denominator and cutoff for each measure. For example, on-time submission rate is reports received by the deadline divided by reports due.

Include a sample evidence check: can a reviewer trace a reported total to its approved records and definitions? Decide rollout criteria before the pilot, and train both field staff and reviewers.

Our position: trustworthy reporting is a chain of definitions, controls and ownership. Software is useful when it strengthens that chain. Zero Impulse can help map your reporting workflow and digital requirements. Bring one indicator and one reporting cycle to begin the conversation.