Skip to content

A practical buying guide

NGO programme records, approvals and donor reporting

How can a programme manager connect field records to a useful donor report?

Waypoint brings projects, donor funding, purchase requests, staff activity, beneficiary records and documents into an organisation workspace. Define a project and reporting period, review the source records and prepare a filtered donor report while keeping recorded activity, commitments and verified financial evidence distinct.

Buying guide updated · VCMP product team, StartMadeSimple Ltd

A practical example

A fictional programme manager needs a quarterly update for one donor. The project has recorded funding in two currencies, a purchase request awaiting review and several support visits to the same beneficiary. The report must show the intended period without turning repeated visits into a count of unique people or treating a request as a completed payment.

What matters most in this setup

  • Define the project, donor and reporting dates before reviewing totals.
  • Keep approval state and source evidence visible to the reviewer.
  • Share only the beneficiary information appropriate for the report's audience.

A useful demonstration, step by step

  1. Choose a synthetic project, its targets and the reporting period. Agree which activities, support records and funding entries the donor update should include, together with the meaning of each indicator.
  2. Add a sample funding record and purchase request, then review the decision queue with the responsible role. Follow a request through the demonstrated states and retain the distinction between a commitment, a receipt and bank-verified expenditure.
  3. Review staff or beneficiary CSV input using a small sample. Match columns, inspect errors and duplicates and confirm the intended records. A Kobo CSV export can be imported; it is not a live connection to Kobo.
  4. Prepare a supported field form online, save a fictional report without connectivity and inspect delivery after reconnecting. Compare the received record with the local draft before treating it as available for the manager's report.
  5. Filter the donor report by donor, project and dates. Review the CSV or print-to-PDF output, keep currencies separate and check whether recorded support includes repeat visits before describing the result.
  6. Ask the intended reviewer to identify one underlying record from the summary and one exception needing follow-up. For a regional pilot, check the working language and numeric formats with the actual team and agree the export and support arrangements.

Check before you commit

  • Definitions of activity, support and unique beneficiaries
  • Reporting period and project filters
  • Recorded funding versus verified expenditure
  • Purchase approval and receipt ownership
  • CSV import review and record access
  • Offline draft delivery confirmation
  • Appropriate information in shared reports

Programme totals describe records entered by the team and may include repeated support. They do not independently establish impact, unique people reached or bank-verified expenditure. The public demo uses synthetic records and simulated delivery; agree the operational pilot, data access and reporting scope before rollout.

Buyer questions, answered

Find a question (14)

Do programme support totals count unique beneficiaries?

Not necessarily. Repeated support visits can contribute more than once to the recorded total. Define the measure before using it in a donor update, and compare the summary with underlying records. Distinguish people, visits, completed activities and outcomes instead of assigning all of them the same label.

Link to this answer

Is a recorded purchase request proof that funds were spent?

A request, an approved commitment, a receipt and verified payment are separate evidence. Review the state and available source documents before describing a value as expenditure. Waypoint donor reports describe recorded funding and commitments; they do not independently reconcile the organisation's bank account.

Link to this answer

Does importing a Kobo CSV create an ongoing integration?

No. The reviewed CSV import maps an exported file into supported staff or beneficiary records. Check the selected columns, errors, duplicate results and role access before saving. Later changes in the source do not automatically establish a corresponding change in Waypoint; plan a separate update procedure if needed.

Link to this answer

How can a donor report protect beneficiary context?

Agree the intended audience and fields before exporting. Review whether names, contact details or sensitive notes are necessary for the reporting purpose, and use suitable summaries where they are not. Have an authorised reviewer inspect the actual output rather than assuming that a useful internal view is appropriate for external sharing.

Link to this answer

How should a programme team define a donor-reporting period?

Agree the project, donor, start date and end date before collecting totals. Check that the underlying records belong to that reporting window.

Link to this answer

What is the difference between recorded donor funding and bank-verified money?

A funding entry describes what the team recorded. Reconcile it with the appropriate financial evidence before describing the amount as received or spent.

Link to this answer

How should a purchase request awaiting approval appear in a programme review?

Keep its review state visible and distinguish the request from an approved commitment or completed payment. Ask the intended reviewer to trace the supporting record.

Link to this answer

How can we avoid counting repeated support as new beneficiaries?

Define the beneficiary identifier and reporting indicator first. Review repeat visits separately from unique people before preparing the donor summary.

Link to this answer

What should a Kobo-to-Waypoint import trial actually prove?

Use a small Kobo CSV export, map the columns and inspect errors and duplicates. This demonstrates a reviewed file transfer, not a live Kobo integration.

Link to this answer

How should field teams verify an offline programme report arrived?

Compare the reconnected submission with the saved draft and check the receiving workspace. A local draft alone does not establish delivery to the manager.

Link to this answer

What information should be removed from a donor-facing beneficiary export?

Agree the audience and reporting purpose, then include only the fields the donor needs. Review a sample export before sharing operational personal details.

Link to this answer

How should a donor report handle funding in two currencies?

Keep the recorded amounts grouped by currency. If conversion is required, document the agreed rate, source and date rather than silently combining totals.

Link to this answer

What should a programme manager inspect behind a headline activity total?

Open a representative underlying record and check its project, date and meaning. Investigate missing approvals or repeated support before interpreting the total as impact.

Link to this answer

How should an NGO accept a programme-reporting pilot?

Have the intended reviewer reproduce a filtered report, trace one source record and explain one exception. Confirm access, delivery and reporting scope before wider rollout.

Link to this answer

Continue your evaluation

Relevant products and official sources

VCMP Waypoint

Waypoint brings NGO projects, donor funding, purchase approvals, people, beneficiaries, documents and fleet planning together with sourced country intelligence and voluntary field-team check-ins.

Explore VCMP Waypoint
NGO Programme & Donor Reporting Software | Waypoint